Skip to content

feat(ccu): add direct install planning - #74

Draft
Kur0x wants to merge 3 commits into
codex/ccu-stack-02-driverfrom
codex/ccu-stack-03-install
Draft

feat(ccu): add direct install planning#74
Kur0x wants to merge 3 commits into
codex/ccu-stack-02-driverfrom
codex/ccu-stack-03-install

Conversation

@Kur0x

@Kur0x Kur0x commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • add repository and launch-package ownership
  • add provider and install-provider transaction handling
  • add lower-layer endpoint/resource plan construction and rollback coverage

Stack

3 of 9. Depends on codex/ccu-stack-02-driver.

Validation

  • git diff --check
  • clean-archive focused install, launch-package, lower-layer, provider, and repository tests
  • 96 tests passed; 53 runtime/CANN-dependent tests skipped at this stack layer

Scope

No communicator integration or direct submission path is enabled here.

if (TileXRCcuBuildInstallEvidence(nextReport, evidence) != TILEXR_SUCCESS) {
return TILEXR_ERROR_INTERNAL;
}
return lowerLayerRet;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repository install has already succeeded here and request.repositoryReceipt owns its device allocation. Returning on the lower-layer failure leaves a failed operation with a live receipt, which callers can reasonably skip releasing and then leak on retry. Please roll back with TileXRCcuReleaseRepositoryInstallReceipt (including rollback-error reporting), or make failure ownership and recovery explicit in the API contract.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants