-
Notifications
You must be signed in to change notification settings - Fork 750
Pass -r to xargs so empty container lists don't log as failed #1909
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
Open
ya-luotao
wants to merge
1
commit into
basecamp:main
Choose a base branch
from
ya-luotao:xargs-no-run-if-empty
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the producer in these pipelines is
docker container ls,-rmakesxargsreturn success on empty stdin, and these commands are emitted as ordinary shell pipelines with nopipefailsetup in the repo. If the Docker query itself fails before printing IDs (for example, daemon unavailable or permission denied), commands such asremove_containerorapp stop --versionnow succeed as no-ops instead of surfacing the Docker error; GNUxargs --helpconfirms-rmeans it will not run the command when there are no arguments. Please preserve failures from the left-hand side while making truly empty container lists no-op.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point on the tradeoff, but I think the impact is narrower than it reads:
app.stop,status,container_health_log) already run withraise_on_non_zero_exit: falseor just capture output, so a failingdocker container lswas never surfaced through the exit code there — nothing is lost.remove_container/remove_containerspaths. There the pre--r"surfacing" was accidental: the daemon error came through as a confusingdocker rmusage error (exit 123) rather than as the real failure. The daemon error itself still lands in the log via stderr either way; only the exit code changes.pipefail(not portable acrossshimplementations) or wrapping every pipeline in ash -cemptiness guard — out of proportion for the "daemon dies between two docker commands" window, where the next docker command in the flow fails loudly anyway.Happy to scope
-rdown to just the best-effort stop pipelines if the maintainers prefer to keep the remove/status paths as they are.