[BUG] Shared IPC compilation and realm fixture oracles retain obsolete contracts #8

Open
opened 2026-10-12 12:11:45 +02:00 by erikinkinen · 0 comments
Owner

Summary

Shared IPC compilation and realm fixture oracles retain obsolete contracts. Maintained validation cannot reach its intended successful boundary.

Reproduction

At the linked original revision, run cargo clippy --all-targets -- -D warnings and cargo test --all-targets. Compilation fails before downstream service tests. After correcting the two library errors, run cargo test --all-targets --no-fail-fast to expose stale realm fixture expectations. The original failing source and current repairs are distinct; failures and true exit statuses are retained.

Expected and actual behavior

The maintained source should compile, discover its original controls and complete the specified checks without warnings. The compiler reports E0425 for validate_canonical_launch_path and E0308 because mount-custody validate returns Result where Result<()> is required. Subsequent current-source validation exposes six stale fixture controls: counted client/channel offsets, startup minor rejection, 72-byte receive header budgets and explicitly valid empty-descriptor pipe pools. One short provisioning buffer also causes an unconditional indexing panic during test compilation.

Environment and identity

  • Component repository/revision and Integration source graph: original lib-ipc source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

Evidence and prior checks

Use the existing canonical path validator, preserve result-code validation while returning unit, and migrate independent fixture inputs to the current ABI without weakening refusal boundaries. Current-source strict Clippy and formatting pass; the full suite initially records 828 passes and six fixture failures. Fresh validation follows the fixture corrections.

Original failing CI job.

Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.

Tracking

Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.

## Summary Shared IPC compilation and realm fixture oracles retain obsolete contracts. Maintained validation cannot reach its intended successful boundary. ## Reproduction At the linked original revision, run cargo clippy --all-targets -- -D warnings and cargo test --all-targets. Compilation fails before downstream service tests. After correcting the two library errors, run cargo test --all-targets --no-fail-fast to expose stale realm fixture expectations. The original failing source and current repairs are distinct; failures and true exit statuses are retained. ## Expected and actual behavior The maintained source should compile, discover its original controls and complete the specified checks without warnings. The compiler reports E0425 for validate_canonical_launch_path and E0308 because mount-custody validate returns Result<u32> where Result<()> is required. Subsequent current-source validation exposes six stale fixture controls: counted client/channel offsets, startup minor rejection, 72-byte receive header budgets and explicitly valid empty-descriptor pipe pools. One short provisioning buffer also causes an unconditional indexing panic during test compilation. ## Environment and identity - Component repository/revision and Integration source graph: [original lib-ipc source](https://git.erikinkinen.fi/erix/lib-ipc/commit/bf08d1998dcecaf6a02b97848ea973a38fb27d82), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## Evidence and prior checks Use the existing canonical path validator, preserve result-code validation while returning unit, and migrate independent fixture inputs to the current ABI without weakening refusal boundaries. Current-source strict Clippy and formatting pass; the full suite initially records 828 passes and six fixture failures. Fresh validation follows the fixture corrections. [Original failing CI job](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/587/jobs/0). Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:47 +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/lib-ipc#8
No description provided.