Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
upstream: Implement retry concurrency budgets #9069
upstream: Implement retry concurrency budgets #9069
Changes from 51 commits
ee13f16
413a55a
43804fd
c43f0cd
24e247d
86cd4d5
eb75475
4a4e502
38c53c8
0970941
d5ec251
8d8cde0
e74e782
b11c614
87ca3a8
9a0c03f
f9137c9
4a50f10
ea64ad7
3002bcd
0430c19
8053b7e
8f23bed
9f409e2
91de3ce
92a8188
a50970e
34bc98c
18c5a98
3378b64
baf91ac
193e537
4fc3fb5
f050c30
a2fb127
3bbe93c
f6162c8
1b45679
0d33ec3
49753ce
b635e91
1f02666
6cee795
7d11191
7ce58e7
c318a95
dde62da
2344034
51a8f33
cf9c6ef
9a8e947
0e100d1
ef41c69
81941c0
12198cd
74e5bbb
5285e3e
d3ed226
659f480
61d7057
f70acbe
a77d1f2
105dd0d
0c46399
b9f46ec
c78c39e
bb9e81e
d21677d
4cc50dd
f9cffe0
94f63e8
4fb492a
005317c
dc5f95e
068e0e7
2446f7b
da5fe31
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We no longer allow an inline upgrade to oneof as it is a breaking change for some clients. I would drop the oneof for now and just verify in code that only one of them is set. @htuch @lizan do we have plans to add some type of automatic oneof upgrade annotation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not really necessary to have the oneof there since it's documented in several places that the budget will override the retry CB. I'll take care of that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattklein123 yes, but it's lower priority than rename and package movement, both of which we really need to make v3 sane. I think it wouldn't hurt to add the annotation now; basically something in https://github.com/cncf/udpa/blob/master/udpa/annotations/migrate.proto#L15 that says "add_to_oneof", with a string providing a
oneof
as a target.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: merge order issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this used anymore? I think you have some leftover code?