mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 14:15:50 +03:00
[PR #163] [MERGED] 162 login fails if user data exists in database #303
Labels
No labels
bug
bug
client
design
documentation
feature
feature
infrastructure
pull-request
ready for development
server
server
spike
technical work
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Stagnum#303
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/EddieTheCubeHead/Stagnum/pull/163
Author: @EddieTheCubeHead
Created: 4/1/2024
Status: ✅ Merged
Merged: 4/1/2024
Merged by: @EddieTheCubeHead
Base:
master← Head:162-login-fails-if-user-data-exists-in-database📝 Commits (3)
e543023162 login fails if user data exists in databasea7fa058162 remove wip mark6dfc39c162 Relax timing-related assert📊 Changes
3 files changed (+41 additions, -17 deletions)
View changed files
📝
server/src/database/entities.py(+1 -1)📝
server/test/auth_features/auth_login_callback_features.py(+39 -15)📝
server/test/pool_features/playback_features.py(+1 -1)📄 Description
Created a test to reproduce the problem, fixed the problem by updating cascade rules for relationship
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.