#10457 please check DNF Counting scripts for end-of-year failure
Closed: Fixed by mattdm. Opened by mattdm.

Describe what you would like us to do:


Traditionally, the Old Mirror Stats script (see #10443 for related) fails every New Year, returning truncated values (mostly zeros) for that day ... and going forward until @smooge pokes at it.

I want to verify that we don't have this same problem the DNF Counting scripts before the report runs. Basically — is data from the last day of the year good?

When do you need this to be done by? (YYYY/MM/DD)


Before report that runs the morning of January 6th would be ideal — so 2022/01/05, or ... tomorrow. I know we're still un-hybernating, so if we miss that and the data is bad, as soon as possible after that.


[Kevin and Mark are out until the 2022-01-10 or later so I will look at this.]

dnf counting databases seem to be running fine. I have been hand running the CentOS scripts and they seem to have handled the changeover mainly because the raw.db uses timestamps versus my crappy filesystme changeover.

Metadata Update from @smooge:
- Issue assigned to smooge

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: downloads, low-gain, medium-trouble

I need to wait until tomorrow's stats are run to hand fix the older tables and make it work for 2022.

I was wrong and didn't need to wait til tomorrow. I think I fixed the data for 2021. Please check the csv files and confirm.

Looks good now! Thank you!!!

Metadata Update from @mattdm:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata