-
-
Notifications
You must be signed in to change notification settings - Fork 96
Closed
Description
The the test added in PR #183 , we seem to generate a Float::MAX-style timestamp in src/construction/heuristics/factories.rs:create_insertion_context (notably at problem.goal.accept_route_state(&mut route_ctx))
I think what's going on here is that the lock management code assumes it can build a valid state when finding a valid actor, when ... I think that what should happen is that at one point problem.goal.evaluate(...) gets called to make sure that no other constraints kick in causing something to be invalid.
This seems to be related to the required breaks feature, as removing the break removes the crashing behavior.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels