feat(nns): support reserved_cycles_limit in canister settings proposals - #11173
Draft
Rachit2323 wants to merge 1 commit into
Draft
feat(nns): support reserved_cycles_limit in canister settings proposals#11173Rachit2323 wants to merge 1 commit into
Rachit2323 wants to merge 1 commit into
Conversation
…d CreateCanisterAndInstallCode proposals
Contributor
Contributor
|
Heads up — CI Main is failing on this commit with a real compile error caused by this change:
Adding Generated by Claude Code |
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
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.
The problem
Every canister has a setting called "reserved cycles limit" - basically a cap on how many cycles it's allowed to keep in reserve. You can already change almost every other canister setting through an NNS vote (who controls it, memory limits, etc), but not this one. The code had it hardcoded to "off," with a comment saying it wasn't supported yet.
What I did
Hooked this setting up the same way the existing settings already work, following the same pattern used for a similar setting called wasm_memory_threshold:
Testing