Closed aphyr closed 9 years ago
Spoke too soon; looks like you might have fixed this between 5df8e1d7838d7bea0bd9cf187922a1469d1bb252 and f00dd0704128707f7a5effccd5837d796f2c01e3 :)
Hi @aphyr , the bug was already fixed in https://github.com/antirez/disque/commit/53ef7b7eb3440c8fdf02e989e7bc83c82a7262c5 :-)
Pretty amazing this was reproducible with Jensen. The bug literally tortured us for weeks! And indeed involved a given sequence of messages in an order that is hard to get if the network acts in a reliable way. On Jul 3, 2015 4:12 AM, "Sun He" notifications@github.com wrote:
Hi @aphyr https://github.com/aphyr , the bug was already fixed in 53ef7b7 https://github.com/antirez/disque/commit/53ef7b7eb3440c8fdf02e989e7bc83c82a7262c5 :-)
— Reply to this email directly or view it on GitHub https://github.com/antirez/disque/issues/97#issuecomment-118211405.
A network partitions test (available on Jepsen a1938c734460f9180ab68177aafc299fb6a09f36) seems to reliably segfault Disque: