Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reload the browser when the circuit ID is unknown

See original GitHub issue

If I launch a components app with dotnet watch run - the reconnection feature doesn’t ever seem to do its thing.

I can retry, and it will successfully connect (see console output) - but it never updates the UI.

My guess is that this happens because the circuit is gone - it’s a new process after all. We should see if we can improve this for inner loopness, and figure out a better experience by default for the case where the circuit is gone.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:14 (11 by maintainers)

Top GitHub Comments

10reactions

danroth27commented, Apr 12, 2019

We discussed this and we think it would help that if the circuit ID is unknown we reload the page.

4reactions

TanayParikhcommented, Dec 8, 2021

Duplicated https://github.com/dotnet/aspnetcore/issues/38305 against this issue. Thread summary is there are concerns with the existing documented approach as it overrides the existing reconnection behavior.

We may want to consider adding additional doc details on the reconnection behavior or provide alternate reconnection configurability (or automatic reloads).