Repository navigation
feat(mxc): migrate Windows driver to schema 1.0.0 - #4252
Open
shailendra-nv wants to merge 2 commits into
Open
shailendra-nv wants to merge 2 commits into
shailendra-nv wants to merge 2 commits into
Conversation
Signed-off-by: Shailendra Singh <shailendras@nvidia.com>
Signed-off-by: Shailendra Singh <shailendras@nvidia.com>
shailendra-nv
requested review from
a team,
derekwaynecarr,
mrunalp and
sjenning
as code owners
October 6, 2026 19:06
This branch has not been deployed
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.
Summary
--operationand--container-id) and remove retired JSON routing/configuration fields.Related Issue
No issue required: this is a targeted MXC dependency/schema compatibility migration requested directly for the Windows branch.
Changes
default_configuration_idgateway setting as a documented no-op for configuration compatibility.baseContainerSupportsIngressHostLoopbackAllowprobe capability, while continuing to execute ordinary ProcessContainer coverage on fallback tiers.probe-mxc-host.ps1and document the operational constraint.Testing
windows:check:arm64windows:lint:arm64windows:build:arm64windows:test:arm64windows:test:unsupported:arm64windows:test:mxc-real:arm64mise run pre-commitwindows:check:x64windows:test:x64windows:test:unsupported:x64windows:test:mxc-real:x64Colossus now runs
wxc-exec.exeProductVersion1.0.0+3cddcbc2(SHA-2568A6D1DB4DD1846981127D9014741BE18B094D07BE967765DFF6754BDA1D40259, valid Authenticode signature). Its previous 0.8.0 installation is preserved atC:\mxc-backup-0.8.0-20261006-1055.The RC3 probe selects
appcontainer-daclon Colossus: basic ProcessContainer is live, while IsolationSession andingress.hostLoopback=alloware unavailable on that Windows host. The live suite now reports those constraints instead of treating them as schema failures.The local ARM64 pre-commit hook cannot build
grpcio-tools 1.78.0from source under Windows ARM64/Python 3.14 because MSVC receives incompatible/std:c++17and/std:c11flags. The complete pre-commit suite passed on Colossus x64.Checklist