Improve Blazor reconnection experience after the server is restarted#8
Conversation
…flect change in ResumeCircuit
🤖 Augment PR SummarySummary: Improves the Blazor Server reconnection experience when the server is restarted or circuit state is unavailable, so clients can recover more gracefully. Changes:
Technical Notes: The E2E scenario disables both reconnection cache and circuit persistence so a disconnected client is expected to be rejected and recover via retry/reload behavior. 🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
| } else { | ||
| this.reloadButton.style.display = 'none'; | ||
| this.rejoiningAnimation.style.display = 'none'; | ||
| this.status.innerHTML = 'The session has been paused by the server.'; |
There was a problem hiding this comment.
In the graceful-pause flow, show({ type: 'pause' }) still sets rejoiningAnimation to display = 'block', and update no longer hides it for the 'pause' case. This can leave the “rejoining” animation visible while showing the paused text/button, which seems like an incorrect UI state.
🤖 Was this useful? React with 👍 or 👎
| // The circuit state cannot be retrieved. It might have been deleted or expired. | ||
| // We do not send an error to the client as this is a valid scenario | ||
| // that will be handled by the client reconnection logic. | ||
| Log.InvalidInputData(_logger); |
There was a problem hiding this comment.
This branch is now treated as a valid/expected scenario (no client error, no abort), but it still logs via Log.InvalidInputData. That may be misleading/noisy operationally (e.g., looks like bad client input rather than a normal “state expired/evicted” case).
🤖 Was this useful? React with 👍 or 👎
2 participants
Benchmark PR from qodo-benchmark#32