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

bot doesn't reconnect after reidentifying #8984

Closed
djohts opened this issue Dec 27, 2022 · 1 comment · Fixed by #8989
Closed

bot doesn't reconnect after reidentifying #8984

djohts opened this issue Dec 27, 2022 · 1 comment · Fixed by #8989

Comments

@djohts
Copy link

djohts commented Dec 27, 2022

Which package is this bug report for?

discord.js

Issue description

here's the debug log:
2022-12-27-debug.log
at the end of it you can see that it tries to identify but it never actually happens

Code sample

I'm currently on phone so here's the file

Package version

14.7.1

Node.js version

18.12.0

Operating system

Linux 42dde76b-d8e7-4868-921f-8c263d171b72 5.15.0-1013-oracle #17~20.04.1-Ubuntu SMP Mon Jul 4 05:29:46 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Priority this issue should have

Medium (should be fixed soon)

Which partials do you have configured?

No Partials

Which gateway intents are you subscribing to?

Guilds, GuildMembers, GuildMessages, MessageContent

I have tested this issue on a development release

No response

@djohts
Copy link
Author

djohts commented Dec 28, 2022

Unsure if someone else has this issue or it is just me, but it gets pretty annoying as I run an API which checks specific guild members for having a role, but it returns false negatives due to this issue and in the last 2 days I've restarted the api about 3 times.

@kodiakhq kodiakhq bot closed this as completed in #8989 Jan 1, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants