Closed mvarela closed 2 years ago
@mvarela We have got this problem too, I discover that some lib use [funcool/promesa "6.0.0"]
and protojure use [funcool/promesa "3.0.0"]
and We're using deps.edn and remove :exclusions [funcool/promesa], but we're trying to fix this problem too, but We don't have some idiomatic solution yet.
IIRC, theres just a small amount of work to do to port to promesa 6.0.0, largely in the area of p/promise -> p/create. Is this the only issue, or is something broken too?
This is the only issue I've noticed. Thanks for having a look!
Just an update that I took a look at upgrading from promesa 3.0.0 to 6.0.0, but ran into a snag where the UTs were failing and I havent had a chance to track it down. Will address when I can.
Thanks, Gregory!
FYI v1.7.0 was released with an update to promesa v6.0
Hi! I'm new to grpc, and trying to use your library to access an in-house grpc service implemented in .NET. I've created the proto file describing the service, and used the clojure protoc plugin to generate the client code, as per the protojure docs.
When doing the following:
I get the following output:
Trace logging shows:
The interesting thing, however, is that I'm running Wireshark, sniffing for localhost traffic to the service port, and no packets are seen (however, if I run
telnet 127.0.0.1 30420
, I see traffic, so the capture seems to be well setup).I run the code in the cider debugger, and it seems that the issue is somewhere in
protojure.internal.grpc.client.providers.http2.core/receive-payload
It seems that
receive-payload
expects a map inresponse
, but the actual value for it isI've checked whether that function might behave as a map (didn't seem likely, from the name), and it does not (calling it with
:status
as a parameter throws).Any ideas of what could be the cause for this error? I'm currently at a loss...