-
-
Notifications
You must be signed in to change notification settings - Fork 734
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
Completed the setup for Guild without matching id in Ready Handler cache - no trace #512
Comments
Is this consistent and reproducible? |
Don't think so, didn't get that during a restart yesterday. I'll try booting (a copy) of the bot up and down a few times to try and reproduce and also check whether the guild that caused this is still present, and report back. |
Guild is not present anymore. No luck with a bunch of starts, didn't get any errors. |
Just happened again after a reconnect (running JDA build is hotfix-zlib branch). https://wastebin.party/yawipuzeqo.css Debug log has those same Caching Presence lines (about a hundred per shard reconnecting) as shown in the OP, didn't see any other suspicious things. |
Is that consistent on shard 0? |
I have only observed these two incidents, might be chance. |
I think I know what's happening:
Edit: Cannot reproduce |
Does this still happen on 48bc751? |
Yes still does (on 305). Got two of these in the aftermath of the discord outage earlier. |
On the websocket enhancement branch: 9f76639
jda debug level log filtered by the shard: |
Got this error on 3.3.1_286 , while booting up shards.
There is no other log or stack trace to indicate the reason, just a bunch of these in the debuglog right before that:
The text was updated successfully, but these errors were encountered: