The corresponding data in the downloaded JSON is indeed from 28 days ago. Expected behaviour is that clicking these download links should always serve the most recent version of the register data.
I wonder if the site is served by two or more different boxes, but not all the git_commit_refs have been recently updated? I’ve just tried visiting https://org-id.guide/_update_lists a few times, and I suspect I’ve now brought all the boxes up to date. (While that has temporarily fixed the problem, I suspect it will come back.)
andylolz
commented
2 years ago
If I click the download JSON button / visit the link to download JSON, the downloaded filename helpfully includes the associated git SHA of the register repo. If I do this a few times, this SHA alternates. Currently, I’m seeing
b20579da7e(the most recent commit in the repo) andd1e4ac9cf8(a commit from 28 days ago).The corresponding data in the downloaded JSON is indeed from 28 days ago. Expected behaviour is that clicking these download links should always serve the most recent version of the register data.
I wonder if the site is served by two or more different boxes, but not all the
git_commit_refs have been recently updated? I’ve just tried visiting https://org-id.guide/_update_lists a few times, and I suspect I’ve now brought all the boxes up to date. (While that has temporarily fixed the problem, I suspect it will come back.)