[BUG] Native wildcard Result imports break provider custody signatures #15

Closed
opened 2026-09-30 17:04:57 +02:00 by erikinkinen · 0 comments
Owner

Summary

Module-level native wildcard imports shadow the standard two-parameter result type in provider custody code and its controls. lib_ipc::Result<T> has one type argument, but these modules declare Result<..., u32>. This source type-arity defect prevents the affected code from compiling as written. Explicitly importing core::result::Result preserves the intended provider error domain.

Reproduction

At e2fsd 0fc774b8ea84cdf9b974c6fb42fde9cd04373719, inspect src/dispatch/mount_custody.rs, src/store/acquisition/link_page_tests.rs, src/store/acquisition/parent_tests.rs, src/store/mount_custody/tests.rs. Each has a module-level lib_ipc::* import and two-parameter result signatures. The selected LibIPC alias is declared in src/error.rs and re-exported by src/lib.rs.

When compilation is re-enabled, compile the affected service and its supported test targets. No reproduction command, compiler diagnostic or exit status is claimed; testing/build/lint execution and CI observation remain deferred by user instruction.

Expected and actual behavior

Expected: the provider methods and fixtures return the standard result with their explicit native numeric error. Actual source: the glob imports the incompatible one-parameter native codec alias. The repair explicitly selects the standard type without changing framing, authority or effect ordering.

Environment and identity

  • Component: e2fsd 0fc774b8ea84cdf9b974c6fb42fde9cd04373719; LibIPC bebb7a740d1eb665e7325e5c6f3a7a0ec501032d.
  • Integration graph: be7e5cbb5f1041fafa44a70df6da38e02db2ad88.
  • Image, VM, toolchain and runtime: no execution for this source audit.
  • Relevant authority: existing original provider routes and custody are unchanged.
  • Last known working revision: not established.

Evidence and prior checks

The source imports, result signatures and selected alias declaration establish the mismatch. The expanded inventory distinguishes module-level collisions from existing explicit standard imports and function-local globs outside enclosing signature scope. Related source defects are tracked in Vfsd and the earlier Posixd repair. No executed test or compiler pass is claimed.

Tracking

Related component review, status and directory work, and phase completion. Close after the source repair and coherent signed publication; deferred test execution does not gate acceptance.

Original special-inode metadata — 30 September 2026

No device, socket, pipe, clock or new provider endpoint is granted.

The full status/directory item remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed.

Related records and contracts
Repository Links
docs PR 4
e2fsd issue 15
fatd issue 6, PR 3
integration PR 12
lib-ipc PR 2
lib-posixabi PR 3
posixd PR 5
ramfsd issue 6, PR 2
rootd PR 2
vfsd PR 3
## Summary Module-level native wildcard imports shadow the standard two-parameter result type in provider custody code and its controls. `lib_ipc::Result<T>` has one type argument, but these modules declare `Result<..., u32>`. This source type-arity defect prevents the affected code from compiling as written. Explicitly importing `core::result::Result` preserves the intended provider error domain. ## Reproduction At `e2fsd` `0fc774b8ea84cdf9b974c6fb42fde9cd04373719`, inspect `src/dispatch/mount_custody.rs`, `src/store/acquisition/link_page_tests.rs`, `src/store/acquisition/parent_tests.rs`, `src/store/mount_custody/tests.rs`. Each has a module-level `lib_ipc::*` import and two-parameter result signatures. The selected LibIPC alias is declared in `src/error.rs` and re-exported by `src/lib.rs`. When compilation is re-enabled, compile the affected service and its supported test targets. No reproduction command, compiler diagnostic or exit status is claimed; testing/build/lint execution and CI observation remain deferred by user instruction. ## Expected and actual behavior Expected: the provider methods and fixtures return the standard result with their explicit native numeric error. Actual source: the glob imports the incompatible one-parameter native codec alias. The repair explicitly selects the standard type without changing framing, authority or effect ordering. ## Environment and identity - Component: `e2fsd` `0fc774b8ea84cdf9b974c6fb42fde9cd04373719`; LibIPC `bebb7a740d1eb665e7325e5c6f3a7a0ec501032d`. - Integration graph: `be7e5cbb5f1041fafa44a70df6da38e02db2ad88`. - Image, VM, toolchain and runtime: no execution for this source audit. - Relevant authority: existing original provider routes and custody are unchanged. - Last known working revision: not established. ## Evidence and prior checks The source imports, result signatures and selected alias declaration establish the mismatch. The expanded inventory distinguishes module-level collisions from existing explicit standard imports and function-local globs outside enclosing signature scope. Related source defects are tracked in [Vfsd](https://git.erikinkinen.fi/erix/vfsd/issues/15) and the earlier [Posixd repair](https://git.erikinkinen.fi/erix/posixd/issues/26). No executed test or compiler pass is claimed. ## Tracking Related [component review](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [status and directory work](https://git.erikinkinen.fi/erix/posixd/issues/25), and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Close after the source repair and coherent signed publication; deferred test execution does not gate acceptance. ### Original special-inode metadata — 30 September 2026 No device, socket, pipe, clock or new provider endpoint is granted. The [full status/directory item](https://git.erikinkinen.fi/erix/posixd/issues/25) remains open for complete FAT metadata, pipe/stream status, the compatibility special-device-number field and remaining full-item integration. Both complete EriX guest generations and external Rust/LLVM rebuilding inside EriX remain required and unperformed. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | docs | [PR 4](https://git.erikinkinen.fi/erix/docs/pulls/4) | | e2fsd | [issue 15](https://git.erikinkinen.fi/erix/e2fsd/issues/15) | | fatd | [issue 6](https://git.erikinkinen.fi/erix/fatd/issues/6), [PR 3](https://git.erikinkinen.fi/erix/fatd/pulls/3) | | integration | [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) | | lib-ipc | [PR 2](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2) | | lib-posixabi | [PR 3](https://git.erikinkinen.fi/erix/lib-posixabi/pulls/3) | | posixd | [PR 5](https://git.erikinkinen.fi/erix/posixd/pulls/5) | | ramfsd | [issue 6](https://git.erikinkinen.fi/erix/ramfsd/issues/6), [PR 2](https://git.erikinkinen.fi/erix/ramfsd/pulls/2) | | rootd | [PR 2](https://git.erikinkinen.fi/erix/rootd/pulls/2) | | vfsd | [PR 3](https://git.erikinkinen.fi/erix/vfsd/pulls/3) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:46 +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/e2fsd#15
No description provided.