NASA-AMMOS
ResumableSimulationDriver behavior when inserting a task between curTime and batch.offsetFromStart()
Checked for duplicates
Yes - I've already checked
Is this a regression?
No - This is a new bug
Version
develop
Describe the bug
Discussion about this originated in https://github.com/NASA-AMMOS/aerie/pull/1051#discussion_r1285081166
The behavior of the ResumableSimulationDriver should be changed to account for the case where a task is inserted between the current time of the simulation and the start time of the next batch of activities (think daemon tasks).
See this quote from @Mythicaeda
What about with daemon tasks? Ie: Let's say that curTime is 10hrs, and that batch is a daemon task that's going to run at 12hrs. The next activity that is placed is at 11hrs. That would give us a task that's been placed between curTime and batch.offsetFromStart.
No one has ever seen this behavior impact anything but it could happen and we should investigate.
Reproduction
This needs reproduction.
Logs
No response
System Info
N/A
Severity
Moderate
