-
Notifications
You must be signed in to change notification settings - Fork 82
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
Remove TLS from gRPC samples #196
Conversation
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.
Left a few comments re port fixing and missing changes on the scala sample.
grpc-example/grpc-example-java/hello-proxy-impl/src/main/resources/application.conf
Show resolved
Hide resolved
8c859e4
to
96c56b6
Compare
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.
Just a minor thing...
605d431
to
58e55e5
Compare
The build failed both gRPC jobs in what seems like a dirty cache (invalid ap-cassandra.jar ZIP format) |
Yeah, I was looking into that, but it's one gRPC job and a Couchbase one. Surprisingly enough none of them should be using the cassandra embedded server as far I can tell. 🤷♂️ |
|
Well, Cassandra is not enabled. And I got this other error, which is blocking this PR anyway: java.lang.IllegalArgumentException: Creation of a gRPC client is useless. The ServiceTest.TestServer must be setup with SSL enabled.
at com.lightbend.lagom.javadsl.testkit.grpc.AkkaGrpcClientHelpers.grpcClient(AkkaGrpcClientHelpers.java:95)
at com.lightbend.lagom.javadsl.testkit.grpc.AkkaGrpcClientHelpers.withGrpcClient(AkkaGrpcClientHelpers.java:65)
at com.lightbend.lagom.javadsl.testkit.grpc.AkkaGrpcClientHelpers.withGrpcClient(AkkaGrpcClientHelpers.java:42)
at com.example.hello.impl.HelloServiceTest.lambda$shouldSayHelloUsingGrpc$89d0e00e$1(HelloServiceTest.java:33)
at com.lightbend.lagom.javadsl.testkit.ServiceTest$.withServer(ServiceTest.scala:318)
at com.lightbend.lagom.javadsl.testkit.ServiceTest.withServer(ServiceTest.scala)
at com.example.hello.impl.HelloServiceTest.shouldSayHelloUsingGrpc(HelloServiceTest.java:31)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) |
@ignasi35, the tests are fixed now. I'm creating the clients directly without using the I'm wondering if it's worth to keep |
...c-example-scala/hello-impl/src/test/scala/com/example/hello/impl/HelloServiceNoSslSpec.scala
Show resolved
Hide resolved
grpc-example/grpc-example-scala/hello-proxy-impl/src/main/resources/logback.xml
Show resolved
Hide resolved
Yeah, that'll simplify things a lot. Let's move that direction. |
raised playframework/play-grpc#322 |
@@ -13,6 +13,7 @@ env: | |||
global: | |||
- TRAVIS_JDK=11 | |||
- JABBA_HOME=$HOME/.jabba | |||
- RUN_DROP_TRAVIS_CACHES_STAGE=true |
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.
I will revert this to false, but first want to have at least one green build.
Last time I created a custom build and set var to true
it didn't work as expected. So forcing it now to move with this PR.
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 instead of hardcoding the ENV_VAR we should remove this line andd set the ENV_VAR on the build settings in the Travis UI
@@ -13,6 +13,7 @@ env: | |||
global: | |||
- TRAVIS_JDK=11 | |||
- JABBA_HOME=$HOME/.jabba | |||
- RUN_DROP_TRAVIS_CACHES_STAGE=true |
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 instead of hardcoding the ENV_VAR we should remove this line andd set the ENV_VAR on the build settings in the Travis UI
@ignasi35, running now without the var. The var is already added to the settings (defaults to true). Once green, I will force a new build just to verify everything is expected. And then we merge. |
@ignasi35, it failed again when running without the var, but after a clean build. I will just restart the build (var is in settings now). |
c30893d
to
e998047
Compare
No description provided.