Closed bernhardkaindl closed 2 years ago
Merging #60 (a16fada) into dev (6a4afe8) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## dev #60 +/- ##
=======================================
Coverage 78.67% 78.67%
=======================================
Files 38 38
Lines 2377 2377
=======================================
Hits 1870 1870
Misses 507 507
Flag | Coverage Δ | |
---|---|---|
unittests | 78.67% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 8c258b4...a16fada. Read the comment docs.
@bernhardkaindl Did you manage to figure out why kombu client gets stuck?
@bernhardkaindl Did you manage to figure out why kombu client gets stuck?
No, I see in the rabbitmq log that both stay connected, but the client does not continue sending requests:
From the kombu_server log, I see that the server sends the response for the sum
method, but the client does not have any logger
calls about sending requests or receiving responses.
I think this lack of logging in the kombu client should be fixed next to ease debugging the combu client in general - ok?
@bernhardkaindl Could you report an issue, I suppose I have some guesses.
approved
Thanks, opened issue #66
Implement the
sum(a, b)
andtick
RPC endpoints forkombu_client.py
andaio_pika_client.py
and usequeue_args={"durable": False}
to be able to connect to the"jsonrpc"
queue created byexamples/aio_pika_*.py
. Makes it also interoperable with these examples.examples/kombu_server.py and examples/kombu_client.py appear to have an issue communicating with each other: The RPC gets stuck very often, but server/client cross-operation with examples/aiopika*.py works fine.
This issue is present with the "jsonrpc" set to durable as well.