Skip to content

Generally reject exit codes other than 0 and 1 - #163

Open
sharkdp wants to merge 1 commit into
lolpack:mainfrom
sharkdp:codex/checker-exit-codes
Open

sharkdp wants to merge 1 commit into
lolpack:mainfrom
sharkdp:codex/checker-exit-codes

Conversation

@sharkdp

@sharkdp sharkdp commented Nov 3, 2026 •

Copy link
Copy Markdown

Reject exit codes other than 0 (success) and 1 (diagnostics) for every type checker.

I checked the upstream exit-code implementations for Zuban, Pyright, Pyrefly, ty, and mypy. All of them use 0 for "no diagnostics", 1 for "diagnostics", and other exit codes for unrelated problems.

This is related to the discussion in #160 and addresses the zuban / SQLAlchemy problem. When merged in isolation, this PR will also affect the zuban run on Salt, since zuban currently exits with exit code 2 on that project (No Python files found to check). This seems like a good thing. Once we ignore the mypy configuration for zuban, the Salt project should be included again.

@sharkdp sharkdp changed the title Reject fatal exit codes from all benchmarked type checkers Generally reject exit codes other than 0 and 1 Nov 3, 2026
@sharkdp
sharkdp marked this pull request as ready for review November 3, 2026 10:06

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant