Every day starting at 00:01 until about 00:36, torn/stats seem to give 0 (v1) or null (v1 as v2 'legacySelections'). I'd suspect it's because of the updating batch around that time, but it's very annoying.
[API] torn/stats incorrect data
Started by DeKleineKobini [2114440] Committee on in Bugs & Issues.
About this thread
Posts archived: 4 / 4 posts (100%) · the total is Torn's reply count + the opening post at the last fetch
Counted by TornLife from the archived posts.
- Archived posts
- 4
- Discussion span
- →
- People posting
- 3
- Likes on archived posts
- 4
- Posts by staff, officers and moderators
- 4
- Authority score
- 59 / 100
- Historical score
- 37 / 100
- Story score
- 37 / 100
- Engagement score
- 45 / 100
Most-liked replies
- splent [2088243] Admin
· 2 likes ·
Hey, Thanks for the report. I added a fallback to the day before, so let's see if this fixes the issue until cron is executed. Thanks! - DeKleineKobini [2114440] Committee
· 1 likes ·
Awesome, now it went straight to the new values at 00:36 without starting to return null values starting at midnight. Thanks for that.
Passing along to Mauro. Thanks..!!
Hey,
Thanks for the report.
I added a fallback to the day before, so let's see if this fixes the issue until cron is executed.
Thanks!
Awesome, now it went straight to the new values at 00:36 without starting to return null values starting at midnight. Thanks for that.