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
I think the issue title is slightly off, since it refers to max twice, rather than min and max.
But setting that aside, this is annoying, I agree. But the problem is one of atomicity. Without the following max_tracelength statement, the first would put the system in a state that violated the invariant max_tracelength >= min_tracelength. Forge doesn't do lookahead, and there's not at present a way to make atomic changes to multiple options at once. I'm happy to take suggestions, though.
bennn
changed the title
Temporal forge needs max_tracelength to be set before max_tracelength
Temporal forge needs max_tracelength to be set before min_tracelengthNov 5, 2024
Temporal Forge code:
Error message:
The text was updated successfully, but these errors were encountered: