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

ingest/automation: Update S3 URLs to uppercase #22

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

joverlee521
Copy link
Contributor

@joverlee521 joverlee521 commented Oct 10, 2024

Description of proposed changes

Automated uploads of files have been failing because of mismatch in casing. Update all S3 URLs to match expected uppercase since change in nextstrain/infra#31.

Checklist

  • Checks pass

Automated uploads of files have been failing because of mismatch in
casing. Update all S3 URLs to match expected uppercase since change in
nextstrain/infra#31.
@joverlee521 joverlee521 requested a review from j23414 October 10, 2024 18:05
Copy link
Collaborator

@j23414 j23414 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

I really do wonder if we should standardize on lowercase names to avoid this kind of error in the future...grr

@joverlee521 joverlee521 merged commit b047081 into main Oct 10, 2024
4 checks passed
@joverlee521 joverlee521 deleted the fix-ingest-automation branch October 10, 2024 18:18
@joverlee521
Copy link
Contributor Author

Manually ran the ingest-to-phylogenetic workflow after merging. Ingest ran successfully and uploaded the new metadata TSV and sequences FASTA.

However, the cache remained the same and did not trigger the phylo workflow...will investigate.

joverlee521 added a commit that referenced this pull request Oct 10, 2024
I noticed that even though files were update in ingest, the cache still
didn't change and phylo did not run.

Traced it back to incorrect S3 URLs leading to the use of
the default hash in the cache. Output message to the GITHUB_STEP_SUMMARY
so that we can immediately see if an S3 file doesn't have a sha256sum.

<#22 (comment)>
joverlee521 added a commit that referenced this pull request Oct 10, 2024
I noticed that even though files were update in ingest, the cache still
didn't change and phylo did not run.

Traced it back to incorrect S3 URLs leading to the use of
the default hash in the cache. Output message to the GITHUB_STEP_SUMMARY
so that we can immediately see if an S3 file doesn't have a sha256sum.

<#22 (comment)>
@joverlee521 joverlee521 mentioned this pull request Oct 10, 2024
2 tasks
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