Remove mypy errors from semantic merge problems due to Internal API removal #44528
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
boring-cyborg
bot
added
area:providers
provider:edge
ashb
approved these changes
Dec 1, 2024
eladkal
approved these changes
Dec 1, 2024
Member
|
Nice! |
got686-yandex
pushed a commit
to got686-yandex/airflow
that referenced
this pull request
Jan 30, 2025
jscheffl
deleted the
hotfix/prevent-mypy-errors-in-edge-with-internal-api-removed
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
I found more mypy errors on main due to parallel removal of AIP-44 internal API calls. This time (again) cause by me merging a PR that was checked in parallel and generated semantic check problems ... it was #44330
Hope to get rid of this state when PR #44434 is merged, but this also was not building and is not fully reviewed.