forgejo/routers
Gusted 068b80814b [BUG] Make logout event non-blocking
- When people click on the logout button, a event is sent to all
browser tabs (actually to a shared worker) to notify them of this
logout. This is done in a blocking fashion, to ensure every registered
channel (which realistically should be one for every user because of the
shared worker) for a user receives this message. While doing this, it
locks the mutex for the eventsource module.
- Codeberg is currently observing a deadlock that's caused by this
blocking behavior, a channel isn't receiving the logout event. We
currently don't have a good theory of why this is being caused. This in
turn is causing that the logout functionality is no longer working and
people no longer receive notifications, unless they refresh the page.
- This patchs makes this message non-blocking and thus making it
consistent with the other messages. We don't see a good reason why this
specific event needs to be blocking and the commit introducing it
doesn't offer a rationale either.

(cherry picked from commit 9c5c08859d)
2024-08-16 14:21:39 +00:00
..
api Revert "Prevent allow/reject reviews on merged/closed PRs" 2024-08-15 10:47:38 +01:00
common feat(api): implement branch/commit comparison API (#30349) 2024-04-21 11:58:18 +02:00
install Fix wrong error highlighting on install page (#4063) 2024-06-11 19:05:05 +00:00
private enable linter testifylint on v8 (#4573) 2024-07-30 19:41:27 +00:00
utils [PORT] drop utils.IsExternalURL (and expand IsRiskyRedirectURL tests) (#3167) 2024-04-15 13:03:08 +00:00
web [BUG] Make logout event non-blocking 2024-08-16 14:21:39 +00:00
init.go s/Gitea/Forgejo in various log messages and comments 2024-04-21 21:26:15 +05:00