-
Notifications
You must be signed in to change notification settings - Fork 224
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
Regression: heroku run -x no longer returns correct exit code #2466
Comments
Thank you for all of the details on this, we are looking into it. In the meantime, for you or anyone else who runs into this issue, the workaround for now is to downgrade to version 8.1.9 using |
So, just an explanation of how this even works internally... when cli/packages/run-v5/lib/dyno.js Line 54 in b451c6b
This cli/packages/run-v5/lib/dyno.js Lines 315 to 328 in b451c6b
|
Related: #2468 |
Confirmed fixed by #2467. |
Fix has landed :) This reverts commit 86df1f8.
Fix has landed :) This reverts commit 86df1f8.
Fix has landed :) This reverts commit 86df1f8.
Fix has landed :) This reverts commit 86df1f8.
Fix has landed :) This reverts commit 86df1f8.
Since 8.2.0:
Note: you have to use
bash -c "exit 2"
as the command; simply usingexit 2
will terminate the shell and then the internalecho
of the status code for later reading will not execute:cli/packages/run-v5/lib/dyno.js
Line 54 in b451c6b
exit 2; echo "\uFFFF heroku-command-exit-status: $?
vsbash -c "exit 2"; echo "\uFFFF heroku-command-exit-status: $?
).The text was updated successfully, but these errors were encountered: