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

TypeError on MESSAGE_REACTION_ADD #4840

Closed
1 task done
Koyamie opened this issue Sep 22, 2020 · 9 comments · Fixed by #4841
Closed
1 task done

TypeError on MESSAGE_REACTION_ADD #4840

Koyamie opened this issue Sep 22, 2020 · 9 comments · Fixed by #4841

Comments

@Koyamie
Copy link
Contributor

Koyamie commented Sep 22, 2020

Please describe the problem you are having in as much detail as possible:
Got few times a TypeError when receiving a MESSAGE_REACTION_ADD event.

2020-09-22_2789

2020-09-22_2790

Further details:

  • discord.js version: latest master
  • Node.js version: v12.18.3
  • Operating system: debian 9
  • Priority this issue should have – please be realistic and elaborate if possible: normal

Relevant client options:

  • partials: ['REACTION','MESSAGE']
  • gateway intents: 13999
  • other: none
  • I have also tested the issue on latest master, commit hash:
@monbrey
Copy link
Member

monbrey commented Sep 22, 2020

Have you tested this with partials enabled for USER and GUILD_MEMBER also?

@Koyamie
Copy link
Contributor Author

Koyamie commented Sep 22, 2020

Have you tested this with partials enabled for USER and GUILD_MEMBER also?

Nope, I don't even know in what particular case this does happen.
I only want the REACTION and MESSAGE partials enabled so testing with others doesn't make sense, goal is to fix in this particual case!

@wasdennnoch
Copy link
Contributor

Partials shouldn't make a difference here as the crash occurs before anything with partials was done. It crashes in a code path that's a straight line from the raw gateway event, without any partials branching. That comes after the crash.

@kyranet
Copy link
Member

kyranet commented Sep 22, 2020

Duplicate of #4821, which has been fixed by #4822.

@Koyamie
Copy link
Contributor Author

Koyamie commented Sep 22, 2020

Duplicate of #4821, which has been fixed by #4822.

I am using the very latest version of d.js, this merge inclued.
This means it is not fixed.

@kyranet
Copy link
Member

kyranet commented Sep 22, 2020

The patch was landed after 12.3.1 landed, if you're using master, can you please provide the commit hash? "Latest master" is ambiguous and may not be actually the latest.

@Koyamie
Copy link
Contributor Author

Koyamie commented Sep 22, 2020

Sorry by latest master I mean latest commit, I'm up to date with this commit : 1e63f37

@kyranet
Copy link
Member

kyranet commented Sep 22, 2020

My bad, I have just confirmed the issue here, I approved the linked PR, sorry for not verifying properly 😅.

@Koyamie
Copy link
Contributor Author

Koyamie commented Sep 22, 2020

No problem, will precise the commit next time!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants