Reset sync stream on retry (#11677) #24274
Conversation
* Fixes to stream reset on retry. Needs cleanup and test * Clean up and docs * Cleanup and added test * Ci fixes * PR feedback * Ci
rickle-msft
requested review from
alzimmermsft,
amishra-dev,
gapra-msft,
jaschrep-msft and
sima-zhu
as code owners
ghost
added
the
|
/azp run azure - storage - tests |
|
No pipelines are associated with this pull request. |
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - storage - ci |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
|
/azp run java - storage - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - storage |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Release network microsoft.network official 2023 02 01 (Azure#24277) * Adds base for updating Microsoft.Network from version stable/2022-11-01 to version 2023-02-01 * Updates readme * Updates API version in new specs and examples * Fixed double header issue (Azure#23896) * Edited description for additional nics (Azure#24071) * swagger 20230201 adding resource guid (Azure#24154) * Appgw: Remove 499 status code from custom error page (Azure#24095) * Add AdminState Property to Virtual Network Gateway Resource Properties (Azure#23978) * add adminstate * update description * add headers to 202 * prettier fix * AppGW: Add default predefined ssl policy field in resource (Azure#24094) * Fix examples (Azure#24274) --------- Co-authored-by: Mikhail <mitryakh@microsoft.com> Co-authored-by: JainRah <108508612+JainRah@users.noreply.github.com> Co-authored-by: sssharma24 <107450300+sssharma24@users.noreply.github.com> Co-authored-by: Prateek Sachan <42961174+prateek2211@users.noreply.github.com> Co-authored-by: nimaller <71352534+nimaller@users.noreply.github.com> Co-authored-by: Sindhu Aluguvelli <sindhureddy216@gmail.com>
Fixes to stream reset on retry. Needs cleanup and test
Clean up and docs
Cleanup and added test
Ci fixes
PR feedback
Ci