Closed Gyllsdorff closed 5 years ago
It's an odd edge case. You're not publishing, but you're enabling publisher confirms. I'll have to recreate and see if I can trace down where things are going awry. I'm not quite sure what could cause that.
I've not been able to reproduce this with your example, with an ack or without.
I'm wondering if your example is not complete and perhaps you are publishing in the consumer?
Also as a FYI you should be able to just do message.json()
to get the JSON body of a message.
I was not able to confirm this. In my latest test, I tried republishing the message that was being consumed and I was still not able to reproduce.
I did however find an issue with Basic.Nack
support out of the ticket. Can you provide sample code that proves out the issue?
I have seen this happen once as well in my own library (based on pamqp). I was never able to re-produce it.
I have a queue with messages with a json string body and a few headers.
When I enabled
enable_publisher_confirms
I suddenly got a lot ofjson.loads(message.body.decode())
errors. When I dumped the message contents I noticed that two message bodies have been concatenated.When I removed
enable_publisher_confirms
the problem disappears.This is a short dev script so I never do
message.ack()
. Can that be what triggers this bug?