Change to make Update and Delete entities throw InvalidInput error for Malformed Etag - #2122
Open
PrasantJillella wants to merge 1 commit into
Open
Change to make Update and Delete entities throw InvalidInput error for Malformed Etag#2122PrasantJillella wants to merge 1 commit into
PrasantJillella wants to merge 1 commit into
Conversation
| - Fixed error code when dequeue message with invalid visibilitytimeout (issue #2083) | ||
| - Fixed error code when sas request authentication failed (issue #2064) | ||
|
|
||
| Table: |
Contributor
There was a problem hiding this comment.
Please add it to Upcoming Release above.
Contributor
Author
There was a problem hiding this comment.
Please review PR #2062 instead of this one.
I will remove this PR.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for contribution! Please go through following checklist before sending PR.
PR Branch Destination
mainbranch.legacy-devbranch.Always Add Test Cases
Make sure test cases are added to cover the code change.
Add Change Log
Add change log for the code change in
Upcoming Releasesection inChangeLog.md.Development Guideline
Please go to CONTRIBUTION.md for steps about setting up development environment and recommended Visual Studio Code extensions.