You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have discovered 2 rough edges in fix_topology() (actual 1 in induce_nodes() and 1 in remove_false_nodes()withinfix_topology()) that can lead to improper identification of loop endpoints that in turn can lead to incorrect topology. Both fixes are currently in the GH20_nodes_tests_fix_topology and tests are passing locally (macOS 14).
CI suite failing on 5/6 FUA, seemingly with only very minor differences.
Relavent chunks for the fixes here in induce_nodes() and here in remove_false_nodes().
Still need to add tests
I can either roll this stuff into #67 or make a fresh PR for it once #67 is merged.
jGaboardi
changed the title
potential for fix_topology() to actually break topology
current loop logic breaks topology in certain scenarios
Oct 29, 2024
Within:
nodes.induce_nodes()
nodes.remove_false_nodes()
see below
Putting this here from Discord:
xref #68
The text was updated successfully, but these errors were encountered: