Skip to content

site: Logging out of the dashboard immediately throws an "unexpected application error" when using the Go backend (including production) #13130

Closed
@Parkreiner

Description

@Parkreiner

Turning this into an issue for documentation purposes. I'm dropping everything and working on this now, and gunning to have this done by end of day

Updates

  • I think I got this figured out – when we started trying to embed more and more data into the HTML to speed up queries, we didn't update all the query logic to account for the fact that even when we log out, there's still going to be user data in the HTML
    • None of the unit tests caught this because the metadata doesn't exist in the JS runtime – it only exists when we're actually serving files through the Go backend

Steps to reproduce

  1. Log into Coder via Google OAuth (I'm using Coder Dogfood)
  2. Click the user icon in the top-right corner
  3. Click "Sign out"
  4. Immediate "Unexpected application error" based on permissions being unavailable

Video

Screen.Recording.2024-05-02.at.9.17.04.AM.mov

Notes

  • As far as I can tell, this is strictly an issue on the UI side. The log out request is correctly going through, but the UI isn't syncing correctly afterwards

Metadata

Metadata

Assignees

Labels

s2Broken use cases or features (with a workaround). Only humans may set this.siteArea: frontend dashboard

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions