Repository navigation
Conversation
The hook printed a red error and exited zero, so a failed synchronization passed as green and left the generated mounts in local.yml stale. The failure it is most likely to hide is a broken docker_command_utils.py, which is one of the two files that trigger the hook in the first place.
potiuk
added
the
closed because of open PR limit
|
Hello @rjgoyln - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 24 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
Summary
update-local-yml-fileprinted a red error and exited zero whenbreeze setup synchronize-local-mountsfailed, so the hook reported green on a failed synchronization and left the generated volume list inscripts/ci/docker_compose/local.ymlstale.scripts/ci/prek/do.breeze.Two existing guards narrow the silent path without closing it: prek's own "files were modified by this hook" check catches a synchronization that succeeds and rewrites the file, and
initialize_breeze_prekalready exits 1 whenbreezeis not onPATH. What remains is a breeze run that fails — most likely a brokendocker_command_utils.py, which both triggers this hook and supplies the mount list the command reads.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines