Repository navigation
Conversation
Squash of the MXC backend branch (#427) replayed onto current main, so the change can run under the current CI workflow. Two things differ from the original branch: - The MXC path computes masked credential-file denies the same way the srt-win path now does, since the access-set helper requires them. - CI runs the boundary suite (mxc.test.ts) in its own process, then the Windows suites main lists. Not ported: per-command proxy attribution (commandId) is not threaded through the MXC wrap.
Two tests failed only because main moved under the branch: - The checked-in list of public exports gains the five MXC names the backend adds to the package entry point. - The boundary suite's TLS block treats "sandbox user is not provisioned" from the dependency check as the expected srt-win miss. Main reports that case from the dependency check now, as a plain error.
@microsoft/mxc-sdk 0.9 declares Node >=24. On Node 22 the Windows legs logged that the SDK was not installed, so backend selection never reached the MXC probe. The other legs stay on 22, the oldest line `engines` allows.
Emit the exact MXC 1.0.0 one-shot request directly: the 1.x SDK has no compile-only buildSandboxPayload. Policy shape is unchanged from #640; hostLoopback stays explicit in both branches as 1.0 requires.
1.0.0 still refused `network.ingress.hostLoopback: 'allow'` unless the host advertised PSEC 1.1 native ingress, which no shipping Windows 11 24H2/25H2 build does, so the mxc backend was never selected on a host with a proxy port and every session fell back to srt-win. mxc 1.0.1 (microsoft/mxc#1490) honors host-loopback allow on PSEC 1.0 hosts as policy-permitted outbound loopback, which is all srt needs to reach its own proxy. The 1.0.0 request schema is unchanged, so only the package pin and lock entry move.
ig-ant
force-pushed
the
claude-laptop/lcc-20261021-183939-c7e08474/mxc-sdk-1.0.1-ci
branch
from
October 21, 2026 20:06
50061ff to
de78823
Compare
…unners The selection probe's error does not say whether the OS build, a feature override or the API itself is the cause.
The MXC backend now runs only when requested, and a configuration it cannot enforce is an error rather than a silent switch to srt-win. Unset means srt-win.
Collaborator
Author
|
Superseded by #766. |
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.
No description provided.