Bump avalanchego to v1.10.6-rc.4 #293
Merged
Conversation
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
darioush
approved these changes
Aug 1, 2023
StephenButtolph
approved these changes
Aug 1, 2023
darioush
pushed a commit
that referenced
this pull request
Apr 25, 2024
* Bump avalanchego to v1.9.0 * go * Update go.mod
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.
This PR bumps AvalancheGo dependency to use v1.10.6-rc.4 and updates the cache sizes used by the chain state cache to use the new sized LRU cache to limit the total memory allocated to the cache based off of bytes size (limited to a total of 20MB) as opposed to a specific number of blocks.
Since AvalancheGo imports Coreth, it will replace the version of AvalancheGo imported by Coreth with the actual current code when it's compiled. As a result, since AvalancheGo has switched to inputting sizes based off of the total memory taken up by these caches instead of the number of elements, we need to update the sizes for the AvalancheGo release.
Otherwise, the chain state cache will go from allocating 100/50/50 elements to the respective caches to allocating that number of bytes to each of those caches, which will end up being zero total blocks.