github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 21:59:09 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #162] [Bug] Not possible to logout #3260

New Issue
Closed
opened 2026-04-20 07:10:58 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 07:10:58 -05:00
Owner
Copy Link

Originally created by @ellite on GitHub (Feb 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/162

Beta 12 (not sure if it affectied previous versions)

Steps to reproduce:

  • Open Pangolin
  • Click the user drowpdown next to your email on the top left
  • Click on logout

Expected:

  • I'm now logged out and see the login screen

Actual:

  • I'm now on the organization selection screen and see the error message: "Error logging out / Failed to logout"

From the network panel I can see this response from the logout endpoint

{"data":null,"success":false,"error":true,"message":"Failed to log out","status":500,"stack":null}

From docker compose logs -f

pangolin  | 2025-02-05T15:42:55.280Z [error]: FOREIGN KEY constraint failed
pangolin  | Stack: SqliteError: FOREIGN KEY constraint failed
pangolin  |     at PreparedQuery.run (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:66:22)
pangolin  |     at QueryPromise.resultCb (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:43:64)
pangolin  |     at QueryPromise.execute (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:12:17)
pangolin  |     at QueryPromise.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17)
pangolin  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {"code":"SQLITE_CONSTRAINT_FOREIGNKEY"}
Originally created by @ellite on GitHub (Feb 5, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/162 Beta 12 (not sure if it affectied previous versions) Steps to reproduce: - Open Pangolin - Click the user drowpdown next to your email on the top left - Click on logout Expected: - I'm now logged out and see the login screen Actual: - I'm now on the organization selection screen and see the error message: "Error logging out / Failed to logout" From the network panel I can see this response from the logout endpoint `{"data":null,"success":false,"error":true,"message":"Failed to log out","status":500,"stack":null}` From docker compose logs -f ``` pangolin | 2025-02-05T15:42:55.280Z [error]: FOREIGN KEY constraint failed pangolin | Stack: SqliteError: FOREIGN KEY constraint failed pangolin | at PreparedQuery.run (file:///app/node_modules/drizzle-orm/better-sqlite3/session.js:66:22) pangolin | at QueryPromise.resultCb (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:43:64) pangolin | at QueryPromise.execute (file:///app/node_modules/drizzle-orm/sqlite-core/session.js:12:17) pangolin | at QueryPromise.then (file:///app/node_modules/drizzle-orm/query-promise.js:21:17) pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {"code":"SQLITE_CONSTRAINT_FOREIGNKEY"} ```
GiteaMirror commented 2026-04-20 07:11:00 -05:00
Author
Owner
Copy Link

@ellite commented on GitHub (Feb 5, 2025):

After clearing the cookies and reloading the page, the issue went away.

<!-- gh-comment-id:2637329313 --> @ellite commented on GitHub (Feb 5, 2025): After clearing the cookies and reloading the page, the issue went away.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#3260
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?