chore: support specific query number #23
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
comphead
changed the title
andygrove
approved these changes
Sep 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added
--querycommand line argument: A new optional parameter that accepts an integer representing the specific query number to run (1-based indexing).Modified the main function signature: Added
query_num: int = Noneparameter to handle the specific query selection.Implemented query selection logic:
If
--queryis specified, only that specific query will be runIf
--queryis not specified, all queries will be run (preserving original behavior)Added validation to ensure the query number is within the valid range for the benchmark
Updated argument parsing: Added the new
--queryargument with proper help text and type validation.