potiuk closed issue #37149: All DAGs triggered through UI fail after upgrading
from 2.6.1 to 2.8.1 when using LocalExecutor
URL: https://github.com/apache/airflow/issues/37149
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
potiuk commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1932315980
Yes it's known issue for Python (not for airflow) to have broken threading
behaviour, specifically when you are using proxies
https://github.com/apache/airflow/discussions/24463 -
luederm commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1930714936
Oh, interesting. I will keep that in mind next time I have compilation
issues in a conda environment.
> You have not mentioned if you have ARM/ M1/2/3 but I guess so. Then u
potiuk commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1928043023
> One notable thing is that when using venv, google-re2 installed through
pip without error.
Of course. This will also work in conda as soon as conda maintainers will
stop g
luederm commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1927995275
I ran the task manually as you suggested. I didn't see much in the log
output besides for:
`INFO - Running on host C`
It also looks like it failed in the UI.
I
potiuk commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1927500318
I tried to reproduce it with venv and could not. I guess the problem is with
mixing of conda packages and `pip` packages - looks like you have conda python
abi installed (which is t
luederm commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1927135274
Hello @jscheffl, thanks for looking into this.
> From your descriptions I assume you can re-produce the error also with a
fresh/clean setup?
Yep, I tested with a fresh
jscheffl commented on issue #37149:
URL: https://github.com/apache/airflow/issues/37149#issuecomment-1925800975
We are running 2.8.1 and all is fine in this area on our side.
From your descriptions I assume you can re-produce the error also with a
fresh/clean setup?
Have you tried one
