Qjuh
Qjuh
> So I’d like to take a point on this. When looking at the code it seems Discord.js uses `Promise.all` when spawning shards. which if one of the process were...
Here are my five cent: 1. 1. data property, keep it private, only get it through toJSON() 2. I‘m not an expert in TS typings but I guess it would...
Are you sure the opus from OpenAI is encoded as 24000 bitrate?
There‘s a PR for that already: #1486
Looks like shard 0 doesn’t get any replies on its websocket connection once shard 1 starts its websocket. Could be an issue with your docker configuration. What do the debug...
That clearly shows that shard 0 is fine sending and receiving heartbeats but will stop receiving them when shard 1 starts to send one. So that definitely looks like some...
Those errors clearly indicate you‘re not on 14.11.0 but at most 14.9.x, because they are debug logs of the old websocket implementation and not the one we use since 14.10.0....
> Personally I think `shard.getStatus()` is redundant, as you can mark shard.status based on what the discordjs/ws emits. It can possibly be a bottleneck in worker sharding, where you need...
I‘ll happily look at your implementation, open a PR and I‘ll take a look. The important part is to do it in a non-breaking way. I‘ll try to allow setting...
> Seems like, out of all of the `WebSocketShardEvents`, only these are being emitted: > > * `WebSocketShardEvents.Ready` > > * `WebSocketShardEvents.AllReady` > > * `WebSocketShardEvents.Resumed` `WebSocketShardEvents.Close` can be added...