fix(relay): match the uring driver's terminal error - #3860
Conversation
#3828 changed the worker driver to return `moq_net::Error` directly, but the io_uring accept path still pattern-matched a `Result`, so `just check` fails on Linux with the `io-uring` feature. Treat a clean close as silent and log any other terminal error, matching the WebSocket path. Closes #3848 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
MERGE Positive improvement: yes. Worth the complexity: yes — three lines, no API or wire change, no new abstraction. Different approach: the WebSocket path uses an This is an automated review, not the maintainer's decision |
|
No issues found. |
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review. Walkthrough
Priority: ⬆️ High Severity of issue fixed: High 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches✨ Simplify code
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. Comment |

Problem
Checkis red on main:rs/moq-relay/src/uring.rs:771still doesif let Err(err) = driver_handle.run(driver).await, but #3828 changed the worker driver to returnmoq_net::Errordirectly. The io_uring path is Linux-only, so macOSjust checknever caught it. Every open PR inherits the failure.Approach
Match the terminal error the way
websocket.rsdoes: a cleanClosedis silent, anything else is logged at debug.Public API and wire impact
None.
Closes #3848
🤖 Generated with Claude Code