Backport "Snapshot txMeta without cloning history (#8363)" #8458
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
Gudahtt
force-pushed
the
backport-snapshot-tx-meta-without-cloning-history
branch
from
f0ae6ef
to
c59fd71
Compare
Builds ready [c59fd71]
|
Backport #8363 to v7.7.9. Note that this uses `clone` instead of `cloneDeep`, because `clone` hadn't yet been replaced by `cloneDeep` on `master`. Backporting that change as well would have been very disruptive, so I've updated this to use `clone` instead to minimize conflicts. It is functionally equivalent.
Gudahtt
force-pushed
the
backport-snapshot-tx-meta-without-cloning-history
branch
from
c59fd71
to
fea5106
Compare
Builds ready [fea5106]
|
whymarrh
approved these changes
Apr 29, 2020
Merged
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.
Backport #8363 to v7.7.9. Note that this uses
cloneinstead ofcloneDeep, becauseclonehadn't yet been replaced bycloneDeeponmaster.Backporting that change as well would have been very disruptive, so I've updated this to use
cloneinstead to minimize conflicts. It is functionally equivalent.