Remove deprecation warning for cgitb in Plugins Manager #41732
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
2 tasks
Member
Likely it's simply a mistake, |
potiuk
approved these changes
Aug 27, 2024
potiuk
pushed a commit
to potiuk/airflow
that referenced
this pull request
Aug 27, 2024
(cherry picked from commit 83ba17f)
potiuk
added a commit
that referenced
this pull request
Aug 27, 2024
utkarsharma2
pushed a commit
that referenced
this pull request
Sep 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Recently when running Airflow (locally but probably also when deployed) a lot of warnings are emitted by Plugins Manager like:
This is caused by a import in plugins_manager.py - and surprisingly besides this import all other types of the specified list actually use
HookLineageReader- unable to trace this down, this PR removes the import and traces. Less noise in logs.As this also will bother all users in Airfow 2.10, I propose to fix this also in the 2.10 code-line