-
Notifications
You must be signed in to change notification settings - Fork 492
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
Add DeviceNotOnline to error codes #3444
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Any reason why .NET 6 pipelines fail? Can't view the error since it azure devops. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
We have some security rules in place that make it so forked PRs (like this one) can't access the credentials we use during our integration testing. Could you convert these changes into a branch on this repo instead? |
@timtay-microsoft I do not have permissions to create a branch on this repo |
Ah, my apologies. I'll go ahead and create that branch for you. #3450 should be merged in shortly |
Your fix has been merged in #3450, so I'll close this PR |
Checklist
main
branch.Description of the changes
Added the error code: 404103 for Device online. So users can handle this error gracefully.
Reference/Link to the issue solved with this PR (if any)
Fixes: #3442