Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix some ErrorCode in IotHubServiceException #3254

Merged
merged 6 commits into from
Apr 7, 2023

Conversation

brycewang-microsoft
Copy link
Contributor

In the case of mapping HttpRequestException into IotHubServiceException, we manually put "RequestTimeout" as StatusCode and "Unknown" as ErrorCode as there's nothing actually returned from the service. Now we add a new ErrorCode "GenericRequestTimeout" and use that instead.

Also addressing a few more fixes in this PR.

@brycewang-microsoft
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@brycewang-microsoft
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@brycewang-microsoft
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@brycewang-microsoft brycewang-microsoft merged commit dc54669 into previews/v2 Apr 7, 2023
@brycewang-microsoft brycewang-microsoft deleted the brycewang/long-haul-exception branch April 7, 2023 18:09
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.

4 participants