Repository navigation
chore(rind): finish transport on rind - #7931
Conversation
Quest-Claim: 7a2f66ed9e56542b
Delete the transport quest, which #7873 implemented, and the links to it. Route moq-cli's startup CPU check through moq-tokio's shared `crypto::install_default`, dropping its direct rind-rustls dependency. Drop the removed-feature migration note from doc/lib and the moq-tokio README (MIGRATE.md carries it), and replace stale aws-lc rationale in moq-gst and the threat model. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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 13 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. |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Quest cleanup — deletes
quest/m1/rind/transport.mdand removes its entry from the epic README's Required list, pluscpu-error.md's Required entry and past-tense Plan rewrite, unblockingcpu-error.md. - moq-cli startup — routes the CPU check through
moq_tokio::crypto::install_default()?like moq-relay/moq-bench, dropping the directrind-rustlsdependency and the unreachable "already installed" error. - Docs — removes the removed-feature migration note from
doc/lib/rs/index.mdandrs/moq-tokio/README.md(MIGRATE.md carries it). - Stale aws-lc text —
moq-gststop docs/tests now give the still-valid reason,.oss-scanner/threat_model.mdsays rustls with rind, anddeny.toml's rsa note names rind.
Verified moq_tokio::crypto::install_default() is unconditional (so moq-cli's default-features = false build still has it), returns a thiserror error that works with anyhow::?, and that no rind_rustls references or transport.md links remain. The remaining aws-lc mentions in .oss-scanner/Dockerfile and threat_model line 42 are still accurate while moq-cli/moq-rtc pull it via str0m/dimpl.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

Problem
moq-dev/moq#7873 implemented
quest/m1/rind/transport.mdbut rewrote the quest instead of deleting it, so it still blocksquest/m1/rind/cpu-error.mdand the MoQ on rind epic.Verification on main
Checked the Goal and the plan items #7873 dropped from the file (
git show 44a24b976 -- quest/m1/rind/transport.md):cargo tree --locked --target all -e normal,build -i {aws-lc-sys,ring}is empty for moq-quic, moq-uring, moq-rtmp, qmux, moq-relay, moq-ffi and moq-c with--all-features, and for moq-tokio with every feature exceptwebrtc. Every remaining aws-lc path (moq-tokiowebrtc, moq-cli's default build) runs through str0m/dimpl in moq-rtc and moq-ice, which moq-rtc on rind owns.aws-lc-rs/ringfeatures; their MIGRATE notes say to drop them. (moq-native's no-op features belong to its rename tombstone, which no build compiles as a dependency.)crypto::provider()?, so every binary built on it (moq-ffi throughClient::new, moq-c, moq-gst, moq-boy) fails setup withUnsupportedCpunaming the feature. moq-relay, moq-bench, and now moq-cli also check at the top ofmain.doc/bin/relay/index.md,doc/bin/cli.md, anddoc/lib/rs/index.md.Approach
moq_tokio::crypto::install_default()?like moq-relay and moq-bench, instead ofrind_rustls::default_provider()plus an unreachable "already installed" error. It drops its directrind-rustlsdependency.doc/lib/rs/index.mdand the moq-tokio README no longer name the removedaws-lc-rs/ringfeatures; that migration note lives in each crate's MIGRATE.md, anddoc/describes only what ships..oss-scanner/threat_model.mdsays rustls with rind, anddeny.toml's rsa note says production signing uses rind.Impact
unsupported CPU: rind requires ...through moq-tokio's typed error.Alternatives
release-c.yml/release-cpp.yml, since moq-c's and moq-ffi's graphs no longer hold aws-lc on any target. Left for the epic's final aws-lc removal: those workflows only run at release, so the change can't be exercised here, andrelease-binary.ymlstill needs NASM for moq-cli until rtc.md lands.Follow-ups
Validation
quest gate just check origin/mainon 5a3ac90 (d95e2bf only edits adeny.tomlcomment): every module passed (check/test rs with 11760 tests, js, gh, markdown, shell, quest, drill, and the rest) exceptcheck flake, which stops before running because this host has no/dev/kvmfor the NixOS VM tests. That precondition fails identically on any checkout; CI runs it on a KVM host.quest check: 588 documents ok.cargo treesweeps listed above.Review
quest review), gpt-6.1-sol, medium effort, round 1.(Written by Claude Opus 5.5)
🤖 Generated with Claude Code