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.
feat : add consistent exit codes #3130
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
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat : add consistent exit codes #3130
Changes from all commits
c765ac38217c17d9a6d8b034007fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
In Bash, exit code 2 conventionally means "incorrect usage / invalid arguments." This PR uses 2 for "not found" instead. This isn't necessarily wrong (kubectl doesn't differentiate at all, and many CLIs define their own schemes), but it's worth documenting this divergence explicitly in
docs/exit-codes.mdso users don't confuse it with the shell convention.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.
Changing the "no conditions yet" exit code from
2to1is semantically correct under the new scheme, but it's a breaking change for scripts relying on the previous behavior. The release note should explicitly mention this: "The exit code for PipelineRuns with no conditions has changed from 2 to 1."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.
PrintErrorcallscmd.Flags().GetString("output")wherecmdis the roottkncommand (passed fromcmd/tkn/main.go). However, the--outputflag is defined on individual subcommands, not on the root.GetString("output")on the root will return""(and a non-nil error which is silently discarded), so the JSON error path will never trigger.Consider resolving the executed subcommand's flags instead, or propagating the output format via a persistent pre-run hook that stores it somewhere accessible at error-handling time.
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.
FromAPIErrorcreates a new*exitcode.Errorwith only the string message, discarding the original Kubernetes*StatusError. Any downstream code that callsk8serrors.IsNotFound(err)orerrors.As(err, &statusErr)after apkg/actionscall will now getfalsebecause the original error is no longer in the chain.Can we store the original and implement
Unwrap():And update
FromAPIErrorto preserve the original:This preserves both the exit code semantics and the original error chain
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.
The
InvalidInputconstant is declared but nothing in this PR ever emits exit code 3.FromAPIErrordoesn't mapk8serrors.IsInvalid()ork8serrors.IsBadRequest()to it, and Cobra flag-parsing errors also bypass this classification entirely.We can probably do
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.
k8serrors.IsTimeout()only matches HTTP 504 from the API server. Context deadline exceeded errors (context.DeadlineExceeded) and client-side request timeouts won't produce exit code 4.Can we add this before the
defaultcaseUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.