1. 29 Dec, 2019 5 commits
    • antirez's avatar
      Fix duplicated CLIENT SETNAME reply. · e61dde88
      antirez authored
      Happened when we set the name to "" to cancel the name.
      Was introduced during the RESP3 refactoring.
      
      See #6036.
      e61dde88
    • Guy Benoish's avatar
      Stream: Handle streamID-related edge cases · cddf1da2
      Guy Benoish authored
      This commit solves several edge cases that are related to
      exhausting the streamID limits: We should correctly calculate
      the succeeding streamID instead of blindly incrementing 'seq'
      This affects both XREAD and XADD.
      
      Other (unrelated) changes:
      Reply with a better error message when trying to add an entry
      to a stream that has exhausted last_id
      cddf1da2
    • Oran Agra's avatar
      config.c adjust config limits and mutable · 52ea44e5
      Oran Agra authored
      - make lua-replicate-commands mutable (it never was, but i don't see why)
      - make tcp-backlog immutable (fix a recent refactory mistake)
      - increase the max limit of a few configs to match what they were before
      the recent refactory
      52ea44e5
    • antirez's avatar
      Inline protocol: handle empty strings well. · 0f28ea16
      antirez authored
      This bug is from the first version of Redis. Probably the problem here
      is that before we used an SDS split function that created empty strings
      for additional spaces, like in "SET    foo          bar".
      AFAIK later we replaced it with the curretn sdssplitarg() API that has
      no such a problem. As a result, we introduced a bug, where it is no
      longer possible to do something like:
      
          SET foo ""
      
      Using the inline protocol. Now it is fixed.
      0f28ea16
    • antirez's avatar
      00e5fefe
  2. 19 Dec, 2019 4 commits
  3. 18 Dec, 2019 8 commits
  4. 17 Dec, 2019 13 commits
  5. 16 Dec, 2019 4 commits
  6. 13 Dec, 2019 1 commit
  7. 12 Dec, 2019 5 commits