At random points in time, /changelog responds with 0s for release streams lazer and tachyon, thus showing nothing for the user count of lazer as a whole.
This happens in intervals of 5 minutes for up to 45 seconds at a time.
On osu-web, this shows up simply as the build entry not having a user count at all
When fetching data directly, it shows up as a 0-ed field. Attaching a (somewhat bulky) dump of json responses over a span of about a minute showcasing the issue
changelog.json
These were gathered in intervals of 3 seconds at about 16:15 UTC and dumped raw into the file. A cut-down pretty-printed version looks more like the following:
changelog_small.json
Note
I know I'm likely the only person who actually polls the endpoint often enough to notice this, however, due to the interval shifting and not being consistent, I am reporting this anyway as this is just... weird
At random points in time, /changelog responds with 0s for release streams
lazerandtachyon, thus showing nothing for the user count of lazer as a whole.This happens in intervals of 5 minutes for up to 45 seconds at a time.
On osu-web, this shows up simply as the build entry not having a user count at all
When fetching data directly, it shows up as a 0-ed field. Attaching a (somewhat bulky) dump of json responses over a span of about a minute showcasing the issue
changelog.json
These were gathered in intervals of 3 seconds at about 16:15 UTC and dumped raw into the file. A cut-down pretty-printed version looks more like the following:
changelog_small.json
Note
I know I'm likely the only person who actually polls the endpoint often enough to notice this, however, due to the interval shifting and not being consistent, I am reporting this anyway as this is just... weird