Repository navigation
refactor: remove targeted clippy exceptions #11524
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -35,11 +35,10 @@ pub fn kill_all() { | |
| CmdLineRunner::kill_all(); | ||
| } | ||
|
|
||
| /// Terminate only after command scopes and their destructors have unwound. | ||
| #[allow(clippy::disallowed_methods)] | ||
| pub fn terminate(code: i32) -> ! { | ||
| /// Convert a requested process status after command scopes have unwound. | ||
| pub fn status(code: i32) -> std::process::ExitCode { | ||
| debug!("exiting with code: {code}"); | ||
| std::process::exit(code) | ||
| std::process::ExitCode::from(code as u8) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When a Windows child returns a status outside Knowledge Base Used: CLI Dispatch Flow There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Windows child exit codes truncatedMedium Severity Replacing Additional Locations (1)Reviewed by Cursor Bugbot for commit 479c2ea. Configure here. |
||
| } | ||
|
|
||
| #[cfg(test)] | ||
|
|
||


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 a Windows tool launched through an executable mise shim returns a status outside
0..=255, casting the status tou8changes it before forwarding it. A status of 256 therefore becomes 0, causing the failed shimmed command to be reported as successful.Knowledge Base Used: Shims