Repository navigation
perf(daemon): use native loopback for Linux-local state - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linux-local daemon traffic can cross a forwarded IPv4 loopback path under WSL. Prefer native IPv6 loopback for positively identified Linux-local state, with IPv4 fallback. Native Windows, shared Windows-backed state and uncertain mount inspection keep IPv4; explicit addresses bind exactly as requested. Generated bootstrap wrappers use automatic selection while retaining the documented old-controller upgrade procedure.
Add decision tests for platform/state classification, address fallback and rejection, native Windows launcher argument/console behavior, and a pinned binary SSH benchmark comparing IPv4/IPv6. Document measuring the operator-provisioned direct guest endpoint separately from host TCP forwarding.
Validation: full
make qualitypassed, coverage 85.9%, independent code/security and architecture reviews clear. Both actual native Windows wrapper cases executed and passed. Live installed validation combined the directly verified guest endpoint with the new Linux-local listener: a 1 GiB upload took 8.72 seconds of daemon operation time and 19.58 seconds for the complete MCP call, versus 40.93/48.84 seconds before. SHA-256 matched and the exact guest artifact was removed with observed absence. The direct-route-only intermediate result was 12.71 seconds of daemon time.Shared-state IPv4 compatibility and existing SSH authentication, ownership and receipt boundaries remain intact.