2 Commits

Author	SHA1	Message	Date
Maikel Linke	d9c296cdb3	Stabilise flaky report specs ... It looks like we have a new race condition that may only be a problem in specs. If you trigger one report, it displays via websockets and then you trigger the next report, there may still be some Javascript active that displays the first report while the second one is loading. I'm not sure if users would navigate that fast though. To minimise the problem, I adjusted the polling to leave more room for the default websockets response.	2024-08-16 17:08:57 +10:00
Maikel Linke	23aa762be2	Add fallback report loading in case websockets fail ... This also resolves a race condition scenario. Even if the report gets rendered via websockets before the controller response is rendered then the fallback script loads the report again. It's not the most beautiful but probably okay until we replace websockts altogether. I'm leaving websockets in at the moment because it can render the report much quicker than polling can.	2024-08-16 15:24:34 +10:00