You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst using https://browsersl.ist, I found a problem in how it was reporting coverage wrongly, and traced the problem to here.
It seems that 30001520 changed usage_global in data.json quite considerably, but regional data, and therefore alt-ww (which in principle should match usage_global exactly), stayed the same.
That resulted in cover: 80% request in alt-ww only covering 73.7%, for example.
Regional data seems to be updated around monthly.
Can I request regional data to be updated off-schedule to fix this mismatch?
The text was updated successfully, but these errors were encountered:
Whilst using https://browsersl.ist, I found a problem in how it was reporting coverage wrongly, and traced the problem to here.
It seems that
30001520
changedusage_global
indata.json
quite considerably, but regional data, and thereforealt-ww
(which in principle should matchusage_global
exactly), stayed the same.That resulted in
cover: 80%
request inalt-ww
only covering73.7%
, for example.Regional data seems to be updated around monthly.
Can I request regional data to be updated off-schedule to fix this mismatch?
The text was updated successfully, but these errors were encountered: