From c9324254136d347c7f4d9565cf9fb5061133a957 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Thu, 12 Nov 2026 10:32:20 -0800 Subject: [PATCH] test(max-age): the JS subscriber expects lite-07 to carry the publisher's max age #8443 returned moq-lite-07-wip to max_age_relay_javascript, but the JS subscriber still asserted every track arrives without a max age, true only of moq-transport. Expect the published age on lite, as the Rust side does. Co-Authored-By: Claude Opus 5.5 --- test/max-age/client.ts | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/test/max-age/client.ts b/test/max-age/client.ts index 9c9a026f5dd..5bca4546dab 100644 --- a/test/max-age/client.ts +++ b/test/max-age/client.ts @@ -46,11 +46,12 @@ try { let broadcast = request.active.peek(); while (!broadcast) broadcast = await request.active.changed(); assert(broadcast); - for (const i of ages.keys()) { + for (const [i, age] of ages.entries()) { const track = broadcast.track(String(i)).subscribe(); // moq-transport never sends MAX_CACHE_DURATION (it would expire the newest group too), - // so every track arrives without a publisher limit. - assert.equal((await track.info()).maxAge?.asMillis(), undefined, `${protocol} track ${i}`); + // so only lite carries the publisher's limit. + const want = protocol.startsWith("moq-lite-") ? age?.asMillis() : undefined; + assert.equal((await track.info()).maxAge?.asMillis(), want, `${protocol} track ${i}`); track.close(); } request.close();