Repository navigation
relays: restore stitcher-moq WebSocket coverage - #60
Conversation
(Written by GPT-6)
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe relay key list now includes Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
Stitcher now serves TLS on TCP 443, resolving the deployment issue that removed its WebSocket column in moq-dev/smoke#53. Add
stitcher-moqback toWEBSOCKET_KEYSand update the README. The existing relay CI job now also testswss://34-72-6-160.sslip.io:443/moq-test.Validation:
/healthreturned HTTP 200 over HTTP/2 with certificate verification enabled.nix develop --command just checkpassed.just relays --only stitcher-moq --required stitcher-moq --publishers rust,js-web --subscribers rust,js-web,js-bun --timeout 30passed using the latest aptmoq0.14.7 and npm latest clients: Rust over WebSocket and QUIC, plus all six WebTransport pairs (8/8 cells, 3/3 endpoints).(Written by GPT-6)