Skip to content

Forward native request timeouts through the CLI adapter - #10

Merged
Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/forward-native-timeout
Sep 25, 2026
Merged

Brian Krabach (bkrabach) merged 1 commit into
mainfrom
fix/forward-native-timeout

Conversation

@bkrabach

@bkrabach Brian Krabach (bkrabach) commented Sep 25, 2026 •

Copy link
Copy Markdown
Collaborator

Current provider-owned native transport passes keyword options, including timeout, through _native_response. The host adapter dropped those options and raised TypeError before a native send. Forward the options unchanged while preserving the existing attribution scope and its cleanup.

Regression cases cover omitted timeout, a scalar deadline and None through success, failure and cancellation, checking exact input identity, one dispatch and restored attribution. The current provider remains responsible for deadline semantics; this adds no replay or cancellation behavior.

Validation: 34 native/image adapter tests pass against provider-openai a4a6ad9f, OpenAI SDK 3.19.2, and websockets 16.1.1; no provider calls. This is a separate compatibility fix from manager-error PR #9. Fresh CI also exposed provider-openai's missing runtime httpx dependency, addressed separately in microsoft/amplifier-module-provider-openai#115. The Microsoft and Unified inherited wrappers were checked; the distinct bkrabach adapter owns its older transport and does not inherit this method.

@bkrabach
Brian Krabach (bkrabach) marked this pull request as ready for review September 25, 2026 12:58
@bkrabach
Brian Krabach (bkrabach) merged commit 1d1838f into main Sep 25, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant