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
Separating this from #6291 as its a different beast and different design, and at the moment not an issue hit by users
The text was updated successfully, but these errors were encountered:
note some conversation from #6281 and the overflow output callback in remote_output_buffered()
remote_output_buffered()
Sorry, something went wrong.
See flux-framework/rfc#427 for a proposed protocol.
Was pondering this and the need.
with the unbuf support, it isn't needed for a large number of use cases now (but would be needed for flux-exec which doesn't use unbuf)
flux-exec
without this support, we probably gotta keep the buffer sizes large at 4 meg libsubprocess: decrease default buffer size #6385
I think we care about #6385 a lot b/c 4 megs is a good chunk of memory or people are launching alot of processes
No branches or pull requests
Separating this from #6291 as its a different beast and different design, and at the moment not an issue hit by users
The text was updated successfully, but these errors were encountered: