1. 05 Sep, 2019 1 commit
  2. 04 Sep, 2019 1 commit
    • antirez's avatar
      redis-cli: always report server errors on read errors. · 08b03e23
      antirez authored
      Before this commit we may have not consumer buffers when a read error is
      encountered. Such buffers may contain errors that are important clues
      for the user: for instance a protocol error in the payload we send in
      pipe mode will cause the server to abort the connection. If the user
      does not get the protocol error, debugging what is happening can be a
      nightmare.
      
      This commit fixes issue #3756.
      08b03e23
  3. 31 Jul, 2019 4 commits
  4. 30 Jul, 2019 1 commit
  5. 07 Jul, 2019 3 commits
  6. 15 May, 2019 3 commits
    • antirez's avatar
      Redis 5.0.5 · c696aebd
      antirez authored
      c696aebd
    • antirez's avatar
      Narrow the effects of PR #6029 to the exact state. · 668661da
      antirez authored
      CLIENT PAUSE may be used, in other contexts, for a long time making all
      the slaves time out. Better for now to be more specific about what
      should disable senidng PINGs.
      
      An alternative to that would be to virtually refresh the slave
      interactions when clients are paused, however for now I went for this
      more conservative solution.
      668661da
    • chendianqiang's avatar
      stop ping when client pause · 3c2800e3
      chendianqiang authored
      3c2800e3
  7. 13 May, 2019 21 commits
  8. 10 May, 2019 6 commits