[nodejs] Re: Streaming fs.readdir?

Hi! For those interested, you might want to follow what's going on in https://github.com/joyent/libuv/pull/1521 and https://github.com/joyent/libuv/issues/1430. If we can get this in libuv, then we'll be able to work on adding a streaming API for reading directories in Node.js. Julien On Tues

[nodejs] Re: exports._unrefActive in timers.js creates the CPU load

Hi, On Wednesday, October 22, 2014 6:21:48 AM UTC-7, Sergei wrote: > > I use node 0.10.30 on CentOS release 6.5 (Final). > I have big problem with exports._unrefActive. > When i have about 2K connections in my app. exports._unrefActivestarts > loading the CPU > > >

[nodejs] Re: exports._unrefActive in timers.js creates the CPU load

Hi, On Friday, October 24, 2014 3:07:24 AM UTC-7, Sergei wrote: > > I did tests. > I have another one nodejs app. And I made tests on it. > This nodejs app isn't HTTP server. It is game server. > It is realtime server where users keep the connection during all time they > are playing. > There is

[nodejs] Re: How to get V8 GarageCollection-related metrics in Node application

Hi, On Sunday, November 16, 2014 8:12:40 AM UTC-8, Phillip Johnsen wrote: > > I just stumbled upon the new core module "tracing". Its part of v0.11 so > this is more for future reference than production use for most projects I > guess. > It brings with it a gc-event which seems promising with be

[nodejs] Re: How to get V8 GarageCollection-related metrics in Node application

Hi again, On Monday, November 17, 2014 3:18:38 PM UTC-8, julien...@joyent.com wrote: > > > On Sunday, November 16, 2014 8:12:40 AM UTC-8, Phillip Johnsen wrote: >> >> I just stumbled upon the new core module "tracing". Its part of v0.11 so >> this is more for future reference than production use

[nodejs] Re: socket.io over https memory leak issue

Hi, On Wednesday, November 19, 2014 2:22:27 PM UTC-8, Pablo Torres wrote: > > My app is seeing the same problem, memory blowing up after some time and > then CPU going to 100%. We've been using socket 1.x since mid August, so > that doesn't solve it. Does anyone have any ideas as to what to try

[nodejs] Re: what is going on with node project

Hi, On Sunday, November 30, 2014 7:16:56 AM UTC-8, manz wrote: > > There is no activity on node project since weeks, node advisory board, > io.js. > > There is something going on and someone have to break the ice. > You can find more information regarding what's next in this recently

[nodejs] Re: BUILDING_NODE_EXTENSION macro

Hi, On Friday, December 5, 2014 2:08:22 AM UTC-8, blazs wrote: > > Is it necessary for Node.js (version 0.11+) addons to define > BUILDING_NODE_EXTENSION macro? The compiler warns me that the macro is > enabled by default. > > The macro is defined on the command line by node-gyp. You can see tha

Re: [nodejs] Some questions on Node's threading and scaling.

Hi! Aria already sent a very thorough and detailed response (thank you!), but I'd just like to comment on a couple of small details. On Saturday, December 6, 2014 8:00:24 AM UTC-8, Aria Stewart wrote: > > > > On 6 Dec 2014, at 03:03, Harry Simons wrote: > > I'm new to Node. It looks very wonde

[nodejs] Re: is the debug node binary supposed to work?

Hi! On Friday, December 12, 2014 2:57:25 PM UTC-8, Matt Ginzton wrote: > > > I went looking for more standard workloads to run to see if the problem > was with my codebase (or, again, the native-code node extensions it uses, > bugs in which could mean all bets are off), and I chanced across a mi

[nodejs] Re: exports._unrefActive in timers.js creates the CPU load

Hi, On Friday, October 24, 2014 2:01:38 PM UTC-7, julien...@joyent.com wrote: > > Let's wait to see if we can land the unordered list implementation in > 0.10.34. In the meantime, please let us know if you have any issue running > your code with the unordered list fix. > Just a heads up to let

[nodejs] Re: exports._unrefActive in timers.js creates the CPU load

Hi again, On Wednesday, December 17, 2014 2:53:15 PM UTC-8, julien...@joyent.com wrote: > > On Friday, October 24, 2014 2:01:38 PM UTC-7, julien...@joyent.com wrote: >> >> Let's wait to see if we can land the unordered list implementation in >> 0.10.34. In the meantime, please let us know if you

[nodejs] Re: is the debug node binary supposed to work?

Hi, On Wednesday, December 17, 2014 9:00:44 AM UTC-8, Matt Ginzton wrote: > > > OK, the extra step to repro is have a package.json with the following > contents > > { > "dependencies": { > "archiver": "0.13", > "connect": "~2.15.0" > } > } > > And then run "npm install archiver connec

[nodejs] Re: exports._unrefActive in timers.js creates the CPU load

On Friday, December 19, 2014 at 10:22:01 AM UTC-8, julien...@joyent.com wrote: > > Hi again, > > On Wednesday, December 17, 2014 2:53:15 PM UTC-8, julien...@joyent.com > wrote: >> >> On Friday, October 24, 2014 2:01:38 PM UTC-7, julien...@joyent.com wrote: >>> >>> Let's wait to see if we can la

Re: [nodejs] What happened to 0.11.15?

Hi! On Sunday, January 11, 2015 at 10:48:56 AM UTC-8, Forrest L Norvell wrote: > > > On Sat, Jan 10, 2015 at 8:59 AM, Ekin Koc wrote: > >> Any idea what's the hold up on 0.12 release? >> > Currently, the only outstanding issue I'm aware of is the merge of v0.10 to v0.12: https://github.com/joyen

Re: [nodejs] What happened to 0.11.15?

Hi! On Monday, January 12, 2015 at 11:40:07 AM UTC-8, Aria Stewart wrote: > > > On Jan 12, 2015, at 2:21 PM, julien.gi...@joyent.com wrote: > > > Currently, the only outstanding issue I'm aware of is the merge of v0.10 > to v0.12: https://github.com/joyent/node/pull/8886. We're doing our best >

[nodejs] Upcoming 0.11.15 release

Hi everyone, All issues in the 0.11.15 milestone have been closed, many thanks to everyone who helped! Please see https://github.com/joyent/node/issues?q=milestone%3A0.11.15+ for more details. Here is the current plan to release Node.js 0.11.15: * A new branch v0.11.15-release will be create

[nodejs] Upcoming 0.10.36 release

Hi everyone, After Node.js 0.10.35 was released, another regression was found in V8's debugger: https://github.com/joyent/node/issues/8948. Also, OpenSSL released new versions of their libraries due to new security vulnerabilities. The goal of the upcoming 0.10.36 release is to fix these issue

[nodejs] Re: Upcoming 0.11.15 release

Hi! On Monday, January 19, 2015 at 7:42:31 PM UTC-8, Andrew Kelley wrote: > > 0.11.5 is the release candidate for 0.12, correct? > > Yes, that is the current plan. Julien -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md O

[nodejs] Node v0.11.15 (Unstable)

for (u)int ops (Yazhong Liu) * buffer: fix and cleanup fill() (Trevor Norris) * buffer: mv floating point read/write checks to JS (Trevor Norris) * build, i18n: improve Intl build, add "--with-intl" (Steven R. Loomis) * build: add small-icu support for binary packages (Julien Gilli) *

[nodejs] Re: What is node's version support policy?

Hi! On Wednesday, January 21, 2015 at 5:30:03 AM UTC-8, Michael Salinger wrote: > > What is node's current policy when it comes to supporting prior stable > versions (i.e. maintenance patches have still been released for 0.8 for > some time, but will they continue to be once 0.12 is released?) >

[nodejs] Upcoming 0.11.16 release and update on v0.12

Hi everyone, Node v0.11.15 was the first release candidate for node v0.12.0. A few issues were found in node v0.11.15 that require another release candidate: node v0.11.16. Hopefully, this will be the last release candidate before node v0.12.0. You can find more info on what needs to be done b

[nodejs] Node v0.11.16 (Unstable)

2015.01.29, Version 0.11.16 (Unstable) * openssl: Upgrade to 1.0.1l * npm: Upgrade to 2.3.0 * url: revert support of `path` for url.format (Julien Gilli) * assert: use util.inspect() to create error messages (cjihrig) * net: throw on invalid socket timeouts (cjihrig) * url: fix parsing of

[nodejs] Node v0.12.0 (Stable)

We are excited to announce the availability of Node.js v0.12! It has been a long process, and we want to thank contributors and all of the community who waited patiently for this event. Node.js has such a vibrant and enthusiastic community, and we're very lucky to have you all supporting us. Node.

[nodejs] Re: Node v0.12.0 (Stable)

Hi William! On Sunday, February 8, 2015 at 4:39:45 AM UTC-8, William Dauchy wrote: > > I think there is a problem with gpg checks: > > gpg: Signature made Fri Feb 6 23:03:40 2015 CET using RSA key ID 888C628D > gpg: Can't check signature: public key not found > > The files checkums have been sign

[nodejs] Re: Node v0.12.0 (Stable)

Hi! On Saturday, February 7, 2015 at 9:20:01 AM UTC-8, André Fiedler wrote: > > nice to see v0.12.0 production ready, but why no ARM PI (Raspberry Pi) > build? > I'm not familiar with the Raspberry Pi platform and what providing binaries for it would require. If I understand correctly, the cur

Re: [nodejs] Re: Node v0.12.0 (Stable)

Hi! On Monday, February 9, 2015 at 8:32:08 AM UTC-8, Aria Stewart wrote: > > > > On Feb 9, 2015, at 6:02 AM, William Dauchy wrote: > > > > ok this release is signed with a different key 888C628D: Julien Gilli < > jgi...@fastmail.fm> > > > Hey Julie

Re: [nodejs] Re: Node v0.12.0 (Stable)

his release is signed with a different key 888C628D: Julien Gilli < >> jgi...@fastmail.fm> >> >> >> Hey Julien -- it might make sense to see if you can get your key signed >> by the old key, so that the web of trust works. >> > > Yes, that is a good sugg

[nodejs] Re: Can't find getting started documentation

Hi! On Thursday, February 19, 2015 at 11:30:44 PM UTC-8, alota takada wrote: > > At http://nodejs.org/documentation/ it says "Here on nodejs.org you will > find three types of documentation, reference documentation, getting started > documentation, and tutorials." > > I can find the reference do

[nodejs] Re: How to build exactly the same node.js as official release

Hi! On Thursday, March 5, 2015 at 6:47:50 AM UTC-8, Cong Liu wrote: > > I want to build exactly the same node.js as official release. So that it's > as same stable and secure as official builds. The configure script > provides various options to build node.js. For example, shared openssl or > n

[nodejs] Node v0.10.37 (Maintenance)

low Object.prototype fields as labels (Julien Gilli) * V8: log version in profiler log file (Ben Noordhuis) * http: fix performance regression for GET requests (Florin-Cristian Gavrila) Source Code: http://nodejs.org/dist/v0.10.37/node-v0.10.37.tar.gz Macintosh Installer (Universal): h

[nodejs] Re: Backport support for http statusMessage to 0.10.x

Hi Pavel! On Tuesday, March 17, 2015 at 9:58:27 PM UTC-7, Pavel Strashkin wrote: > > I'm wondering whether it's possible to > backport a35a2f0192f78c762ed1009025e673cf09862d4d from 0.12.x to 0.10.x. > There are few reasons "why": > Could you please file an issue in Node.js' issues tracker here:

[nodejs] Node v0.10.38 (Maintenance)

Hi, This release upgrades OpenSSL to version 1.0.1m, which includes fixes for several CVEs that were disclosed recently. More information is available here: https://www.openssl.org/news/secadv_20150319.txt. 2015.03.23, Version 0.10.38 (Maintenance) * openssl: upgrade to 1.0.1m (Addressing multi

[nodejs] Node v0.12.1 (Stable)

Hi, This release upgrades OpenSSL to version 1.0.1m, which includes fixes for several CVEs that were disclosed recently. More information is available here: https://www.openssl.org/news/secadv_20150319.txt. 2015.03.23, Version 0.12.1 (Stable) * openssl: upgrade to 1.0.1m (Addressing multiple CV

[nodejs] Re: Node.js 0.12.0 on CentOS 6 (by rpm)

Hi Henrique, On Thursday, March 26, 2015 at 12:05:12 PM UTC-7, Henrique Taunay wrote: > > Given my environment I can ONLY install packages through RPM, and as I > might be inclined to generate my own rpm of Node.js 0.12.0, I would like to > know if there is any specific reason why the latest ver

[nodejs] Node v0.12.2 (Stable)

: unref timer in parent sockets (Fedor Indutny) * path: refactor for performance and consistency (Nathan Woltman) * smalloc: extend user API (Trevor Norris) * src: fix for SIGINT crash on FreeBSD (Fedor Indutny) * src: fix builtin modules failing with --use-strict (Julien Gilli) * watchdog: fix

[nodejs] Node v0.12.3 (Stable)

n for loops (adamk) * debugger: don't spawn child process in remote mode (Jackson Tian) * net: do not set V4MAPPED on FreeBSD (Julien Gilli) * repl: make 'Unexpected token' errors recoverable (Julien Gilli) * src: backport ignore ENOTCONN on shutdown race (Ben Noordhuis) * src: fi

[nodejs] Node v0.12.4 (Stable)

Hi everyone, There's a new stable release of Node.js available, node v0.12.4. Here are the details: 2015.05.22, Version 0.12.4 (Stable) * npm: upgrade to 2.10.1 * V8: revert v8 Array.prototype.values() removal (cjihrig) * win: bring back xp/2k3 support (Bert Belder) Source Code: http://node

[nodejs] Re: is the debug node binary supposed to work?

On Friday, December 19, 2014 at 3:30:12 PM UTC-8, julien.gi...@joyent.com wrote: > > Hi, > > On Wednesday, December 17, 2014 9:00:44 AM UTC-8, Matt Ginzton wrote: >> >> >> OK, the extra step to repro is have a package.json with the following >> contents >> >> { >> "dependencies": { >> "ar

[nodejs] Re: is the debug node binary supposed to work?

On Tuesday, June 9, 2015 at 4:01:37 PM UTC-7, julien.gi...@joyent.com wrote: > > > > On Friday, December 19, 2014 at 3:30:12 PM UTC-8, julien.gi...@joyent.com > wrote: >> >> Hi, >> >> On Wednesday, December 17, 2014 9:00:44 AM UTC-8, Matt Ginzton wrote: >>> >>> >>> OK, the extra step to repro is

[nodejs] node v0.10.39 (Maintenance)

1.0.1o (Addressing multiple CVEs) * install: fix source path for openssl headers (Oguz Bastemur) * install: make sure opensslconf.h is overwritten (Oguz Bastemur) * timers: fix timeout when added in timer's callback (Julien Gilli) * windows: broadcast WM_SETTINGCHANGE after install (Ma

[nodejs] Re: issue while doing profiling of node server

On Tuesday, June 23, 2015 at 4:58:43 AM UTC-7, Prasoon Gupta wrote: > > I am using node 0.12.0 for my application, When try to run node server > with "--prof" > > my application is not responding. > > the simple command I am using is > > node --prof server.js > > Your problem could be related

[nodejs] Node.js v0.10.40 (Maintenance)

Hi everyone, A new maintenance release of Node.was just released. This release upgrades OpenSSL to version 1.0.1p, which fixes a security vulnerability (CVE-2015-1793). More details about the vulnerability can be found [on OpenSSL's website](http://openssl.org/news/secadv_20150709.txt). More det

[nodejs] Node.js v0.12.7 (Stable)

Hi, A new stable release of Node.js, node v0.12.7 just came out. In addition to upgrading npm and fixing a couple of bugs, this release upgrades OpenSSL to version 1.0.1p, which fixes a security vulnerability (CVE-2015-1793). More details about the vulnerability can be found [on OpenSSL's website