[BUG] Read-header update leaves transitive IPC revisions inconsistent #34
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/vfsd#34
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Vfsd's read-header update selects the new LibIPC revision while three transitive dependencies still select the older revision. CI rejects the inconsistent graph before Cargo checks.
Reproduction
Run the normal push workflow at Vfsd
367a1c1e8c077f12b12f7f7b78c50d7f86187bed. Run 371 fails insetup-component-ci-overrides.py.Expected and actual behavior
All manifests in the selected graph must agree on one LibIPC revision. Vfsd selects
61b43723; selected LibBootstrap53c000f6, LibCapABI356d6702and LibTime3e998d1fselect03e87a2d. The helper reports a conflicting revision for LibIPC and stops before compiling or running tests.Environment and identity
The failure is in the x86-64 component CI source setup, using the workflow's pinned Integration helper
8184ef4b6443384222266be7d40a312b55d2c17e. It precedes image construction and guest execution. The preceding Vfsd workflow ata2b5ef91passes; this is not evidence about the repaired guest read path.Evidence and prior checks
The linked original run retains the conflict and selected manifests. The graph needs updating from suppliers to consumers; weakening the single-revision check or replacing selected Git objects would leave the mismatch unresolved.
Tracking
Read-path repair, implementation PR, phase completion.
The LibCapABI, LibTime and LibBootstrap updates and Vfsd’s matching pins are published. Vfsd run375 passes both original jobs at
5126e7c9. The remaining consumer pins are published too; both Integration catalogs are being checked before publication.Updated the helper criterion to match the canonical dependency policy: internal manifests track
main, and maintained source selection retains one exact commit per repository throughout the graph. CI390 passes with pinned helper74d8e383; Integration f0316cd5 aligns both source catalogs. Graph consistency remains required under the migrated workflow.