[BUG] Acquisition metadata fixtures confuse retained sources and object aliases #20

Closed
opened 2026-10-01 15:46:57 +02:00 by erikinkinen · 0 comments
Owner

Summary

Native acquisition metadata controls choose the first provider component instead
of the requested file, and a root/cwd control assigns distinct inode observations
to two references to the same actual object. Real source custody makes these
assumptions invalid, so these controls cannot establish the stated routing and
identity properties.

Reproduction

Source-derived reproduction, not an executed test: inspect
acquisition_scope/metadata_tests.rs and cwd/native/fixture.rs at Vfsd
62f347280e. The shared bootstrap keeps an original
work-directory candidate. The file fixture then acquires another candidate, while
metadata controls choose components.iter().next() instead of that file's identity.
The file scope has equal root and cwd objects; writing separate observations under
their identical handle key overwrites the first observation.

Expected and actual behavior

Expected: independently scripted provider objects supply metadata for the actual
selected file, root and cwd. Aliases of one object agree; distinct root/cwd controls
acquire genuinely distinct directories.

Actual, established from source: map order can select the source directory, and
the root/cwd control expects conflicting serials from one map key. No compiler,
test failure, exit status or runtime reproduction is claimed. Repair the controls
using literal provider identities and real contextual cwd derivation; retain
independent cleanup and add alias-lifetime coverage.

Environment and identity

  • Component repository/revision and Integration source graph: Vfsd 62f347280e; Integration 00a17bcea0bb415d1b283c78998d9071a5334e02.
  • Image profile, digest and build/runtime configuration: host test fixtures; no image built or run.
  • Hardware or VM, architecture, firmware and toolchain versions: no compiler or VM reproduction performed.
  • Input/session route and granted authority relevant to reproduction: native acquisition fixtures; no production authority boundary is alleged to fail.
  • Last known working revision, if known: not established by execution.

Evidence and prior checks

The actual fixture bootstrap, file-scope producer and map-key assignments establish
the mismatch. Testing, builds and CI observation remain deferred. Source repair
and additional authored controls do not establish an execution pass.

Tracking

Related: retained cwd migration,
Vfsd review, and the
phase completion tracker.

Source-complete repair is signed and pushed in
Vfsd 812a205c,
with the updated contract in
Docs 20649047.
Metadata now follows independently scripted object identity. Distinct root/cwd
observations use actual cwd derivation, and a new control preserves one inode
observation through source and sibling retirement. Original file effects are
selected explicitly, and scope teardown observes the actual receiver. The six
metadata controls, among 36 updated acquisition-family controls, remain authored
and unrun. Closed as source-complete under the testing/CI waiver; no execution
pass is claimed.

## Summary Native acquisition metadata controls choose the first provider component instead of the requested file, and a root/cwd control assigns distinct inode observations to two references to the same actual object. Real source custody makes these assumptions invalid, so these controls cannot establish the stated routing and identity properties. ## Reproduction Source-derived reproduction, not an executed test: inspect acquisition_scope/metadata_tests.rs and cwd/native/fixture.rs at Vfsd 62f347280ed660f9e53599853670675636a45059. The shared bootstrap keeps an original work-directory candidate. The file fixture then acquires another candidate, while metadata controls choose components.iter().next() instead of that file's identity. The file scope has equal root and cwd objects; writing separate observations under their identical handle key overwrites the first observation. ## Expected and actual behavior Expected: independently scripted provider objects supply metadata for the actual selected file, root and cwd. Aliases of one object agree; distinct root/cwd controls acquire genuinely distinct directories. Actual, established from source: map order can select the source directory, and the root/cwd control expects conflicting serials from one map key. No compiler, test failure, exit status or runtime reproduction is claimed. Repair the controls using literal provider identities and real contextual cwd derivation; retain independent cleanup and add alias-lifetime coverage. ## Environment and identity - Component repository/revision and Integration source graph: Vfsd 62f347280ed660f9e53599853670675636a45059; Integration 00a17bcea0bb415d1b283c78998d9071a5334e02. - Image profile, digest and build/runtime configuration: host test fixtures; no image built or run. - Hardware or VM, architecture, firmware and toolchain versions: no compiler or VM reproduction performed. - Input/session route and granted authority relevant to reproduction: native acquisition fixtures; no production authority boundary is alleged to fail. - Last known working revision, if known: not established by execution. ## Evidence and prior checks The actual fixture bootstrap, file-scope producer and map-key assignments establish the mismatch. Testing, builds and CI observation remain deferred. Source repair and additional authored controls do not establish an execution pass. ## Tracking Related: [retained cwd migration](https://git.erikinkinen.fi/erix/vfsd/issues/16), [Vfsd review](https://git.erikinkinen.fi/erix/vfsd/pulls/3), and the [phase completion tracker](https://git.erikinkinen.fi/erix/integration/issues/65). Source-complete repair is signed and pushed in [Vfsd 812a205c](https://git.erikinkinen.fi/erix/vfsd/commit/812a205c8e1878de4a2dd21e822cd5603f18e1c7), with the updated contract in [Docs 20649047](https://git.erikinkinen.fi/erix/docs/commit/20649047eb44d77583833f8b6efbaca6cceea595). Metadata now follows independently scripted object identity. Distinct root/cwd observations use actual cwd derivation, and a new control preserves one inode observation through source and sibling retirement. Original file effects are selected explicitly, and scope teardown observes the actual receiver. The six metadata controls, among 36 updated acquisition-family controls, remain authored and unrun. Closed as source-complete under the testing/CI waiver; no execution pass is claimed.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:18 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/vfsd#20
No description provided.