Bug Description:
Polling needs to become more sophisticated. The motivation behind this issue is we want speed, so we send many requests until we get the status response "All Complete." The problem that arises is responses are not guaranteed to return in the same order they were sent out, so a "Minimizing" status can get hung up somehow and return after we progress to "2 of 3" or "All Complete".
To Reproduce:
This existing ticket already describes how to reproduce this issue. The bug it describes doesn't occur anymore, but if you watch the status field while you wait, you will see conformers advance, and then return to "minimizing" when they really should not.
Expected behavior
Once we advance past "minimizing" or any status, really, we should not move backward. Add logic to make sure laggard responses are just ignored.
Tool: CB Downloads polling logic
Bug Description: Polling needs to become more sophisticated. The motivation behind this issue is we want speed, so we send many requests until we get the status response "All Complete." The problem that arises is responses are not guaranteed to return in the same order they were sent out, so a "Minimizing" status can get hung up somehow and return after we progress to "2 of 3" or "All Complete".
To Reproduce: This existing ticket already describes how to reproduce this issue. The bug it describes doesn't occur anymore, but if you watch the status field while you wait, you will see conformers advance, and then return to "minimizing" when they really should not.
https://github.com/GLYCAM-Web/website/issues/119
Expected behavior Once we advance past "minimizing" or any status, really, we should not move backward. Add logic to make sure laggard responses are just ignored.