1. Dec 03, 2012
  2. Dec 02, 2012
  3. Dec 01, 2012
    • isaacs's avatar
      benchmark: Add net-pipe benchmark · 3149d2f7
      isaacs authored
      Just sends a buffer to a server, which echoes it back, and then measures
      the Gbits/second.  Very similar to throughput.js, but using a single
      process, so that it's possible to dtrace and get the jsstack frames for
      profile comparison.
      3149d2f7
  4. Nov 27, 2012
  5. Nov 24, 2012
    • Ben Noordhuis's avatar
      js2c: raise proper Exception, not a string · aa3441ae
      Ben Noordhuis authored
      Fixes the following error message:
      
        TypeError: exceptions must be old-style classes or derived
        from BaseException, not str
      
      Fixes #4303.
      aa3441ae
    • Ben Noordhuis's avatar
      crypto: allow negative numbers in setOptions() · 335f2089
      Ben Noordhuis authored
      OR'ing together two large values, like `SSL_OP_ALL | SSL_OP_NO_TICKET`,
      produces a negative number. To wit:
      
        assert((0x80000000 | 0x4000) === -0x7fffc000); // true
        assert((0x80000000 | 0x4000) ===  0x80004000); // false!
      
      It's easy to work around by doing a logical shift, like this:
      
        assert((0x80000000 | 0x4000) >>> 0 ===  0x80004000); // true
      
      But that's not very intuitive. Let's be more lenient in what we accept.
      335f2089
  6. Nov 22, 2012
  7. Nov 21, 2012
  8. Nov 20, 2012
  9. Nov 17, 2012
  10. Nov 12, 2012
  11. Nov 11, 2012
  12. Nov 10, 2012
  13. Nov 09, 2012
  14. Nov 07, 2012
    • Nathan Rajlich's avatar
      readline: use a "string_decoder" to parse "keypress" events · 3c91a7ae
      Nathan Rajlich authored
      While updating the readline test cases to test both "terimal: false" and
      "terminal: true" mode, it turned out that the test case testing utf8 chars
      being sent over multiple write() calls was failing. The solution is to use
      a string_decoder instance when parsing the "keypress" events.
      3c91a7ae
    • Nathan Rajlich's avatar
      readline: don't emit "line" events with a trailing '\n' char · e95e0952
      Nathan Rajlich authored
      Before this commit, readline was inconsistent in whether or not it would emit
      "line" events with or without the trailing "\n" included. When "terminal"
      mode was true, then there would be no "\n", when it was false, then the "\n"
      would be present. However, the trailing "\n" doesn't add much, and most of the
      time people just end up stripping it manually.
      
      Part of #4243.
      e95e0952
  15. Nov 06, 2012
  16. Nov 04, 2012