-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bsweger/hotfix cladetime #12
Conversation
We're fixing up cladetime to get a proper test case added for the scenario that caused the error, but in the meantime, let's use the hotfix so we can get the latest data uploaded to S3
This will make it easier to manually recreate a prior run in the event of a problem
@@ -17,7 +17,7 @@ | |||
# requires-python = "==3.12" | |||
# dependencies = [ | |||
# "click", | |||
# "cladetime@git+https://github.com/reichlab/cladetime" | |||
# "cladetime@git+https://github.com/reichlab/cladetime@elr/use_metadata_url" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -4,6 +4,11 @@ on: | |||
schedule: | |||
- cron: "37 04 * * 1" # 4:37 AM UTC every Mon | |||
workflow_dispatch: | |||
inputs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Allowing someone to pass in YYYY-MM-DD when running this workflow manually makes it easier to recover in the event of an error.
In this case, I think we can pass in the dates of the failed runs:
2024-10-25
: not the current date, so script will set the time to 11:59 PM (i.e., will include info from the 10/25 Nextstrain run)2024-12-02
: is today, so script will use the action's run time as the as_of timestamp
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems plausible to me!
This PR addresses a problem reported by @trobacker: https://reichlab.slack.com/archives/C06ESFN6Y79/p1733154604469869
The root cause is the same Cladetime issue that @elray1 and @zkamvar hotfixed last week
There are two commits:
main
branch)