[Bug] Stuck Generation Loop in Main Account (WebSocket Deadlock)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.5k
- Forks
- 4.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hello Arena Support Team,
I’m reaching out because my account seems to be experiencing a persistent issue. When I log in, prompts I type appear on screen but the system does not generate any response. This happens across multiple devices (phone and laptop) and browsers. Interestingly, Arena works fine in guest mode or incognito when I’m not logged in, but as soon as I sign into my account, the issue returns.
Another detail: it doesn’t behave like the usual infinite generation problem, and I don’t get the “something is wrong” error message either. Instead, nothing happens.
This makes me think the problem is account-specific rather than a general outage or browser cache issue. Could you please check if there’s a problem with my account state or session data, and advise on how to resolve it?
Thank you for your help.
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
The report names no source files or tests. Start by reproducing the authenticated-only failure across browsers and tracing the account/session WebSocket path; done means identifying and fixing the session state that prevents generation for signed-in users, with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100