- Mar 22, 2011
- Mar 21, 2011
-
-
Ryan Dahl authored
-
- Mar 20, 2011
-
-
Ryan Dahl authored
-
- Mar 19, 2011
-
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
-
koichik authored
-
Dean McNamee authored
-
Ryan Dahl authored
Thanks to Stéphan Kochen for the fix and Maurice Fonk for reproducing the bug. Closes GH-784. Closes GH-803.
-
Ryan Dahl authored
-
Ryan Dahl authored
-
- Mar 18, 2011
- Mar 15, 2011
-
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
-
Ryan Dahl authored
https://groups.google.com/forum/#!topic/nodejs-dev/V5fB69hFa9o Closes GH-787.
-
Felix Geisendörfer authored
I have seen a lot of people trying to pass objects to crypto's update functions, assuming that it would somehow serialize the object before hashing. In reality, the object was converted to '[object Object]' which was then hashed, without any error message showing. This patch modifies the DecodeBytes function (used exclusively by crypto at this point) to complain when receiving anything but a string or buffer. Overall this should be a less-suprising, more robust behavior.
-
-
Theo Schlossnagle authored
Data being sent out of order.
-
Ryan Dahl authored
-
- Mar 12, 2011
-
-
koichik authored
-
koichik authored
-
Theo Schlossnagle authored
Closes GH-774.
-
- Mar 11, 2011
- Mar 10, 2011
- Mar 09, 2011
-
-
Tom Hughes authored
Change the natives to use this class instead of creating completely new strings. Reduces memory usage by about 1 MB.
-
- Mar 08, 2011
-
-
Ryan Dahl authored
-
Tom Hughes authored
This ensures that the check_function_exists() for fdatasync in the libeio CMakeLists.txt is not run, since that fails on some versions of OSX (http://public.kitware.com/Bug/view.php?id=10044).
-