-
Notifications
You must be signed in to change notification settings - Fork 5.5k
mysql_filter: fix integration test flakes #6272
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
Changes from 2 commits
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 |
|---|---|---|
|
|
@@ -2,7 +2,7 @@ admin: | |
| access_log_path: /dev/null | ||
|
Member
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. Question: Why are we using this config vs. just using the default config and config modifiers? Would that have made it easier to prevent this issue?
Member
Author
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. I think we could have done it either way. However, @gvalentinivmw might know more. We could have still run into this issue as the config modifiers don't constrain IP addresses AFAIK.
Member
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. OK that's fine. It's not a big deal either way, though I think in general it's better to use the stock config in case that changes in the future.
Contributor
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. For the record, I think the problem here is related to a bug I reported a while back: #5556 it'd be nice to make tests that do not care about ports not have to specify anything about them, or care about ipv6 vs ipv4.
Member
Author
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. Yea, that'd definitely be helpful. |
||
| address: | ||
| socket_address: | ||
| address: 127.0.0.1 | ||
| address: "{}" | ||
| port_value: 0 | ||
| static_resources: | ||
| clusters: | ||
|
|
@@ -15,13 +15,13 @@ static_resources: | |
| - endpoint: | ||
| address: | ||
| socket_address: | ||
| address: 127.0.0.1 | ||
| address: "{}" | ||
| port_value: 0 | ||
| listeners: | ||
| name: listener_0 | ||
| address: | ||
| socket_address: | ||
| address: 0.0.0.0 | ||
| address: "{}" | ||
| port_value: 0 | ||
| filter_chains: | ||
| - filters: | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.