[BUG] Cannot call write after a stream was destroyed
See original GitHub issueDescribe the bug My bot has commands that allow to turn on sound effects that might be funny, but when running these commands, the console sometimes has an error with some commands and the song won’t open due to this error.
To Reproduce Steps to reproduce the behavior:
- Run
this.client.player.play(message, "https://youtu.be/pFqS716gUzo");
code - See
Cannot call write after a stream was destroyed
error
Expected behavior The behavior I expected was for the song to start playing
Please complete the following information:
- Node Version: 12.5.3
- Discord.js Version: 12.22.1
Additional context
Normally this code was working properly until a few days ago but it no longer works and gives Cannot call write after a stream was destroyed
error
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
Cannot call write after a stream was destroyed #4284 - GitHub
This issue happens because you don't have enough disk space left on the server. Run pm2 flush to empty the logs.
Read more >Error [ERR_STREAM_DESTROYED]: Cannot call write after a ...
It worked locally, but when it got to aws, the error happened because node is running as user 'webapp'. It looks like that...
Read more >Node.js Stream writable.destroy() Method - GeeksforGeeks
In the above example, an error occurs because the write() method was called after the stream was destroyed. Reference: https://nodejs.org/api/ ...
Read more >Error [ERR_STREAM_DESTROYED] - Node-RED Forum
I get the following error occasionally which I need to trap and issue something like ... Cannot call write after a stream was...
Read more >Worker failures from stream write contention - GenieACS Forum
This happens to me on current master builds as well. Smells like a state management bug (trying to write to a socket that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
maybe you can try without install
ytdl-core
. who knows can 🤷♂️problem was solved thanks to this code thank you very much