From 1b1b55feccf59a23eaef4d4636b7551be25e3910 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 18 Nov 2026 12:05:03 -0800 Subject: [PATCH 1/2] chore(quest): claim quest/m0/backport-relay-high-key.md Quest-Claim: f2f9b41c31104b4d From d5e10c8ffc0a76375b0213a060dc4c389d598f38 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Wed, 18 Nov 2026 12:27:18 -0800 Subject: [PATCH 2/2] chore(quest): finish the far-ahead group key backport The fix lands on release in #9109. Co-Authored-By: Claude Opus 5.5 --- quest/m0/backport-relay-high-key.md | 29 ----------------------------- 1 file changed, 29 deletions(-) delete mode 100644 quest/m0/backport-relay-high-key.md diff --git a/quest/m0/backport-relay-high-key.md b/quest/m0/backport-relay-high-key.md deleted file mode 100644 index 49f77abe62..0000000000 --- a/quest/m0/backport-relay-high-key.md +++ /dev/null @@ -1,29 +0,0 @@ -# [M] Backport the far-ahead group key fix to release - -## Goal - -A relay on `release` holds no arrival entries for groups it no longer caches, -and a reader's wake no longer walks groups below its floor, so one publisher -that jumps to a far-ahead group key and keeps publishing below it cannot grow -a relay's memory or burn its shared runtime's CPU. Ships in a `moq-net` patch -in the next release. - -## Plan - -Decided 2026-11-17 (maintainer, [moq-dev/moq#9010](https://github.com/moq-dev/moq/pull/9010#issuecomment-6959731587)): ✅ -backport the track fix to `release` as a separate PR after it lands on -`main`, per RELEASE.md (rejected: shipping it only with the cut). - -Port the track half of the fix from -[moq-dev/moq#9044](https://github.com/moq-dev/moq/pull/9044) in -`rs/moq-net/src/model/track.rs`: arrival entries carry their own position, so -dead ones are compacted from anywhere once they outnumber the cached groups, -and the arrival walk moves a reader's cursor past leading entries it is never -handed (dead, or below its floor). `release` still indexes the queue by an -`offset`, so this is a hand port, not a cherry-pick. Reproduce first with the -PR's `a_far_ahead_key_pins_nothing_behind_it` test; if `release` cannot hit it, -delete this quest and say why in the PR. - -The front's track-info cleanup stays on `main`: it is not part of the decision. - -Public API: none. Wire: none.