Skip to content
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

Closed
schnapster opened this issue Oct 8, 2017 · 10 comments
Assignees
Labels
bug status: completed has been completed but is not yet released status: need more info in need of additional details

Comments

@schnapster
Copy link
Contributor

17:07:17.292 [JDA [1 / 2] MainWS-ReadThread] [ERROR] n.d.j.core.requests.WebSocketClient - Completed the setup for Guild: G:SNIP(SNIP) without matching id in Ready Handler cache

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:

17:07:09.482 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:10.533 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching MESSAGE_DELETE event during init!
17:07:10.932 [JDA [1 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:11.543 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching MESSAGE_CREATE event during init!
17:07:11.544 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:11.572 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:14.197 [JDA [1 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:15.113 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching MESSAGE_CREATE event during init!
17:07:15.113 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:15.358 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching MESSAGE_CREATE event during init!
17:07:15.427 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:15.427 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:15.460 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
17:07:17.256 [JDA [0 / 2] MainWS-ReadThread] [DEBUG] n.d.j.core.requests.WebSocketClient - Caching PRESENCE_UPDATE event during init!
@MinnDevelopment
Copy link
Member

Is this consistent and reproducible?

@MinnDevelopment MinnDevelopment added the status: need more info in need of additional details label Oct 12, 2017
@schnapster
Copy link
Contributor Author

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.

@schnapster
Copy link
Contributor Author

Guild is not present anymore. No luck with a bunch of starts, didn't get any errors.

@MinnDevelopment MinnDevelopment self-assigned this Oct 16, 2017
@schnapster
Copy link
Contributor Author

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.

@MinnDevelopment
Copy link
Member

Is that consistent on shard 0?

@schnapster
Copy link
Contributor Author

I have only observed these two incidents, might be chance.
One thing to note is that I cache some guild data on guild join, and this guild is not in the database, which means the GuildJoin event was missed (probably happened during the reconnect).

@MinnDevelopment
Copy link
Member

MinnDevelopment commented Oct 22, 2017

I think I know what's happening:

  1. Disconnect
  2. Connect
  3. READY -> stores guild ids to build
  4. GUILD_CREATEs for those guild ids
  5. GUILD_CREATE for new joined guild, no matching id -> error to console

Edit: Cannot reproduce

@MinnDevelopment
Copy link
Member

Does this still happen on 48bc751?

@schnapster
Copy link
Contributor Author

Yes still does (on 305). Got two of these in the aftermath of the discord outage earlier.

@schnapster
Copy link
Contributor Author

On the websocket enhancement branch: 9f76639

Completed the setup for Guild: G:Taz Studio(404660633095766027) without matching id in ReadyHandler cache
   at net.dv8tion.jda.core.handle.ReadyHandler.guildSetupComplete(ReadyHandler.java:191)
    at net.dv8tion.jda.core.handle.GuildCreateHandler.lambda$handleInternally$0(GuildCreateHandler.java:45)
    at net.dv8tion.jda.core.entities.EntityBuilder.createGuildFirstPass(EntityBuilder.java:351)
    at net.dv8tion.jda.core.handle.GuildCreateHandler.handleInternally(GuildCreateHandler.java:39)
    at net.dv8tion.jda.core.handle.SocketHandler.handle(SocketHandler.java:37)
    at net.dv8tion.jda.core.requests.WebSocketClient.onDispatch(WebSocketClient.java:1042)
    at net.dv8tion.jda.core.requests.WebSocketClient.onEvent(WebSocketClient.java:896)
    at net.dv8tion.jda.core.requests.WebSocketClient.handleBinary(WebSocketClient.java:1123)

jda debug level log filtered by the shard:
jda.log

@discord-jda discord-jda locked and limited conversation to collaborators May 25, 2018
@MinnDevelopment MinnDevelopment added the status: in progress already in the process of being implemented label Jul 22, 2018
@MinnDevelopment MinnDevelopment added status: completed has been completed but is not yet released and removed status: in progress already in the process of being implemented labels Sep 2, 2018
MinnDevelopment added a commit that referenced this issue Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug status: completed has been completed but is not yet released status: need more info in need of additional details
Projects
None yet
Development

No branches or pull requests

2 participants