We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ribosome.js uses exec to run the rna file, and patches stdout and stderr in the callback, hence preventing "live" update of stdout and stderr.
exec
stdout
stderr
The fix is to use spawn instead of exec: https://stackoverflow.com/questions/10232192/exec-display-stdout-live
spawn
A simple workaround is to first generate the rna file, then run that. Still, having the same semantics for both methods would be preferable.
I'll gladly provide a patch for the JS version, but I won't bother with the others (if they do suffer from the same issue, which is not sure).
The text was updated successfully, but these errors were encountered:
Sure. Do send a JS patch. Thanks!
Sorry, something went wrong.
ribosome.js: pipe the stdout/stderr of the spawned process to that of…
4cdb14c
… the ribosome process adresses sustrik#59
8215a86
Successfully merging a pull request may close this issue.
ribosome.js uses
exec
to run the rna file, and patchesstdout
andstderr
in the callback, hence preventing "live" update of stdout and stderr.The fix is to use
spawn
instead ofexec
: https://stackoverflow.com/questions/10232192/exec-display-stdout-liveA simple workaround is to first generate the rna file, then run that. Still, having the same semantics for both methods would be preferable.
I'll gladly provide a patch for the JS version, but I won't bother with the others (if they do suffer from the same issue, which is not sure).
The text was updated successfully, but these errors were encountered: