You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8bbb787
Browse filesBrowse the repository at this point in the historyBrowse files
Fix qc throttling and 'session expired': Bearer auth for events, no refresh storm (0.5.1, qc 0.4.2) (#284)
- authenticateRequest's token client called setSession() with an empty
refresh token, which auth-js rejects, so every Bearer request through it
(qc's /api/events) was a 401. Use a client carrying the Authorization
header and getUser(token).
- qc reconnected /api/events on 401 straight after a refresh with no
backoff, rotating refresh tokens in a tight loop (GoTrue logged several
per 60ms) until the session died. Now one refresh per rejection, then stop.
Parallel 401s share one refresh; a stale-token 401 just retries.
- qc waits out 429s (Retry-After, which the middleware now sends).
- The TUI no longer loads 40 chats on start to join their live rooms: the
events stream joins all of the user's conversations on connect.
- Closing one SSE connection no longer drops the user from every room while
another of their connections is open.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: packages/qryptchat/package.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
{
2
2
"name": "@profullstack/qryptchat",
3
-
"version": "0.4.1",
3
+
"version": "0.4.2",
4
4
"description": "qc: qrypt.chat in your terminal. A full-screen end-to-end encrypted chat client (ML-KEM-1024), plus a scriptable CLI and an MCP server.",
0 commit comments