Fix for extra transactions & nodes appearing after destroy all composites#2389
Draft
andromeda-224 wants to merge 1 commit into
Draft
Fix for extra transactions & nodes appearing after destroy all composites#2389andromeda-224 wants to merge 1 commit into
andromeda-224 wants to merge 1 commit into
Conversation
|
|
This pull request is stale because it has been open for 6 months with no activity. Consider reviewing and taking an action on this pull request. |
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.




Prerequisites
Reviewed the checklist
Reviewed feedback from the "Sonar Cloud" bot. Note that you have to wait
for the "CI / Unit Tests") to complete first. Failed Unit tests can be
debugged by adding the label "verbose logging" to the GitHub PR.
Description of the Change
The change is allow a flag from composite expand/contract functions to filter through to addTransaction and to not swap the source and destination when source id is higher than destination id for undirected transactions when the call comes from compositing.
Alternate Designs
Why Should This Be In Core?
Benefits
Possible Drawbacks
Verification Process
Extra transactions & nodes test:
Steps for merge nodes issue:
Steps for importing directed and undirected transactions:
rc2test_4_250825.csv
Steps to copy & paste and undo:
Applicable Issues