-
Notifications
You must be signed in to change notification settings - Fork 33
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
Spring boot 3.1.2 #398
Spring boot 3.1.2 #398
Conversation
...src/test/kotlin/pl/allegro/tech/servicemesh/envoycontrol/groups/NodeMetadataValidatorTest.kt
Show resolved
Hide resolved
9f765b1
to
eb572b4
Compare
...trol-tests/src/main/kotlin/pl/allegro/tech/servicemesh/envoycontrol/reliability/Toxiproxy.kt
Show resolved
Hide resolved
...sts/src/main/kotlin/pl/allegro/tech/servicemesh/envoycontrol/EndpointMetadataMergingTests.kt
Outdated
Show resolved
Hide resolved
...runner/src/main/kotlin/pl/allegro/tech/servicemesh/envoycontrol/chaos/api/ChaosController.kt
Outdated
Show resolved
Hide resolved
4d976e3
to
620b841
Compare
620b841
to
213d4ee
Compare
213d4ee
to
0d542b8
Compare
import java.net.ServerSocket | ||
import pl.allegro.tech.servicemesh.envoycontrol.logger | ||
|
||
object Ports { |
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.
Maybe it can be moved to test, because it is only used there
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.
moving Ports to test causes errors in envoy-control-tests
, since it has evony-control-core
as a dependency
No description provided.