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
I would expect us to do something with execErr here unless it can truly be ignored, but its not clear if it can be.
execErr
execErr is dropped on the floor if its not an exit error.
Return it if ctx.Err() is nil?
ctx.Err()
N/A
Just curious as to whether ignoring it is the correct thing to do.
go version : go version go1.21.3 darwin/arm64
go version
Operating System and version (e.g. Linux, Windows, MacOS): MacOS Ventura 13.6
Link to your project or a code example to reproduce issue: N/A
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Expected Behaviour
I would expect us to do something with
execErr
here unless it can truly be ignored, but its not clear if it can be.Current Behaviour
execErr
is dropped on the floor if its not an exit error.Possible Solution
Return it if
ctx.Err()
is nil?Steps to Reproduce (for bugs)
N/A
Context
Just curious as to whether ignoring it is the correct thing to do.
Your Environment
go version
: go version go1.21.3 darwin/arm64Operating System and version (e.g. Linux, Windows, MacOS): MacOS Ventura 13.6
Link to your project or a code example to reproduce issue: N/A
The text was updated successfully, but these errors were encountered: