Joseph Doherty 51ebded300 fix: correct MaxBytes enforcement and consumer start sequence after purge ...

StreamManager.Capture now accounts for full message size (subject +
payload + 16-byte overhead) when checking MaxBytes, matching Go's
memStoreMsgSize. PullConsumerEngine uses stream FirstSeq instead of
hardcoded 1 for DeliverAll after purge. Fix 6 tests with Go parity
assertions and updated MaxBytes values.

2026-02-24 23:59:37 -05:00

26 KiB

Raw Blame History

View Raw