00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:03:46  <MI6>joyent/node: tjfontaine created branch v0.11.9-release - http://git.io/nPvaFQ
00:04:56  * skabbesquit (Quit: skabbes)
00:06:09  <MI6>node-review: #112 ABORTED http://jenkins.nodejs.org/job/node-review/112/
00:07:17  * brsonjoined
00:13:38  * kazuponjoined
00:20:08  * skabbesjoined
00:26:30  * dshaw_quit (Quit: Leaving.)
00:35:21  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:35:39  * TooTallNatejoined
00:36:03  * AvianFlujoined
00:39:53  <trevnorris>tjfontaine: I've updated the test so net module uses keep-alive. same result. topping out at 20k req/sec
00:40:36  <MI6>joyent/node: tjfontaine created tag v0.11.9 - http://git.io/IyrOSw
00:40:50  <MI6>joyent/node: Timothy J Fontaine master * 1a7d3e2 : Now working on 0.11.10 (+2 more commits) - http://git.io/KMFzgA
00:41:30  <trevnorris>othiym23: to know definitively you'll need to use --trace-opt to see when the method has been optimized (or even if it was)
00:41:53  <trevnorris>othiym23: if inputs are stable, then not very many iterations.
00:41:56  <tjfontaine>trevnorris: I was just curious, I'd like to see it in context of dtrace flame graphs :)
00:42:16  <tjfontaine>but for now I'm kinda busy, so I can't do it myself
00:42:45  <trevnorris>tjfontaine: i'll be interested to see those also. after node summit i'm going to start hammering on this stuff.
00:43:00  <othiym23>trevnorris: the inputs are pretty stable and there shouldn't be any hidden class violations in our tests, but I don't know how many "not very many" is
00:43:14  <othiym23>trevnorris: also, our code is so closure-happy that I think a lot of it won't ever get optimized
00:43:52  <trevnorris>othiym23: heh, yeah. closures will pretty much screw that. what are you trying to benchmark?
00:45:58  <MI6>joyent/node: Timothy J Fontaine v0.10 * a34bbaf : blog: Post for v0.11.9 - http://git.io/3g0xdg
00:47:17  * kazuponquit (Ping timeout: 265 seconds)
00:50:19  * piscisaureus_quit (Ping timeout: 252 seconds)
01:07:45  <MI6>nodejs-master: #715 UNSTABLE osx-x64 (3/677) smartos-ia32 (8/677) linux-x64 (2/677) smartos-x64 (12/677) osx-ia32 (3/677) http://jenkins.nodejs.org/job/nodejs-master/715/
01:11:44  <othiym23>trevnorris: the tracing core of the New Relic stuff
01:13:57  * mcavagequit (Remote host closed the connection)
01:14:37  <MI6>node-review: #113 UNSTABLE osx-x64 (2/677) smartos-x64 (10/677) centos-x64 (6/677) windows-x64 (29/677) linux-x64 (1/677) osx-ia32 (2/677) windows-ia32 (27/677) centos-ia32 (5/677) smartos-ia32 (9/677) http://jenkins.nodejs.org/job/node-review/113/
01:16:45  <trevnorris>othiym23: cool. let me know when you and groundwater_ get some results on the number of calls made in cls w/ your shim vs async listeners. :)
01:16:55  <groundwater_>trevnorris: oh don't you worry!
01:16:57  <groundwater_>heh
01:18:07  * kenperkinsquit (Ping timeout: 241 seconds)
01:18:27  * TooTallNatequit (Quit: Computer has gone to sleep.)
01:23:20  <MI6>nodejs-v0.10-windows: #332 UNSTABLE windows-ia32 (10/604) windows-x64 (32/604) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/332/
01:25:24  <MI6>nodejs-v0.10: #1612 UNSTABLE smartos-x64 (10/604) smartos-ia32 (6/604) linux-x64 (2/604) linux-ia32 (1/604) http://jenkins.nodejs.org/job/nodejs-v0.10/1612/
01:25:41  * kenperkinsjoined
01:34:45  * hzquit
01:43:37  * kazuponjoined
01:44:32  * piscisaureus_joined
01:46:47  * TooTallNatejoined
01:50:45  * dshaw_joined
01:54:22  * dap_quit (Quit: Leaving.)
01:59:33  * octetcloudquit (Ping timeout: 248 seconds)
02:00:04  * AvianFluquit (Read error: Connection reset by peer)
02:01:23  * AvianFlujoined
02:02:03  * paulfryzelquit (Remote host closed the connection)
02:03:13  * paulfryzeljoined
02:03:22  * paulfryzelquit (Remote host closed the connection)
02:04:32  * brsonquit (Quit: leaving)
02:04:46  * brsonjoined
02:07:15  * dshaw_quit (Quit: Leaving.)
02:11:49  * qardjoined
02:13:23  * qardpart
02:15:01  * brsonquit (Ping timeout: 248 seconds)
02:15:02  * piscisaureus_quit (Ping timeout: 248 seconds)
02:15:33  * TooTallNatequit (Ping timeout: 245 seconds)
02:16:40  * kazuponquit (Ping timeout: 245 seconds)
02:24:15  * mcavagejoined
02:25:02  * abraxasjoined
02:26:02  * TooTallNatejoined
02:27:57  * TooTallNatequit (Client Quit)
02:28:28  * brsonjoined
02:28:50  * AvianFluquit (Read error: Connection reset by peer)
02:29:25  * mcavagequit (Ping timeout: 272 seconds)
02:29:27  * AvianFlujoined
02:37:41  * dshaw_joined
02:42:33  * kazuponjoined
02:46:48  * kazuponquit (Ping timeout: 245 seconds)
02:48:57  * dshaw_quit (Quit: Leaving.)
02:50:13  * brsonquit (Ping timeout: 248 seconds)
02:54:06  * jmar777quit (Remote host closed the connection)
03:05:42  * TooTallNatejoined
03:15:17  * piscisaureus_joined
03:20:01  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
03:26:07  * jmar777joined
03:27:54  * inolenquit (Quit: Leaving.)
03:45:02  * brsonjoined
03:49:25  * brsonquit (Ping timeout: 248 seconds)
03:54:42  * jmar777quit (Remote host closed the connection)
03:54:48  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
04:00:10  * kazuponjoined
04:03:12  * stagasjoined
04:07:05  * brsonjoined
04:13:06  * hueniversequit (Quit: Leaving.)
04:18:20  * abraxasquit (Remote host closed the connection)
04:25:04  * abraxasjoined
04:28:27  * inolenjoined
04:30:06  * brsonquit (Ping timeout: 265 seconds)
04:32:37  * inolenquit (Ping timeout: 248 seconds)
05:12:30  * defunctzombie_zzchanged nick to defunctzombie
05:28:37  * jmar777joined
05:29:09  * inolenjoined
05:31:14  * indexzerojoined
05:33:28  * inolenquit (Ping timeout: 245 seconds)
05:38:28  * defunctzombiechanged nick to defunctzombie_zz
05:52:36  * skabbespart
06:11:18  * paulfryzeljoined
06:15:58  * paulfryzelquit (Ping timeout: 245 seconds)
06:16:51  * dshaw_joined
06:40:58  <MI6>nodejs-v0.10-windows: #333 UNSTABLE windows-ia32 (11/604) windows-x64 (10/604) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/333/
06:58:25  * AvianFluquit (Remote host closed the connection)
07:02:55  * jmar777quit (Remote host closed the connection)
07:20:28  * m76joined
07:28:54  * AvianFlujoined
07:36:58  * AvianFluquit (Ping timeout: 240 seconds)
07:45:53  * hueniversejoined
07:55:39  * rendarjoined
07:59:32  * `3E|Zzzchanged nick to `3E|Semi-Zzz
08:13:12  * paulfryzeljoined
08:17:38  * paulfryzelquit (Ping timeout: 245 seconds)
08:18:22  * bnoordhuisjoined
08:25:13  * `3E|Semi-Zzzchanged nick to `3E|TRAIN
08:37:24  * dshaw_quit (Quit: Leaving.)
09:08:18  * dshaw_joined
09:08:18  * dshaw_quit (Client Quit)
09:13:57  * paulfryzeljoined
09:14:20  * `3E|TRAINchanged nick to `3E
09:18:28  * paulfryzelquit (Ping timeout: 245 seconds)
09:37:32  * jameshowejoined
09:38:14  <jameshowe>hmm, is indutny only around for the 12 hours that I'm not
09:45:41  * stagasquit (Ping timeout: 248 seconds)
10:08:23  * dshaw_joined
10:09:52  <indutny>heya
10:11:43  <indutny>jameshowe: sorry, textual crashed
10:11:50  <indutny>jameshowe: can you resend me your message, please?
10:14:38  * paulfryzeljoined
10:17:38  <indutny>heya
10:17:42  <indutny>bnoordhuis: sup?
10:18:53  * paulfryzelquit (Ping timeout: 245 seconds)
10:22:34  * dqminhjoined
10:23:10  * kazuponquit (Remote host closed the connection)
10:28:48  * bnoordhuisquit (Read error: Connection reset by peer)
10:29:03  * bnoordhuisjoined
10:31:49  <indutny>bnoordhuis: yt?
10:39:33  * dshaw_quit (Ping timeout: 248 seconds)
10:49:46  <MI6>nodejs-v0.10: #1613 UNSTABLE smartos-x64 (4/604) smartos-ia32 (4/604) http://jenkins.nodejs.org/job/nodejs-v0.10/1613/
10:52:12  * jameshowequit (Quit: Leaving)
11:01:41  * hzjoined
11:08:45  * dshaw_joined
11:13:33  * dshaw_quit (Ping timeout: 272 seconds)
11:15:27  * paulfryzeljoined
11:19:43  * paulfryzelquit (Ping timeout: 245 seconds)
11:35:20  * dshaw_joined
11:39:40  * dshaw_quit (Ping timeout: 246 seconds)
11:46:04  * bnoordhuisquit (Ping timeout: 265 seconds)
11:48:41  * bnoordhuisjoined
11:50:08  <bnoordhuis>indutny: what's up?
11:50:36  <indutny>bnoordhuis: is that fs-watch-recursive failure reproducible on your mac?
11:50:53  <indutny>if yes - I wonder if this patch will fix it https://github.com/joyent/node/pull/6394#issuecomment-28973749
11:51:31  <bnoordhuis>indutny: yes, it's reproducible
11:51:51  <bnoordhuis>let me test that patch
11:51:54  <indutny>thanks
11:52:23  <bnoordhuis>indutny: still fails
11:52:35  <bnoordhuis>AssertionError: "testsubdir/watch.txt" == "testsubdir" at FSWatcher.<anonymous> (/Users/bnoordhuis/src/master/test/simple/test-fs-watch-recursive.js:53:14)
11:52:38  <indutny>gosh
11:52:44  <indutny>well
11:52:49  <indutny>I think the test is broken
11:52:53  <indutny>I'll add setTimeout too it
11:54:20  * c4milojoined
12:16:13  * paulfryzeljoined
12:18:45  * abraxasquit (Remote host closed the connection)
12:20:33  * paulfryzelquit (Ping timeout: 245 seconds)
12:51:22  * bajtosjoined
12:59:23  * m76quit (Read error: Connection reset by peer)
12:59:36  * bnoordhuisquit (Ping timeout: 272 seconds)
13:00:41  * bnoordhuisjoined
13:07:53  * robonerdquit (Ping timeout: 246 seconds)
13:09:12  * robonerdjoined
13:16:58  * paulfryzeljoined
13:21:23  * paulfryzelquit (Ping timeout: 245 seconds)
13:27:45  * indexzeroquit (Quit: indexzero)
13:29:24  * bnoordhu1sjoined
13:31:40  * bnoordhuisquit (Ping timeout: 264 seconds)
13:56:54  * AvianFlujoined
13:57:43  * bnoordhu1schanged nick to bnoordhuis
13:59:48  * jmar777joined
14:11:14  * jmar777quit (Read error: Connection reset by peer)
14:11:43  * jmar777joined
14:16:07  * AvianFluquit (Remote host closed the connection)
14:17:43  * paulfryzeljoined
14:19:19  * kevinswiberjoined
14:19:23  * abraxasjoined
14:22:13  * paulfryzelquit (Ping timeout: 245 seconds)
14:24:26  * AvianFlujoined
14:24:43  * abraxasquit (Ping timeout: 272 seconds)
14:37:22  * dshaw_joined
14:38:12  * bnoordhu1sjoined
14:39:42  * AvianFluquit (Ping timeout: 246 seconds)
14:41:02  * jmar777quit (Remote host closed the connection)
14:41:40  * dshaw_quit (Ping timeout: 245 seconds)
14:42:31  * bnoordhu1squit (Ping timeout: 240 seconds)
14:48:45  * jmar777joined
14:57:20  * geertjquit (Remote host closed the connection)
15:11:03  * pachetjoined
15:11:03  * pachetquit (Changing host)
15:11:03  * pachetjoined
15:13:37  * mcavagejoined
15:13:39  * mcavagequit (Remote host closed the connection)
15:14:08  * mcavagejoined
15:14:14  * mcavagequit (Remote host closed the connection)
15:14:20  * mcavagejoined
15:18:40  * paulfryzeljoined
15:20:47  <MI6>nodejs-master: #716 UNSTABLE osx-x64 (2/677) smartos-ia32 (6/677) smartos-x64 (7/677) osx-ia32 (2/677) http://jenkins.nodejs.org/job/nodejs-master/716/
15:23:03  * paulfryzelquit (Ping timeout: 245 seconds)
15:28:40  * defunctzombie_zzchanged nick to defunctzombie
15:38:17  * dshaw_joined
15:38:29  * hzquit
15:38:39  * mikealquit (Quit: Leaving.)
15:42:38  * dshaw_quit (Ping timeout: 245 seconds)
15:43:16  * mikealjoined
15:46:39  * stagasjoined
15:53:10  * mikealquit (Quit: Leaving.)
15:55:54  * AvianFlujoined
15:58:17  * bradleymeckjoined
15:59:12  * kazuponjoined
16:01:13  * m76joined
16:08:03  * mikealjoined
16:11:16  * inolenjoined
16:17:56  * mikealquit (Quit: Leaving.)
16:19:13  * paulfryzeljoined
16:20:46  * abraxasjoined
16:21:51  * mikealjoined
16:23:28  * paulfryzelquit (Ping timeout: 245 seconds)
16:24:54  * abraxasquit (Ping timeout: 240 seconds)
16:36:46  * mikealquit (Quit: Leaving.)
16:38:53  * dshaw_joined
16:42:12  * dap_joined
16:42:25  * mikealjoined
16:43:03  * dshaw_quit (Ping timeout: 245 seconds)
16:45:09  * wavdedjoined
16:48:52  * bajtosquit (Quit: bajtos)
16:51:25  * hzjoined
16:51:58  * mikealquit (Quit: Leaving.)
16:52:58  * kazuponquit (Remote host closed the connection)
16:53:25  * kazuponjoined
16:56:19  * kazupon_joined
16:57:37  * kazuponquit (Read error: Connection reset by peer)
17:05:35  * dshaw_joined
17:07:22  * octetcloudjoined
17:07:33  * mikealjoined
17:12:13  <indutny>whoa
17:15:28  <bnoordhuis>that's what she said
17:20:02  * paulfryzeljoined
17:22:52  * bajtosjoined
17:24:18  * paulfryzelquit (Ping timeout: 245 seconds)
17:36:22  * TooTallNatejoined
17:36:49  * jmar777quit (Read error: Connection reset by peer)
17:37:19  * jmar777joined
17:39:38  * bnoordhu1sjoined
17:41:34  <groundwater_>trevnorris: ping
17:49:30  * kazupon_quit (Remote host closed the connection)
17:49:56  * kazuponjoined
17:54:28  * kazuponquit (Ping timeout: 264 seconds)
17:56:40  * pachetquit (Ping timeout: 245 seconds)
17:58:27  * piscisaureus_joined
18:00:06  * pachetjoined
18:00:07  * pachetquit (Changing host)
18:00:07  * pachetjoined
18:04:53  * brsonjoined
18:07:45  * pachetquit (Ping timeout: 272 seconds)
18:14:07  * st_lukejoined
18:14:21  <trevnorris>groundwater_: pong
18:14:39  <groundwater_>trevnorris: i was just looking at https://github.com/joyent/node/pull/6555
18:14:56  <groundwater_>i'm not actually surprised by that behavior, am i missing something?
18:20:49  * paulfryzeljoined
18:22:30  * dshaw_quit (Quit: Leaving.)
18:24:20  * kevinswi_joined
18:24:29  * kevinswiberquit (Ping timeout: 252 seconds)
18:25:08  * paulfryzelquit (Ping timeout: 245 seconds)
18:26:52  * bnoordhu1squit (Ping timeout: 264 seconds)
18:27:59  <trevnorris>groundwater_: does it do the same thing in your shim?
18:28:25  <groundwater_>trevnorris: i'd have to check, but it's not a functionality we use in the agent
18:28:33  <trevnorris>true
18:28:37  <groundwater_>i think we should decide the approach we want
18:28:41  <groundwater_>the shim can adjust
18:29:49  * pachetjoined
18:37:22  * mcavagequit (Remote host closed the connection)
18:38:54  <trevnorris>ah suck. this is another result of me programming it, then feature request coming afterwards.
18:40:52  * pachetquit (Quit: leaving)
18:43:55  * mcavagejoined
18:45:27  <trevnorris>groundwater_: ugh. and there's another issue. I thought the after callbacks were supposed to run if the error was handled. but for some reason aren't.
18:48:41  <trevnorris>man. I just need to rewrite the whole thing...
18:50:43  <hueniverse>trevnorris tjfontaine: how would you measure event loop delay and b8 heap size for the purpose of sending 503 to prevent a server from running out of memory?
18:51:18  <hueniverse>we're using process.memoryUsage and setTimeout but that feels lacking
18:51:39  <hueniverse>I've looked at the toobusy module but I don't like going to C++ level
18:51:43  <hueniverse>any other options?
18:57:48  * paulfryzeljoined
18:58:17  * dshaw_joined
18:59:41  * piscisaureus_quit (Ping timeout: 272 seconds)
19:00:22  * kazuponjoined
19:00:54  <groundwater_>trevnorris: i guess we're missing test coverage in this area right?
19:01:53  <groundwater_>i think we should be careful about providing complex edge case behavior
19:02:04  <groundwater_>because what if that decision turns out to be crazy later
19:02:29  * brsonquit (Ping timeout: 272 seconds)
19:03:41  * brsonjoined
19:04:49  * kazuponquit (Ping timeout: 252 seconds)
19:06:21  * inolenquit (Quit: Leaving.)
19:08:05  * mikealquit (Quit: Leaving.)
19:08:52  * brsonquit (Ping timeout: 264 seconds)
19:10:28  * brsonjoined
19:14:19  * wavdedquit (Quit: Nighty night)
19:17:10  * mikealjoined
19:18:22  * mcavagequit (Remote host closed the connection)
19:19:44  * mcavagejoined
19:19:45  * pachetjoined
19:19:45  * pachetquit (Changing host)
19:19:45  * pachetjoined
19:19:50  * mcavagequit (Read error: Connection reset by peer)
19:19:54  * wavdedjoined
19:20:13  * mcavagejoined
19:23:17  * stagasquit (Ping timeout: 265 seconds)
19:25:33  * brsonquit (Ping timeout: 272 seconds)
19:26:02  * sblomquit (Disconnected by services)
19:26:30  * sblomjoined
19:27:35  <indutny>bnoordhuis: yt?
19:27:52  * brsonjoined
19:28:09  * sblom_joined
19:30:52  * brsonquit (Client Quit)
19:30:57  * bajtospart
19:31:07  * brsonjoined
19:32:53  * bnoordhu1sjoined
19:34:00  * sblomquit (Disconnected by services)
19:34:16  * dap_quit (Ping timeout: 246 seconds)
19:37:20  * bnoordhu1squit (Ping timeout: 272 seconds)
19:37:30  * sblomjoined
19:44:19  * c4miloquit (Remote host closed the connection)
19:45:01  * skabbesjoined
19:51:42  * jmar777quit (Read error: Connection reset by peer)
19:52:10  * jmar777joined
19:56:49  <bnoordhuis>indutny: what's up?
19:57:46  <indutny>bnoordhuis: what do you think about exposing uv_fs_t's new_path?
19:58:22  <bnoordhuis>indutny: that's an implementation detail
19:58:31  <indutny>bnoordhuis: well, req->path too
19:58:35  <indutny>lets hide it then :)
19:59:00  <indutny>ah, its not present on windows...
19:59:01  <indutny>gosh
20:03:27  * dap_joined
20:04:21  * Benviejoined
20:04:33  <indutny>bnoordhuis: so, any thoughts?
20:04:51  <indutny>bnoordhuis: or comments
20:04:51  * Benvie_quit (Ping timeout: 246 seconds)
20:05:22  <bnoordhuis>indutny: none whatsoever. my EEG is a fully flat line right now
20:05:30  <indutny>ok
20:05:35  <indutny>meditation? :)
20:05:46  <bnoordhuis>no, just tired
20:06:47  * wavdedquit (Quit: Hasta la pasta)
20:07:27  * sblomquit (Ping timeout: 272 seconds)
20:07:58  <indutny>bnoordhuis: oh, ok
20:08:03  <indutny>you should have some rest
20:08:23  <indutny>heh, its hard to do both opensource stuff and enterprise
20:08:26  <indutny>or just corporate
20:08:36  * c4milojoined
20:08:44  <indutny>I myself have a hard time managing it together
20:09:07  <indutny>ok, brb
20:09:08  <indutny>need to reboot
20:11:10  * mikealquit (Quit: Leaving.)
20:18:32  * kevinswi_quit (Remote host closed the connection)
20:21:31  * skabbesquit (Quit: skabbes)
20:21:45  * mikealjoined
20:24:18  * mikealquit (Client Quit)
20:24:19  * dap_quit (Quit: Leaving.)
20:24:23  <trevnorris>bnoordhuis: i'm trying to use perf to get a stack trace on futex system calls. looking like: perf record -g -e syscalls:sys_enter_futex ./node script.js
20:24:23  <trevnorris>know of a better way on linux to do this?
20:25:19  <bnoordhuis>trevnorris: aggregates or single system calls?
20:25:37  * mikealjoined
20:26:09  <trevnorris>bnoordhuis: aggregates would be fine. I have a script that's spending 45% of it's time in futex and trying to figure out where that's coming from.
20:26:59  <bnoordhuis>trevnorris: perf works. you could also use systemtap
20:27:40  * isaacs_mobilejoined
20:30:14  <isaacs_mobile>Pork belly taco ftw!!!!!!!
20:31:28  * skabbesjoined
20:32:43  <indutny>isaacs_mobile: hey man
20:32:48  <indutny>are you still in italy?
20:33:25  <isaacs_mobile>No back in Oakland.
20:33:47  * isaacs_mobilequit (Quit: Leaving)
20:34:04  * isaacs_mobilejoined
20:37:15  * stagasjoined
20:38:09  * isaacs_mobilequit (Remote host closed the connection)
20:40:08  * bradleymeckquit (Quit: bradleymeck)
20:41:06  * sblomjoined
20:42:07  * sblomquit (Disconnected by services)
20:49:24  * st_lukequit (Remote host closed the connection)
20:49:52  * st_lukejoined
20:50:32  * kevinswiberjoined
20:51:16  * piscisaureus_joined
20:54:35  * st_lukequit (Ping timeout: 272 seconds)
21:01:50  * brsonquit (Quit: leaving)
21:02:06  * brsonjoined
21:03:11  * dap_joined
21:04:33  * st_lukejoined
21:06:37  * bradleymeckjoined
21:09:19  * bnoordhuisquit (Remote host closed the connection)
21:12:16  * pachetquit (Quit: leaving)
21:16:50  * m76quit (Read error: Connection reset by peer)
21:39:04  <trevnorris>isaacs: ping
21:39:14  * jmar777quit (Remote host closed the connection)
21:41:41  * sblomjoined
22:14:49  * pachetjoined
22:16:22  <isaacs>trevnorris: pong
22:16:40  * brsonquit (Ping timeout: 245 seconds)
22:16:40  <trevnorris>isaacs: do we care if nextTick() is not infinitely recursive?
22:16:48  <isaacs>trevnorris: what do you mean?
22:17:03  <isaacs>trevnorris: i think, as of 0.12, we don't care how deep it goes
22:17:19  <isaacs>trevnorris: recurse your nextticks forever, it's fine. also, you can do a while(true); and we won't stop you
22:17:21  <trevnorris>isaacs: the nextTickQueue is only cleared when it's been processed. no more checking if we've gone to N depth.
22:17:35  <isaacs>trevnorris: yeah, depth no longer matters.
22:17:37  <isaacs>we don't care.
22:17:49  <trevnorris>yeah. but that means the nextTickQueue will never be cleared
22:17:55  <trevnorris>and you'll get a fatal memory error
22:18:09  <trevnorris>because we aren't checking depth
22:18:21  <trevnorris>of course, it's like several million callbacks deep that will happen
22:19:37  <trevnorris>> (function t() { process.nextTick(t); }());
22:19:37  <trevnorris>> FATAL ERROR: JS Allocation failed - process out of memory
22:20:34  <trevnorris>isaacs: so, should nextTick be immune to that? i mean, it's a ridiculous edge case and your code is borked anyways if you reach it.
22:20:43  <othiym23>can we modify core to print out a "INFINITE RECURSION, DUMBASS" message on exit in those cases?
22:20:51  <trevnorris>that's what it used to do
22:20:59  <othiym23>not with that exact text ;)
22:21:02  * brsonjoined
22:21:09  <trevnorris>heh, true. I do like that text better.
22:21:42  <othiym23>I have an annoying ticket I'm dealing with right now that only arises when bunyan and request simultaneously do something dumb
22:21:53  <trevnorris>heh awesome.
22:21:57  <othiym23>but we have to deal with it because we use bunyan
22:22:05  <isaacs>trevnorris: what do you recommend we do in that case?
22:22:07  <othiym23>so I'm all about making blame clear in error messages
22:22:15  <isaacs>i mean, on the one hand, yeah, it's dume
22:22:15  * AvianFluquit (Remote host closed the connection)
22:22:17  <isaacs>*dumb
22:22:32  <isaacs>but on the other hand, why are we using up resources for recursive nextticks? why not just clear it?
22:22:48  <trevnorris>it's a performance hit to splice the nextTickQueue array
22:23:36  <trevnorris>isaacs: should a nextTick from a nextTick still be run on the same tick of the eloop?
22:23:46  <trevnorris>(yeah, those terms aren't confusing at all :P )
22:24:03  * paulfryzelquit (Remote host closed the connection)
22:25:01  <trevnorris>so I pushed off doing that until the queue is finished being processed. even under extreme circumstances in core it never gets deeper than a few thousand in a single tick of the eloop
22:28:19  * AvianFlujoined
22:28:32  * st_lukequit (Remote host closed the connection)
22:29:57  <trevnorris>isaacs: I don't care that the script fails. but for the sake of saving us time helping others figure out the cause of their FATAL ERROR I think we should print a message once during it's execution.
22:30:24  <trevnorris>just so it's less cryptic a reason to die.
22:31:19  <trevnorris>other choice is to just splice the nextTickQueue after N executions. thus still allowing an infinite recursion. think if we're doing anything that's my option of choice.
22:33:56  <isaacs>trevnorris: yeah, that sounds reasonable
22:34:07  <trevnorris>isaacs: cool.
22:37:38  * indexzerojoined
22:38:25  <trevnorris>isaacs: oh, and I finally figured out a way to trace down unnamed callbacks using their SharedFunctionInfo address. sounds dumb, but is actually not obvious to do.
22:39:40  * rendarquit
22:42:49  <isaacs>neat
22:45:09  * sblomquit (Ping timeout: 272 seconds)
22:46:25  <trevnorris>isaacs: quick review? https://github.com/joyent/node/pull/6563
22:47:52  <trevnorris>yeah. you have to do a custom build of node and print out the generated hydrogen code at the Z trace phase along with --trace-opt. that'll allow you to find the callsite of those unnamed callbacks passed to things like nextTick.
22:49:36  * mikealquit (Quit: Leaving.)
22:56:08  * bradleymeckquit (Quit: bradleymeck)
23:03:19  <MI6>joyent/node: Trevor Norris master * 5757642 : node: allow nextTick infinite recursion - http://git.io/rpM0EA
23:04:05  <trevnorris>isaacs: thanks for the review :)
23:04:27  <isaacs>np
23:04:46  <trevnorris>tjfontaine: you need to teach me some time how to get a good set of stack traces using dtrace or whatever whenever a specific system call is made.
23:05:10  <trevnorris>perf hasn't done it for me yet.
23:06:35  * piscisaureus_quit (Ping timeout: 265 seconds)
23:14:31  * sblomjoined
23:23:35  <MI6>nodejs-master: #717 UNSTABLE osx-x64 (2/677) smartos-ia32 (8/677) smartos-x64 (8/677) osx-ia32 (3/677) http://jenkins.nodejs.org/job/nodejs-master/717/
23:25:05  * paulfryzeljoined
23:29:52  * paulfryzelquit (Read error: Connection reset by peer)
23:30:22  * paulfryzeljoined
23:31:13  * kevinswiberquit (Remote host closed the connection)
23:31:36  * pachetquit (Quit: leaving)
23:34:22  * jmar777joined
23:34:43  * paulfryzelquit (Ping timeout: 245 seconds)
23:36:48  * piscisaureus_joined
23:40:49  * inolenjoined
23:56:46  * mikealjoined
23:57:57  * brsonquit (Ping timeout: 248 seconds)
23:59:53  * brsonjoined