[BUG] Gate native serving modules with their host-excluded dependencies #25

Closed
opened 2026-10-02 08:52:34 +02:00 by erikinkinen · 0 comments
Owner

Summary

Five recently introduced VFS implementation modules are declared unconditionally, although their required backend/state modules are enabled only for unit tests or the native x86_64 EriX target. An ordinary host build therefore selects imports whose defining modules are absent. This is a source-confirmed configuration defect; no build or CI reproduction was executed.

Reproduction

At VFS revision 55498e81b8b74428c44d1a41da966e43dc02589f, inspect the module declarations in src/main.rs and imports in candidate_control, permission_update, scope_candidate_control, scope_namespace, and scope_permission_update. Select a non-test Linux host configuration: backend_transport, backend_provider, namespace, and related native modules are excluded, while these five consumers remain selected. An eventual cargo build in that configuration exercises the inconsistency. That command has not been run under the current execution waiver.

Expected and actual behavior

Expected: the ordinary host executable selects its documented host configuration, while native serving modules and their dependencies are enabled together for unit tests and EriX builds. Actual source selection: these five modules import native dependencies that are conditionally absent. No compiler diagnostic, exit status, or runtime result is claimed. Apply the existing any(test, all(target_arch = "x86_64", target_os = "none")) gate consistently to these consumers and the new advisory-lock scope module.

Environment and identity

  • Component: VFS 55498e81b8b74428c44d1a41da966e43dc02589f; Integration catalog 9110676622b1c88817b1fe4383f1fa23ccc20805.
  • Configuration: ordinary non-test host build; native x86_64 EriX and unit-test configurations retain these implementations.
  • Image, hardware, firmware, and runtime route: no execution involved; not applicable to source selection.
  • Authority: no new grant or route is required by the repair.
  • Last known working revision: not established.

Evidence and prior checks

The unconditional declarations and conditional imports are directly inspectable in the pinned sources. Repair the source selection and review both host and native/test predicates. Tests, builds, lint checks, generated documentation, VM execution, and CI observation remain deferred by user instruction. This finding does not assert an observed CI failure.

Tracking

Coordinate VFS review, advisory locks, and phase completion. Close after coherent signed source publication, with execution explicitly waived rather than represented as passed.

## Summary Five recently introduced VFS implementation modules are declared unconditionally, although their required backend/state modules are enabled only for unit tests or the native x86_64 EriX target. An ordinary host build therefore selects imports whose defining modules are absent. This is a source-confirmed configuration defect; no build or CI reproduction was executed. ## Reproduction At VFS revision `55498e81b8b74428c44d1a41da966e43dc02589f`, inspect the module declarations in `src/main.rs` and imports in `candidate_control`, `permission_update`, `scope_candidate_control`, `scope_namespace`, and `scope_permission_update`. Select a non-test Linux host configuration: `backend_transport`, `backend_provider`, `namespace`, and related native modules are excluded, while these five consumers remain selected. An eventual `cargo build` in that configuration exercises the inconsistency. That command has not been run under the current execution waiver. ## Expected and actual behavior Expected: the ordinary host executable selects its documented host configuration, while native serving modules and their dependencies are enabled together for unit tests and EriX builds. Actual source selection: these five modules import native dependencies that are conditionally absent. No compiler diagnostic, exit status, or runtime result is claimed. Apply the existing `any(test, all(target_arch = "x86_64", target_os = "none"))` gate consistently to these consumers and the new advisory-lock scope module. ## Environment and identity - Component: VFS `55498e81b8b74428c44d1a41da966e43dc02589f`; Integration catalog `9110676622b1c88817b1fe4383f1fa23ccc20805`. - Configuration: ordinary non-test host build; native x86_64 EriX and unit-test configurations retain these implementations. - Image, hardware, firmware, and runtime route: no execution involved; not applicable to source selection. - Authority: no new grant or route is required by the repair. - Last known working revision: not established. ## Evidence and prior checks The unconditional declarations and conditional imports are directly inspectable in the pinned sources. Repair the source selection and review both host and native/test predicates. Tests, builds, lint checks, generated documentation, VM execution, and CI observation remain deferred by user instruction. This finding does not assert an observed CI failure. ## Tracking Coordinate [VFS review](https://git.erikinkinen.fi/erix/vfsd/pulls/3), [advisory locks](https://git.erikinkinen.fi/erix/posixd/issues/32), and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Close after coherent signed source publication, with execution explicitly waived rather than represented as passed.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:19 +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#25
No description provided.