Skip to content
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

Update ADR/AF/MUR refresh lookup time interval #5238

Closed
1 task
patphongs opened this issue Sep 8, 2022 · 1 comment · Fixed by #5241
Closed
1 task

Update ADR/AF/MUR refresh lookup time interval #5238

patphongs opened this issue Sep 8, 2022 · 1 comment · Fixed by #5241
Assignees
Milestone

Comments

@patphongs
Copy link
Member

patphongs commented Sep 8, 2022

The problem

When ADRs, AFs, or MURs are published, our script will only looks up in the past 8 hours which cases need to be published to the website. The timeframe is from 06:00 - 19:55 EDT, 5:00 - 18:55 EST, and 10:00 - 23:55 UTC.

"schedule": crontab(minute="*/5", hour="10-23"),

For EDT, the script runs from 06:00 - 19:55 EDT every 5 minutes and checks for published cases from the last 8 hours. Starting at 06:00 EDT, it will check published cases within the past 8 hours. This misses a little over 2 hours of time in which a case is published between 19:56 and 22:00 EDT.

The script runs from 05:00 - 18:55 EST every 5 minutes and checks for published cases from the last 8 hours. Starting at 05:00 EST, it will check published cases within the past 8 hours. This misses a little over 2 hours of time in which a case is published between 18:56 and 21:00 EST.

What's we're after

In order to account for the gap/missing time to check for published cases, we need to update the script so that it checks the entire interval between 19:56 - 6:00 EDT and 18:56 - 5:00 EST which cases have been published.

Completion criteria

  • Script runs for 10 hour period
@cnlucas
Copy link
Member

cnlucas commented Sep 21, 2022

We need to modify RECENTLY_MODIFIED_CASES and RECENTLY_MODIFIED_AOS execution to 10 hours

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants