This repository has been archived by the owner on Mar 24, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 232
pypy snappy compression seg fault on larger messages #508
Labels
Comments
We could also use some tests for this case in |
woh python-snappy could use some love. last code commit was three years ago and there is no CI hooked up. |
from googling. |
emmettbutler
added a commit
that referenced
this issue
Mar 24, 2016
yungchin
added a commit
that referenced
this issue
Apr 13, 2016
* parsely/master: (130 commits) Import sys as _sys Handle intepreter shutdown in RequestHandler fix compare link, increment version changelog, increment version use a None check to enable tests that do not use a Producer enqueue popped message fix NoneType error in producer for large messages Fix then vs than typo handle IllegalGeneration in SimpleConsumer. fixes #515 ensure consumer exists before producing remove self.consumer reference from tearDownClass fix protocol tests for python 3 stop producer tests from sharing a consumer instance. fixes #484 clearer message test and warn about pypy snappy segfaulting on some messages. fixes #508 remove unused import clarify documentation around latest available offsets. fixes #494 reformat protocol tests for readability clean up readme readme note about managed consumer ... Conflicts: pykafka/__init__.py pykafka/broker.py pykafka/connection.py
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a carry over from #480. It is also an upstream python snappy issue but we should track it some how.
So any byte array above a certain size causes a seg fault.
while
passes
Perhaps a warning doc for pypy users.
The text was updated successfully, but these errors were encountered: