You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Snakemake requires at least one top level key in a config file, so including a bogus key here that should not be used anywhere in the Snakemake workflow
More precisely, Snakemake requires a YAML file with a top-level map/dict/object type. It may be empty; keys are not required.
We could avoid the bogus config key above by using flow syntax for a map ({}) instead, e.g.
# TODO: If the ingest workflow ever runs too long, we should figure out a way# to subset the ingest data. Currently, the CI just runs the default ingest workflow.{}
The bogus config key also got propagated to measles, rabies, and oropouche, and seems likely to propagate further over time. It'd be nice to avoid, IMO.
The ingest workflow current runs in <1 minute so I figured it'd be nice
to add as an additional check in the GH Action CI workflow.
If the ingest workflow ever runs for too long, we should figure out a
way to subset the ingest data.
The CI build config includes a bogus key because Snakemake requires the
config file to have at least one top level key.
Previous CI run without the bogus key ran into an error¹
```
snakemake.exceptions.WorkflowError: Config file must be given as JSON or YAML with keys at top level.
```
¹ <https://github.com/nextstrain/zika/actions/runs/9948628997/job/27483549394#step:9:17>
joverlee521
changed the title
Change bogus key to empty object
ingest: Add example build-config/ci/config.yaml
Oct 29, 2024
Originally posted by @tsibley in 44f27a5
The text was updated successfully, but these errors were encountered: