-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Improve startup information printed when Breeze starts #58926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted.
9b35e93 to
30eb022
Compare
jason810496
approved these changes
Dec 2, 2025
Member
jason810496
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix!
github-actions bot
pushed a commit
that referenced
this pull request
Dec 2, 2025
…58926) We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted. (cherry picked from commit 6c50b62) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 2, 2025
…58926) We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted. (cherry picked from commit 6c50b62) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 2, 2025
…58926) (#58927) We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted. (cherry picked from commit 6c50b62) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Dec 3, 2025
…58926) (#58927) We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted. (cherry picked from commit 6c50b62) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
RoyLee1224
pushed a commit
to RoyLee1224/airflow
that referenced
this pull request
Dec 3, 2025
We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted.
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output. The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary. This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


We were using lru_cache to only print environment check output once, but the method was called once with quiet = False and once without, which made it double-print the output.
The check was done in both - commmands and "docker_utils.enter_shell" and that was really unnecessary.
This PR changes it so that environment check is done only once at the command entry, also the "executable bit" information that was somewhat useless is now replaced with printing a detailed version of Python used - which might help with diagnostics of some strange issues in case the output is copy&pasted.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.