[BUG] General exact-object fixtures cannot prepare native resolver custody #21
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#21
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
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:src/exact_objects/tests/exact_test_backend.rs:mounted_state_with_flagssupplies three handle rows and never attaches native invocation storage.src/exact_objects/tests/mod.rs:ResolverBackendimplements the old path methods and ordinary close, while native acquisition methods retain the trait's refusal defaults.resolve_powerbox_objectintoresolve_context_objectandprepare_resolver_context, which require actual native scope, branch and candidate custody.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
812a205c8e1878de4a2dd21e822cd5603f18e1c7; Integration00a17bcea0bb415d1b283c78998d9071a5334e02, whose runtime Vfsd selector remainse4e6cb58bb639cbac326043e818e52054b084f7e.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 updatec21b2e11. 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 referenced this issue2026-10-01 16:26:09 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 16:26:11 +02:00
erikinkinen referenced this issue2026-10-01 16:26:11 +02:00
erikinkinen referenced this issue from erix/docs2026-10-01 16:26:12 +02:00
erikinkinen referenced this issue from erix/integration2026-10-01 16:26:12 +02:00
erikinkinen referenced this issue from erix/posixd2026-10-01 16:26:13 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-10-01 16:26:13 +02:00
erikinkinen referenced this issue from erix/ramfsd2026-10-01 16:26:14 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-10-01 16:26:14 +02:00
erikinkinen referenced this issue from erix/fatd2026-10-01 16:26:14 +02:00