Running reflect on a tls endpoint gives porting error

[michealroberts]

Describe the bug

To reproduce

So I have deployed a very simple connect-go service to Google Cloud Run, whereby I receive an endpoint. I then run the following command e.g.,

evans --tls --host https://service-name-***.region.run.app -r

And I receive this error:

evans: failed to run REPL mode: failed to instantiate a new spec: failed to instantiate the spec: failed to list packages by gRPC reflection: failed to list services from reflection enabled gRPC server: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: address https://service-name-***.region.run.app:50051: too many colons in address"

Please note, in the above I have changed the default URL endpoint in this example.

However, as you can see evans is looking at: https://service-name-***.region.run.app:50051: ...

I have confirmed that it is running by using a simple client:

This also logs on the server:

So I feel I have confirmed that the service is running, healthy and can call the rpc I am targeting.

I think how evans extracts the default port here is an issue ... perhaps it is the command I am using? It might need some extra blanked port information?

Expected behavior

Evans should be able to detect the reflection from that service.

Screenshots

n/a

Environment

• OS: macOS Sanoma Version 14.5 (23F79)
• Terminal: Hyper but also default Mac Terminal, and vscode terminal
• Evans version: evans 0.10.11

Additional context

n/a