Unsigned integer underflow in max_batch_size #2352
Closed
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.
Passing
--max-batch-size
to the launcher actually had no effect because after a few requests the max_size passed to State::next_batch would underflow becoming a large positive number.In the scheduler, as soon as the cached batch size reached the
max_batch_size
themax_size
passed to next_batch becomes 0. Since the only check in that funcion isand it's called after the
batch_requests.len()
has become 1, it doesn't do anything to prevent more than 0 requests from being batched.Now we have cached batch in the server that is larger than
max_batch_size
andmax_size - batch_size as usize
underflows.