Open CloudburstSys opened 1 month ago
This seems to be within Discord.JS itself as part of it making network requests. If one takes longer than the timeout to complete, it'll throw an AbortError in a way we cannot catch.
This may be a networking issue. Will continue to investigate.
~well, we can say (hopefully with confidence) that this issue has been solved, with an unrelated build script change, for some reason lmao #16~
nvm.
We've come to the conclusion that these errors are unavoidable and, instead, are focusing on solutions on how to mitigate these errors instead of failing uncontrollably.
This issue is being closed and given the wontfix tag
An uncommited change to Bilby's production codebase seems to be working despite being bad practice. This issue is now officially resolved
This was not fixed :/
Commit 9bf07d1 did not fix this issue, reopening.
No clue why this occurs or what piece of code causes this, but it seems to be a timeout within Discord.JS itself.