-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArgumentException when using QoSOptions with only TimeoutValue set #1475
Comments
Looks like this PR should fix the problem: #1279 The documentation even says you can set the Timeout option on its own but it breaks it :\ |
I also ran into this issue today. #908 describes the same issue and as @LukePammant already mentioned, there is a PR that would fix this. Would be great to have this fix. In the mean time the workaround is to simply add all three options as described in step 6/8 of this issue. |
Oh hello. I ran into this issue again today using v18.0.0 and ended up finding this issue again. :) Would be great if PR #1279 would be merged and a new version could be created. |
This issue is still not fixed |
Dear community, |
Expected Behavior / New Feature
According to documentation, it should be possible to set only TimeoutValue in QoSOptions.
Actual Behavior / Motivation for New Feature
When setting only TimeoutValue in QoSOptions, an ArgumentException occurs:
When adding ExceptionsAllowedBeforeBreaking and DurationOfBreak the exception disappears. I have this exception since I've upgraded from v15.0.0 to v17.0.0 and installed Ocelot.Provider.Polly.
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: