fix: automatic batching can exceed max_bytes

[quettabit]

closes #107

[greptile-apps]

Greptile Summary

This PR prevents automatic batches from exceeding max_bytes by checking a record’s metered size before adding it.

• Flushes a producer’s pending batch before accepting a record that would exceed the configured byte limit.
• Carries an overflowing record into the next asynchronous batch rather than overfilling the current batch.
• Adds coverage for exact-limit and pre-overflow batching behavior.

Confidence Score: 5/5

The PR appears safe to merge, with no outstanding findings.

The byte-limit checks preserve oversized single-record behavior while preventing multi-record batches from exceeding max_bytes. The previous concurrency-ordering thread was resolved after quettabit clarified that concurrent submit() calls have no ordering guarantee.

Important Files Changed

Filename	Overview
src/s2_sdk/_batching.py	Adds pre-insertion byte-limit checks and carries overflowing records into the next generated batch.
src/s2_sdk/_producer.py	Flushes a non-empty accumulator before a submitted record would exceed the configured byte limit.
tests/test_batching.py	Verifies batching at the exact byte limit and flushing before an overflow.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Receive record] --> B{Accumulator empty?}
    B -->|Yes| D[Add record]
    B -->|No| C{Would exceed max_bytes?}
    C -->|Yes| E[Flush current batch]
    C -->|No| D
    E --> D
    D --> F{Batch full or next record would overflow?}
    F -->|Yes| G[Yield or submit batch]
    F -->|No| A

Loading

_{Reviews (2): Last reviewed commit: "initial commit" | Re-trigger Greptile}