Frontend: a request without an answer no longer signs people out - #810
Merged
Merged
Conversation
A Mac woke from sleep before its network was back; the session check failed with Safari's 'Load failed' and the app deleted the saved session and sent the user to /login, offline, where the page fell into the global error screen. Only a 4xx from the backend now ends the session; on no answer or a 5xx the session is kept and re-checked when the browser is back online. The error boundaries recognise network failures, report them as warnings and reload the page by themselves once the connection returns. Fixes ANYTHINGMCP-CLOUD-FRONTEND-7
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ANYTHINGMCP-CLOUD-FRONTEND-7 (
TypeError: Load failed, Safari on a Mac): the breadcrumbs show every request failing at once at 16:56:19, the laptop's network not being there. The session check on/api/users/metreated that as a rejected token: it deleted the saved session and pushed the user to/loginwhile offline, and 12 s later the page fell into the global error screen.onlineevent. A real 401 still signs out throughAUTH_EXPIRED_EVENT.Load failed,Failed to fetch, chunk load errors) say "Connection lost", are reported as warnings withnetwork: yes, and reload the page by themselves once the connection is back (at most once per 30 s, so nothing can loop).Fixes ANYTHINGMCP-CLOUD-FRONTEND-7