-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
testing: update Go to 1.19 #5717
Changes from 2 commits
b6d2646
60e30ec
f43eb33
bd15195
e39236f
a1f6c85
dcb733c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -116,28 +116,31 @@ type lbConfigJSON struct { | |
// When parsing a config update, the following validations are performed: | ||
// - routeLookupConfig: | ||
// - grpc_keybuilders field: | ||
// - must have at least one entry | ||
// - must not have two entries with the same `Name` | ||
// - within each entry: | ||
// - must have at least one `Name` | ||
// - must not have a `Name` with the `service` field unset or empty | ||
// - within each `headers` entry: | ||
// - must not have `required_match` set | ||
// - must not have `key` unset or empty | ||
// - across all `headers`, `constant_keys` and `extra_keys` fields: | ||
// - must not have the same `key` specified twice | ||
// - no `key` must be the empty string | ||
// - must have at least one entry | ||
// - must not have two entries with the same `Name` | ||
// - within each entry: | ||
// - must have at least one `Name` | ||
// - must not have a `Name` with the `service` field unset or empty | ||
// - within each `headers` entry: | ||
// - must not have `required_match` set | ||
// - must not have `key` unset or empty | ||
// - across all `headers`, `constant_keys` and `extra_keys` fields: | ||
// - must not have the same `key` specified twice | ||
// - no `key` must be the empty string | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Some of these are sub bullet points. How do we handle these with the new formatting? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Missed this. It looks really bad without a marker at the start of the line. I used |
||
// - `lookup_service` field must be set and must parse as a target URI | ||
// - if `max_age` > 5m, it should be set to 5 minutes | ||
// - if `stale_age` > `max_age`, ignore it | ||
// - if `stale_age` is set, then `max_age` must also be set | ||
// - ignore `valid_targets` field | ||
// - `cache_size_bytes` field must have a value greater than 0, and if its | ||
// value is greater than 5M, we cap it at 5M | ||
// value is greater than 5M, we cap it at 5M | ||
// | ||
// - routeLookupChannelServiceConfig: | ||
// - if specified, must parse as valid service config | ||
// | ||
// - childPolicy: | ||
// - must find a valid child policy with a valid config | ||
// | ||
// - childPolicyConfigTargetFieldName: | ||
// - must be set and non-empty | ||
func (rlsBB) ParseConfig(c json.RawMessage) (serviceconfig.LoadBalancingConfig, error) { | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
This one was a sub-bullet earlier. Sorry, missed this in the last pass.
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.
Fixed