Repository navigation
Pin SparkQwen maintenance image for TP2 sidecars - #69
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.
Pin the SparkQwen maintenance image that preserves full blocking chat content after refusal detection and recognizes packed checkpoint projection names. Update the source, engine, install-tree and image identities together in the recipe and pin manifest.
The existing per-node fabric configuration and
.70shared-host allocation remain supported. No admission, routing or runtime lifecycle behavior changes.Validation: recipe/materialization and pin checks, static checks, formatting, lint, interchange, package-install smoke, and the full test suite. Native GB10 image build and a drained 03/04 activation passed. Both ranks run digest
ea6a2df03adfc8802a1baf6ab1d4b55c69dd76588f36bfd5d189781500e75830at utilization 0.70, with the existing port-1 rails and zero restarts. Blocking/streaming refusal-content canaries and the normal gateway content check passed. CI passes on Node 22 and 24.