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
Using the CLI parameter --scenarios results in broken DAGs due to incorrect conversion of the parameter into egon-data.configuration.yaml. This causes the following error:
Error Message
Broken DAG: [.../eGon-data/SH1/code/src/egon/data/airflow/dags/pipeline.py]
Traceback (most recent call last):
File "<string>", line 7, in __init__
File ".../code/src/egon/data/datasets/__init__.py", line 277, in __post_init__
last = list(self.tasks.last)[0]
IndexError: list index out of range
Cause
The parameter --scenarios is being incorrectly written into the YAML file as:
--scenarios: '[''status2019'', ''eGon2035'']'
Expected Behavior
The parameter should be correctly translated into YAML as:
--scenarios:
- status2019
- eGon2035
Steps to Reproduce
Use the CLI to run a scenario.
Observe the resulting YAML and notice the incorrect format.
Try to run the pipeline and observe the broken DAG error.
Impact
The pipelines are unable to execute due to invalid configurations.
Manual correction of the YAML file is required as a workaround.
Proposed Solution
Adjust the conversion logic to ensure the --scenarios parameter is written into the YAML file in the correct format.
The text was updated successfully, but these errors were encountered:
I think we faced that problem at some point. Since we always work with powerd-data by creating the egon-data.configuration.yaml in advance, the required changes were probably never done.
Description
Using the CLI parameter
--scenarios
results in broken DAGs due to incorrect conversion of the parameter intoegon-data.configuration.yaml
. This causes the following error:Error Message
Cause
The parameter
--scenarios
is being incorrectly written into the YAML file as:Expected Behavior
The parameter should be correctly translated into YAML as:
Steps to Reproduce
Impact
Proposed Solution
Adjust the conversion logic to ensure the
--scenarios
parameter is written into the YAML file in the correct format.The text was updated successfully, but these errors were encountered: