Closed xayanide closed 2 years ago
you sneaky little-
Additionally, once this issue is reproduced, Quaver gets stuck at the shuttingDown
asynchronous function and does not exit its process on its own similar to this issue #128.
The scope of issue #128 lies on it getting stuck due to lack of permissions to send a locale string.
In this case of this issue itself, I haven't found out yet... The only way to shut down Quaver from there is to manually end the process. I think this one should be taken into account with this issue as well.
:tada: This issue has been resolved in version 3.4.0-next.44 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 3.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Describe the bug What isn't working as intended, and what does it affect? Everything works as intended, affects functionality.
Only works with slash commands This bug is not that important to fix, but it's up to you if you want spend the time to fix it.
Affected versions What versions are affected by this bug? (e.g. >=3.0.1, 2.5.1-2.6.3, >=1.2.0) All versions
Steps to reproduce Steps to reproduce the behavior. (e.g. click on a button, enter a value, etc. and see error)
reply({
, even effective withdeferReply({
SHIFT
and left click the trash button of the recently sent message by Quaver Must be done in Quick succession.Expected behavior What is expected to happen? A check in interactionCreate that returns if the interaction message no longer exists (probably needs more conditions).
Actual behavior What actually happens? Attach or add errors or screenshots here as well. Since Quaver is still busy and there is no check for the reproduced issue, it is still doing its activities while the message that it sent no longer exists, therefore the crash
DiscordAPIError: Unknown Message
.