peter-csala

Please bear in mind that it is safe only if you create a new `ResilienceContext` per execution! ## New context for each execution ```cs var taskIdKey = new ResiliencePropertyKey("TaskId"); var...

At the end of March or beginning of April, I can start working on this. @martincostello you can assign this ticket to me.

I was thinking to create sample codes (with reference links) to the followings: - HttpClient - RestSharp - Flurl - Refit - (Kiota) What do you guys think? Is it...

@MannusEtten Could you please check [this documentation page](https://www.pollydocs.org/community/http-client-integrations.html)? Does it address your concerns? If so, could you please close this issue?

Hey @MannusEtten, I was on holiday last week so, apologize for the late response. In case of Polly you can decorate a HTTP network call with resilience behavior either explicitly...

Your proposed solution (as far as I understand) works with single exception type only. You can't chain them. IMHO having different classes for simple and advanced scenarios does not help...

@Mahantesh-DotNet Please allow me to reformat your shared code fragment to make it more legible ### Retry 1 ```cs /// /// Retry these codes for 3 times for every second...

@Mahantesh-DotNet No, your implementation does not work correctly. Let me demonstrate it. Here is a simplified version of your code: ```cs public static async Task Main() { var strategy =...

Whenever the CB is open then you don't have to retry immediately because it will fail with a `BrokenCircuitException`. I would recommend the following approach instead: ```cs static IAsyncPolicy RetryBrokenCircuit()...

> I am thinking, how about we add a `Outcome Outcome` field to existing `BreakDurationGeneratorArguments`? That could solve the breaking change problem. But the usage of the `Outcome` would be...