Skip to content

Fix null mounts projection in proven unallocated Volume classification - #159

Merged
chen21019 merged 1 commit into
mainfrom
fix/web170-nullable-volume-relations
Oct 3, 2026
Merged

chen21019 merged 1 commit into
mainfrom
fix/web170-nullable-volume-relations

Conversation

@chen21019

Copy link
Copy Markdown

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: null projection is preserved by the resource setter but rejected by
the shared classifier, so the native table hides the resource.

Minimal repair

  • Accept null only for the optional expanded mounts projection, never as proof
    of absent allocation and never convert it to a manufactured empty array.
  • Retain complete pool relationship, scoped mount-cache, exact-volume mount,
    project, fingerprint, nonempty raw ID and backend authorization guards.
  • Require native/Ember arrays rather than arbitrary objects with length: 0.
  • Add actual Store/Volume regression coverage and align the numeric 1.6.170
    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.

@chen21019
chen21019 requested a review from a team as a code owner October 3, 2026 00:29
@chen21019
chen21019 merged commit 71effe4 into main Oct 3, 2026
4 checks passed
@chen21019
chen21019 deleted the fix/web170-nullable-volume-relations branch October 3, 2026 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant