-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ipdb no longer works in task execution thread #31784
Comments
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. |
@phanikumv can you please assign this to me |
Replacing With below dag
|
Also, the below dag is failing in airflow 2.4.0 and 26.1 for me with the same error. It doesn't look like an airflow issue.
|
This issue has been automatically marked as stale because it has been open for 30 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author. |
This issue has been closed because it has not received response from the issue author. |
I have met same issue with ipdb |
Apache Airflow version
2.6.1
What happened
We want to use
"import ipdb; ipdb.set_trace()"
in the task execution thread (the python callable)
This just broke when upgrading from 2.4.0 to 2.6.1.
Now we get the following stack trace:
What you think should happen instead
We should get into the ipdb debugging shell.
How to reproduce
import ipdb; ipdb.set_trace()
Operating System
Debian 11.3
Versions of Apache Airflow Providers
No response
Deployment
Astronomer
Deployment details
No response
Anything else
I reported this exact same bug back in 2.3.4, and it was fixed, but it has come back. Can we please add tests to make sure debuggers like ipdb won't break with future releases?
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: