After :closeing a study, the frontend requests the /projects to populate the dashboard. Before receiving the response, the websocket might have notified the frontend that the study was closed, but the response of the previous request might say that it is still closing. Since there won't be any new websocket message updating the state of the closed study, the study card in dashboard will remain locked.
This PR workarounds that by asking one more time what the state of the project is if the latest state is closing
What do these changes do?
After
:close
ing a study, the frontend requests the/projects
to populate the dashboard. Before receiving the response, the websocket might have notified the frontend that the study was closed, but the response of the previous request might say that it is still closing. Since there won't be any new websocket message updating the state of the closed study, the study card in dashboard will remain locked.This PR workarounds that by asking one more time what the state of the project is if the latest state is
closing
Related issue/s
How to test
Dev-ops checklist