-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
interp: different behavior of pipefail
for multiline scripts
#870
Comments
mvdan
changed the title
Different behavior of
interp: different behavior of Apr 16, 2023
pipefail
for multiline scriptspipefail
for multiline scripts
mvdan
added a commit
that referenced
this issue
Apr 16, 2023
We supported both options separately, but when used together, a command like false | true would fail to exit the shell properly. Add tests and fix the bug. Fixes #870.
mvdan
added a commit
that referenced
this issue
Apr 17, 2023
We supported both options separately, but when used together, a command like false | true would fail to exit the shell properly. Add tests and fix the bug. Fixes #870.
diamondburned
pushed a commit
to diamondburned/mvdan-sh
that referenced
this issue
May 9, 2023
We supported both options separately, but when used together, a command like false | true would fail to exit the shell properly. Add tests and fix the bug. Fixes mvdan#870.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using Task and hit this issue and was directed here: go-task/task#392 (comment)
I want my script to fail on pipe errors.
cmd1
works/fails as expected, butcmd2
never fails:Why does
pipefail
not work in the second case?The text was updated successfully, but these errors were encountered: