Fixes #2104 Add Simulation Queue Position Display to Simulations Page #2624
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR Fixes #2104 by adding a queued label and queue position display to the Simulations page, addressing issue #2104. The motivation is to provide users with clear feedback on their simulation's status in the processing queue, rather than showing all queued jobs as "computing." This improves transparency and user experience by indicating both the queue position and when a simulation is actively calculating.
Changes
Updated the Simulations page to display:
Tests
Manually verified the following cases in the UI:
Simulations with queue_position > 0 display "POSITION IN QUEUE: X" (orange tag) in the status column and the correct number in the Queue Position column.
Simulations with queue_position === 0 display "CALCULATING" (blue tag) in the status column and 0 in the Queue Position column.
Simulations with no queue_position display "CALCULATING" (blue tag) in the status column and a dash ("—") in the Queue Position column.
Completed and errored simulations display the correct status and a dash in the Queue Position column.
Screenshots
Note: I am not aware of what data values to enter into the simulation, so I test all possibilities in the UI, not hardcoded, so if you can guide me through this to make sure it is working properly.