From 20b877833e3127fd7cebd8dd5e1353ded4460b0d Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Fri, 13 Nov 2026 10:52:59 -0800 Subject: [PATCH] quest: plan the uring error and live-history demand follow-ups Co-Authored-By: Claude Opus 5.5 --- quest/m1/live-history-demand.md | 26 ++++++++++++++++++++++++++ quest/m1/uring-io-error.md | 18 ++++++++++++++++++ 2 files changed, 44 insertions(+) create mode 100644 quest/m1/live-history-demand.md create mode 100644 quest/m1/uring-io-error.md diff --git a/quest/m1/live-history-demand.md b/quest/m1/live-history-demand.md new file mode 100644 index 00000000000..af4b64cf749 --- /dev/null +++ b/quest/m1/live-history-demand.md @@ -0,0 +1,26 @@ +# [S] A JS live reader keeps a history reader's floor + +## Goal + +When a JS track has a live reader with no `ranges` and a history reader at the +same time, the subscription's demand still reaches back to the history +reader's floor. Settle with a test whether it does. Fix it if it doesn't, or +delete this quest if the test shows it already does. + +## Plan + +Decided 2026-11-13 (maintainer, /quest-run follow-up from +[moq-dev/moq#8643](https://github.com/moq-dev/moq/pull/8643)): ✅ m1 (rejected: m0, m2). + +Unverified. A scratch test during #8643 gave a demand of `[{}]` for that pair, +which looks like an open live range with no floor. Start from a test that +pins the demand the pair should produce, and compare with Rust's equivalent. +[Lite-07 FETCH is single-group only](/quest/m2/subscribe-ranges/lite07-fetch.md) +rewrites how JS keeps fill and demand ranges apart (`LiveRanges.edit`), so +this starts after it lands. + +Public API: none expected. Wire: none. + +## Required + +- [Lite-07 FETCH is single-group only](/quest/m2/subscribe-ranges/lite07-fetch.md) - rewrites the JS fill and demand ranges this checks diff --git a/quest/m1/uring-io-error.md b/quest/m1/uring-io-error.md new file mode 100644 index 00000000000..62be162be0b --- /dev/null +++ b/quest/m1/uring-io-error.md @@ -0,0 +1,18 @@ +# [XS] An io_uring I/O error names its cause once + +## Goal + +`moq_uring::Error::Io` shows its `std::io::Error` once when printed with +anyhow's `{:#}` or walked as a source chain. Today it displays +`"io error: {0}"` and also makes that error its `#[from]` source, so the +relay's startup failure prints the cause twice. + +## Plan + +Decided 2026-11-13 (maintainer, /quest-run follow-up from +[moq-dev/moq#8642](https://github.com/moq-dev/moq/pull/8642)): ✅ m1 (rejected: m0). + +Recommended: keep the variant and `#[from]`, and drop `{0}` from its message. +Check the callers that print a `moq_uring::Error` with plain `{}`, since they +would then lose the cause; switch them to `{:#}` or a chain where they do. +Only the Display text changes, so no API breaks.