Jean Boussier

This looks like the server closing the connection for whatever reason. Not actionable.

Closing as stale. The bug should be solved in 5.x already.

Closing as non actionable. I assume the server is closing the connection for some reason (maybe max-clients?). I don't see anything we can do about it.

Closing this given that the network layer was entirely rewritten in 5.x, so hopefully whatever this bug was is now gone. If some people still notice this issue with redis-rb...

Closing as non-actionable. This whole code has been rewritten in 5.x anyway, so I assume whatever the bug was, it's probably no longer present.

The network layer has been entirely rewritten in 5.x, so I'm going to assume this issue no longer applies. Feel free to comment if you see similar issues on 5.x...

See https://github.com/rails/rails/commit/50d59e9c3e2da833c0122112d744b34f543f4df2

> just call `xmlFreeNode` on them to avoid the parenting overhead. I tried that and got some crashes because the pointers weren't allocated, not too shure what kind of shenanigans...

@maniSHarma7575 it's not a "syntax" difference. One is strings the other is symbols. However your PR is nowhere near enough, this repo contains 3 alternative implementations, one in Ruby, one...

> I'm not sure why expected behavior is correct. Because result of `JSON.dump` is not changed from old version. @hsbt he's not trying to fix a regression, but do prevent...