Correct instructions to rehash nodes after migration #6028
Merged
Conversation
This file contains 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
After a migration that can affect the hash of the migrated node, the instructions to rehash the node are provided. However, these instructions are currently incorrect and likely to lead to confusion for the user. Here the instructions are corrected both when a specific entry point requires rehashing or not.
|
I think we agreed once it was my fault for always testing your code too diligently. 😉 |
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.
Fixes #6027
After a migration that can affect the hash of the migrated node, the instructions to rehash the node are provided. However, these instructions are currently incorrect and likely to lead to confusion for the user.
Here the instructions are corrected both when a specific entry point requires rehashing or not.