Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
nssp source produces weekly data. The way the source records timestamp of data is with
week_end
column, while our db does the same thing usingtime_value
column. Thing is, nssp sourceweek_end
column uses the last day of an epi week (example: 2024-07-06) to mark data from that week, whiletime_value
uses the first day of the same epi week (example: 2024-06-30), hence this discrepancy in pre-release calculation ofmax_age
in number of days for nssp in sircal. This PR to fix will add 6 days to the originalmax_age
to account for this discrepancy, which will shut sircal up in system-monitoring.Changelog