-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
Add an option for AttachMe to be quiet on stdout/stderr #8
Comments
@smola I think attachme agent should be writing only to stderr. Is it still an issue for you? Let me know in case stdout gets polluted with attachme messages as well. |
Unfortunately, stderr pollution is also a problem in my use case, since the caller is a 3rd party which captures both stdout and stderr. |
@big-andy-coates Yes, that was the problem. I was using this in a subprocess, and the parent process did not expect the child to have any extra output. |
Great. Maybe close this issue as a duplicate then? |
I'm debugging JVM processes that get called by other programs and whose stdout/stderr get examined. AttachMe messages to stdout/stderr break the calling process by introducing unexpected output.
It would be nice to add an additional agent option (maybe
quiet=[y/n]
) to avoid printing anything, at least for anything that is not a fatal error. That would make it possible to debug JVM cli apps that get called from scripts, etc.The text was updated successfully, but these errors were encountered: