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"}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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:
Expected:
Actual:
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
@ellite commented on GitHub (Feb 5, 2025):
After clearing the cookies and reloading the page, the issue went away.