Repository navigation
fix(minimald): add new ListenArgs fields to the test_cli initializer - #1757
Conversation
The egress and proxy-port flags were added to ListenArgs without updating the unit-test initializer, so the minimald test target failed to compile and clippy --all-targets went red on main. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EgnhoZwtoZz6vFJZcfvZ3K
|
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. 📝 WalkthroughWalkthroughThe ChangesCLI Test Fixture Defaults
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The fixture now supplies defaults for the added options, and no material merge-blocking risk is evident in the supplied scope. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
A rabbit checks the fixture with care, Comment |
Summary
clippy --workspace --all-targetsfails onmainwith E0063: thetest_clihelper incrates/minimald/src/main.rsbuildsListenArgsby hand and is missinghostname_proxy_port,zone_answerer_portandegress_deny_all_opt_out, so theminimaldtest target doesn't compile. This adds the three fields, with the same defaults the microVM init path uses (None,None,false).How it started: a semantic merge conflict between three PRs, with no textual conflict to flag it.
hostname_proxy_portandzone_answerer_porttoListenArgs.egress_deny_all_opt_out.[worker:coverage]) added thetest_clihelper, which constructsListenArgswith a struct literal. It merged on 2026-09-28, after both of the others, but was evidently written and validated against a base that predated them. Its initializer never picked up the new fields, and it merged without CI re-running against the updatedmain.The root gap is that the merge path doesn't re-validate a PR against the current base tip (no merge queue or require-up-to-date rule), so two individually green PRs can break
maintogether. Enabling a merge queue or "require branches to be up to date" on the ruleset would prevent this class of failure. That's a repo-settings decision, so I haven't changed anything.Testing
cargo clippy --workspace --al 8000 l-targets --locked -- -D warnings: clean (failed with E0063 before the change)cargo fmt --check -p minimald: cleanChecklist
BREAKING CHANGE:footer present if this is a breaking change (n/a)🤖 Generated with Claude Code
https://claude.ai/code/session_01EgnhoZwtoZz6vFJZcfvZ3K
Generated by Claude Code
Summary by CodeRabbit