Fix standard hedging #4633
Merged
Fix standard hedging #4633
Conversation
This file contains 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
joperezr
added
the
servicing-consider
|
Thanks for the PR @martintmk, we have now began our lock down and stabilization period for 8.0. Do you think this PR is something we should consider for 8.0, or is it okay to let this one be part of 8.1 instead? |
joperezr
removed
the
servicing-consider
Without this PR the standard hedging is basically broken, so is a must from my perspective. |
geeknoid
approved these changes
Oct 30, 2023
|
Chatted with @martintmk offline, this is approved for 8.0 |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hedging should assign the action resilience context to cloned request message, otherwise the inner handler might use incorrect context.
Microsoft Reviewers: Open in CodeFlow