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

DAG Import Errors #34

Closed
FredrikBakken opened this issue Sep 13, 2022 · 1 comment · Fixed by #35
Closed

DAG Import Errors #34

FredrikBakken opened this issue Sep 13, 2022 · 1 comment · Fixed by #35

Comments

@FredrikBakken
Copy link
Contributor

Versions

Airflow: 2.3.4
LakeFS: 0.80.1
LakeFS Provider: 0.44.0

Error Message

Broken DAG: [/home/$USER/airflow/dags/ingest/ingest.py] Traceback (most recent call last):
  File "/home/$USER/.local/lib/python3.10/site-packages/airflow/models/taskmixin.py", line 244, in <listcomp>
    return [self.dag.get_task(tid) for tid in self.downstream_task_ids]
  File "/home/$USER/.local/lib/python3.10/site-packages/airflow/models/dag.py", line 2115, in get_task
    raise TaskNotFound(f"Task {task_id} not found")
airflow.exceptions.TaskNotFound: Task get_branch_commit not found

Operators with Error Message

Operator Does it have the error?
LakeFSCommitOperator ✔️
LakeFSCreateBranchOperator
LakeFSGetCommitOperator ✔️
LakeFSGetObjectOperator
LakeFSMergeOperator ✔️
LakeFSUploadOperator ✔️

Correlation

The correlation between the operators with the error message and the operators that does not have the error message is that;

self.task_id = kwargs.get("task_id")

is noted in the __init__() function for all the operators with the DAG error. The two operators that does not have this error message, does not have self.task_id mentioned in the __init__() function. Removing this line from the operators that have the DAG error, makes them work as expected.

@FredrikBakken
Copy link
Contributor Author

@arielshaqed , I've added a new comment to the closed PR (#35 (comment)). Please let me know if there is anything else I could help out with 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants