feat: enable asynchronous canister creation with subnet ID in the URL#9982
Merged
Conversation
eichhorl
reviewed
Apr 23, 2026
Contributor
eichhorl
left a comment
eichhorl
left a comment
There was a problem hiding this comment.
The PR title doesn't seem to match the changes
Contributor
Author
What I meant to say is that this PR is needed if the synchronous update call endpoint /api/v4/subnet/.../call returns 202 and thus the user needs to process the update call (to create canister as nothing else is allowed on /api/v4/subnet/.../call) asynchronously (by polling /api/v3/subnet/.../read_state for the /request_status). |
eichhorl
approved these changes
Apr 23, 2026
alin-at-dfinity
approved these changes
Apr 23, 2026
This reverts commit c287538.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR enables to retrieve the status of an (asynchronous) update call via the (existing) public HTTP endpoint
/api/v3/subnet/<effective_subnet_id>/read_stateon the replica. It is specified in this PR.In more detail, this PR is needed if the synchronous update call endpoint
/api/v4/subnet/.../callreturns 202 and thus the user needs to process the update call (to create canister as nothing else is allowed on/api/v4/subnet/.../call) asynchronously (by polling/api/v3/subnet/.../read_statefor the/request_status/...).