Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

agentdev run recurses while patching ResponsesHostServer with current Agent Framework hosting

未关闭
  • 哪里不对？
#893 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
66/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend, devtools

调研方向

Start by locating _PatchingFinder.find_spec and _patch_foundry_hosting_module in the agentdev import hook, then trace how _patched is set around the patch call. Reproduce with the listed Python and Agent Framework versions using the provided agentdev run command. Done means the hosting patch completes without recursive import failure and the agent server starts on port 8088.

由索引模型根据 Issue 内容生成。

描述

needs attention

Bug description

agentdev run crashes with a RecursionError before the hosted agent starts when used with the current agent-framework-foundry-hosting package. The recursion occurs in agentdev's import hook while it tries to patch ResponsesHostServer; the hosting package resolves that attribute lazily, and the resulting submodule import re-enters the same hook.

Environment

  • OS: Windows 11
  • Python: 3.11
  • agent-dev-cli==0.0.1b260427 (latest available when tested)
  • agent-framework-core==1.19.0
  • agent-framework-foundry==1.13.1
  • agent-framework-foundry-hosting==1.0.0b260918
  • azure-ai-agentserver-responses==2.2.0

The agent framework versions are pinned by the application. agent-dev-cli==0.0.1b260427 declares agent-framework-core>=1.1.1,<1.3.0, which conflicts with core 1.19.0. A normal pip install proposes downgrading core to 1.2.2, so the CLI was installed with --no-deps to preserve the application's pinned dependencies. Its websockets>=13.0 dependency was installed separately.

Steps to reproduce

  1. Create a Python 3.11 virtual environment.

  2. Install the versions listed above, then install agent-dev-cli==0.0.1b260427 with --no-deps (and its websockets>=13.0 dependency).

  3. Use an agent entrypoint that imports AgentSessionStoreProvider and ResponsesHostServer from agent_framework_foundry_hosting and hosts the agent with ResponsesHostServer.run_async().

  4. From the directory containing main.py, run:

    python -m agentdev run main.py --port 8088 --verbose

Actual result

The agentdev bootstrap reports that import hooks were installed, then startup fails with RecursionError during imports. The repeated call path is:

_PatchingFinder.find_spec → _check_and_patch → _patch_foundry_hosting_module → hasattr(module, ResponsesHostServer) → agent_framework_foundry_hosting.__getattr__ → importlib.import_module → _PatchingFinder.find_spec again.

In the tested hook, _patched is set only after the patch function returns, so it does not prevent this re-entrant call. The process exits before binding port 8088; readiness/health endpoints are unavailable.

Expected result

agentdev run should complete the hosting patch and start the agent server on the requested port without recursive import failure.

Additional context

Running the entrypoint without agentdev does not produce this recursion. The standalone process completes imports (about 9 seconds on a warm run, about 30 seconds on a cold run) and proceeds to agent initialization. This isolates the reported RecursionError to agentdev's patch/import-hook path. The local standalone run later encountered separate Azure CLI credential expiration, unrelated to this issue.

A possible fix is to establish a re-entrancy guard before calling the patch routine, or avoid attribute access that invokes module-level __getattr__ while inspecting the hosting module.

主要语言
JavaScript
星标
2.1k
派生
262
平均合并
17 小时 25 分钟
30 天内合并 PR
28

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

microsoft/foundry-dev-tools 的其他 Issue

查看 microsoft/foundry-dev-tools 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。