Fix leaf hash slice capacity in AWS/GCP fetchLeafHashes - #1175
Merged
roger2hk merged 1 commit intoSep 14, 2026
Merged
Conversation
AlCutter
approved these changes
Sep 14, 2026
roger2hk
force-pushed
the
fix-migration-slice-capacity
branch
from
September 14, 2026 17:02
e6878e8 to
b39679c
Compare
AlCutter
approved these changes
Sep 14, 2026
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.
The slice holds leaf hashes, not bundles, so preallocate
maxBundles*layout.EntryBundleWidthto match the POSIX implementation.