peter-csala

Can you please provide some feedback?

Health is the number one priority nowadays, so no worries. :) I could not found anything about v8's new configuration process under the [v8 pull request](https://github.com/App-vNext/Polly/pull/748). Where can I find...

Hi @reisenberger, is there any progress regarding this feature suggestion?

@martincostello Please assign to me, otherwise I will forget it :)

After the V8 migration I can not reproduce the problem. The application can be stopped any time.  @martincostello I think we can close this issue if you agree.

@martincostello I've updated the samples to use the current API. I've also respected the anti-pattern regarding mixture of result and exception usage. Could you please check it again?

Here is an example how to achieve it: ```cs new ResiliencePipelineBuilder() .AddRetry(new() { MaxRetryAttempts = 3, ShouldHandle = async args => { if(args.Outcome.Result is not null) { HttpResponseMessage message =...

Sorry I assumed that you are using the V8 API, not the V7. Tomorrow I'll post the V7 version.

In case of V7 you have several ways to achieve the desired behaviour. In the below samples I'll use `HttpResponseMessage` because I'm more familiar with that compared to Flurl. But...

@martintmk It seems good to me. Regarding to the renaming. I agree with the `OnHandled` and `OnUnhandled` prefixes but we pass both the `context` and the `outcome` to the methods....