jscheffl commented on PR #62309: URL: https://github.com/apache/airflow/pull/62309#issuecomment-3941633293
> Hey @jscheffl! Thanks for quick reply 🙂 > > > Can you please let me/us know which workflows break down? > > It's the workflow I already said. If you install prek with uv (which is how we suggest you to do it in the contributor guide [here](https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst#installing-prek-hooks)) this assertion no longer seems to pass after these changes. But perhaps I'm doing something else wrong? But I went from a working setup, pulling main, and then a failing setup. > > Here is the output: > > ```shell > onikolas@u88ab6c93fa7f51:~/code/oss/airflow$ breeze start-airflow --backend postgres --forward-credentials --terminal-multiplexer tmux > > Docker container engine detected. > Good version of Docker: 28.2.2. > Good version of docker-compose: 2.33.1 > Host python version is 3.11.11 (main, Mar 17 2025, 21:02:09) [Clang 20.1.0 ] > Checking prek installed for /home/ANT.AMAZON.COM/onikolas/.local/share/uv/tools/apache-airflow-breeze/bin/python3 > > Error checking for prek-installation: > > /home/ANT.AMAZON.COM/onikolas/.local/share/uv/tools/apache-airflow-breeze/bin/python3: No module named prek > > Make sure to install prek. For example by running: > > uv tool install prek > > Or if you prefer pipx: > > pipx install prek > > onikolas@u88ab6c93fa7f51:~/code/oss/airflow$ uv tool install prek > > `prek` is already installed > ``` @o-nikolas Sorry, I was not at the PC reading your message. "the workflow" and "lot of workflows" is not a real hint. But tested myself. Interesting, I have prek also installed as tool and it is in the venv but still does not find it. Yeah you might be right, then we shoudl revert this. Next time... please be more specific and constructive. -- 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]
