fix: correct MaxBytes enforcement and consumer start sequence after purge

Browse Source

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.

...

This commit is contained in:

Joseph Doherty

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

parent 1f83df12e4

commit 51ebded300

8 changed files with 6404 additions and 24 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

6359

.slopwatch/baseline.json

File diff suppressed because it is too large Load Diff