[BUG] Dependency setup can promote an untracked nested source to its ancestor checkout #106

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

Summary

Dependency setup can promote an untracked nested source to its ancestor checkout. Maintained validation cannot reach its intended successful boundary.

Reproduction

Place an independent Cargo source archive without Git metadata inside an ignored or untracked directory of another genuine checkout. Pass the archive directory to the maintained dependency-setup entry point. Compare the selected repository root and manifests with the explicit input. 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. validate_repository_sources can resolve the ancestor Git root and scan that checkout rather than the explicitly selected archive. With no Git boundary at all it falls back to raw directory input. This can validate the wrong source graph or fail later against unrelated pins; it does not establish the requested source identity.

Environment and identity

  • Component repository/revision and Integration source graph: original integration 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

Require a real Git boundary, and admit a nonroot package only when its exact Cargo.toml is tracked by that boundary. Preserve actual repository roots and legitimately tracked nested packages. Add genuine Git positive and ignored/untracked/non-Git negative fixtures without synthetic dependency revisions or source substitutions. Initial consumer attempts with invalid archive boundaries are preserved as validation-driver failures, not compiler results.

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 Dependency setup can promote an untracked nested source to its ancestor checkout. Maintained validation cannot reach its intended successful boundary. ## Reproduction Place an independent Cargo source archive without Git metadata inside an ignored or untracked directory of another genuine checkout. Pass the archive directory to the maintained dependency-setup entry point. Compare the selected repository root and manifests with the explicit input. 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. validate_repository_sources can resolve the ancestor Git root and scan that checkout rather than the explicitly selected archive. With no Git boundary at all it falls back to raw directory input. This can validate the wrong source graph or fail later against unrelated pins; it does not establish the requested source identity. ## Environment and identity - Component repository/revision and Integration source graph: [original integration source](https://git.erikinkinen.fi/erix/integration/commit/9e6b0997fabd1bdbe462cf28c151f39ee0e382cf), [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 Require a real Git boundary, and admit a nonroot package only when its exact Cargo.toml is tracked by that boundary. Preserve actual repository roots and legitimately tracked nested packages. Add genuine Git positive and ignored/untracked/non-Git negative fixtures without synthetic dependency revisions or source substitutions. Initial consumer attempts with invalid archive boundaries are preserved as validation-driver failures, not compiler results. 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:39:17 +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#106
No description provided.