51ebded300
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.
24 lines
787 B
C#
24 lines
787 B
C#
using NATS.Server.JetStream.Models;
|
|
|
|
namespace NATS.Server.Tests;
|
|
|
|
public class JetStreamStreamPolicyRuntimeTests
|
|
{
|
|
[Fact]
|
|
public async Task Discard_new_rejects_publish_when_max_bytes_exceeded()
|
|
{
|
|
// Each message = subject("s.a"=3) + payload(2) + overhead(16) = 21 bytes.
|
|
// MaxBytes=25 holds exactly one message; second publish is rejected.
|
|
await using var fx = await JetStreamApiFixture.StartWithStreamConfigAsync(new StreamConfig
|
|
{
|
|
Name = "S",
|
|
Subjects = ["s.*"],
|
|
MaxBytes = 25,
|
|
Discard = DiscardPolicy.New,
|
|
});
|
|
|
|
(await fx.PublishAndGetAckAsync("s.a", "12")).ErrorCode.ShouldBeNull();
|
|
(await fx.PublishAndGetAckAsync("s.a", "34")).ErrorCode.ShouldNotBeNull();
|
|
}
|
|
}
|