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
thread 'main' panicked at .cargo/registry/src/index.crates.io-6f17d22bba15001f/spade-2.11.0/src/cdt.rs:882:17:
assertion `left != right` failed
left: []
right: []
stack backtrace:
0: rust_begin_unwind
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:652:5
1: core::panicking::panic_fmt
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:72:14
2: core::panicking::assert_failed_inner
3: core::panicking::assert_failed
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:363:5
4: spade::cdt::ConstrainedDelaunayTriangulation<V,DE,UE,F,L>::add_splitting_constraint_edge_fallback
at .cargo/registry/src/index.crates.io-6f17d22bba15001f/spade-2.11.0/src/cdt.rs:882:17
5: spade::cdt::ConstrainedDelaunayTriangulation<V,DE,UE,F,L>::try_add_constraint_inner
at .cargo/registry/src/index.crates.io-6f17d22bba15001f/spade-2.11.0/src/cdt.rs:834:13
6: spade::cdt::ConstrainedDelaunayTriangulation<V,DE,UE,F,L>::add_constraint_and_split
at .cargo/registry/src/index.crates.io-6f17d22bba15001f/spade-2.11.0/src/cdt.rs:1140:9
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
The text was updated successfully, but these errors were encountered:
Thanks for sharing! I've got the feeling that this is going to take a few more iterations until it's completely crash free.
Please keep in mind removing the assertion will remove the crash but may result in an incorrect triangulation (more specifically: The edges may not be connected with constraints in a way that you would expect). Remove it on your own risk 😁
After the 2.11 release, I have this assertion panicking
spade/src/cdt.rs
Lines 880 to 882 in 442fd2e
If I remove it, everything seems to work as expected
This time it's with
f64
🙂The text was updated successfully, but these errors were encountered: