Fix incompat of request.form with anyio 4.14.0 in aws auth manager#68834
Open
amoghrajesh wants to merge 1 commit into
Open
Fix incompat of request.form with anyio 4.14.0 in aws auth manager#68834amoghrajesh wants to merge 1 commit into
amoghrajesh wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Was generative AI tooling used to co-author this PR?
Fixes broken CI as seen in https://github.com/apache/airflow/actions/runs/27941132600/job/82677618222, its due to this diff:
anyio 4.14.0 tightened the type stub for
from_thread.runto require a callable returning a plain Coroutine. Starlette'srequest.formreturnsAwaitableOrContextManager[FormData]which is awaitable but not a Coroutine, so mypy now rejects it.Introduce a
small _fetch_formasync helper that wrapsawait request.form()sofrom_thread.runreceives a properly-typed coroutine function, without changing the sync handler architecture.{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.