fix: Use None instead of 0 if no compute allocation is specified#601
Merged
fix: Use None instead of 0 if no compute allocation is specified#601
Conversation
dsarlis
changed the title
hansl
approved these changes
Apr 28, 2020
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
2 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.
Based on the thread in #596 it was concluded that it's better to use
Noneinstead of using some default value for optional arguments to canister install (like compute and memory allocation) on the dfx side. This means that if these arguments are not set explicitly, they will not be included in the request sent to the "system" at all and it's up to the "system" to use the default values for them per public spec.The current PR makes the change for the compute allocation.