-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Error on non-zero exit statuses for pipeline elements #13817
Copy link
Copy link
Closed
Labels
A:error-handlingHow errors in externals/nu code are caught or handled programmatically (see also unhelpful-error)How errors in externals/nu code are caught or handled programmatically (see also unhelpful-error)category:enhancementNew feature or requestNew feature or requeststatus:needs-designthis feature requires designthis feature requires design
Milestone
Description
Related problem
Since #13515 non-zero exit status of a command on a trailing pipeline position errors. The same isn't true for pipeline elements.
So a) will error, while b) will not.
Assuming that b) doesn't collect its input.
# a)
foo | may-fail
# b)
foo | may-fail | barDescribe the solution you'd like
According to @IanManske, changing that isn't possible with the current code structure
I still wanted to open an issue, since this might change at some point. If it does, I would appreciate it if nushell would error for both scenarios a) and b)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A:error-handlingHow errors in externals/nu code are caught or handled programmatically (see also unhelpful-error)How errors in externals/nu code are caught or handled programmatically (see also unhelpful-error)category:enhancementNew feature or requestNew feature or requeststatus:needs-designthis feature requires designthis feature requires design