Skip to content

Validate max-parallel and cap it at the number of runs - #19

Merged
danielmarbach merged 1 commit into
mainfrom
validate-max-parallel
Oct 13, 2026
Merged

danielmarbach merged 1 commit into
mainfrom
validate-max-parallel

Conversation

@danielmarbach

Copy link
Copy Markdown
Contributor

max-parallel was only parsed: abc failed with a raw cast error, 0 and negative values silently ran sequentially, and 2.5 became 2. Anything other than a positive integer now fails with max-parallel must be a positive integer, but was '<value>'. An empty value is still treated as 1.

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: auto and timing-based ordering and is not being pursued.

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.
@danielmarbach
danielmarbach merged commit 3f38742 into main Oct 13, 2026
1 check passed
@danielmarbach
danielmarbach deleted the validate-max-parallel branch October 13, 2026 07:00
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.

2 participants