Fix null mounts projection in proven unallocated Volume classification - #159
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.
Root cause
Packaged QA v1.6.506 has the exact inactive local Volume in the Store with a
complete empty pool Collection and scoped mount cache. Its API-expanded
mounts: nullprojection is preserved by the resource setter but rejected bythe shared classifier, so the native table hides the resource.
Minimal repair
of absent allocation and never convert it to a manufactured empty array.
project, fingerprint, nonempty raw ID and backend authorization guards.
release metadata and lock baseline without changing the dependency graph.
Focused Chrome 153: 13/13 pass, zero failures/skips/todo. Independent scoped
source review: no blocker. Official immutable archive validation and packaged
QA lifecycle acceptance remain separate; historical HOLDs and the full matrix
are not promoted. No API/Auth/Engine, HAProxy or company deployment changes.