GitHub PushEvent at 2014-06-13 01:28:22
Repository: redis
Actor: mattsta
Payload: {"shas":[["4930d903fc341faf4c5dce7197f4f81af941dfa5","5d2e33f2c005733405d84da249995e6fe1b8bfe9@monfort.co.il","Fix eval usage in tests to conform with eval semantics","yoav",false],["fdaab0234787d1bb835680825ea919d7cba3723e","5d2e33f2c005733405d84da249995e6fe1b8bfe9@monfort.co.il","Merge remote-tracking branch 'upstream/unstable' into unstable","yoav",false],["3e0e51dd9fcfa9c361d716ba2fc935a40fadace3","1fa2ef4755a9226cb9a0a4840bd89b158ac71391@genges.com","Fix lack of SA_ONSTACK under Cygwin\n\nFixes #232","Matt Stancliff",false],["7c4decb10183224ad9b33505bd6d5cbdb5d8d98b","1fa2ef4755a9226cb9a0a4840bd89b158ac71391@genges.com","Fix lack of strtold under Cygwin\n\nRenaming strtold to strtod then casting\nthe result is the standard way of dealing with\nno strtold in Cygwin.","Matt Stancliff",false],["33f943b4cddb0bf90b436ccd47d12363e13d0fce","1fa2ef4755a9226cb9a0a4840bd89b158ac71391@genges.com","Fix blocking operations from missing new lists\n\nBehrad Zari discovered [1] and Josiah reported [2]: if you block\nand wait for a list to exist, but the list creates from\na non-push command, the blocked client never gets notified.\n\nThis commit adds notification of blocked clients into\nthe DB layer and away from individual commands.\n\nLists can be created by [LR]PUSH, SORT..STORE, RENAME, MOVE,\nand RESTORE.  Previously, blocked client notifications were\nonly triggered by [LR]PUSH.  Your client would never get\nnotified if a list were created by SORT..STORE or RENAME or\na RESTORE, etc.\n\nBlocked client notification now happens in one unified place:\n  - dbAdd() triggers notification when adding a list to the DB\n\nTwo new tests are added that fail prior to this commit.\n\nAll test pass.\n\nFixes #1668\n\n[1]: https://groups.google.com/forum/#!topic/redis-db/k4oWfMkN1NU\n[2]: #1668","Matt Stancliff",false],["94e3bb568ac2cb7763a1caab299337ed72149e4c","1d02310a57e007b2f82bbbc851398577147e74f9@gmail.com","Fixed typo in word avarege in result message of --intrinsic-latency analyzer","Andy Grunwald",false],["b187c591e39e072fa169bf60a1a46bebc855973b","5a4f26b21ebc770c5837d49e7c35574b29654610@archlinux.us","Small typo fixed","Jan-Erik Rediger",false],["8a588ac14d229aa330d7b2daea1778c606e6588b","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","More trailing spaces in sentinel.c removed.","antirez",false],["dc8584696a3f97fc1fda90b4c50fb3f8f7dda0cf","05ec9c5d0cc56db66b61b33927052b738d645c1b@gmail.com","fix issue 1787","zionwu",false],["072982d83c83b161f555538bad6a82815d1c36eb","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Scripting: better Lua number -> string conversion in luaRedisGenericCommand().\n\nThe lua_to*string() family of functions use a non optimal format\nspecifier when converting integers to strings. This has both the problem\nof the number being converted in exponential notation, which we don't\nuse as a Redis return value when floating point numbers are involed,\nand, moreover, there is a loss of precision since the default format\nspecifier is not able to represent numbers that must be represented\nexactly in the IEEE 754 number mantissa.\n\nThe new code handles it as a special case using a saner conversion.\n\nThis fixes issue #1118.","antirez",false],["3307db49bd9b8eceaa9672ecfb1d32a5ba7497ce","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Regression test for issue #1118.","antirez",false],["3758f27bc1d3be0b12676fa9a7f26678e4789c6c","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Fixed dbuf variable scope in luaRedisGenericCommand().\n\nI'm not sure if while the visibility is the inner block, the fact we\npoint to 'dbuf' is a problem or not, probably the stack var isx\nguaranteed to live until the function returns. However obvious code is\nbetter anyway.","antirez",false],["134fd9eaf4b683e200be1d42d20632767c6e2e5c","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Tests for min-slaves-* feature.","antirez",false],["14fb0ac649062d250659a153aa576870e151cb4b","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Don't process min-slaves-to-write for slaves.\n\nReplication is totally broken when a slave has this option, since it\nstops accepting updates from masters.\n\nThis fixes issue #1434.","antirez",false],["1e221d101cd834c8f13fe570ce4ee2c69bffa109","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Merge pull request #1788 from zionwu/unstable\n\nfix issue 1787","Salvatore Sanfilippo",false],["e8ebd7d0e05b72d3ab749093493ee3c1cf7023d0","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Merge pull request #1789 from yoav-steinberg/fix_eval_in_tests\n\nFix eval usage in tests to conform with eval semantics","Salvatore Sanfilippo",false],["113be48221ad07706a15f253657cc805acb8047a","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Merge pull request #1780 from badboy/patch-8\n\nSmall typo fixed","Salvatore Sanfilippo",false],["a2403227c7b164e546e53bf329c70caaadef2c14","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Merge pull request #1772 from andygrunwald/typo-avarege-average\n\nFixed typo in word avarege in result message of --intrinsic-latency analyzer","Salvatore Sanfilippo",false],["a2c2ef7de593ca9ae80b09c3b243965a746a106c","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Cluster: SET-CONFIG-EPOCH should update currentEpoch.\n\nSET-CONFIG-EPOCH, used by redis-trib at cluster creation time, failed to\nupdate the currentEpoch, making it possible after a failover for a\nserver to set its configEpoch to a value smaller than the current one\n(since configEpochs are obtained using currentEpoch).\n\nThe bug totally break the Redis Cluster algorithms and protocols\nallowing for permanent split brain conditions about the slots\nconfiguration as shown in issue #1799.","antirez",false],["32d0a79f7871052429f38c65ee0b341c7fbbe3e5","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Cluster: check that configEpoch never goes back.\n\nSince there are ways to alter the configEpoch outside of the failover\nprocedure (for exampel CLUSTER SET-CONFIG-EPOCH and via the configEpoch\ncollision resolution algorithm), make always sure, before replacing our\nconfigEpoch with a new one, that it is greater than the current one.","antirez",false]],"size":49,"ref":"refs/heads/5-short-clusterables","head":"f60e2727f5d6b418a5d8b31e3090b4e9172a2ea7"}