Fix NodeUpdateTransaction always updating node zero (0.120) #10135
+47
−18
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.
Description:
Cherry pick of #10134 to
release/0.120
.createdTimestamp
if it's missing and an inner transaction. This is because nodes erroneously sent us updates instead of creates when migrating state.NodeUpdateTransaction
updating the wrong nodeNodeDeleteTransaction
deleting the wrong nodeRelated issue(s):
Fixes #10133
Notes for reviewer:
Checklist