[BUG] The default catalog cannot build its configured Rootd #789

Open
opened 2026-11-14 12:30:27 +01:00 by erikinkinen · 0 comments
Owner

Summary

The default component graph cannot build its configured Rootd. Updating old
Cargo declarations to the current dependency policy is necessary, but does not
supply the IPC, CapABI and orchestration contracts that Rootd actually uses.

Reproduction

  1. Inspect the default components.toml and cargo-repos.toml at
    Integration 5231942e.
  2. Audit each selected source's original Cargo declarations against the
    branch = "main" policy. The audit finds 217 noncompliant Git dependency
    declarations across 52 selected components.
  3. Separately, correct those declarations in a controlled catalog selection,
    retaining Rootd's runtime source, and prepare its genuine locked, offline
    native compilation with rootd-runtime,rootd-integration-policy for
    x86_64-unknown-none.

Step 3 is a controlled local probe, not an unchanged public reproduction recipe:
its declaration-only catalog repair has not been published. It exposes the
remaining provider mismatch instead of treating a declaration-policy pass as
proof that the graph compiles.

Expected and actual behavior

Expected: the catalog supplies both compliant declarations and the complete
contracts needed by its selected Rootd; the native build produces an ELF.

Actual: the controlled Rootd compilation fails with 35 compiler diagnostics,
including:

E0433: could not find `invocation` in `ipc_syscall_x86_64`
E0422: cannot find ... `VfsMetadataNamespaceRequestV1` in ... `lib_ipc`
E0425: cannot find ... `SLOT_TTYD_LOCAL_TIMED_QUERY_ENDPOINT_V1` in ... `lib_capabi`
E0405: cannot find trait `TimedDeadlineEffects` in ... `rootd_integration_orchestration`
E0425: cannot find function `verify_vfs_original_fat_directory_growth` ...

Other missing contracts include process-generation cleanup/terminal events and
VFS metadata request/response sizes. These are compile-time API mismatches;
they do not establish a runtime security failure.

Environment and identity

  • Rootd source remains
    ea068948.
  • The probe selects public
    IPC 911d4df0 and
    CapABI c232e76e.
  • The orchestration source is based on catalog-selected
    Integration 2efa2fc7,
    with only Cargo declaration changes in the probe.
  • Linux x86-64 host, Rust 1.93.1, native x86_64-unknown-none release build;
    warnings denied, one compiler job, original 120-second hard/30-second stall
    limits and 16 MiB captured-output bound.
  • No known working complete default graph is established by this investigation.

Evidence and prior checks

The declaration audit, genuine native compilation and full-image acceptance are
separate results. The controlled declaration-policy checks pass; Rootd's native
compilation fails. Selected IPC/CapABI tests pass independently, which does not
resolve their incompatibility with this Rootd.

The observed live CI failure stopped at the dependency-policy caller, before
Rootd compilation. The 35 compiler errors come from the separate controlled
probe. A complete default image build, boot and guest acceptance have not been
performed for the repaired graph.

Tracking

Related: shared CI preparation #518,
orchestration provider #784,
Phase 6 completion #65.
The older catalog mismatch #68
tracked a different historical pin-alignment failure and is closed.

  • Publish a coherent default catalog with compliant original declarations.
  • Supply Rootd's actual IPC, CapABI and orchestration contracts without
    removing required checks or restoring deprecated APIs.
  • Build the configured Rootd through the maintained native source gateway.
  • Complete the original full-image and guest gates on that exact graph.
## Summary The default component graph cannot build its configured Rootd. Updating old Cargo declarations to the current dependency policy is necessary, but does not supply the IPC, CapABI and orchestration contracts that Rootd actually uses. ## Reproduction 1. Inspect the default `components.toml` and `cargo-repos.toml` at [Integration 5231942e](https://git.erikinkinen.fi/erix/integration/src/commit/5231942e62c9b6a976d670d802d76580c7163f95). 2. Audit each selected source's original Cargo declarations against the `branch = "main"` policy. The audit finds 217 noncompliant Git dependency declarations across 52 selected components. 3. Separately, correct those declarations in a controlled catalog selection, retaining Rootd's runtime source, and prepare its genuine locked, offline native compilation with `rootd-runtime,rootd-integration-policy` for `x86_64-unknown-none`. Step 3 is a controlled local probe, not an unchanged public reproduction recipe: its declaration-only catalog repair has not been published. It exposes the remaining provider mismatch instead of treating a declaration-policy pass as proof that the graph compiles. ## Expected and actual behavior Expected: the catalog supplies both compliant declarations and the complete contracts needed by its selected Rootd; the native build produces an ELF. Actual: the controlled Rootd compilation fails with 35 compiler diagnostics, including: ```text E0433: could not find `invocation` in `ipc_syscall_x86_64` E0422: cannot find ... `VfsMetadataNamespaceRequestV1` in ... `lib_ipc` E0425: cannot find ... `SLOT_TTYD_LOCAL_TIMED_QUERY_ENDPOINT_V1` in ... `lib_capabi` E0405: cannot find trait `TimedDeadlineEffects` in ... `rootd_integration_orchestration` E0425: cannot find function `verify_vfs_original_fat_directory_growth` ... ``` Other missing contracts include process-generation cleanup/terminal events and VFS metadata request/response sizes. These are compile-time API mismatches; they do not establish a runtime security failure. ## Environment and identity - Rootd source remains [`ea068948`](https://git.erikinkinen.fi/erix/rootd/src/commit/ea068948437f32d9da9614834bd4da1aa7a456e5). - The probe selects public [IPC `911d4df0`](https://git.erikinkinen.fi/erix/lib-ipc/src/commit/911d4df034e2b8dec06ddbcee3a0f52aad47fc0a) and [CapABI `c232e76e`](https://git.erikinkinen.fi/erix/lib-capabi/src/commit/c232e76ee337fbbc6191c2a44aa979a743483bd1). - The orchestration source is based on catalog-selected [Integration `2efa2fc7`](https://git.erikinkinen.fi/erix/integration/src/commit/2efa2fc7122dc459649630b0baa736981e0a4bfc), with only Cargo declaration changes in the probe. - Linux x86-64 host, Rust 1.93.1, native `x86_64-unknown-none` release build; warnings denied, one compiler job, original 120-second hard/30-second stall limits and 16 MiB captured-output bound. - No known working complete default graph is established by this investigation. ## Evidence and prior checks The declaration audit, genuine native compilation and full-image acceptance are separate results. The controlled declaration-policy checks pass; Rootd's native compilation fails. Selected IPC/CapABI tests pass independently, which does not resolve their incompatibility with this Rootd. The observed live CI failure stopped at the dependency-policy caller, before Rootd compilation. The 35 compiler errors come from the separate controlled probe. A complete default image build, boot and guest acceptance have not been performed for the repaired graph. ## Tracking Related: [shared CI preparation #518](https://git.erikinkinen.fi/erix/integration/pulls/518), [orchestration provider #784](https://git.erikinkinen.fi/erix/integration/pulls/784), [Phase 6 completion #65](https://git.erikinkinen.fi/erix/integration/issues/65). The older [catalog mismatch #68](https://git.erikinkinen.fi/erix/integration/issues/68) tracked a different historical pin-alignment failure and is closed. - [ ] Publish a coherent default catalog with compliant original declarations. - [ ] Supply Rootd's actual IPC, CapABI and orchestration contracts without removing required checks or restoring deprecated APIs. - [ ] Build the configured Rootd through the maintained native source gateway. - [ ] Complete the original full-image and guest gates on that exact graph.
erikinkinen added this to the Alpha 1 milestone 2026-11-14 12:30:27 +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/integration#789
No description provided.