[BUG] Resolve nested native realm witness modules explicitly #16

Closed
opened 2026-09-29 18:01:31 +02:00 by erikinkinen · 0 comments
Owner

Summary

The two native realm-client executables load their witness through an explicit path in the shared native adapter. Its nested directory, resize and stream witness declarations rely on implicit child paths. Applying rustfmt to either executable resolves those children beside the witness file, where they do not exist, and stops before formatting the complete binary. These child modules need explicit paths to their actual witness subdirectory.

Reproduction

From the Posixd repository, apply rustfmt --edition 2021 src/realm_byte_client.rs src/realm_binding_client.rs. The current descriptor-ownership working tree exposes the same existing witness declarations in both binaries. No build or test execution is required to observe the formatter's module-resolution refusal.

Expected and actual behavior

Expected: both executable roots resolve all authored witness modules and can be formatted.

Observed: rustfmt exits with status 1 and reports failed to resolve mod directories for the nonexistent src/byte_client/directories.rs. The existing file is src/byte_client/witness/directories.rs; resize and external witnesses have the same declaration pattern. Use explicit child paths, including the new descriptor witness, so every binary refers to the intended files.

Environment and identity

  • Component: Posixd, branch feature/posix-compat; published base c5fab30e9689ea99ed0b7149cca75ac629bc37c7, with descriptor ownership edits in progress.
  • Configuration: source formatting of both executable roots; native x86-64 witness modules are selected by their existing cfg/path declarations.
  • No image, hardware or VM execution was used. The selected installed rustfmt produced the observed source-resolution error.
  • No route or native authority is acquired by the correction.
  • Last known working revision for these nested declarations: not established.

Evidence and prior checks

Implemented in signed source 7c7e44d9. Explicit native-witness child module paths now resolve the existing controls when rustfmt traverses both binary roots. Existing lifecycle controls are retained. This is source/formatting evidence only; compiler, test and CI execution remain deferred. Closed under the implementation acceptance waiver.

The observation is a formatter failure, not a claimed compiler failure, test result or CI regression. Tests, builds and CI observation remain deferred by user instruction. Correct the declared child paths and apply formatting; retain the existing native witness behavior and authored coverage.

Tracking

Related descriptor ownership: #15. Owning review: #5. Phase tracking: erix/integration#65.

## Summary The two native realm-client executables load their witness through an explicit path in the shared native adapter. Its nested directory, resize and stream witness declarations rely on implicit child paths. Applying rustfmt to either executable resolves those children beside the witness file, where they do not exist, and stops before formatting the complete binary. These child modules need explicit paths to their actual witness subdirectory. ## Reproduction From the Posixd repository, apply `rustfmt --edition 2021 src/realm_byte_client.rs src/realm_binding_client.rs`. The current descriptor-ownership working tree exposes the same existing witness declarations in both binaries. No build or test execution is required to observe the formatter's module-resolution refusal. ## Expected and actual behavior Expected: both executable roots resolve all authored witness modules and can be formatted. Observed: rustfmt exits with status 1 and reports `failed to resolve mod directories` for the nonexistent `src/byte_client/directories.rs`. The existing file is `src/byte_client/witness/directories.rs`; resize and external witnesses have the same declaration pattern. Use explicit child paths, including the new descriptor witness, so every binary refers to the intended files. ## Environment and identity - Component: Posixd, branch `feature/posix-compat`; published base `c5fab30e9689ea99ed0b7149cca75ac629bc37c7`, with descriptor ownership edits in progress. - Configuration: source formatting of both executable roots; native x86-64 witness modules are selected by their existing cfg/path declarations. - No image, hardware or VM execution was used. The selected installed rustfmt produced the observed source-resolution error. - No route or native authority is acquired by the correction. - Last known working revision for these nested declarations: not established. ## Evidence and prior checks Implemented in [signed source `7c7e44d9`](https://git.erikinkinen.fi/erix/posixd/commit/7c7e44d94d96b0c6c0574ac765047fd3eaa8e44f). Explicit native-witness child module paths now resolve the existing controls when rustfmt traverses both binary roots. Existing lifecycle controls are retained. This is source/formatting evidence only; compiler, test and CI execution remain deferred. Closed under the implementation acceptance waiver. The observation is a formatter failure, not a claimed compiler failure, test result or CI regression. Tests, builds and CI observation remain deferred by user instruction. Correct the declared child paths and apply formatting; retain the existing native witness behavior and authored coverage. ## Tracking Related descriptor ownership: https://git.erikinkinen.fi/erix/posixd/issues/15. Owning review: https://git.erikinkinen.fi/erix/posixd/pulls/5. Phase tracking: https://git.erikinkinen.fi/erix/integration/issues/65.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:05 +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/posixd#16
No description provided.