Update AddTransientHttpErrorPolicy once Polly v7 is released
See original GitHub issueI’m not sure if you are already aware of this, but Polly v7 will distinguish between RetryPolicy
and AsyncRetryPolicy
. Since all methods on the HttpClient
are async, it would make sense if AddTransientHttpErrorPolicy
only accepted AsyncPolicy
(note: not IAsyncPolicy
since the sync version of RetryPolicy also implements that interface for some weird reason).
https://github.com/App-vNext/Polly/wiki/Polly-v7-breaking-changes
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (8 by maintainers)
Top Results From Across the Web
Update AddTransientHttpErrorPolicy once Polly v7 is ...
No changes to AddTransientHttpErrorPolicy(...) will be necessary to take advantage of Polly v7 cleaning up the sync/async split in Polly.
Read more >PollyHttpClientBuilderExtensions. ...
The policy builder will be preconfigured to trigger application of the policy for requests that fail with conditions that indicate a transient failure....
Read more >Microsoft.Extensions.Http.Polly 7.0.10
Version Downloads Last updated
8.0.0‑preview.7.23375.9 6,179 12 days ago
8.0.0‑preview.6.23329.11 8,450 a month ago
8.0.0‑preview.5.23302.2 6,267 2 months ago
Read more >Polly + API Services That Return Errors as Results
AddTransientHttpErrorPolicy will check the followings: 408 Timeout; 5xx Server error; HttpRequestException. So as you can see neither 400, 404, ...
Read more >The CORRECT way to implement Retries in .NET - YouTube
I've been using Polly for a long time. One of the things you have to be careful of though is when making HttpRequests...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll catch up with @glennc and discuss with him. I can’t think of a reason why we wouldn’t do this. We want users to get the best version of things.
This is done!