Add retries when initial connection fails

[pranavkm]

In this particular case, the client failed to connect with Error: WebSocket closed with status code: 1006. The recommendation here is to collect server logs. Unfortunately the linked build is old and deleted, so we no longer have any logs to look at.

Given that the Blazor auth tests appear to continue running just fine and this test works locally, the change I have:

a) Adds some retries in case the browser is unable to establish the SignalR connection
b) Change the connection detection to be more robust than tossing in a delay.

[BrennanConroy]

Idk any details about this. How long does a browser refresh take? Is this just because the server takes some time to get setup? If so, is there a way to wait for the server to be ready before trying to connect?

[pranavkm]

Here's the logs that we have

[2020-03-25T23:29:57Z] [Info] https://localhost:50863/_framework/blazor.server.js 0:5359 "[2020-03-25T23:29:57.084Z] Information: Normalizing '_blazor' to 'https://localhost:50863/_blazor'."
[2020-03-25T23:30:02Z] [Info] https://localhost:50863/_framework/blazor.server.js 0:5359 "[2020-03-25T23:29:57.505Z] Information: WebSocket connected to wss://localhost:50863/_blazor?id=wXSTzHmh9YZV4R9olS75zQ."
[2020-03-25T23:30:06Z] [Severe] https://localhost:50863/_framework/blazor.server.js 0:5162 "[2020-03-25T23:30:03.278Z] Error: Connection disconnected with error 'Error: WebSocket closed with status code: 1006 ().'."

It's not entirely clear why this was closed. The server should be running because we wouldn't have attempted to establish a SignalR connection without first getting the pre-rendered content.