ckohen
ckohen
Think maybe there should be a note on why this is different. Don't know if this should be part of that note, but using the /api route causes all subdomains...
Zod errors are poopy though 😢
Ok, I think i've nailed down when this could possibly happen. The oddity is that it has to involve stage channels, which you have said aren't involved. Anyways, as of...
Ok, drilled down a bit and found that presence updates add a member based on the user only (PU doesn't come with a member), don't know why yet, but that's...
Cool, so that confirms that is indeed where the issue comes from. I am debating whether we can safely remove the member being added in presence events in a semver...
`parent` is the same no matter what type of thread it is. because private threads do also belong to channels. `parent` is only nullable because of the cache access. If...
ah.....right, the minor detail of interactions. - not sure if its still the case but there's this bug https://github.com/discordjs/discord.js/issues/5960 which was causing crashes due to the same type of assumption...
Again, *all* threads behave exactly the same in regards to `parentId` and `parent`. It doesn't have to do with the type of thread, its where its received from Sweepers don't...
The rateLimit event is fired when discord.js preemptively blocks a request from hitting a rate limit, not when we encounter an actual ratelimit. By the time a request is re-queued...
That's not how sublimits work, we don't know about them until we hit them, and even then we don't know what combination of parameters cauesd it. We get no information...