1. 22 Apr, 2017 1 commit
  2. 15 Mar, 2017 1 commit
  3. 22 Feb, 2017 2 commits
  4. 20 Dec, 2016 1 commit
  5. 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
  6. 18 Nov, 2016 1 commit
  7. 31 Oct, 2016 1 commit
  8. 14 Oct, 2016 1 commit
  9. 24 Aug, 2016 1 commit
  10. 27 Jul, 2016 1 commit
    • antirez's avatar
      Multiple GEORADIUS bugs fixed. · 356a6304
      antirez authored
      By grepping the continuous integration errors log a number of GEORADIUS
      tests failures were detected.
      
      Fortunately when a GEORADIUS failure happens, the test suite logs enough
      information in order to reproduce the problem: the PRNG seed,
      coordinates and radius of the query.
      
      By reproducing the issues, three different bugs were discovered and
      fixed in this commit. This commit also improves the already good
      reporting of the fuzzer and adds the failure vectors as regression
      tests.
      
      The issues found:
      
      1. We need larger squares around the poles in order to cover the area
      requested by the user. There were already checks in order to use a
      smaller step (larger squares) but the limit set (+/- 67 degrees) is not
      enough in certain edge cases, so 66 is used now.
      
      2. Even near the equator, when the search area center is very near the
      edge of the square, the north, south, west or ovest square may not be
      able to fully cover the specified radius. Now a test is performed at the
      edge of the initial guessed search area, and larger squares are used in
      case the test fails.
      
      3. Because of rounding errors between Redis and Tcl, sometimes the test
      signaled false positives. This is now addressed.
      
      Whenever possible the original code was improved a bit in other ways. A
      debugging example stanza was added in order to make the next debugging
      session simpler when the next bug is found.
      356a6304
  11. 06 Jul, 2016 1 commit
  12. 28 Jun, 2016 3 commits
  13. 15 Jun, 2016 2 commits
  14. 05 Jun, 2016 1 commit
  15. 31 May, 2016 1 commit
  16. 18 May, 2016 1 commit
  17. 06 May, 2016 1 commit
  18. 25 Apr, 2016 1 commit
  19. 18 Apr, 2016 1 commit
  20. 02 Mar, 2016 4 commits
  21. 18 Feb, 2016 1 commit
  22. 08 Jan, 2016 1 commit
    • antirez's avatar
      Scripting: handle trailing comments. · f43c794b
      antirez authored
      This fix, provided by Paul Kulchenko (@pkulchenko), allows the Lua
      scripting engine to evaluate statements with a trailing comment like the
      following one:
      
          EVAL "print() --comment" 0
      
      Lua can't parse the above if the string does not end with a newline, so
      now a final newline is always added automatically. This does not change
      the SHA1 of scripts since the SHA1 is computed on the body we pass to
      EVAL, without the other code we add to register the function.
      
      Close #2951.
      f43c794b
  23. 11 Dec, 2015 2 commits
  24. 28 Nov, 2015 1 commit
  25. 04 Nov, 2015 1 commit
  26. 03 Nov, 2015 1 commit
  27. 30 Oct, 2015 3 commits
  28. 09 Oct, 2015 1 commit
  29. 06 Oct, 2015 1 commit
  30. 15 Sep, 2015 1 commit
    • antirez's avatar
      Test: fix false positive in HSTRLEN test. · 846da5b2
      antirez authored
      HINCRBY* tests later used the value "tmp" that was sometimes generated
      by the random key generation function. The result was ovewriting what
      Tcl expected to be inside Redis with another value, causing the next
      HSTRLEN test to fail.
      846da5b2