We encountered a binary that caused a panic due to insertLabeledEdge returning Nothing.
It seems like this could happen in one of two cases:
The source or the destination vertex doesn't exist
An edge between source and destination already exists
By using replaceLabeledEdge instead, we can avoid panicking in the second case where refinement execution can proceed without issue.
However, it would be nice to make sure that the appearance of a parallel edge isn't an indicator of a larger issue in the algorithm, or if using replaceLabeledEdge is a good enough fix.
We encountered a binary that caused a panic due to
insertLabeledEdge
returningNothing
. It seems like this could happen in one of two cases:By using
replaceLabeledEdge
instead, we can avoid panicking in the second case where refinement execution can proceed without issue. However, it would be nice to make sure that the appearance of a parallel edge isn't an indicator of a larger issue in the algorithm, or if usingreplaceLabeledEdge
is a good enough fix.