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

Bsweger/hotfix cladetime #12

Merged
merged 2 commits into from
Dec 2, 2024
Merged

Bsweger/hotfix cladetime #12

merged 2 commits into from
Dec 2, 2024

Conversation

bsweger
Copy link
Contributor

@bsweger bsweger commented Dec 2, 2024

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:

  1. Point to the cladetime hotfix branch (to be reverted once the fix is merged to cladetime)
  2. A GitHub workflow change that allows us to specify an as_of date when manually running the action (this can't be fully tested until the change is merged, because we can only assume required AWS permissions from the main branch)

image

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
@bsweger bsweger requested a review from elray1 December 2, 2024 17:37
@@ -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"
Copy link
Contributor Author

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:
Copy link
Contributor Author

@bsweger bsweger Dec 2, 2024

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:

@bsweger bsweger requested a review from zkamvar December 2, 2024 17:49
Copy link
Contributor

@elray1 elray1 left a 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!

@bsweger bsweger merged commit dd7129f into main Dec 2, 2024
@bsweger bsweger deleted the bsweger/hotfix-cladetime branch December 2, 2024 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants