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
Ideally we'd send logs and IO stream side effects over the RemoteREPL channel as they happen rather than buffering them in the server until the command is done executing. This would be especially helpful for long-running commands.
As part of this, it would be helpful if @remote(stdout) would forward a more faithful stdout-like object to the server so that redirect_stdout would work, making it easier to get the desired client-centric behavior mentioned in #29:
redirect_stdout(@remote(stdout)) doprintln("hi")
end
Completely stateful redirection such as
redirect_stdout(@remote(stdout))
would also be helpful as it should solve part of #15
The text was updated successfully, but these errors were encountered:
Ideally we'd send logs and IO stream side effects over the RemoteREPL channel as they happen rather than buffering them in the server until the command is done executing. This would be especially helpful for long-running commands.
As part of this, it would be helpful if
@remote(stdout)
would forward a more faithful stdout-like object to the server so thatredirect_stdout
would work, making it easier to get the desired client-centric behavior mentioned in #29:Completely stateful redirection such as
would also be helpful as it should solve part of #15
The text was updated successfully, but these errors were encountered: