fix(system): validate launcher and timeit integer arguments - #601
Merged
singaraiona merged 1 commit intoSep 20, 2026
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes for users
Malformed numeric startup arguments are rejected instead of being silently truncated or overflowing:
-c/--cores,-t/--timeit, and-Q/--querylognow require complete, range-checked integer values. Invalid values fail startup with a non-zero status before the runtime starts.The same strict parsing is used by
.sys.args,.sys.timeit, and.sys.cmd "timeit ...", so values such as2abc, overflowing core counts, and1.5now return an error instead of changing runtime state unexpectedly.Validation
3924/3924core tests passed-WerrorAll checks pass.