[BUG] General exact-object fixtures cannot prepare native resolver custody #21

Closed
opened 2026-10-01 16:19:23 +02:00 by erikinkinen · 0 comments
Owner

Summary

The general exact-object resolver fixture still models ordinary path opens and a single remembered fixed-entry path. It does not provide the native acquisition methods or invocation storage required by the current resolver. Dependent launch, metadata, permission, resize and invocation controls therefore cannot exercise their intended successful resolution path.

Reproduction

Source inspection at Vfsd 812a205c8e1878de4a2dd21e822cd5603f18e1c7:

  1. Inspect src/exact_objects/tests/exact_test_backend.rs: mounted_state_with_flags supplies three handle rows and never attaches native invocation storage.
  2. Inspect src/exact_objects/tests/mod.rs: ResolverBackend implements the old path methods and ordinary close, while native acquisition methods retain the trait's refusal defaults.
  3. Follow resolve_powerbox_object into resolve_context_object and prepare_resolver_context, which require actual native scope, branch and candidate custody.
  4. Inspect dependent assertions that assume exactly one ordinary open, no resolution-time cleanup, and provider handle one.

These are source observations. No test command, clean-checkout execution or CI reproduction was performed under the current execution deferral.

Expected and actual behavior

Expected: the fixture supplies independently scripted provider objects, actual native ownership and adequate caller-counted storage; each control reaches its intended dispatch or failure boundary and observes original cleanup.

Actual: the legacy fixture cannot satisfy native preparation. Its ordinary-open counters, fixed provider numbers and remembered path do not describe the current resolver's owners or effects. This is a regression in the test setup; no production authority defect is alleged.

Environment and identity

  • Component repository/revision and Integration source graph: Vfsd 812a205c8e1878de4a2dd21e822cd5603f18e1c7; Integration 00a17bcea0bb415d1b283c78998d9071a5334e02, whose runtime Vfsd selector remains e4e6cb58bb639cbac326043e818e52054b084f7e.
  • Image profile, digest and build/runtime configuration: source inspection only; no image was built or executed.
  • Hardware or VM, architecture, firmware and toolchain versions: not exercised for this finding.
  • Input/session route and granted authority relevant to reproduction: test-only authenticated namespace resolution followed by exact endpoint dispatch and original provider cleanup.
  • Last known working revision, if known: not established.

Evidence and prior checks

Original general fixture, original storage setup, and native resolver requirements. Builds, tests, lint checks, VM/profiler execution and CI observation remain deferred; no runtime result or warning-free build is claimed.

Tracking

Part of native retained-directory migration, reviewed in Vfsd#3, and tracked by phase completion.

Source-complete in Vfsd d9bb26fa, with manual update c21b2e11. The fixture now provisions actual native invocation storage, independent literal namespace objects and shared production acquisition adapters. Dependent controls observe original pins, cleanup and effects. Literal reply faults are explicitly armed after resolution and still require the original live owner and route. Legacy fake handles, global bound-entry paths and ordinary open/close counters are removed; directory escape controls explicitly derive a narrowed root.

All published commits are signed and pushed. Fifty-six resolver-dependent controls remain authored and unrun. Formatting was applied through rustfmt stdin; tests, builds, lint/format checks, generated documentation, VM/profiler execution and CI observation remain deferred. Closed as a source-complete fixture repair under that deferral. The broader native migration, coherent runtime adoption and guest self-hosting remain open.

## Summary The general exact-object resolver fixture still models ordinary path opens and a single remembered fixed-entry path. It does not provide the native acquisition methods or invocation storage required by the current resolver. Dependent launch, metadata, permission, resize and invocation controls therefore cannot exercise their intended successful resolution path. ## Reproduction Source inspection at Vfsd `812a205c8e1878de4a2dd21e822cd5603f18e1c7`: 1. Inspect `src/exact_objects/tests/exact_test_backend.rs`: `mounted_state_with_flags` supplies three handle rows and never attaches native invocation storage. 2. Inspect `src/exact_objects/tests/mod.rs`: `ResolverBackend` implements the old path methods and ordinary close, while native acquisition methods retain the trait's refusal defaults. 3. Follow `resolve_powerbox_object` into `resolve_context_object` and `prepare_resolver_context`, which require actual native scope, branch and candidate custody. 4. Inspect dependent assertions that assume exactly one ordinary open, no resolution-time cleanup, and provider handle one. These are source observations. No test command, clean-checkout execution or CI reproduction was performed under the current execution deferral. ## Expected and actual behavior Expected: the fixture supplies independently scripted provider objects, actual native ownership and adequate caller-counted storage; each control reaches its intended dispatch or failure boundary and observes original cleanup. Actual: the legacy fixture cannot satisfy native preparation. Its ordinary-open counters, fixed provider numbers and remembered path do not describe the current resolver's owners or effects. This is a regression in the test setup; no production authority defect is alleged. ## Environment and identity - Component repository/revision and Integration source graph: Vfsd `812a205c8e1878de4a2dd21e822cd5603f18e1c7`; Integration `00a17bcea0bb415d1b283c78998d9071a5334e02`, whose runtime Vfsd selector remains `e4e6cb58bb639cbac326043e818e52054b084f7e`. - Image profile, digest and build/runtime configuration: source inspection only; no image was built or executed. - Hardware or VM, architecture, firmware and toolchain versions: not exercised for this finding. - Input/session route and granted authority relevant to reproduction: test-only authenticated namespace resolution followed by exact endpoint dispatch and original provider cleanup. - Last known working revision, if known: not established. ## Evidence and prior checks [Original general fixture](https://git.erikinkinen.fi/erix/vfsd/src/commit/812a205c8e1878de4a2dd21e822cd5603f18e1c7/src/exact_objects/tests/mod.rs), [original storage setup](https://git.erikinkinen.fi/erix/vfsd/src/commit/812a205c8e1878de4a2dd21e822cd5603f18e1c7/src/exact_objects/tests/exact_test_backend.rs), and [native resolver requirements](https://git.erikinkinen.fi/erix/vfsd/src/commit/812a205c8e1878de4a2dd21e822cd5603f18e1c7/src/exact_objects/native.rs). Builds, tests, lint checks, VM/profiler execution and CI observation remain deferred; no runtime result or warning-free build is claimed. ## Tracking Part of [native retained-directory migration](https://git.erikinkinen.fi/erix/vfsd/issues/16), reviewed in [Vfsd#3](https://git.erikinkinen.fi/erix/vfsd/pulls/3), and tracked by [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Source-complete in [Vfsd `d9bb26fa`](https://git.erikinkinen.fi/erix/vfsd/commit/d9bb26fae9e98edc4e9f3ed5647eb0161dd13238), with [manual update `c21b2e11`](https://git.erikinkinen.fi/erix/docs/commit/c21b2e110f43c0d5d706a482af92a97a301ceaef). The fixture now provisions actual native invocation storage, independent literal namespace objects and shared production acquisition adapters. Dependent controls observe original pins, cleanup and effects. Literal reply faults are explicitly armed after resolution and still require the original live owner and route. Legacy fake handles, global bound-entry paths and ordinary open/close counters are removed; directory escape controls explicitly derive a narrowed root. All published commits are signed and pushed. Fifty-six resolver-dependent controls remain authored and unrun. Formatting was applied through rustfmt stdin; tests, builds, lint/format checks, generated documentation, VM/profiler execution and CI observation remain deferred. Closed as a source-complete fixture repair under that deferral. The broader native migration, coherent runtime adoption and guest self-hosting remain open.
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#21
No description provided.