Skip to content

Crash when using a required break and relations #182

@rtpg

Description

@rtpg

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions