Tamagoch wrote: ↑Mon Dec 02, 2024 5:48 pm
Hi Tim,
I suppose the stats update is processed per user and per team, so it wasn't equal enough, to be honest.
Hi
As I recall, there are at least two sets of stats available as XML files.
One is for users and the other is for teams.
They could be updated (by the project) at different times and they could be accessed (and downloaded) at different times.
So, they can only be valid at the time when they were imported into the FB tabulation scripts (and assuming they have higher credit values than the previous downloaded stats).
Any issues therefore at any point in the chain, such as a server issue with the project, a power outage anywhere on the internet, or any data loss or disconnection can cause the FB League tables to be "stuck" at the previous update.
And as the FB Leagues are compiled and displayed based on whatever data has been made available, so there is always a chance that a problem earlier on in the chain can cause issues with the FB website and its ability to display the most recent stats.
Tamagoch wrote: ↑Mon Dec 02, 2024 5:48 pm
For example, I have lost some places because my stats wasn't updated since saturday and some users were lucky to be updated on Sunday night. That's how it works in case of project issues.
I don't know if we can propose an additional coding for Sebastian. That could be an emergency script that catch up the stats based on 'Time reported' value for uploaded tasks. But that should be designed carefully, it's too much to think of, I understand
Otherwise we could cut off a 'bad day' and make a sprint even shorter.
This time our race was red-flagged and the track authorities refused to continue it. My car had a transponder issue, that happens
As mentioned, if there is a problem with the project (either being offline or the stats are not exported correctly or on time) so there's NOTHING for FB to display EXCEPT the previous stats that were collected successfully. So, no extra coding can magically make stats appear, if the project does not update them.
However, the one thing I did ask Sebastien to include (but which hasn't happened) is for the Sprint League tables to show the time of when the last data set was correctly downloaded. So, at least members would know that at least a few hours of stats had been collected previously.
We therefore have to 100% rely on the projects and their power suppliers and their internet connections to be working 24/7 during the Sprints. If not then the chain breaks and we can do nothing to make this any better.
regards
Tim