Data Recovery Request: Account deletion bug caused by silent merge (Recovery Email
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.5k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Description
Description of the Issue
I am reporting a critical account logic bug that led to the loss of 3 months of research data. I am currently stuck in an infinite 404/Login loop.
How the bug happened
- I have a primary Google account. My QQ email is set as the "Recovery Email" for this Google account.
- Due to persistent captcha issues, I tried to test a "new" account using my QQ email.
- The system silently merged the QQ login with my existing Google User ID (likely due to the recovery email relationship) without any notification.
- Thinking it was a separate temporary account, I deleted the account while logged in via QQ.
- This action unexpectedly deleted my primary Google account's data as well.
Current "Zombie" State
Now, when I try to log in via Google:
- It says "You are logging back into lmarena".
- It immediately redirects to a 404 page.
- After refreshing, the UI shows I am logged in, but I cannot accept the Terms of Service (it keeps saying "Failed").
- This proves the database record is in a "corrupted/half-deleted" state but the User ID still exists.
Why this is urgent
This account contains 3 months of my intellectual work, ideas, and critical chat history. Losing this is devastating to me. Since the system returns a 404 instead of "Account Not Found," I believe the data might still be recoverable in the backend (e.g., in a "soft delete" state).
Request
I hope the developers check the database logs for this conflict. I am the legitimate owner of both emails and can provide any proof needed.
Primary Google Email:wang****@gmail.com
Recovery QQ Email:3308******@qq.com
Approx. Deletion Time:[Dec 25th,UTC 07:00]
Please help me recover my life's work. Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named. Start by reviewing database logs and account-deletion/login records around Dec 25 at 07:00 UTC; done would be determining whether the account data is recoverable and whether the reported merge and deletion behavior is reproducible.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100