-
Notifications
You must be signed in to change notification settings - Fork 786
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
The behavior of retry policy is not consistent. #1042
Comments
You are right, maybe it is a problem, for the second one, we just update the status but not remove the method configuration, so it won't do fallback to wildcard. From your scenario, which one do you think it is reasonable? |
I think no fallback makes sense as it is specified to disable the policy. |
It will be marked as todo |
3 tasks
/close |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Kitex has the ability to configure the retry policy dynamically, but the semantics is not consistent in these conditions:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
the behavior of these conditions above should keep consistent.
Screenshots
If applicable, add screenshots to help explain your problem.
Kitex version:
Please provide the version of Kitex you are using.
Environment:
The output of
go env
.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: