-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
covid-19.datasettes.com serving same content as cdc-vaccination-history.datasette.io #28
Comments
https://covid-19.datasettes.com/-/databases.json confirms only the [
{
"name": "cdc",
"path": "cdc.db",
"size": 243044352,
"is_mutable": false,
"is_memory": false,
"hash": "6ef56caef05bcdd551041bf4943587202e4dfd78d10c311baa9368959227f9e2"
}
] |
Here's the problem: https://covid-19.datasettes.com/ is currently showing the data from https://github.com/simonw/cdc-vaccination-history / https://cdc-vaccination-history.datasette.io/ - I think I may be re-using a service name somewhere. |
https://github.com/simonw/cdc-vaccination-history/blob/main/.github/workflows/scrape.yml uses https://github.com/simonw/covid-19-datasette/blob/main/.github/workflows/scheduled.yml uses Maybe I messed up the DNS settings or domain settings in Cloud Run? |
They look correct in the "Domain mappings" panel: https://console.cloud.google.com/run/domains?project=datasette-222320 |
It's not the domain mapping: https://covid-19-j7hipcg4aq-uc.a.run.app/ is the underlying Cloud Run instance for |
I have no idea how this could have happened. I'm re-running the workflow at https://github.com/simonw/covid-19-datasette/actions/workflows/scheduled.yml to see if that fixes this (with a fresh deploy), but I'd really like to understand the root cause of this. Could it be a weird Cloud Run bug? |
Filed a bug report with Cloud Run here: https://issuetracker.google.com/issues/214373195 |
https://covid-19.datasettes.com/ and https://covid-19-j7hipcg4aq-uc.a.run.app/ are showing the correct things again now - running the deploy again fixed it. I'd really love to know what happened to cause this though! |
Thanks for addressing this mysterious issue so quickly! This data is really helpful. |
Reported here: https://twitter.com/mullender/status/1481689689018880003
The text was updated successfully, but these errors were encountered: