1. 31 Jul, 2022 1 commit
  2. 07 Jul, 2022 1 commit
  3. 05 Jul, 2022 3 commits
  4. 26 Jun, 2022 12 commits
  5. 04 May, 2022 1 commit
  6. 24 Apr, 2022 1 commit
    • Orgad Shaneh's avatar
      Fix warnings on Win64 · eedb37a6
      Orgad Shaneh authored
      read.c:399:27: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
        399 |                     obj = (void*)(long)cur->type;
            |                           ^
      eedb37a6
  7. 23 Apr, 2022 4 commits
  8. 22 Apr, 2022 2 commits
  9. 05 Apr, 2022 2 commits
  10. 29 Mar, 2022 1 commit
  11. 24 Mar, 2022 1 commit
  12. 18 Mar, 2022 1 commit
  13. 03 Feb, 2022 1 commit
    • Björn Svensson's avatar
      Handle any pipelined unsubscribe in async · 7123b87f
      Björn Svensson authored
      Redis responds to an unsubscribe with one or many replies, depending
      on the current subscribe state. When channels/patterns names are
      provided in a command each given name will trigger a reply even if
      duplicated or not subscribed to.
      To know when we can return from the subscribed state we need to do
      bookkeeping on pending additional unsubscribe replies, and make sure
      we receive them all before switching state.
      7123b87f
  14. 02 Feb, 2022 2 commits
  15. 01 Feb, 2022 4 commits
  16. 28 Jan, 2022 1 commit
    • Bjorn Svensson's avatar
      Avoid incorrect call to the previous reply's callback (#1040) · be41ed60
      Bjorn Svensson authored
      * No reuse of the previous reply callback
      
      When multiple replies are parsed from a socket in one read
      a previously found callback might get reused when the current
      reply has no known callback.
      
      This can be triggered by the added testcase which unsubscribe to
      subscribed (A,B) and a non-subscribed channel (X).
      Without this correction a callback for wrong channel is called.
      -  In 'unsubscribe B X A', B's callback is called when handling X.
      -  Now this is not done, i.e. there is no callback called for X.
      
      * Re-push monitor callback for each reply
      
      MONITORING used the same callback for all replies while parsing
      multiple responses. This handling was changed to avoid calling
      the wrong callback in some scenarios.
      Now also change monitorings repush to work with this change.
      
      Includes an added async monitoring testcase.
      be41ed60
  17. 24 Jan, 2022 1 commit
  18. 18 Jan, 2022 1 commit