Bad Frame Read about librabbitmq HOT 13 OPEN

I'd appreciate any suggestions on how to further debug this.

from librabbitmq.

We're seeing bad frame reads, too but in /librabbitmq/__init__.py, in drain_events.

from librabbitmq.

This looks very similar to #30

There is a bug at https://github.com/celery/librabbitmq/blob/master/Modules/_librabbitmq/connection.c#L1343 where an empty (0 byte) body always triggers an exception, even if it was deliberately sent as empty.

I have a patch that fixes this issue in my env in pull request #59.

from librabbitmq.

Any news?

from librabbitmq.

That patch #59 has been merged. Try upgrading to 1.6.x and see if you still have the issue.

from librabbitmq.

I believe you missed this merge when releasing 1.6.1:

https://github.com/celery/librabbitmq/commits/v1.6.1 < contains no
commit abbd949

Can you please release 1.6.2?

from librabbitmq.

👍 could you please release 1.6.2 ?

from librabbitmq.

@ask could you release a new version with the fix for this?

from librabbitmq.

I have the last version and still getting this Bad Frame Read issue, anyone fixed it ?

from librabbitmq.

1.6.1 hasn't got this fix IIRC. It's in master and the 1.6 branch though, so checking out either should get around the problem.

from librabbitmq.

Hello,

Any news about 1.6.2?

from librabbitmq.

I get "bad frame read" exception in 1.6.1. maybe I should use other amqp lib instead of librabbitmq.

from librabbitmq.

It's been a couple years since I issued a patch for this bug.
#59 (comment)

from librabbitmq.