setupCanister with targetCanisterId
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 35
- Forks
- 6
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Creating two canisters with specific targetCanisterId's results in error when one of them tries to call the other "Canister ... doesn't exist"
pic-js docs specify "The Id of the canister to create. Can only be used on Bitcoin, Fiduciary, II, SNS and NNS subnets."
Does that mean I have to load the NNS state, so we can have a Feduciary subnet where canisters can be installed and then the above scenario will not result in errors?
Contributor guide
No contributing guide indexed for this repository
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 two-canister setup described in the issue, using specific targetCanisterId values and the cross-canister call. Read the pic-js setupCanister documentation and compare its subnet and state requirements with the observed error. Done means the supported configuration or required setup is confirmed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100