-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hedis hangs on reading big zset #15
Comments
It looks like this bug is only present when the library is compiled with profiling on. I recompiled with profiling off and this bug went away. The tip off to look examine the weather the profiling level was on or off was the repeated use of |
Just tried GHC 7.8. Profiling-enabled hedis still goes into the loop. Profiling-disabled finishes it's work, but instead of result prints "RedisBug: ConnectionLost" twice, strace for non-profiling version run: |
Update: played a bit with non-profiling version. Most of the time it does hang, sometimes it works good, and I saw this "ConnectionLost" only when running with strace. |
Seems part of hang is due to attoparsec bug haskell/attoparsec#70 Downgrading to 0.11.3.4 helps. @Davorak mentioned that this doesn't fix all errors, since code from original report still fails on his machine with 0.11 versions of attoparsec producing output
|
Also got bitten by this while using hedis and had to downgrade to < attoparsec 0.12. Is there a fix in sight? Specifically, rpop on a fairly large value hangs indefinitely. |
@ozataman fix is quite straight-forward -- fix attoparsec's behaviour and make a pull-request! |
Thanks, but we can’t all be solving all the problems we encounter in OSS. I was more interested in bumping the issue and finding out if anybody had anything in the works.
|
So, this is now working with latest attoparsec. |
Here is a piece of code:
You can comment out 2 lines that fill redis after first time you run it. On my machine, this hangs with redis 2.6. Also tried with latest 2.8 one.
strace output: https://gist.github.com/k-bx/cd3cb178412ea9c50e71
The text was updated successfully, but these errors were encountered: