-
Notifications
You must be signed in to change notification settings - Fork 12
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
[BUG] The green_urls
datasets are empty since 2024-04-16
#574
Comments
hi @br0ken - thanks, for the heads up. I'll look into this and update when I have more |
? I have absolutely no idea what this is about. I do not know anything about what you sent. This is not me. You got the wrong Br0ken. This is the correct person https://github.com/BR0kEN- |
Thanks @mrchrisadams. Just FYI, this is still the case for the snapshots that appear after |
@mrchrisadams would you please have a look? |
hi @BR0kEN- sorry about this, I've looked into it, and I think I see the issue now. I've pushed a change to the cronjob that was running each morning, and run the job now to generate the snapshots again as intended. There should be snapshot for If it helps clarify things, this was the playbook run, to set up the corrected cronjobs on the relevant machine: There should be another one tomorrow, of the expected size, and so on. However, it's it's a bit of a faff to backfill the other daily snapshots from mid April, and there is some other work on the project that needs to take precedence, so I won't be able to backfill these for a while. We do store all the day's greenchecks in parquet files, which are optimised for aggregate queries - these lend themselves well to recreating all the green domains for a given day, so it's doable, just not in the next week or so. I've created #592 to track it, and I'm closing this issue. |
The
green_urls
datasets are empty starting from2024-04-16
.Steps to reproduce the behavior:
green_urls_2024-04-16.db.gz
,green_urls_2024-04-17.db.gz
, orgreen_urls_2024-04-18.db.gz
.Expected behavior
The database should not be empty.
Actual behavior
The database is empty.
The text was updated successfully, but these errors were encountered: