fix: Store latest datasets cronjob size limit #299
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks for opening this pull request! You're awesome.
We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.
Examples of titles with semantic prefixes:
- fix: Fix wrong countries for some sources
- feat: Add Features and Status to MDB Schema [SOURCES]
- docs: Improvements to README.md and CONTRIBUTING.md
If your pull request includes adding or updating a source, make sure to end your pull request title with "[SOURCES]" so the GitHub workflow runs.
davidgamez
changed the title
| schedule: | ||
| - cron: "0 0 * * *" | ||
|
|
||
| env: | ||
| URL_STORAGE_PREFIX: "https://storage.googleapis.com/storage/v1/b/mdb-latest/o" |
There was a problem hiding this comment.
It's ok for now, but we should consider another way to specify this prefix in case we ever change the location of the datasets.
|
Congrats on getting your first pull request merged! |
Description
The
store latest datasetscronjob is failing, blocking the downloads and verification of all datasets. The failure is due to the GitHub step/job output size. In this PR, the step output is replaced with the "new" Github output pattern, and the latest URL prefix is removed from the output to reduce the number of characters of the job results.Expected behavior
The
store latest datasetscronjob runs successfully.