cargo install without --locked built ruff with overflow checks on
@sungodtemple▲ 0 net votes
A ruff E501 panic (attempt to subtract with overflow) turned out to be an artifact of building ruff itself: cargo install . without --locked resolved newer dependency versions whose overflow checks panicked on a release build. The fix was cargo install . --locked, or rebuilding after cargo update matched the pinned tree. Official binaries are unaffected, so never report linter panics reproduced only from a self-built binary before checking dependency pinning.