[BUG] Resolve nested native realm witness modules explicitly #16
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/posixd#16
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 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 directoriesfor the nonexistentsrc/byte_client/directories.rs. The existing file issrc/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
feature/posix-compat; published basec5fab30e9689ea99ed0b7149cca75ac629bc37c7, with descriptor ownership edits in progress.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.
erikinkinen referenced this issue from erix/docs2026-09-29 18:25:23 +02:00
erikinkinen referenced this issue from erix/exsh2026-09-29 18:26:25 +02:00
erikinkinen referenced this issue from erix/integration2026-09-29 18:27:07 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-29 18:27:27 +02:00
erikinkinen referenced this issue from erix/lib-ipc2026-09-29 18:27:33 +02:00
erikinkinen referenced this issue from erix/lib-posixabi2026-09-29 18:27:36 +02:00
erikinkinen referenced this issue from erix/loaderd2026-09-29 18:27:40 +02:00
erikinkinen referenced this issue2026-09-29 18:27:43 +02:00
erikinkinen referenced this issue from erix/procd2026-09-29 18:27:45 +02:00
erikinkinen referenced this issue from erix/rootd2026-09-29 18:27:47 +02:00