You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Port the .NET failure-handling fix from microsoft/agent-framework#7497 into the shared Go Responses provider path so response.failed events surface structured ErrorContent instead of empty updates. The Go change also applies the same fallback to failed non-streaming responses when the provider omits explicit error details, using a default message/code rather than silently dropping the failure.
No. This keeps the public Go API unchanged and only corrects how existing failed Responses API events are surfaced to callers.
Tests and Examples
go test ./provider/openaiprovider
go test ./provider/foundryprovider
Added coverage for streaming response.failed events and failed responses without explicit provider error details
Notes
Duplicate check: no recent [dotnet-port-fixes] or [dotnet-port-api] issue/PR title in microsoft/agent-framework-go matched this failure-handling area.
The fix is intentionally scoped to the shared OpenAI Responses translation path used by Foundry, so no exported API or docs/example updates were needed.
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch dotnet-port-fixes-response-failed-error-content-5fff6162ef959527.
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Summary
Port the .NET failure-handling fix from microsoft/agent-framework#7497 into the shared Go Responses provider path so
response.failedevents surface structuredErrorContentinstead of empty updates. The Go change also applies the same fallback to failed non-streaming responses when the provider omits explicit error details, using a default message/code rather than silently dropping the failure.Ported .NET PRs
Upstream commit referenced:
d56e81357e5179b6f916b180c0cb34ea2e73c80b.Breaking Changes
No. This keeps the public Go API unchanged and only corrects how existing failed Responses API events are surfaced to callers.
Tests and Examples
go test ./provider/openaiprovidergo test ./provider/foundryproviderresponse.failedevents and failed responses without explicit provider error detailsNotes
[dotnet-port-fixes]or[dotnet-port-api]issue/PR title inmicrosoft/agent-framework-gomatched this failure-handling area.Note
This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
The changes have been pushed to branch
dotnet-port-fixes-response-failed-error-content-5fff6162ef959527.Click here to create the pull request
To fix the permissions issue, go to Settings → Actions → General and enable Allow GitHub Actions to create and approve pull requests. See also: gh-aw FAQ
Show patch preview (230 of 230 lines)