1. 24 Jan, 2018 1 commit
  2. 09 Jan, 2018 1 commit
  3. 04 Dec, 2017 1 commit
  4. 01 Dec, 2017 9 commits
  5. 30 Nov, 2017 1 commit
  6. 24 Nov, 2017 1 commit
  7. 23 Nov, 2017 1 commit
    • Oran Agra's avatar
      fix string to double conversion, stopped parsing on \0 even if the string has more data. · adf2701c
      Oran Agra authored
      getLongLongFromObject calls string2ll which has this line:
      /* Return if not all bytes were used. */
      so if you pass an sds with 3 characters "1\01" it will fail.
      
      but getLongDoubleFromObject calls strtold, and considers it ok if eptr[0]==`\0`
      i.e. if the end of the string found by strtold ends with null terminator
      
      127.0.0.1:6379> set a 1
      OK
      127.0.0.1:6379> setrange a 2 2
      (integer) 3
      127.0.0.1:6379> get a
      "1\x002"
      127.0.0.1:6379> incrbyfloat a 2
      "3"
      127.0.0.1:6379> get a
      "3"
      adf2701c
  8. 30 Oct, 2017 1 commit
  9. 13 Aug, 2017 1 commit
  10. 03 Jul, 2017 1 commit
    • antirez's avatar
      Fix GEORADIUS edge case with huge radius. · b2cd9fca
      antirez authored
      This commit closes issue #3698, at least for now, since the root cause
      was not fixed: the bounding box function, for huge radiuses, does not
      return a correct bounding box, there are points still within the radius
      that are left outside.
      
      So when using GEORADIUS queries with radiuses in the order of 5000 km or
      more, it was possible to see, at the edge of the area, certain points
      not correctly reported.
      
      Because the bounding box for now was used just as an optimization, and
      such huge radiuses are not common, for now the optimization is just
      switched off when the radius is near such magnitude.
      
      Three test cases found by the Continuous Integration test were added, so
      that we can easily trigger the bug again, both for regression testing
      and in order to properly fix it as some point in the future.
      b2cd9fca
  11. 16 Jun, 2017 1 commit
  12. 15 Jun, 2017 1 commit
  13. 28 Apr, 2017 2 commits
  14. 22 Apr, 2017 3 commits
    • antirez's avatar
      Defrag: test currently disabled, too many false positives. · c861e1e1
      antirez authored
      Related to #3786.
      c861e1e1
    • antirez's avatar
      Defrag: fix test false positive. · a1739085
      antirez authored
      Apparently 1.4 is too low compared to what you get in certain setups
      (including mine). I raised it to 1.55 that hopefully is still enough to
      test that the fragmentation went down from 1.7 but without incurring in
      issues, however the test setup may be still fragile so certain times this
      may lead to false positives again, it's hard to test for these things
      in a determinsitic way.
      
      Related to #3786.
      a1739085
    • oranagra's avatar
      add test for active defrag · 0fb5c4eb
      oranagra authored
      0fb5c4eb
  15. 14 Apr, 2017 1 commit
  16. 15 Mar, 2017 1 commit
  17. 22 Feb, 2017 3 commits
  18. 20 Dec, 2016 1 commit
  19. 19 Dec, 2016 1 commit
  20. 13 Dec, 2016 1 commit
  21. 05 Dec, 2016 1 commit
    • antirez's avatar
      Geo: improve fuzz test. · b1fc06f7
      antirez authored
      The test now uses more diverse radius sizes, especially sizes near or
      greater the whole earth surface are used, that are known to trigger edge
      cases. Moreover the PRNG seeding was probably resulting into the same
      sequence tested over and over again, now seeding unsing the current unix
      time in milliseconds.
      
      Related to #3631.
      b1fc06f7
  22. 29 Nov, 2016 4 commits
  23. 28 Nov, 2016 2 commits
    • antirez's avatar
      PSYNC2: stop sending newlines to sub-slaves when master is down. · eab865a0
      antirez authored
      This actually includes two changes:
      
      1) No newlines to take the master-slave link up when the upstream master
      is down. Doing this is dangerous because the sub-slave often is received
      replication protocol for an half-command, so can't receive newlines
      without desyncing the replication link, even with the code in order to
      cancel out the bytes that PSYNC2 was using. Moreover this is probably
      also not needed/sane, because anyway the slave can keep serving
      requests, and because if it's configured to don't serve stale data, it's
      a good idea, actually, to break the link.
      
      2) When a +CONTINUE with a different ID is received, we now break
      connection with the sub-slaves: they need to be notified as well. This
      was part of the original specification but for some reason it was not
      implemented in the code, and was alter found as a PSYNC2 bug in the
      integration testing.
      eab865a0
    • antirez's avatar
      PSYNC2: Test (WIP). · 16559a02
      antirez authored
      This is the PSYNC2 test that helped find issues in the code, and that
      still can show a protocol desync from time to time. Work is in progress
      in order to find the issue. For now the test is not enabled in "make
      test" and must be run manually.
      16559a02