ephraimbuddy commented on PR #27829:
URL: https://github.com/apache/airflow/pull/27829#issuecomment-1346094951
> Which pre-commit ? This does not seem like it is run in image (it would be
/opt/airflow path then). Each pre-commit has their own dependencies and you
need to make sure they are installed when they are run - they heave their
dependencies declrated in .pre-commit-config.yml file..
```
Update output of breeze commands in
BREEZE.rst.........................................Failed
- hook id: update-breeze-cmd-output
- exit code: 1
OK. The setup_autocomplete screenshot is embedded in BREEZE.rst.
OK. The testing_helm-tests screenshot is embedded in BREEZE.rst.
OK. The release-management_generate-constraints screenshot is embedded in
BREEZE.rst.
OK. The static-checks screenshot is embedded in BREEZE.rst.
OK. The exec screenshot is embedded in BREEZE.rst.
OK. The setup screenshot is embedded in BREEZE.rst.
OK. The prod-image_pull screenshot is embedded in BREEZE.rst.
OK. The ci-image_build screenshot is embedded in BREEZE.rst.
OK. The release-management_verify-provider-packages screenshot is embedded
in BREEZE.rst.
OK. The ci screenshot is embedded in BREEZE.rst.
OK. The prod-image_build screenshot is embedded in BREEZE.rst.
OK. The k8s_build-k8s-image screenshot is embedded in BREEZE.rst.
OK. The ci-image screenshot is embedded in BREEZE.rst.
OK. The k8s screenshot is embedded in BREEZE.rst.
OK. The release-management_prepare-airflow-package screenshot is embedded in
BREEZE.rst.
OK. The k8s_run-complete-tests screenshot is embedded in BREEZE.rst.
OK. The ci_free-space screenshot is embedded in BREEZE.rst.
OK. The release-management_prepare-provider-packages screenshot is embedded
in BREEZE.rst.
OK. The testing_tests screenshot is embedded in BREEZE.rst.
OK. The k8s_upload-k8s-image screenshot is embedded in BREEZE.rst.
OK. The ci-image_pull screenshot is embedded in BREEZE.rst.
OK. The setup_self-upgrade screenshot is embedded in BREEZE.rst.
OK. The release-management_release-prod-images screenshot is embedded in
BREEZE.rst.
OK. The ci_resource-check screenshot is embedded in BREEZE.rst.
OK. The compile-www-assets screenshot is embedded in BREEZE.rst.
OK. The ci_get-workflow-info screenshot is embedded in BREEZE.rst.
OK. The prod-image screenshot is embedded in BREEZE.rst.
OK. The k8s_configure-cluster screenshot is embedded in BREEZE.rst.
OK. The k8s_tests screenshot is embedded in BREEZE.rst.
OK. The ci_selective-check screenshot is embedded in BREEZE.rst.
OK. The k8s_deploy-airflow screenshot is embedded in BREEZE.rst.
OK. The k8s_setup-env screenshot is embedded in BREEZE.rst.
OK. The stop screenshot is embedded in BREEZE.rst.
OK. The shell screenshot is embedded in BREEZE.rst.
OK. The ci-image_verify screenshot is embedded in BREEZE.rst.
OK. The testing screenshot is embedded in BREEZE.rst.
OK. The release-management screenshot is embedded in BREEZE.rst.
OK. The k8s_logs screenshot is embedded in BREEZE.rst.
OK. The ci_fix-ownership screenshot is embedded in BREEZE.rst.
OK. The ci_find-newer-dependencies screenshot is embedded in BREEZE.rst.
OK. The k8s_shell screenshot is embedded in BREEZE.rst.
OK. The k8s_status screenshot is embedded in BREEZE.rst.
OK. The release-management_prepare-provider-documentation screenshot is
embedded in BREEZE.rst.
OK. The prod-image_verify screenshot is embedded in BREEZE.rst.
OK. The k8s_k9s screenshot is embedded in BREEZE.rst.
OK. The setup_config screenshot is embedded in BREEZE.rst.
OK. The k8s_delete-cluster screenshot is embedded in BREEZE.rst.
OK. The testing_docker-compose-tests screenshot is embedded in BREEZE.rst.
OK. The setup_regenerate-command-images screenshot is embedded in BREEZE.rst.
OK. The k8s_create-cluster screenshot is embedded in BREEZE.rst.
OK. The start-airflow screenshot is embedded in BREEZE.rst.
OK. The cleanup screenshot is embedded in BREEZE.rst.
OK. The build-docs screenshot is embedded in BREEZE.rst.
OK. The setup_version screenshot is embedded in BREEZE.rst.
OK. The testing_integration-tests screenshot is embedded in BREEZE.rst.
Traceback (most recent call last):
File
"/Users/ephraimbuddy/Documents/astronomer/airflow/dev/breeze/src/airflow_breeze/breeze.py",
line 49, in <module>
main()
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/core.py",
line 1130, in __call__
return self.main(*args, **kwargs)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/rich_click/rich_group.py",
line 21, in main
rv = super().main(*args, standalone_mode=False, **kwargs)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/core.py",
line 1055, in main
rv = self.invoke(ctx)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/core.py",
line 1654, in invoke
super().invoke(ctx)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/core.py",
line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/core.py",
line 760, in invoke
return __callback(*args, **kwargs)
File
"/Users/ephraimbuddy/.cache/pre-commit/repofp_wavck/py_env-python3/lib/python3.10/site-packages/click/decorators.py",
line 26, in new_func
return f(get_current_context(), *args, **kwargs)
File
"/Users/ephraimbuddy/Documents/astronomer/airflow/dev/breeze/src/airflow_breeze/commands/main_command.py",
line 113, in main
check_for_rosetta_environment()
File
"/Users/ephraimbuddy/Documents/astronomer/airflow/dev/breeze/src/airflow_breeze/commands/main_command.py",
line 159, in check_for_rosetta_environment
from inputimeout import TimeoutOccurred, inputimeout
ModuleNotFoundError: No module named 'inputimeout'
Some of the commands changed since last time images were generated.
Image generation is needed. Please run this command:
breeze setup regenerate-command-images
```
Ok. I think I need to install it on my PC
--
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]
