1. 08 Jan, 2016 2 commits
    • 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
    • antirez's avatar
      Lua debugger: fix crash printing nested or deep objects. · a75aa4bf
      antirez authored
      Example of offending code:
      
      > script debug yes
      OK
      > eval "local a = {1} a[1] = a\nprint(a)" 0
      1) * Stopped at 1, stop reason = step over
      2) -> 1   local a = {1} a[1] = a
      > next
      1) * Stopped at 2, stop reason = step over
      2) -> 2   print(a)
      > print
      
      ... server crash ...
      
      Close #2955.
      a75aa4bf
  2. 16 Dec, 2015 3 commits
  3. 27 Nov, 2015 1 commit
  4. 18 Nov, 2015 1 commit
  5. 17 Nov, 2015 28 commits
  6. 09 Nov, 2015 1 commit
    • antirez's avatar
      Scripting: fix redis.call() error reporting. · 1b5d24eb
      antirez authored
      Arguments arity and arguments type error of redis.call() were not
      reported correctly to Lua, so the command acted in this regard like
      redis.pcall(), but just for two commands. Redis.call() should always
      raise errors instead.
      1b5d24eb
  7. 05 Nov, 2015 2 commits
  8. 04 Nov, 2015 1 commit
  9. 30 Oct, 2015 1 commit