Repository navigation
Validate max-parallel and cap it at the number of runs - #19
Merged
Merged
Conversation
A non-numeric value failed with a raw cast error, and 0, negative or fractional values silently became sequential or were truncated. Anything but a positive integer now fails with a message naming the input.
rbev
approved these changes
Oct 13, 2026
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.
max-parallelwas only parsed:abcfailed with a raw cast error,0and negative values silently ran sequentially, and2.5became2. Anything other than a positive integer now fails withmax-parallel must be a positive integer, but was '<value>'. An empty value is still treated as1.The value is also capped at the number of runs, so the logged value reflects what actually runs.
Split out of #18, which explored
max-parallel: autoand timing-based ordering and is not being pursued.