-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
imagepruning: temporarily disable event handling #87
Conversation
…til ansible updates
@sjenning you probably want to revert this and find the real wiring problem
… doesn't need the answer
Underlying gonum/graph assigns conflicting IDs to new nodes after node deletion. Thus two different nodes amy be assigned the same ID. This leads to panic when an edge is set between them. Temporarily disabling event handling until the package is fixed. This ensures that no new nodes will be added to the graph after the first node gets removed. Signed-off-by: Michal Minář <[email protected]>
ed3cecd
to
d206b32
Compare
That doesn't seem unreasonable. Are we retaining handles to node ids somewhere other than edges maintained by the graph? |
We take references to whole nodes and keep them until the end. I don't see how that should prevent us from connecting newly added nodes once a single node is deleted from the graph (which is modifiable and allows for node removals). |
There's a unit test you'll need to remove too. |
Yes, sorry about that. Here's updated commit: miminar@706c1b3 |
Underlying gonum/graph assigns conflicting IDs to new nodes after node
deletion. Thus two different nodes amy be assigned the same ID. This
leads to panic when an edge is set between them.
Temporarily disabling event handling until the package is fixed. This
ensures that no new nodes will be added to the graph after the first
node gets removed.