You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to have RTalk.request(...) throw an exception instead of printing a stack trace when an exception occurs?
I have the following use case: Due to potentially long execution times of R expressions, I would like to be able to terminate their execution. I am currently doing this by closing the RConnection and then terminating the Rserve process (which only runs locally). This causes the socket input stream to throw SocketException: Socket closed while blocking on is.read(), which results in the stack trace.
Thank you in advance!
Greetings,
Jonathan
The text was updated successfully, but these errors were encountered:
Hi @s-u !
Would it be possible to have RTalk.request(...) throw an exception instead of printing a stack trace when an exception occurs?
I have the following use case: Due to potentially long execution times of R expressions, I would like to be able to terminate their execution. I am currently doing this by closing the
RConnection
and then terminating the Rserve process (which only runs locally). This causes the socket input stream to throwSocketException: Socket closed
while blocking onis.read()
, which results in the stack trace.Thank you in advance!
Greetings,
Jonathan
The text was updated successfully, but these errors were encountered: