Open dkey-pugh opened 5 years ago
Thanks @dkey-pugh.
I am not seeing this currently but I know the problem you are talking about. I think it is due to network issues.
I don't think we know that the websocket has died without trying something, and since we were waiting for something to complete, we don't know to try something else.
That would fit with what I am experiencing - I would suggest that an improved handling of the issue would be a 'nice-to-have' but if the trigger is down to the nature of the test instance or exaccerbated by the hosting then that's less of a blocker
Testing on the AWS instance and I am getting the Please Wait spiner covering a system hang or error. In other words, patiently waiting as instructed is pointless and a refresh indicates that the sesson had expired. Is this being used as a stand in error message? It's particularly noticeable testing in Firefox where it is far more frequent than in Chrome but I cannot determine whether this is related to the environment not the browser as such.