Skip to content

Conversation

@philipthomas-MSFT
Copy link
Contributor

Description

Fixes an issue when Error string/stream from Gateway response cannot be deserialized.
For more information, see #4162

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

Closing issues

To automatically close an issue: closes #4162

@philipthomas-MSFT philipthomas-MSFT marked this pull request as draft January 4, 2024 14:07
@philipthomas-MSFT philipthomas-MSFT self-assigned this Jan 4, 2024
@philipthomas-MSFT philipthomas-MSFT marked this pull request as ready for review January 4, 2024 22:41
Copy link
Member

@ealsur ealsur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great progress! Thanks for doing this

ealsur
ealsur previously approved these changes Jan 9, 2024
Copy link
Member

@ealsur ealsur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a few small nits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge Enables automation to merge PRs

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Handle invalid JSON HTTP response from Gateway for error scenarios

5 participants