1. 30 Jan, 2017 5 commits
  2. 27 Jan, 2017 2 commits
    • antirez's avatar
      Add panic() into redisassert.h. · 7c2153da
      antirez authored
      This header file is for libs, like ziplist.c, that we want to leave
      almost separted from the core. The panic() calls will be easy to delete
      in order to use such files outside, but the debugging info we gain are
      very valuable compared to simple assertions where it is not possible to
      print debugging info.
      7c2153da
    • antirez's avatar
      serverPanic(): allow printf() alike formatting. · dc83ddf0
      antirez authored
      This is of great interest because allows us to print debugging
      informations that could be of useful when debugging, like in the
      following example:
      
          serverPanic("Unexpected encoding for object %d, %d",
              obj->type, obj->encoding);
      dc83ddf0
  3. 13 Jan, 2017 3 commits
  4. 12 Jan, 2017 11 commits
  5. 21 Dec, 2016 4 commits
  6. 20 Dec, 2016 7 commits
    • antirez's avatar
    • antirez's avatar
      Geo: fuzzy test inconsistency report fixed to show all points. · f3add069
      antirez authored
      We need to report all the points added into the set, not just the ones
      matching the Tcl distance algo.
      f3add069
    • antirez's avatar
      Geo: fix GEOHASH return value for consistency. · 056c81e4
      antirez authored
      The same thing observed in #3551 by gnethercutt also fixed for
      GEOHASH as the original PR did.
      056c81e4
    • antirez's avatar
      Geo: fix edge case return values for uniformity. · d5036018
      antirez authored
      There were two cases outlined in issue #3512 and PR #3551 where
      the Geo API returned unexpected results: empty strings where NULL
      replies were expected, or a single null reply where an array was
      expected. This violates the Redis principle that Redis replies for
      existing keys or elements should be indistinguishable.
      
      This is technically an API breakage so will be merged only into 4.0 and
      specified in the changelog in the list of breaking compatibilities, even
      if it is not very likely that actual code will be affected, hopefully,
      since with the past behavior basically there was to acconut for *both*
      the possibilities, and the new behavior is always one of the two, but
      in a consistent way.
      d5036018
    • Justin Carvalho's avatar
    • antirez's avatar
      a0e95118
    • antirez's avatar
      Only show Redis logo if logging to stdout / TTY. · 3334a409
      antirez authored
      You can still force the logo in the normal logs.
      For motivations, check issue #3112. For me the reason is that actually
      the logo is nice to have in interactive sessions, but inside the logs
      kinda loses its usefulness, but for the ability of users to recognize
      restarts easily: for this reason the new startup sequence shows a one
      liner ASCII "wave" so that there is still a bit of visual clue.
      
      Startup logging was modified in order to log events in more obvious
      ways, and to log more events. Also certain important informations are
      now more easy to parse/grep since they are printed in field=value style.
      
      The option --always-show-logo in redis.conf was added, defaulting to no.
      3334a409
  7. 19 Dec, 2016 7 commits
  8. 16 Dec, 2016 1 commit
    • antirez's avatar
      Switch PFCOUNT to LogLog-Beta algorithm. · 2e375d4f
      antirez authored
      The new algorithm provides the same speed with a smaller error for
      cardinalities in the range 0-100k. Before switching, the new and old
      algorithm behavior was studied in details in the context of
      issue #3677. You can find a few graphs and motivations there.
      2e375d4f