Fix watermark regression and request count inconsistency in style batching
- Use max() when updating the watermark so it only ever moves forward,
preserving the invariant "furthest extent of the batch in this route."
- Always decrement chunk_group_requests when absorbing a candidate,
not only when the chunk group was already tracked by the batch.
- Add two unit tests for the newly-introduced-route scenario where a
candidate brings a new chunk group into the batch scope.
Co-Authored-By:
Claude <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment