fix: lazy_update_boundary_heights needs to handle uninitialized memory#2286
Merged
Conversation
a1e4711 to
3a4b51f
Compare
3a4b51f to
8a3d757
Compare
This comment has been minimized.
This comment has been minimized.
shuklaayush
approved these changes
Nov 30, 2025
This comment has been minimized.
This comment has been minimized.
shuklaayush
approved these changes
Nov 30, 2025
…al accesses" This reverts commit 8a3d757deaf7f5b6c6f21ac16aa710a40eb79d52.
42f0e0d to
a35cd12
Compare
lazy_update_boundary_heights needs to handle large initial accesseslazy_update_boundary_heights needs to handle uninitialized memory
Commit: a35cd12 |
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.
towards INT-5617
The metering update did not account for the initial 8->4 split from
handle_uninitialized_memory