-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sloshy says he announced his presence, but he didn't #85
Comments
|
Access to the problematic room was granted now, so I pushed a minor update to https://chat.stackexchange.com/transcript/message/65422188#65422188 |
I guess the thread which ran the client on the other server crashed with the first traceback, and then no longer responded. It's hard to see how this could be fixed, other than by refactoring ChatExchange to be async instead of threaded. |
https://chat.stackoverflow.com/transcript/message/57225157#57225157 will have failed because of write access issues and the subsequent ones were probably blocked because of that. Something wrong in how the queue is (not) drained?
The text was updated successfully, but these errors were encountered: