Closed febkosq8 closed 1 year ago
Edit : Nvm, it's still happening with the cache clean.
Old Update : Added the npm cache clean command to my Heroku procfile along with npm start
seems to have stopped the issue.
If I remove the cache clean then the problem seems to come back. IDK why this is the case.
worker: npm cache clean --force && npm start
Happenes too, when i try to add a song to the queue
☹️ I guess this needs a complete rewrite for voice connection part
I have the same error with: v6.2.0 discord-player version, djs 14.9.0 and djs/voice 0.16.0
The voice connection handler was rewritten in discord-player@dev
, please give it a try report any issues.
Tried out discord-player@6.6.0-dev
. I still got a AbortError on kicking the bot from vc.
From the recent research, it is confirmed that aborts are always emitted from player.events
in the form of an event and it does not cause the process to crash. Abort specific errors may be emitted in their own event in the future but for now I am going to close this issue. Aborts usually happen upon attempting to perform something on illegal context or timeouts. Use the error event and forward the message to the user if necessary.
For me the AbortErrors used to be caught in my unhandled exception not player.events.
Good news is that I am no longer getting AbortErrors in the latest version - discord-player@6.6.1
.
Describe the bug Bot will throw a AbortError when its stops the queue, either through command or disconnection. This was supposed to be patched already keep happening mostly for me in Heroku.
Since I am handling uncaughtException in my code, my bot doesn't crash. (otherwise would have crashed the bot completely)
Attaching error stack below :
To Reproduce Steps to reproduce the behavior:
Expected behavior
Please complete the following information: