Cycles spent to create canister, but canister ID was never obtained
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Rust
- Stars
- 204
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
When I was deploying, the deployment was interrupted, the cycles were deducted, but not deployed, one of them did not have a canisterid, and one of them had a canisterid. There is a report of canisterid not found canisterid, and there is another one that I found canisterid through a query, but a 403 error is reported.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the interrupted deployment described in the issue and compare the cases where a canister ID was missing or returned a 403 error. Trace the deployment and canister-ID handling entry points, then confirm that interrupted deployments report a consistent result and preserve the relevant error details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100