BSOD when trying to read public chat
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I am not positive that it had anything to do with the chat, but I was reading public chat. I also may have hit the rate limit because I was using a script to read the chat. So this may have been a bit of a stress test.
In my public folder there is a file processor.py that I was running and which was triggering the chat reads. The code that notices the rate limiting didn't exist yet so it would have been taxing.
my log id: 2a833f154467c8d242bfd71c
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
Start with the public-folder processor.py script and the supplied log ID 2a833f154467c8d242bfd71c. Reproduce the public chat reads under the reported rate-limit stress, then trace the client behavior that follows and determine whether it causes the BSOD. Done means the failure is reproduced or ruled out with evidence and the triggering behavior is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100