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 the way how google-re2 compiled library talks to
Python) and I guess this interferes with the pip installed packages. I guess
the way how airflow forks processes, and uses shared memory to communicate,
might interface with it.
You can do two things to verify this hypothesis.
1. Run task manually in your env (might be imperfect - as it does one less
fork)
you will find both values to replace by looking in your log and finding
`airflow', 'tasks', 'run`:
```python
airflow tasks run example_bash_operator this_will_skip
PUT_RUN_ID_OF_A_TASK_YOU_RUN_HERE --local --subdir PATH_TO_YOUR_EXAMPLE_DAG
```
This one should run and print something like:
```
[2024-02-05T18:07:59.543+0100] {task_command.py:423} INFO - Running
<TaskInstance: example_bash_operator.this_will_skip
manual__2024-02-05T16:44:54+00:00 [skipped]> on host jaroslaws-macbook-pro.local
```
2. Create your environment from the scratch using `pip venv` and repeat the
standarlone tests. It should work flawlessly (worked when I created everything
from scratch).
Can you please send us back result of those experiments?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
