Skip to content

fix: don't change graph on incorrect call to tmp_remove_nodes#266

Open
vincentkoppen wants to merge 4 commits into
mainfrom
pgm/crash_on_tmp_remove
Open

fix: don't change graph on incorrect call to tmp_remove_nodes#266
vincentkoppen wants to merge 4 commits into
mainfrom
pgm/crash_on_tmp_remove

Conversation

@vincentkoppen
Copy link
Copy Markdown
Member

@vincentkoppen vincentkoppen commented Jun 1, 2026

If tmp_remove_nodes was called with a non-existing node, this could change the graph afterwards.
This PR fixes that by always keeping track of the which nodes are removed and then always restoring these (and the relevant edges)

PS: review is probably easiest with "hide whitespaces" on for the tests, since I introduced a class for the tmp_remove_nodes tests and github doesn't generate a nice diff unfortunately

Signed-off-by: Vincent Koppen <vincent.koppen@alliander.com>
Signed-off-by: Vincent Koppen <vincent.koppen@alliander.com>
Signed-off-by: Vincent Koppen <vincent.koppen@alliander.com>
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 1, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant