[azure-search-documents] Enable HTTPX async transport for AnyIO/Trio callers
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
调研方向
The issue involves modifying the async HTTP transport layer in azure-core to support HTTPX for Trio compatibility. Start by examining the existing async client pipeline in azure/search/documents/aio/_client.py and the related azure-core issue #41382. Understand how transports are configured and swapped. The acceptance test requires running representative async Search/index operations under both asyncio and Trio backends via anyio.run. Focus on ensuring transport ownership and cleanup work correctly with both credential types.
由索引模型根据 Issue 内容生成。
描述
Motivation
Microsoft Agent Framework is exploring AnyIO support so its Python agents can run with either asyncio or Trio. Its Azure AI Search integration uses azure.search.documents.aio.SearchClient and azure.search.documents.indexes.aio.SearchIndexClient (and, when available, the async knowledge-base retrieval client). These clients depend on azure-core; the default azure-core async HTTP transport uses aiohttp, which is asyncio-specific. Agent Framework currently lists aiohttp explicitly for this integration as a consequence. HTTPX's async client supports both asyncio and Trio.
Request
Please provide a supported, documented HTTPX async transport for azure-search-documents, rather than requiring the aiohttp transport to use its async clients. If changing the azure-core async default from aiohttp to HTTPX is acceptable, that would address this; otherwise a stable azure-core HTTPX transport option that can be selected without bringing in aiohttp would suffice. Please include the async Search, index-management, and knowledge-base paths, plus credentials/transport ownership and cleanup, in the backend-compatibility assessment.
The useful acceptance check is the same representative async Search/index operation run under anyio.run(main, backend="asyncio") and anyio.run(main, backend="trio") with no asyncio-only transport in the Trio path (both key-based and async token credentials where supported). This is a request for end-to-end support, not an assertion that substituting one HTTP client alone makes every SDK layer Trio-compatible.
Related work and references
- Shared
azure-coreHTTPX transport request: https://github.com/Azure/azure-sdk-for-python/issues/41382. This issue tracks the Azure AI Search client-level support and coverage. azure-search-documentsdepends onazure-core: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/search/azure-search-documents/pyproject.toml- Async client pipeline: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/search/azure-search-documents/azure/search/documents/aio/_client.py
- Agent Framework integration manifests its current aiohttp dependency: https://github.com/microsoft/agent-framework/blob/main/python/packages/azure-ai-search/pyproject.toml
- HTTPX backend support: https://www.python-httpx.org/async/#supported-async-environments
- 主要语言
- Python
- 星标
- 5.6k
- 派生
- 3.4k
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 194
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Azure/azure-sdk-for-python 的其他 Issue
-
[Teams Chatbot]: Clarify Python dev-feed publication from a branch versus PyPI release可能已有人在做 @jianingwang123 于 12 天前认领。 未关闭customer-reported question
难度 2/5 1-3 小时 新手友好度 62/100
Azure/azure-sdk-for-python#49548 · 1 条评论 · 2 个 reaction · 已指派 2 人 ·
维护者通常 1 天内回复
-
azure-ai-evaluation: a content-harm score of 0 (no harm) is parsed as NaN in _parse_content_harm_response (numeric branch uses 0 < x instead of 0 <= x)可能已有人在做 @pujitha24 于 28 天前认领。 未关闭Evaluation Service Attention
难度 2/5 1-3 小时 新手友好度 84/100
Azure/azure-sdk-for-python#49190 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
Azure/azure-sdk-for-python#49183 · 1 个 reaction ·
维护者通常 1 天内回复
-
azure-ai-evaluation: PromptyEvaluatorBase falls back to the first digit anywhere in the judge's reply, and the threshold turns a stray digit into a wrong pass/fail (15 evaluators)可能已有人在做 @wasim-builds 于 22 天前认领。 未关闭Evaluation Service Attention
难度 2/5 1-3 小时 新手友好度 75/100
Azure/azure-sdk-for-python#49153 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
azure-search-documents ContentUnderstandingSkill is missing model_name and model_deployment可能已有人在做 @wasim-builds 于 22 天前认领。 未关闭Search Service Attention
难度 2/5 1-3 小时 新手友好度 74/100
Azure/azure-sdk-for-python#48555 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
查看 Azure/azure-sdk-for-python 的全部 Issue
相似的 Issue
-
area/config comp/tools P2 platform/telegram type/bug
难度 2/5 1-3 小时 新手友好度 74/100
NousResearch/hermes-agent#145412 ·
维护者通常 1 天内回复
-
[oblt-aw][autodoc] Update docs for security org scaffolding and Docs AI menu permission changes可能已有人在做 @github-actions 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
Community project: hosted MOSS-Image studio with a visual JSON layout builder (no ComfyUI needed)未关闭
难度 1/5 1-3 小时 新手友好度 65/100
OpenMOSS/MOSS-Image#27 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
deepspeedai/DeepSpeed#8925 · 1 条评论 ·
维护者通常 3 天内回复
-
external integration integration-submission
难度 2/5 1-3 小时 新手友好度 68/100
langchain-ai/docs#7077 ·
维护者通常 1 天内回复