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

Circular dependency issue when trying to locally test DAG #34558

Closed
1 of 2 tasks
drobert-bfm opened this issue Sep 22, 2023 · 4 comments
Closed
1 of 2 tasks

Circular dependency issue when trying to locally test DAG #34558

drobert-bfm opened this issue Sep 22, 2023 · 4 comments
Labels
area:core kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet pending-response stale Stale PRs per the .github/workflows/stale.yml policy file

Comments

@drobert-bfm
Copy link

Apache Airflow version

2.7.1

What happened

Attempting to test DAG sanity by running dag.test():

if name == 'main':
test_http_sensor().test()

python my_sensor_dag.py

I receive the following error:

ImportError: cannot import name 'Dataset' from partially initialized module 'airflow'

What you think should happen instead

According to what I can figure out in the documentation, it should be possible to run DAG.test() outside the airflow scheduler/executor in order to validate a DAG.

How to reproduce

  1. Activate .venv which contains Airflow execution
  2. create dag with if name == 'main' as shown above
  3. run the code: python .py

Operating System

CentOS 8 Stream

Versions of Apache Airflow Providers

apache-airflow-providers-common-sql==1.7.1
apache-airflow-providers-ftp==3.5.1
apache-airflow-providers-http==4.5.1
apache-airflow-providers-imap==3.3.1
apache-airflow-providers-mysql==5.3.1
apache-airflow-providers-sqlite==3.4.3

Deployment

Virtualenv installation

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@drobert-bfm drobert-bfm added area:core kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet labels Sep 22, 2023
@boring-cyborg
Copy link

boring-cyborg bot commented Sep 22, 2023

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

@Taragolis
Copy link
Contributor

Unfortunetly we need a bit more details (full error stack trace) and DAG sample for able to reproduce and understand what going wrong.

@github-actions
Copy link

github-actions bot commented Oct 9, 2023

This issue has been automatically marked as stale because it has been open for 14 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Oct 9, 2023
@github-actions
Copy link

This issue has been closed because it has not received response from the issue author.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core kind:bug This is a clearly a bug needs-triage label for new issues that we didn't triage yet pending-response stale Stale PRs per the .github/workflows/stale.yml policy file
Projects
None yet
Development

No branches or pull requests

2 participants