d2orbc
d2orbc
under the conditions of my API consumer, this seems to affect ~44 in 100k (sampled across PGCR range 13927500000-13927600000)
Workaround: two checks: - values.playerCount != len(entries) - on a well formed PGCR it should match the length of entries. - startingPhaseIndex/activityWasStartedFromBeginning is missing - on a well formed PGCR...
If I detect a malformed PGCR response, I now re-request with a cache bust appended to the URL. It appears it can be resolved with the cache bust after one...
Vast majority get the correct response in under 10 seconds, but I had two instances today that took almost exactly 5 minutes to update with the correct response. I'm busting...
Presumably still a thing On Fri, May 23, 2025, 4:09 AM github-actions[bot] ***@***.***> wrote: > Closed #1886 as completed. > > — > Reply to this email directly, view it...
Similar to #1374 and #1575 but with BungieCredentialType
reopen
I instruct people to unlink and relink Twitch. I didn't realize just a login with Twitch would do it. Thanks! In lieu of the numeric ID being exposed, is there...
open please?
Any idea what happened here? Was an incident filed internally for that?