Uh oh!
There was an error while loading. Please reload this page.
add --no-transform-percent to flynt to avoid transform logging text to f-string which conflicts check-lazy-logging hook - #36677
Closed
Lee-W wants to merge 1 commit into
Closed
Conversation
Lee-Wforce-pushed
the
disable-flynt-transform-on-percent
branch
3 times, most recently
from
January 9, 2024 10:54
fb0bc68 to
160cdacCompare
This was referenced Jan 9, 2024
…form loggging text to f-string which conflict check-lazy-logging hook
Lee-Wforce-pushed
the
disable-flynt-transform-on-percent
branch
from
January 9, 2024 14:32
160cdac to
2ded0fbCompare
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
airflow/.pre-commit-config.yaml
Line 248 in 8e8c080
airflow/.pre-commit-config.yaml
Line 984 in 8e8c080
^ 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 newsfragments.