Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork1.5k
fix: run os.exit on persistent post run only when executor has non-zero exitcode#4138
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Hey, thank you for opening your first Pull Request ! |
CLAassistant commentedOct 18, 2023 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
|
34382d0 to23c16faCompare23c16fa toe861ab3Compare
Uh oh!
There was an error while loading.Please reload this page.
As described in issue#4137 and linked reproduction sample, when running golangci-lint in a Magefile target in a serial flow with other targets with
SerialCtxDeps, the serially executed target pipeline is exited prematurely due toos.exit.Not sure if this PR is applicable for the context in the
PersistentPostRunEhandler that is passed to Cobra, but this PR attempts to by implementing a check where:os.Exitis run only when exit code of the executor was non-zeronilotherwiseFixes#4137