revert(minvmd): back out abandoned gvproxy networking spec (#404) - #477
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
💤 Files with no reviewable changes (8)
📝 WalkthroughWalkthroughRemoves the Changesgvproxy crate and minvmd networking removal
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
Reverts the merged work from the abandoned tracking issue #404.
What this reverts
crates/gvproxycrate,crates/minvmd/src/net.rs, and the Cargo workspace/dep wiring (cleangit revertof ff6a212).docs/specs/03-spec-minvmd-networking-gvproxy/(added by docs(spec-minvmd-networking-gvproxy): minvmd networking — gvproxy userspace net for VM sessions #407, docs(arch-minvmd-networking-gvproxy): minvmd networking — gvproxy userspace net for VM sessions #445).Why
#404 wedged: the task decomposition split
State.gvproxy_pid(Task 1.3) from itsrun.rsconstructors (Task 1.2) into independent sibling tasks, so neither PR compiled on macOS alone. The spec was abandoned rather than rescued.Safety
No external dependents: only
crates/minvmdreferenced thegvproxycrate;sandbox2wiring was deferred and never landed. Workspace manifest validates after revert (cargo metadataclean).Status of the tree
Summary by CodeRabbit
Refactor
Documentation