00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:10:53  * dsantiagoquit (Ping timeout: 240 seconds)
00:13:36  * dsantiagojoined
00:19:07  <tjfontaine>LOUDBOT: HOLY SHIT TODAY WAS RELATIVELY PRODUCTIVE
00:19:07  <LOUDBOT>tjfontaine: ARE YOU READY FOR YOUR TWITTER CLIENT TO BE BROKEN?
00:19:12  <tjfontaine>probably
00:19:20  <tjfontaine>LOUDBOT: SEARCH PRODUCTIVITY
00:19:20  <LOUDBOT>tjfontaine: <MDWRIGHT:#ncsulug> EVERYONE KNOWS THE BEST WAY TO MEASURE PRODUCTIVITY IS BY NUMBER OF COMMMITS
00:19:26  <tjfontaine>amen.
00:26:24  * qardquit (Quit: Leaving.)
00:33:02  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:36:03  * loladirojoined
00:43:46  * hueniversejoined
00:51:51  * TooTallNatejoined
00:54:09  * dsantiagoquit (Ping timeout: 246 seconds)
00:58:20  * dsantiagojoined
01:02:02  * bnoordhuisjoined
01:03:52  <trevnorris>oy, creating a c api is way harder than creating a js api.
01:05:41  * mikealquit (Quit: Leaving.)
01:06:23  * bnoordhuisquit (Ping timeout: 246 seconds)
01:19:07  * mikealjoined
01:20:56  * loladiroquit (Quit: loladiro)
01:24:47  * TooTallNatequit (Quit: Computer has gone to sleep.)
01:27:08  <trevnorris>tjfontaine: api thought. just do a single duplex stream. forget read/write.
01:37:35  * abraxasjoined
01:37:42  * bradleymeckjoined
02:17:33  * dominictarrjoined
02:20:53  * groundwa_quit (Ping timeout: 240 seconds)
02:22:41  * groundwaterjoined
02:24:45  * qardjoined
02:29:46  * mikealquit (Quit: Leaving.)
03:00:00  * mikealjoined
03:07:13  * hzquit
03:08:38  * bradleymeckquit (Quit: bradleymeck)
03:16:19  * julianduquequit (Quit: leaving)
03:45:04  * bradleymeckjoined
03:48:53  * mikealquit (Ping timeout: 240 seconds)
03:49:58  * loladirojoined
03:50:59  * TooTallNatejoined
03:58:19  * AvianFlujoined
04:01:16  * AvianFlu_quit (Ping timeout: 240 seconds)
04:05:19  * AvianFlu_joined
04:05:26  * AvianFluquit (Ping timeout: 240 seconds)
04:07:45  * bradleymeckquit (Quit: bradleymeck)
04:08:21  <trevnorris>hello out there, anyone around to bounce some ideas off?
04:14:29  * mikealjoined
04:16:03  * qardquit (Quit: Leaving.)
04:18:08  * kazuponjoined
04:53:00  * AvianFlu_quit (Read error: Connection reset by peer)
04:53:46  * paddybyersjoined
04:54:22  * AvianFlujoined
04:55:39  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
05:04:51  * mikealquit (Read error: Connection reset by peer)
05:05:31  * defunctzombie_zzchanged nick to defunctzombie
05:05:34  * txdvjoined
05:06:21  * txdv_quit (Read error: Connection reset by peer)
05:08:47  * paddybyersquit (Ping timeout: 256 seconds)
05:11:33  * mikealjoined
05:17:50  * c4miloquit (Remote host closed the connection)
05:19:58  * defunctzombiechanged nick to defunctzombie_zz
05:31:10  * loladiroquit (Quit: loladiro)
05:33:38  * mikealquit (Quit: Leaving.)
05:49:02  * st_lukequit (Remote host closed the connection)
06:09:43  * defunctzombie_zzchanged nick to defunctzombie
06:16:31  * isaacsquit (Quit: Lost terminal)
06:23:40  * bajtosjoined
06:32:14  * dominictarrquit (Quit: dominictarr)
06:45:34  * defunctzombiechanged nick to defunctzombie_zz
06:51:57  * rendarjoined
07:36:30  * kazupon_joined
07:37:10  <indutny>hoya
07:37:15  <indutny>just got back to the internet :)
07:37:26  * juliangruberquit (Ping timeout: 240 seconds)
07:37:42  * kazupon_quit (Remote host closed the connection)
07:37:50  * ryahquit (Ping timeout: 240 seconds)
07:38:10  * kazupon_joined
07:38:15  * kazuponquit (Ping timeout: 240 seconds)
07:38:28  * kazupon_quit (Read error: Connection reset by peer)
07:38:50  * kazuponjoined
07:39:52  * ryahjoined
07:43:35  * juliangruberjoined
07:55:31  * defunctzombie_zzchanged nick to defunctzombie
07:56:59  * hzjoined
08:05:01  * defunctzombiechanged nick to defunctzombie_zz
08:28:52  * jameshowejoined
08:29:05  * jameshowequit (Client Quit)
08:36:43  * leonvvjoined
09:02:52  * st_lukejoined
09:03:23  * mralephquit (Read error: Operation timed out)
09:03:47  * mralephjoined
09:10:45  * leonvvquit (Remote host closed the connection)
09:16:44  * ral_changed nick to ral
09:16:58  * ralquit (Changing host)
09:16:58  * raljoined
09:54:17  * kazuponquit (Remote host closed the connection)
09:55:01  * kazuponjoined
10:06:00  * kazuponquit (Remote host closed the connection)
10:23:20  * abraxasquit (Remote host closed the connection)
11:09:18  * kazuponjoined
11:10:27  * `3E|GONEchanged nick to `3E
11:14:00  * leonvvjoined
11:22:04  * st_lukequit (Remote host closed the connection)
11:22:20  * bajtosquit (Quit: bajtos)
11:44:18  * jameshowejoined
11:57:49  * loladirojoined
12:00:03  * loladiroquit (Client Quit)
12:05:32  * leonvvquit (Remote host closed the connection)
12:07:56  * julianduquejoined
12:08:31  * julianduquequit (Remote host closed the connection)
12:09:15  * julianduquejoined
12:30:18  * kazuponquit (Remote host closed the connection)
12:37:24  * dominictarrjoined
12:50:45  * jmar777joined
12:58:24  * bajtosjoined
13:06:10  * c4milojoined
13:11:31  * c4miloquit (Remote host closed the connection)
13:14:52  * jameshowequit (Quit: Leaving)
13:29:06  * dominictarrquit (Quit: dominictarr)
13:40:45  * kazuponjoined
13:46:21  * kazuponquit (Ping timeout: 264 seconds)
13:56:03  * c4milojoined
13:57:32  * c4miloquit (Remote host closed the connection)
13:58:41  * piscisaureus_joined
14:02:11  * c4milojoined
14:03:44  * c4miloquit (Remote host closed the connection)
14:04:35  * c4milojoined
14:08:37  <piscisaureus_>ola
14:36:00  * c4miloquit (Remote host closed the connection)
14:37:29  * isaacsjoined
14:39:29  * dsantiagoquit (Quit: Computer has gone to sleep.)
14:39:59  <isaacs>whoa, my dtach socket, and irssi, crashed completely about 8 hours ago
14:40:01  <isaacs>that's so weird
14:40:44  * pachetjoined
14:40:44  * pachetquit (Changing host)
14:40:44  * pachetjoined
14:41:44  <isaacs>ircretary: tell bnoordhuis Ping. A fellow wants to take over the mmap module, make it use node-gyp, etc. Any objections to this?
14:41:44  <ircretary>isaacs: I'll be sure to tell bnoordhuis
15:03:42  * c4milojoined
15:05:42  <indutny>heya!
15:05:46  <indutny>I'm back to the internet :)
15:09:29  <isaacs>indutny: wb!
15:09:55  <indutny>:)
15:09:57  <indutny>thanks
15:15:48  * kazuponjoined
15:18:32  * kazuponquit (Remote host closed the connection)
15:19:49  * `3Echanged nick to `3rdEden
15:33:40  * c4miloquit (Remote host closed the connection)
15:34:55  * c4milojoined
15:37:57  * julianduquequit (Ping timeout: 264 seconds)
15:54:51  <MI6>joyent/node: Timothy J Fontaine master * f88b8da : test: regression test for #5798 setImmediate (+1 more commits) - http://git.io/LKaDAw
15:56:20  <tjfontaine>isaacs: thanks
15:56:34  <MI6>joyent/node: isaacs v0.10 * ff8a405 : npm: Upgrade to 1.3.3 - http://git.io/RRdudQ
15:57:07  <MI6>joyent/node: isaacs master * 9da67fa : npm: Upgrade to 1.3.3 - http://git.io/JmIvVQ
15:57:18  * defunctzombie_zzchanged nick to defunctzombie
15:57:25  <isaacs>tjfontaine: you haven't done a libuv release yet, correct?
15:57:31  <tjfontaine>correct
16:00:06  <isaacs>ok, i'll do that one. it's easy :)
16:00:15  <isaacs>just testing with the latest uv master HEAD
16:00:18  <tjfontaine>oh
16:00:20  <tjfontaine>that's broken
16:00:28  <tjfontaine>because of the errno changes, iirc
16:01:09  <piscisaureus_>http://www.gizoogle.net/index.php?search=node.js&se=Gizoogle+Dis+Shiznit
16:01:29  <tjfontaine>haha
16:02:31  <isaacs>tjfontaine, bnoordhuis: libuv master HEAD doesn't build with node master on os x
16:02:46  <tjfontaine>isaacs: right because of the errno changes
16:02:51  <isaacs>../deps/uv/include/uv.h:171:3: note: 'uv_errno_t' declared here
16:02:51  <isaacs>} uv_errno_t; ^
16:02:51  <isaacs>fatal error: too many errors emitted, stopping now [-ferror-limit=]
16:02:51  <isaacs>20 errors generated.
16:02:51  <isaacs>make[1]: *** [/Users/isaacs/dev/js/node-master/out/Release/obj.target/node/src/node.o] Error 1
16:02:54  <isaacs>make: *** [node] Error 2
16:02:56  <isaacs>yeah
16:02:59  <isaacs>too many errors
16:03:30  <tjfontaine>so we can do a release with out a uv upgrade, or we can wait for ben to integrate :)
16:07:21  * tjfontainetaps on jenkins.nodejs.org ssh port
16:07:48  * leonvvjoined
16:16:52  * bnoordhuisjoined
16:24:14  <tjfontaine>isaacs: ok, cert installed I think
16:24:16  <tjfontaine>bnoordhuis: gday
16:29:16  * dsantiagojoined
16:35:46  * ik_changed nick to ik
16:41:52  * c4milo_joined
16:42:03  * bajtos_joined
16:42:17  <MI6>nodejs-master: #302 UNSTABLE smartos-x64 (8/611) http://jenkins.nodejs.org/job/nodejs-master/302/
16:42:35  * kenperkins_joined
16:43:57  * hzquit (Disconnected by services)
16:44:01  * hzjoined
16:46:10  * mcavage_joined
16:46:16  <bnoordhuis>tjfontaine: hey
16:46:37  <tjfontaine>hey
16:46:46  <tjfontaine>how are you feeling today?
16:48:22  * dsantiag_joined
16:50:58  * dsantiagoquit (*.net *.split)
16:50:58  * c4miloquit (*.net *.split)
16:50:59  * bajtosquit (*.net *.split)
16:50:59  * mcavagequit (*.net *.split)
16:50:59  * kenperkinsquit (*.net *.split)
16:51:00  * bajtos_changed nick to bajtos
16:55:20  * c4milo_quit (Remote host closed the connection)
16:55:26  * leonvvquit (Remote host closed the connection)
16:56:05  * c4milojoined
16:57:42  <bnoordhuis>tjfontaine: could be worse, could be better
16:58:14  <tjfontaine>at least you're alive :)
16:58:30  <bnoordhuis>yeah, that's something :)
16:59:20  * hzquit (Disconnected by services)
16:59:23  * hzjoined
17:00:34  <bnoordhuis>isaacs: re mmap module, i think i have an email from that guy in my backlog
17:01:32  * juliangruber_joined
17:02:37  * kenperkinsjoined
17:02:59  <tjfontaine>bnoordhuis: how do you feel about doing a libuv v0.11 release and doing the integration work? :P
17:04:23  * juliangruberquit (Ping timeout: 246 seconds)
17:04:23  * juliangruber_changed nick to juliangruber
17:04:24  * kenperkins_quit (Ping timeout: 246 seconds)
17:07:56  <bnoordhuis>tjfontaine: i was planning on doing that
17:08:02  <bnoordhuis>is there a rush?
17:08:30  <tjfontaine>there's no rush exactly, just that isaac wanted me to do a v0.11 node release
17:08:49  <MI6>nodejs-v0.10: #281 UNSTABLE smartos-ia32 (6/594) smartos-x64 (10/594) http://jenkins.nodejs.org/job/nodejs-v0.10/281/
17:09:34  * defunctzombiechanged nick to defunctzombie_zz
17:10:58  <bnoordhuis>tjfontaine: ah okay. i can maybe do that tonight
17:11:03  <bnoordhuis>okay, dinner. biab
17:11:06  <tjfontaine>enjoy
17:11:10  <bnoordhuis>thanks :)
17:11:28  <tjfontaine>:)
17:12:06  <MI6>nodejs-v0.10-windows: #109 UNSTABLE windows-ia32 (150/594) windows-x64 (9/594) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/109/
17:13:54  * TooTallNatejoined
17:14:15  * defunctzombie_zzchanged nick to defunctzombie
17:15:16  * bnoordhuisquit (Ping timeout: 240 seconds)
17:15:43  * defunctzombiechanged nick to defunctzombie_zz
17:17:56  * mikealjoined
17:18:21  <creationix>is it possible to use libuv in multi-threaded environments?
17:18:27  <creationix>I'd have a unique event loop per thread
17:22:49  * loladirojoined
17:24:45  * leonvvjoined
17:29:54  * piscisaureus_quit (Ping timeout: 246 seconds)
17:30:39  * defunctzombie_zzchanged nick to defunctzombie
17:38:30  * c4miloquit (Remote host closed the connection)
17:38:51  <tjfontaine>trevnorris: ugh, you can't be serious
17:38:56  * c4milojoined
17:42:22  <trevnorris>tjfontaine: what?
17:43:13  * c4miloquit (Ping timeout: 246 seconds)
17:43:14  <tjfontaine>5798
17:43:20  <tjfontaine>I've commented
17:46:25  <trevnorris>tjfontaine: then we should really get our ideas of how this should work, and what the documentation says, straightened out.
17:46:48  <tjfontaine>we should remove nextTick from the documentation :P
17:47:32  <trevnorris>and wtf is up with setTimeout(...,0)?
17:47:45  <tjfontaine>it's an implementation detail
17:48:08  <tjfontaine>because everything gets put into buckets based on the time
17:48:19  <tjfontaine>so there's only one jump from c/js for each bucket
17:48:33  <tjfontaine>so if you schedule them on the same tick you get the same experience as setImmediate
17:49:21  <trevnorris>if setImmediate is going to fire before nextTick, then we shouldn't even be using it internally.
17:49:39  <trevnorris>nextTick that is
17:50:26  <tjfontaine>it's not that setImmediate "fires" before nextTick, if you schedule a nextTick outside of the setImmediate it will fire first
17:50:45  <tjfontaine>it's just that everything queued for setImmediate is fired, and then execution continues
17:51:21  <tjfontaine>which is exactly how the rest of our timers work
17:51:45  <tjfontaine>so before this commit, setImmediate was an oddball
17:51:56  * mikealquit (Quit: Leaving.)
17:53:07  * mikealjoined
17:54:20  <trevnorris>did we add documentation that setImmediate can starve I/O?
17:55:09  <tjfontaine>we updated the documentation, but it can't starve io in anyway different than scheduling a lot of timeouts with the same timer, it doesn't starve in the same way that nextTick does
17:56:02  <MI6>nodejs-master-windows: #109 UNSTABLE windows-ia32 (23/611) windows-x64 (19/611) http://jenkins.nodejs.org/job/nodejs-master-windows/109/
18:03:09  * pachetquit (Ping timeout: 264 seconds)
18:04:26  * mikealquit (Quit: Leaving.)
18:07:23  * mikealjoined
18:15:11  * mcavage_quit (Remote host closed the connection)
18:25:08  <ryah>when is 0.12 coming out?
18:25:14  <ryah>and will it be faster?
18:27:54  <tjfontaine>WIR, and some things TLS again
18:32:52  <isaacs>ack, just accidentally unpublished npm
18:32:59  <isaacs>that's WAY too easy to do. stupid --force
18:37:03  * piscisaureus_joined
18:45:12  * bajtosquit (Quit: bajtos)
18:46:55  <isaacs>piscisaureus_, bnoordhuis: hey
18:47:06  <isaacs>libuv master is not playing nice with node-master on os x
18:47:12  <isaacs>too many errors, fails to build.
18:47:42  <tjfontaine>isaacs: ben said he was going to do the integration tonight (I presume he means his night)
18:48:25  * piscisaureus_quit (Ping timeout: 276 seconds)
18:49:44  * pachetjoined
18:56:14  <tjfontaine>before I push this, does this look right? https://github.com/tjfontaine/node/commit/5d344ae75f101f13989b83277bf23683b02cbd4e
18:59:28  * defunctzombiechanged nick to defunctzombie_zz
19:00:19  * leonvvquit (Remote host closed the connection)
19:01:03  * dominictarrjoined
19:12:46  * inolenquit (Ping timeout: 240 seconds)
19:13:08  <isaacs>tjfontaine: i need to push npm 1.3.4 first
19:13:18  <isaacs>tjfontaine: also, you shouldn't have to merge deps/npm into master, it sould already be there.
19:13:38  <isaacs>oh, i guess that's why it's on the conflicts list :)
19:13:43  <tjfontaine>:)
19:13:53  * inolenjoined
19:14:10  <tjfontaine>so the work flow I did: git merge upstream/v0.10, git reset deps/uv deps/npm, resolve remaining conflicts, commit
19:15:07  <isaacs>ok
19:15:20  <isaacs>i usually `git checkout master -- deps/{uv,npm}`
19:15:25  <isaacs>but i think reset will do the same thing
19:15:57  <tjfontaine>ya, the difference will be that I see the unmerged changes
19:17:16  <tjfontaine>brb lunch
19:17:32  <isaacs>tjfontaine: k, i'll have npm done by the time you get back
19:18:04  * mcavagejoined
19:18:12  * mcavagequit (Remote host closed the connection)
19:18:25  * mcavagejoined
19:29:46  * qardjoined
19:36:24  * hzquit
19:36:53  * mikealquit (Quit: Leaving.)
19:55:59  * paddybyersjoined
19:56:45  * wpreuljoined
19:59:08  <wpreul>on node 0.10.12 seeing 4000 objects with the following structure: { callback, domain } in a core dump. Does this object structure look familiar to anyone?
19:59:54  <tjfontaine>hm, if it were a timer it should be _onTimeout
20:01:20  * piscisaureus_joined
20:07:04  * piscisaureus_quit (Ping timeout: 246 seconds)
20:07:16  * mikealjoined
20:07:19  * julianduquejoined
20:09:42  * CAPSLOCKBOTquit (Ping timeout: 264 seconds)
20:10:18  * LOUDBOTquit (Ping timeout: 264 seconds)
20:13:00  * defunctzombie_zzchanged nick to defunctzombie
20:15:03  * CAPSLOCKBOTjoined
20:15:28  <MI6>joyent/node: isaacs v0.10 * 5e86519 : npm: Upgrade to 1.3.4 - http://git.io/gERhDg
20:15:34  * LOUDBOTjoined
20:15:51  <isaacs>tjfontaine: so
20:15:53  <tjfontaine>so
20:15:56  <isaacs>tjfontaine: build?
20:16:03  <isaacs>oh, need to land 0.10 merge first
20:16:05  <isaacs>so npm isn't borked
20:16:10  <tjfontaine>right
20:17:04  <tjfontaine>so this time I am going to let npm come through the merge?
20:17:12  <isaacs>tjfontaine: yes
20:17:14  <tjfontaine>k
20:17:23  * bajtosjoined
20:17:27  <isaacs>tjfontaine: in fact, `git checkout upstream/v0.10 -- deps/npm` even
20:17:52  <tjfontaine>k
20:20:29  * bajtosquit (Client Quit)
20:21:17  * bnoordhuisjoined
20:22:02  <tjfontaine>isaacs: I don't think we did "now working on 0.11.4" on last release, should I fix that in the merge or a separate commit?
20:23:02  * paddybyersquit (Ping timeout: 240 seconds)
20:23:14  <bnoordhuis>tjfontaine: are you doing a release?
20:24:03  <tjfontaine>bnoordhuis: at the moment just doing the v0.10 merge to v0.11
20:24:17  <bnoordhuis>okay
20:24:58  <bnoordhuis>i'd already prepared the libuv api change for node but it's conflicts galore after our recent v8 upgrade
20:25:27  <bnoordhuis>nothing i can't fix, mind you, but it will take me a while to sort out
20:25:29  <isaacs>tjfontaine: orly??
20:25:34  <tjfontaine>bnoordhuis: ok well then we may just do a release with out a new libuv until you can solidify that
20:25:56  <bnoordhuis>yeah, that's probably best
20:26:02  <tjfontaine>isaacs: https://github.com/joyent/node/blob/master/src/node_version.h#L27
20:26:13  <isaacs>ooh, whoops
20:26:19  <isaacs>tjfontaine: yeah, go ahead and change that asap
20:26:24  <MI6>nodejs-v0.10: #282 UNSTABLE smartos-x64 (1/594) http://jenkins.nodejs.org/job/nodejs-v0.10/282/
20:26:28  <tjfontaine>ok, I'll do it in the merge
20:27:11  <isaacs>sure
20:27:48  <tjfontaine>ok this looks pretty good, https://github.com/tjfontaine/node/commit/48c542db523d88c79f62c6346b91bdf4b828ff6b
20:28:55  <isaacs>tjfontaine: yep, lgtm
20:29:05  <MI6>joyent/node: Timothy J Fontaine master * 48c542d : Merge remote-tracking branch 'upstream/v0.10' (+17 more commits) - http://git.io/1jeGDQ
20:29:08  <isaacs>bnoordhuis: we can pull the latest libuv into node-master after 11.4
20:29:21  <isaacs>bnoordhuis: it's a big change, so it'd be good to land right *after* a release, rather than right before one
20:30:12  * jmar777quit (Remote host closed the connection)
20:30:38  <MI6>joyent/node: tjfontaine created branch v0.11.4-release - http://git.io/HLj65Q
20:30:49  * jmar777joined
20:32:24  <bnoordhuis>isaacs: agreed
20:32:44  <tjfontaine>lots more things to prune in an unstable branch :)
20:34:50  <isaacs>tjfontaine: did the windows keys load on your computer?
20:34:58  <isaacs>er, vm
20:35:28  <tjfontaine>isaacs: yup, and things appeared to build fine
20:35:33  <tjfontaine>but we'll find out shortly
20:35:40  * jmar777quit (Ping timeout: 276 seconds)
20:35:56  <isaacs>kewl!
20:36:36  * dominictarrquit (Quit: dominictarr)
20:37:17  <tjfontaine>how descriptive do you tend ot be in on the unstables?
20:38:54  <isaacs>in teh changelog?
20:38:58  <isaacs>same as stables
20:39:39  <tjfontaine>k
20:41:13  <isaacs>tjfontaine: typically unstables have more changes, so you dont' need to pruneit down soo far
20:41:14  <tjfontaine>isaacs: https://gist.github.com/tjfontaine/5987663
20:41:29  <tjfontaine>I consolidated some of the things, like the v8 upgrade
20:43:01  <isaacs>yep
20:43:06  <isaacs>as you do :)
20:43:22  <MI6>nodejs-master: #303 UNSTABLE linux-ia32 (1/612) smartos-ia32 (1/612) smartos-x64 (9/612) http://jenkins.nodejs.org/job/nodejs-master/303/
20:44:00  <tjfontaine>isaacs: lgty then?
20:44:10  <tjfontaine>spaced properly of course
20:45:23  <isaacs>tjfontaine: pruned https://gist.github.com/isaacs/5987684
20:45:35  <isaacs>tjfontaine: pretty much any chagnes to anything internal is unnecessary to mention
20:45:48  <isaacs>and dep upgrades are nameless
20:46:25  <tjfontaine>alright
20:47:30  <MI6>nodejs-v0.10-windows: #110 UNSTABLE windows-x64 (11/594) windows-ia32 (11/594) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/110/
20:51:04  * hzjoined
20:51:40  <MI6>joyent/node: Timothy J Fontaine v0.11.4-release * b5b8419 : 2013.07.12, Version 0.11.4 (Unstable) - http://git.io/uVIGrw
20:51:51  <tjfontaine>ok, so I'm changing the order of operations slightly
20:52:11  <tjfontaine>blerg why didn't it change the version
20:52:29  <isaacs>tjfontaine: yes, change up whatever makes it more efficient. do bump the version, though ;)
20:53:09  <tjfontaine>:)
20:53:31  <tjfontaine>https://github.com/joyent/node/blob/v0.11.4-release/src/node_version.h#L29
20:53:36  <tjfontaine>so that's right
20:54:50  * tjfontainewatches all the jenkins executors light up
20:56:10  <isaacs>tjfontaine: oh, right
20:56:30  <isaacs>tjfontaine: so, basically, we've been lying between 11.3 and 11.4, claiming that it's already the 11.4 release?
20:56:33  <tjfontaine>ok so this is something I didn't realize from the 0.11.3 issue, master is still marked as 1
20:56:40  <tjfontaine>isaacs: yes
20:56:46  <tjfontaine>well
20:56:46  <tjfontaine>no
20:56:55  <tjfontaine>we've been saying builds have been releases :)
20:57:15  <isaacs>tjfontaine: right, but why is it 11.4?
20:57:17  <isaacs>and nto 11.3?
20:57:21  * isaacsso confused
20:57:43  <isaacs>yeah, on master right now:
20:57:44  <isaacs>#define NODE_MAJOR_VERSION 0
20:57:44  <isaacs>#define NODE_MINOR_VERSION 11
20:57:44  <isaacs>#define NODE_PATCH_VERSION 4
20:57:44  <isaacs>#define NODE_VERSION_IS_RELEASE 1
20:57:54  <tjfontaine>right
20:58:16  <tjfontaine>so when this is done, and I merge v0.11.4-release into master, I change that to be 0 11 5 0
20:58:26  <tjfontaine>and say "now working on v0.11.5"
20:58:54  <isaacs>right
20:58:57  <isaacs>weird
20:59:10  <tjfontaine>which was the step/commit that got dropped after the last release
21:00:16  <isaacs>tjfontaine: ohh
21:00:24  <isaacs>tjfontaine: right, you called it a 4 in the merge commit
21:00:30  <isaacs>tjfontaine: now i understand what you were asking.
21:00:35  <isaacs>tjfontaine: yea... next time, don't do that :)
21:00:40  <isaacs>it's confusing
21:00:53  <tjfontaine>:)
21:00:58  <isaacs>tjfontaine: hopefully, next time it's a robot who doesn't make mistakes like us lovable meatbags
21:01:04  <tjfontaine>hehe
21:01:45  <tjfontaine>it's getting better, at least my laptop doesn't have to suffer the same fate as yours :)
21:04:31  <isaacs>remember: no `make website-upload`
21:04:46  <tjfontaine>good protip
21:05:00  * dominictarrjoined
21:05:01  <tjfontaine>what do I do for the blog?
21:05:15  * pachet_joined
21:05:25  <trevnorris>bnoordhuis: i'm curious, what reason was there for typedef'ing uv_*_s to uv_*_t?
21:05:57  <tjfontaine>trevnorris: it's a common pattern to make the types opaque, so people don't try and rely on struct members
21:07:01  * pachetquit (Ping timeout: 256 seconds)
21:07:55  * defunctzombiechanged nick to defunctzombie_zz
21:13:18  <MI6>nodejs-master-windows: #110 UNSTABLE windows-ia32 (18/612) windows-x64 (16/612) http://jenkins.nodejs.org/job/nodejs-master-windows/110/
21:13:47  <isaacs>tjfontaine: blog posts are always done from the stable branch
21:14:35  <isaacs>tjfontaine: i keep node checked out into two separate folders, and i think there's a command in that gist that will generate it in the right place for you, from the email.md file and the shasums
21:14:57  * paddybyersjoined
21:15:41  <tjfontaine>isaacs: right so just copy the blog to the stable, I can do that
21:21:26  <isaacs>yep
21:22:08  * mikealquit (Quit: Leaving.)
21:22:10  * piscisaureus_joined
21:25:38  * mikealjoined
21:25:53  * rendarquit
21:26:58  <trevnorris>tjfontaine: cool thanks. i'm totally biting off more than I can chew with this one: http://git.io/xv-VOw
21:27:30  <tjfontaine>heh what are you doing?
21:28:34  <trevnorris>trying to make a c api that is similar to node's
21:29:01  <trevnorris>isaacs had mentioned a node.c implementation would be cool, so thought it would be a good way to learn c and understand libuv better.
21:29:45  <tjfontaine>heh
21:31:07  <isaacs>trevnorris: neat!
21:31:52  <trevnorris>isaacs: hopefully. though i'm sure my code will make bnoordhuis throw up a little. :)
21:32:04  * mikealquit (Quit: Leaving.)
21:34:25  * defunctzombie_zzchanged nick to defunctzombie
21:35:16  <MI6>joyent/node: tjfontaine created tag v0.11.4 - http://git.io/tFUNJA
21:35:44  * mikealjoined
21:37:59  * bnoordhuisquit (Ping timeout: 259 seconds)
21:39:58  <tjfontaine>isaacs: http://nodejs.org/dist/v0.11.4/ msi appears to be signed relatively appropriately
21:40:30  <trevnorris>tjfontaine: for some reason chrome thinks that page is in danish :P
21:40:44  <tjfontaine>the shasums, but ya :)
21:42:19  * txdv_joined
21:42:46  * txdvquit (Read error: Connection reset by peer)
21:43:11  * hzquit
21:44:03  * piscisaureus_quit (Ping timeout: 260 seconds)
21:46:59  <tjfontaine>isaacs: ok to continue to with things? doing make blog-upload in stable, and sending the email, merging -release back into master?
21:48:23  * paddybyersquit (Ping timeout: 256 seconds)
21:48:53  <tjfontaine>brb
21:49:37  * pachet_quit (Quit: leaving)
21:51:27  <tjfontaine>hm
21:58:51  <isaacs>tjfontaine: lgtm!
21:58:58  <tjfontaine>salright
21:59:10  <tjfontaine>only a few more pieces I can break from here :)
21:59:34  <isaacs>tjfontaine: pkgsrc ftw!
22:01:54  <tjfontaine>it's odd that `make blog-upload` requires a built tree :)
22:02:16  * mcavagequit (Remote host closed the connection)
22:05:27  * st_lukejoined
22:06:11  <trevnorris>tjfontaine: _http_client.js line 148 lint error, indent comment
22:06:50  <tjfontaine>sweet mary and joseph how did that happen
22:07:37  <tjfontaine>oh bad vim paste
22:07:57  <tjfontaine>I don't think that necessarily warrants a new build, :)
22:07:58  <trevnorris>heh
22:10:15  <trevnorris>hm. yeah I think it does. that lint error will destroy everything. :P
22:10:36  <tjfontaine>isaacs: ruling?
22:10:46  <trevnorris>oh, i'm totally kidding.
22:10:54  <tjfontaine>hehe, well it will make `make test` unhappy
22:13:42  <tjfontaine>ok I'm going to continue on my way
22:14:36  <MI6>joyent/node: Timothy J Fontaine v0.10 * 21dd5f4 : blog: v0.11.4 release - http://git.io/H6BqvA
22:17:40  <MI6>joyent/node: Timothy J Fontaine master * 81c2a36 : Now working on 0.11.5 (+2 more commits) - http://git.io/lkI6gg
22:19:20  <MI6>joyent/node: Timothy J Fontaine master * c898704 : lint: fix _http_client.js after v0.10 merge - http://git.io/BhkKoA
22:19:25  <tjfontaine>trevnorris: ^^ :)
22:19:40  <isaacs>tjfontaine: no, do not make a new build for a lint error.
22:19:46  <tjfontaine>isaacs: nod
22:19:52  <isaacs>tjfontaine: but DO let it burn your soul a little bit.
22:20:00  <trevnorris>haha
22:20:01  <tjfontaine>it was my fault for not linting after the merge
22:20:21  <tjfontaine>and forgetting that the CI doesn't lint, just runs the test suites
22:20:22  <trevnorris>he admits it! GUILTY!!!
22:20:29  <tjfontaine>yes, all my fault
22:20:35  * mikealquit (Quit: Leaving.)
22:20:44  <tjfontaine>totally and utterly my fault :)
22:21:44  <trevnorris>tjfontaine: just for you https://github.com/joyent/node/pull/5842
22:22:01  <tjfontaine>trevnorris: aww, thanks :)
22:22:44  <trevnorris>ah, now I remember why I didn't do this to begin with. the license at the top is longer than the actual code :P
22:22:45  <tjfontaine>trevnorris: I think it also needs to go to all.markdown not just toc
22:22:54  <trevnorris>oh yeah. thanks.
22:22:55  <tjfontaine>trevnorris: heh, like many of our tests :)
22:23:29  <trevnorris>tjfontaine: true.
22:24:14  <trevnorris>i was thinking, while not applicable for core (so probably best left up to user-land) it'd be trivial at this point to shim in a smalloc.alloc(size, obj, TYPE)
22:24:28  <trevnorris>where TYPE is uint8, uint16, etc.
22:24:44  <trevnorris>instead of just always assigning a uint8 to it.
22:25:14  <trevnorris>isaacs: thoughts? ^
22:26:17  * defunctzombiechanged nick to defunctzombie_zz
22:27:09  <tjfontaine>I'm not completely advocating this atm, but it would be neat if I could change that for Buffer instances
22:28:13  <isaacs>trevnorris: hrm. i'd kick it down thte road until we actually need it
22:28:24  <isaacs>trevnorris: probably best left to userland if core doesn't need to use it
22:28:32  <trevnorris>thought about that, but would be dangerous/difficult since we pass those around internally expecting it to behave specifically.
22:28:54  <trevnorris>isaacs: yeah. that was my thought. was just one of those, but it would just take a few more lines of code, moments.
22:28:56  <tjfontaine>ya, which is why I'm not advocating it, just something that I thought would be neat :)
22:29:33  <isaacs>tjfontaine: nicely done on the build :)
22:29:49  <tjfontaine>isaacs: still plenty of tooling to write to make it easier
22:29:54  <tjfontaine>:)
22:30:11  <trevnorris>you know, it almost hurts me to admit this, but the ArrayBuffer impl in v8 isn't that bad. and since it allows you to pass in data, we could get around the memset issue.
22:30:31  <isaacs>trevnorris: ooh... that's pretty rad
22:30:52  <trevnorris>isaacs: yeah. it's on my list of experimental things to try.
22:31:45  <tjfontaine>they still don't memcpy it?
22:31:50  <tjfontaine>er
22:31:52  <tjfontaine>poorly phrased
22:32:00  <tjfontaine>do they memcpy on that path?
22:32:15  <trevnorris>no. if you pass a char* in the cc api no memcpy occurs, iirc
22:33:13  <trevnorris>tjfontaine: yeah. it doesn't memcpy http://git.io/co6sxQ
22:33:57  * mcavagejoined
22:34:32  <tjfontaine> Allocator::Allocate that is set with V8::SetArrayBufferAllocator. <-- we can even eventually get an arena allocator back in
22:34:32  * mcavagequit (Read error: Connection reset by peer)
22:34:46  <tjfontaine>:)
22:34:53  * mcavagejoined
22:35:17  <MI6>nodejs-v0.10: #283 UNSTABLE smartos-ia32 (4/594) smartos-x64 (4/594) osx-ia32 (1/594) http://jenkins.nodejs.org/job/nodejs-v0.10/283/
22:35:38  <tjfontaine>ArrayBuffer::Externalize is also quite handy
22:37:13  <MI6>nodejs-master: #304 UNSTABLE linux-ia32 (1/612) smartos-ia32 (4/612) linux-x64 (1/612) smartos-x64 (8/612) http://jenkins.nodejs.org/job/nodejs-master/304/
22:37:47  <tjfontaine>oh, trevnorris your "dispose" idea is called Neuter, that's an *excellent* name :)
22:39:41  * sblomjoined
22:39:54  <tjfontaine>ya I'm leaning towards the feeling we might be able to make Buffer inherit from ArrayBuffer now
22:40:33  <trevnorris>tjfontaine: Neuter? is that like an official term or something?
22:40:50  * leonvvjoined
22:40:58  <tjfontaine>trevnorris: that's an official part of the ArrayBuffer api for externalized ArrayBuffers
22:40:59  <trevnorris>and yeah. i'm going to do some performance experimentation with ArrayBuffer to see if it'll work.
22:41:12  <tjfontaine>(which nearly all of our buffers are)
22:41:17  <tjfontaine>or rather would be
22:41:36  <trevnorris>the only issue is that we'll break backwards compatibility for .slice, and casting a TypedArray over an ArrayBuffer is freakishly slow.
22:42:10  <trevnorris>awesome. maybe i'll change the api to smalloc.neuter()
22:42:27  <tjfontaine>but they really can't get much movement between Buffer -> TypedArray now as it is?
22:42:33  <tjfontaine>not without the memcpy
22:43:05  <tjfontaine>at the very least this provides a path to hoist a buffer to an ArrayBuffer
22:43:07  <trevnorris>well, technically if Buffer#dispose() is implemented then we can. because we'll be able to reassign the memory to an array buffer
22:43:22  <trevnorris>w/o a memcpy that is
22:44:27  * bnoordhuisjoined
22:47:35  <MI6>nodejs-v0.10-windows: #111 UNSTABLE windows-x64 (11/594) windows-ia32 (12/594) http://jenkins.nodejs.org/job/nodejs-v0.10-windows/111/
22:48:58  * bnoordhuisquit (Ping timeout: 245 seconds)
22:49:13  <MI6>nodejs-master: #305 UNSTABLE linux-ia32 (1/612) smartos-x64 (9/612) http://jenkins.nodejs.org/job/nodejs-master/305/
22:53:18  <MI6>nodejs-master-windows: #111 UNSTABLE windows-ia32 (14/612) windows-x64 (15/612) http://jenkins.nodejs.org/job/nodejs-master-windows/111/
23:01:55  * wpreulquit (Ping timeout: 276 seconds)
23:04:46  * dominictarrquit (Quit: dominictarr)
23:05:26  <isaacs>ircretary: tell piscsaureus How's execSync coming? you can get $200 to finish it: https://www.bountysource.com/issues/82455-any-chance-of-a-synchronous-child_process-exec-spawn-in-the-future/bounties
23:05:26  <ircretary>isaacs: I'll be sure to tell piscsaureus
23:06:18  <sblom>isaacs: That's a great business model for StrongLoop!
23:06:58  * mikealjoined
23:08:50  <tjfontaine>he'll have to fight with https://github.com/mgutz/execSync :P
23:10:22  * AvianFluquit (Remote host closed the connection)
23:12:15  <isaacs>haha
23:12:48  * dominictarrjoined
23:13:11  <sblom>Can you imagine subcontracting our bountysource bounties to odesk? It's like OSS engineering arbitrage!
23:13:20  <sblom>s/our/out/
23:13:43  <tjfontaine>haha
23:16:32  <tjfontaine>LOUDBOT: SEARCH ARBITRAGE
23:16:33  <LOUDBOT>PEERGUARDIAN IS SO AWESOME I LOVE IT
23:19:35  * pooyajoined
23:20:14  * loladiroquit (Quit: loladiro)
23:20:24  <trevnorris>ooh. I like those.
23:24:29  <trevnorris>isaacs: api extension question. buffer.writeUint8(2).writeUint32LE(256)... and have the new write automatically write to where the old one left off.
23:24:42  <tjfontaine>no, it already returns the offset?
23:24:52  <trevnorris>nope. returns undefined.
23:25:00  <tjfontaine>I think we have an issue on this
23:25:08  <tjfontaine>where we agreed to do the new offset
23:25:08  <trevnorris>yup. and it's assigned to me. :)
23:25:27  <trevnorris>yeah. but this is sort of the new offset + more
23:25:39  <tjfontaine>https://npmjs.org/package/buffercursor already does this
23:25:44  <trevnorris>the reason for returning the new offset was so they could keep track of where to write next.
23:28:58  * piscisaureus_joined
23:29:19  <trevnorris>tjfontaine: this way it could also work with fill. e.g. buffer.fill('abc', 0, 6).writeUint16LE(10)...
23:29:26  * piscisaureus_quit (Client Quit)
23:32:02  <tjfontaine>trevnorris: the thing is to do this we need to add api for finding out where we are, and moving the pointer, it's not quite as simple of a semantic to get right for people who aren't expecting the current position offset to change out from underneath them
23:32:47  <tjfontaine>trevnorris: otoh, returning the new offset allows you to not have to worry how large the type was just written, which is considerably more straight forward
23:33:56  <trevnorris>tjfontaine: i'm writing them both up. each is a trivial fix.
23:40:43  * leonvvquit (Remote host closed the connection)
23:48:40  <trevnorris>ok. I should say trivial if you know cc. wtf, can a template function not have a return type?
23:51:41  <tjfontaine>isaacs: sigh, ping
23:52:07  <trevnorris>ah, nm. expanded macro had a different return type.