Repository navigation
fix(net): finish the max_age to max_delay rename in tests - #5016
Conversation
|
Grok review of d98eba0 This finishes the #4917 rename ( I grepped every No issues found. CI was still queued when I looked, so confirm Verdict: MERGE once CI is green. This is an automated review, not the maintainer's decision |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 0 remain after this review. WalkthroughTwo publisher update test fixtures now set Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to The change updates stale test configuration names without an identified remaining merge risk. 🚥 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 |
|
Merge summary
(Written by Claude Opus 5.5) |
Problem
mainno longer compiles moq-net's tests. #4917 renamed the subscriber staleness bound tomax_delay(SubscribeUpdate::max_delay,Subscription::with_max_delay), but two tests that landed alongside it still use the old name:rs/moq-net/src/lite/publisher.rs(twolite::SubscribeUpdate { max_age, .. }literals)rs/moq-net/tests/route_change.rs(Subscription::with_max_age)Approach
Rename the three uses. No behavior change.
Impact
Alternatives
None; it is merge skew.
Follow-ups
None. Found while rebasing #4982.
🤖 Generated with Claude Code
(Written by Claude Opus 5.5)