Repository navigation
quest: import #8571, #8577, and #8559 - #8582
Merged
Merged
Conversation
Plans PipeWire DMA-BUF capture without the chunk-size bound (m1 XS), measured group order for buffered exports (m1 S), QUIC recovery after an outage (m3 M), restores per-stream deadlines (m4 L), and a moq-transport range FETCH over known holes (m4 M), narrowing the IETF scope freeze. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kixelated
marked this pull request as ready for review
November 12, 2026 19:07
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 26 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: the full diff of this quest-only import. All linked quest documents resolve.
quest/m1/pipewire-dmabuf-chunk.md: plans removing the chunk-size bound for DMA-BUF capture.quest/m1/export-order.md: plans measuring Ascending against Descending for moq-mux exports.quest/m3/quic-path-return.md: plans faster resumption and an RTT outlier guard after an outage.quest/m4/ietf-range-fetch.md: plans multi-group FETCH over known holes, and the notes narrowing the IETF freeze inietf-scopeandsubscribe-ranges.quest/m4/quic-deadline.md: restores the pruned deadline quest with a consumer.
claude-sonnet-5-5 | 𝕏
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Quest-only.
/quest-importof the four open issues without thequestlabel, interviewed with the maintainer on 2026-11-12.quest/m1/pipewire-dmabuf-chunk.md[XS]: Hyprland's portal writes a placeholder DMA-BUF chunk size, anddma_buf_chunk_containsdrops every frame. The fd's allocation size becomes the only bound, and the tests build on PipeWire 1.0.x headers.quest/m1/export-order.md[S]: measure Ascending against Descending for moq-mux exports on the outage and a sustained deficit, then ship the order that loses less video;quest/m3/quic-path-return.md[M]: after an outage, moq-quic sends again within an RTT and keeps a sample spanning the outage out of smoothed RTT;quest/m4/quic-deadline.md[L], restored from the m5 quest that moq-dev/moq#8423 pruned, now with a consumer.quest/m4/ietf-range-fetch.md[M]: a Rust moq-transport publisher answers a multi-group FETCH when every group is cached or proven never produced (Prior Group ID Gap in,0x8Cout), and refuses otherwise. Recorded as a narrowing of the IETF scope freeze inquest/m2/ietf-scope/README.mdandquest/m2/subscribe-ranges/README.md.--mux-rate 0.Decisions
dma_buf_maxsize_containspatch as written; the same fix in m3).quic-deadline: MPEG-TS trunks under a stated delay #8559, export order: ✅ measure both orders, then pick, in m1 S (rejected: Ascending for every moq-mux export; Ascending only forts/flvunder--delay; changing moq-net's default). The maintainer's points are recorded in the Plan: descending prioritizes recovery for adaptive bitrate players and keeps an aggregated upstream from starving a short budget, and the right order may depend on the maximum latency.quic-deadline: MPEG-TS trunks under a stated delay #8559, QUIC: ✅ the recovery quest in m3, plus quic-deadline restored in m4 (rejected: recovery only; nothing on QUIC until the order fix is measured). quic-careful-resume stays deleted.Choices I made without asking (the structure, per the skill): the order quest requires Finalize moq-lite-07, because lite-06 serves an ascending request newest-first, and it takes Buffered playback subscribes in ascending order's rule (buffered means ascending) as its starting hypothesis. #8559 closes with the m3 recovery quest, the last of its quests to land. The order quest records earliest-deadline-first relay scheduling as raised but not planned.
Impact
None (quests only). The planned quests report no public API or wire change. The range FETCH quest uses only draft-defined markers.
Validation
quest checkpasses (503 documents). I verified each issue's claims against the code before the interview: file and line anchors, the PRs behind them, and the current refusal and default-order paths. No behavior to exercise.Follow-ups
All five kept (maintainer, 2026-11-12, in the merge pick).
Models
Size: M
Implementer: Claude Code, claude-opus-5-5, unknown effort
🤖 Generated with Claude Code
(Written by Opus 5.5)
Review
Rewritten by
quest reviewafter each round.Head: 69cf858
Base: origin/main at 7e68d17
Reviewer: Codex, gpt-6.1-sol, high effort
Session:
01a1d126-d7d1-7b33-bb21-de94a5648f28, round 1Score: 10/10,
The scoped diff changes only quest plans, preserves the recorded decisions, and introduces no actionable defects or runtime regressions.Findings: none