-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move timeout and progress reports to Simulation #1028
base: master
Are you sure you want to change the base?
Conversation
c858c27
to
fb8d00a
Compare
@nfi Added the commit that migrates the progress report to this PR. It's the last set timeout that should get precedence. I'm not sure what decides the order. |
I get an exception when I deactivate and then reactivate a simulation script:
|
fb8d00a
to
62e9c95
Compare
Fixed in latest update. |
If you run a simulation until timeout, and then reload the simulation, the new simulation will immediately timeout without running anything. Also, it is no longer possible to continue running a simulation after first timeout. |
62e9c95
to
655fa22
Compare
Fixed. |
655fa22
to
8a8b235
Compare
Add a method that gets the time of the first scheduled item in the queue.
8a8b235
to
cd0e082
Compare
This moves the code for handling timeouts from LogScriptEngine to Simulation.
This removes the duplicate progress reports when using multiple script engines.
cd0e082
to
e806f49
Compare
This moves the code for handling timeouts
and progress reports from LogScriptEngine to Simulation.