client: don't time out long logins, report login progress#17
Open
peterzen wants to merge 1 commit into
Open
Conversation
The first login after startup connects wallets and DEX servers synchronously in the /api/login handler, which can outlast the HTTP server's 2-minute WriteTimeout. When that happened, login completed server-side but the response carrying the auth cookie was cut off, leaving the user stuck on the unlock screen until a hard refresh. Clear the write deadline for the login response so it always arrives. Also report finer-grained login progress through the existing LoginNote pipe: per-item completion counts for wallets and DEX servers, plus a periodic note naming the wallets or servers a slow login is still waiting on, so the unlock screen shows what is actually happening. If the websocket drops while the login request is pending, the login form now flags the displayed status as possibly stale.
There was a problem hiding this comment.
Pull request overview
This PR fixes a long-login edge case where the first post-startup login can exceed the webserver write timeout, preventing the auth cookie from reaching the browser. It also improves UX during slow logins by emitting granular progress notes and signaling when displayed login status may be stale due to a websocket disconnect.
Changes:
- Clear the HTTP response write deadline for the login endpoint to ensure the auth cookie is delivered even if login work takes a long time.
- Add a
loginProgresshelper in Core to emit per-item completion counts and periodic “waiting on …” notes during wallet and DEX connection phases. - Update the login form UI to append/remove a “connection lost” hint on websocket close/open while a login request is in flight.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| client/webserver/site/src/js/forms.ts | Adds websocket close/open handlers during login to flag potentially stale progress text. |
| client/webserver/api.go | Clears the login response write deadline to avoid cutting off auth cookie delivery on long logins. |
| client/core/core.go | Introduces structured login progress reporting for wallet/DEX connection phases via login notes. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses the long-standing stuck-unlock-screen issue (upstream decred#3031): the first login after startup connects wallets and DEX servers synchronously in the login handler, which could outlast the HTTP server's 2-minute write timeout — login completed server-side but the auth cookie never reached the browser, leaving the user stuck until a hard refresh.