Bug #21925
Updated by Peter Amstutz 5 months ago
fetchProcessProgressBarStatus triggers hundreds of times, when it is only supposed to trigger periodically. Example: https://workbench.tordo.arvadosapi.com/processes/tordo-xvhdp-bd68mbek1to5upj Open the network debugger, and you'll see hundreds of requests in a short period of time. Once loading is finished and it knows the state of the container, it does seem to stop doing it. requests. I believe this is affecting Cypress tests for the process panel, by slowing things down and also re-rendering continuously which causes cy.waitForDom() to time out. Stephen says: "Ah, I added the process resource object to the dependency array of the useeffect triggering reloading the stats so it reloads it every time the resource gets modified during loading"