GitHub PushEvent at 2014-10-02 19:36:42
Repository: node
Actor: jwueller
Payload: {"shas":[["d9b4cc323f481bf465384b2012ba5043e18fe098","042dc4512fa3d391c5170cf3aa61e6a638f84342@izs.me","Revert \"crypto: add SPKAC support\"\n\nThis reverts commit 7f66e44dc1e90e7abda2a9ed02d7e8163e1f6358.","isaacs",true],["a555992d5ebd93ae873f002e8ff26dba596a62b8","042dc4512fa3d391c5170cf3aa61e6a638f84342@izs.me","Revert \"doc: crypto: document SPKAC additions\"\n\nThis reverts commit aa94450b31a28d6251df3b88fdd652ddd1e67a69.","isaacs",true],["5ef03bc3eed4da297ffabafc633b07e4f0171861","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","doc: http: add cross-links for easier clicking\n\nMake it a little easier to navigate the http module documentation by\nturning class names and methods into links to the appropriate section.","Ben Noordhuis",true],["5bc5210b923697ab53f0ac0aa8616e28b16b73e9","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","doc: http: reword IncomingMessage 'close' event\n\nThe bit that says \"before response.end() was called or able to flush\"\ndoesn't apply to incoming streams.\n\nFixes #6359.","Ben Noordhuis",true],["7bf46ba4cedefe8d3b6548a314ad64fc0cfd89f1","798166b07f515e5bdd466c55e512e86917378b51@gmail.com","crypto: add SPKAC support\n\nImplements new class 'Certificate' within crypto object for working\nwith SPKAC's (signed public key & challenge) natively.","Jason Gerfen",true],["990141502d2056b93a62042933c574bb0d1fcdab","798166b07f515e5bdd466c55e512e86917378b51@gmail.com","doc: crypto: document SPKAC additions\n\nDocument the SPKAC functionality that was added in commit 7bf46ba.","Jason Gerfen",true],["ab037455094c9e3b9922ae2a380911b2b41ba7ce","748902ab7d31877eb5a6e67b4914e51dda4553ca@gmail.com","http_parser: expose pause/resume method for parser","Timothy J Fontaine",true],["085dd30e93da67362f044ad1b3b6b2d997064692","042dc4512fa3d391c5170cf3aa61e6a638f84342@izs.me","http: provide backpressure for pipeline flood\n\nIf a client sends a lot more pipelined requests than we can handle, then\nwe need to provide backpressure so that the client knows to back off.\nDo this by pausing both the stream and the parser itself when the\nresponses are not being read by the downstream client.\n\nFix GH-6214","isaacs",true],["ca363cf1ae9631cd6465c3a0028ca0af823a68fb","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","debugger: make busy loops SIGUSR1-interruptible\n\nCommit 30e5366b (\"core: Use a uv_signal for debug listener\") changed\nSIGUSR1 handling from a signal handler to libuv's uv_signal_*()\nfunctionality to fix a race condition (and possible hang) in the\nsignal handler.\n\nWhile a good change in itself, it made it impossible to interrupt\nlong running scripts.  When a script is stuck in a busy loop, control\nnever returns to the event loop, which in turn means the signal\ncallback - and therefore the debugger - is never invoked.\n\nThis commit changes SIGUSR1 handling back to a normal signal handler\nbut one that treads _very_ carefully.","Ben Noordhuis",true],["4234bcce486f5c037c9bcc5d121565b2bec9449c","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","debugger: fix SIGUSR1 bootstrap race condition\n\nBefore this commit, the SIGUSR1 signal handler wasn't installed until\nlate in the bootstrapping process and we were prone to miss signals\nsent by other processes.\n\nThis commit installs an early-boot signal handler that merely records\nthe fact that we received a signal.  Once the debugger infrastructure\nis in place, the signal is re-raised, kickstarting the debugger.\n\nAmong other things, this means that simple/test-debugger-client is\nnow _much_ less likely to fail.","Ben Noordhuis",true],["ceb8740a636e59b1e34cb3db0c3c4c79bb501dfa","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","dns: rename domain to hostname\n\nA follow-up commit will save the domain name on the request object but\nwe can't call that property 'domain' because that gets intercepted by\nsrc/node.cc and lib/domain.js to implement the node.js feature of the\nsame name.\n\nTo avoid confusion, rename all variables called 'domain' to 'hostname'.","Ben Noordhuis",true],["a2d1cbef6baabd767cef523078eb4e5921429d09","59bd0a3ff43b32849b319e645d4798d8a5d1e889@bnoordhuis.nl","dns: set hostname property on error object\n\nMake debugging and logging easier: when a DNS lookup for a hostname\nfails, set the hostname as a property on the error object.\n\nFixes #5393.","Ben Noordhuis",true],["7063c59b97fa4f365f9e5ec1f563235ede4104db","2e687df1861dff46b1954016c7b2cad32e8742d4@gmail.com","cpplint: disallow comma-first in C++","Fedor Indutny",true],["2bc30f239be3e56d642eda38df98c656d55b4d86","2e687df1861dff46b1954016c7b2cad32e8742d4@gmail.com","cpplint: disallow if one-liners","Fedor Indutny",true],["ed186c971c3a3c724bdccdcc2e5b70f57588dd69","266bbf644f3674ab209c4709d090256bac1c7bb7@gmail.com","doc: child_process corrections and cleanups\n\n- Make explicit that .disconnected is set before the disconnect event,\n  and it is not allowed to send messages after calling .disconnect(),\n  even while waiting for a delayed disconect event.\n- Remove obsolete claim that explicit exit is required\n- Describe silent: in the options for fork()\n- Describe .connected as the property it is, not just as an aside in\n  the disconnect() method","Sam Roberts",true],["2e16037201b6338914d41048660c1ce713094893","266bbf644f3674ab209c4709d090256bac1c7bb7@gmail.com","doc: cluster documentation cleanup and corrections\n\n- fixed some incomprehensible wording (\"event assigned to...\"?)\n- removed undocumented and unnecessary process properties from example\n- corrected the docs on the default for the exec setting\n- described when workers are removed from cluster.workers\n- described addressType, which was documented as existing, but not what\n  values it might have\n- spell out more clearly the limitations of setupMaster\n- describe disconnect in sufficient detail that why a child does or does\n  not exit can be understood\n- clarify which cluster functions and events are available on process or\n  just on the worker, as well as which are not available in children,\n- don't describe events as the same, when they have receive different\n  arguments\n- fix misleading disconnect example: since disconnect already calls\n  close on all servers, doing it again in the example is a no-op, not\n  the \"force close\" it was claimed to be\n- document the error event, not catching it will kill your node\n- describe suicide better, it is important, and a bit unintuitive\n  (process.exit() is not suicide?)\n- use worker consistently throughout, instead of child.","Sam Roberts",true],["f051b8919fec8efd8ef050f580cfcabea3d2534c","748902ab7d31877eb5a6e67b4914e51dda4553ca@gmail.com","http_parser: expose pause/resume method for parser","Timothy J Fontaine",true],["b97c28f59ee898a81f0df988c249359c9b42701d","042dc4512fa3d391c5170cf3aa61e6a638f84342@izs.me","http: provide backpressure for pipeline flood\n\nIf a client sends a lot more pipelined requests than we can handle, then\nwe need to provide backpressure so that the client knows to back off.\nDo this by pausing both the stream and the parser itself when the\nresponses are not being read by the downstream client.\n\nBackport of 085dd30","isaacs",true],["54910044b33a6405c72ad085915a55c575c027fc","08f2b8d6eec7ff3467f34fc159cf89c1998811d6@gmail.com","http: add statusMessage\n\nNow the status message can be set via req.statusMessage = 'msg';","Patrik Stutz",true],["8fc48bcf4ca49f16b910b388481030870f78665f","748902ab7d31877eb5a6e67b4914e51dda4553ca@gmail.com","uv: Upgrade to v0.10.18","Timothy J Fontaine",true]],"size":1000,"ref":"refs/heads/master","head":"25702abc5638bbecffa92e8349d2a871a5f592c9"}