00:00:16  <ryah>okay guys i ahve to go. i'll BB in about 6 hours
00:00:42  <bnoordhuis>say hi to your mom from me, ryah
00:02:59  * piscisaureus_joined
00:03:55  <piscisaureus>ryah: naah this patch wasn't yet landed because I had to get out of the train
00:27:16  <bnoordhuis>curious... /buffer/102400 clustered with 8 workers is only twice as fast as non-clustered master
00:27:36  <bnoordhuis>network congestion?
00:36:30  <igorzi>bnoordhuis: there should be no other traffic on that network.. what numbers are you getting?
00:36:50  <bnoordhuis>igorzi: let me gist it
00:37:54  <bnoordhuis>igorzi: https://gist.github.com/1340878
00:38:05  <CIA-95>libuv: Bert Belder fseventflags * rd35b903 / (7 files in 4 dirs): Add flags to uv_fs_event_init - http://git.io/gA2yiA
00:38:13  <bnoordhuis>### master - /bytes/10240
00:38:13  <bnoordhuis>log2.xml , 2156.7, 0.0, 10876, 0.0, 0
00:38:19  <piscisaureus>bnoordhuis: igorzi: will that do? --^
00:38:22  <bnoordhuis>wait, sorry
00:38:30  <bnoordhuis>### master - /bytes/102400
00:38:30  <bnoordhuis>log3.xml , 23.5, 0.0, 63751, 0.0, 35
00:38:47  <bnoordhuis>^ worrisome
00:39:35  <bnoordhuis>piscisaureus: on either backend <- s/either/any/
00:40:05  <bnoordhuis>piscisaureus: s/NFS shares/NFS mounts/
00:40:56  <bnoordhuis>otherwise lgtm i suppose
00:42:29  <CIA-95>libuv: Bert Belder master * r1997e10 / (7 files in 4 dirs): Add flags to uv_fs_event_init - http://git.io/a3-39Q
00:44:36  <piscisaureus>why is libuv not upgraded in node?
00:45:55  <igorzi>piscisaureus: i think we were waiting for your uv_fs_event change
00:46:33  <piscisaureus>igorzi: but the uv_pipe_connect change also needs to be reflected in node right?
00:47:02  <igorzi>piscisaureus: yes
00:47:22  <igorzi>piscisaureus: let me do that
00:49:07  <piscisaureus>igorzi: ket me upgrade libuv now
00:49:28  <igorzi>piscisaureus: k
00:49:58  <igorzi>piscisaureus: does this https://gist.github.com/1340893 look ok to you?
00:50:38  <CIA-95>node: Bert Belder master * rb54da8a / (13 files in 4 dirs): Upgrade libuv to 1997e10b50 - http://git.io/qNs6EQ
00:51:35  <piscisaureus>igorzi: yes, looks okay
00:52:57  * mikealquit (Quit: Leaving.)
00:55:53  * ericktquit (Quit: erickt)
01:02:33  <CIA-95>node: Igor Zinkovsky master * r6545a6d / src/pipe_wrap.cc : make updates to work with latest libuv api changes - http://git.io/ow_iDw
01:05:31  <CIA-95>node: Igor Zinkovsky master * r1a9286c / src/fs_event_wrap.cc : update fs_event_wrap.cc to work with new uv_fs_event_init api - http://git.io/yGHOkw
01:06:22  * dapquit (Quit: Leaving.)
01:06:39  <CIA-95>node: Igor Zinkovsky master * r7335a42 / test/simple/test-module-loading.js : fix test-module-loading on windows - http://git.io/hqAXGA
01:13:03  <igorzi>bnoordhuis: are you done with the cluster?
01:13:38  <bnoordhuis>igorzi: almost, i'm waiting for the i/o benchmark to finish
01:14:42  <igorzi>bnoordhuis: cool, no rush.. just checking
01:15:30  <isaacs>sweet. i can pipe one directory into another. tar packing/extracting should be done this weekend.
01:15:59  * isaacsquit (Quit: isaacs)
01:16:50  <igorzi>isaacs: very cool
01:22:43  * AvianFlu_joined
01:23:29  * AvianFluquit (Disconnected by services)
01:25:23  <bnoordhuis>i/o write regression in 0.6 on linux, 17.4 vs 21.6 mb/s
01:25:42  <bnoordhuis>almost 20% slower...
01:26:44  <bnoordhuis>i/o read performance is up 35% though, 26.6 vs 19.7 mb/s
01:29:09  <bnoordhuis>igorzi: the cluster is yours again
01:30:03  <igorzi>bnoordhuis: thx.. how about startup benchmark?
01:32:10  <bnoordhuis>igorzi: we're almost on par with 0.2.6 again
01:32:19  <bnoordhuis>49 ms vs 45 ms
01:32:26  <bnoordhuis>0.4 started up in ~75 ms
01:32:37  <bnoordhuis>so we're doing pretty good there
01:32:56  <bnoordhuis>startup memory footprint is down with ~2.5 MB too, compared to 0.4
01:33:35  <igorzi>bnoordhuis: nice.. i should measure the memory footprint between cygwin and native as well
01:35:22  <igorzi>bnoordhuis: what's up with that 23 r/s (for bytes/102400)?
01:35:22  * brsonquit (Quit: leaving)
01:35:56  <piscisaureus>hmm
01:36:04  <bnoordhuis>igorzi: some serious regression
01:36:23  <bnoordhuis>i had to actually patch node to make the benchmark pass at all
01:36:34  <bnoordhuis>it would fail with an assertion in uv_err_name()
01:36:36  <piscisaureus>it is very difficult difficult to make stat() polling and ReadDirectoryChangesW act the same
01:37:12  <igorzi>piscisaureus: even with the new flags?
01:37:24  <piscisaureus>the problem is that ReadDirectoryChangesW is handle-based
01:37:50  <piscisaureus>if a directory up towards the root is renamed then ReadDirectoryChangesW will not notice
01:37:57  <piscisaureus>but the stat poller will
01:38:31  <piscisaureus>maybe we should just say that behaviour is undefined
01:41:55  <piscisaureus>ah
01:42:08  <piscisaureus>it locks the directory
01:42:16  <piscisaureus>so it can't be renamed
01:53:03  <piscisaureus>that's actually not nice
01:53:29  <piscisaureus>if the user decides to watch an entire tree by calling fs.watch many times, then the tree shape is locked
01:53:57  <bnoordhuis>https://gist.github.com/1340957 <- benchmark stats
01:56:34  <bnoordhuis>../src/unix/linux.c: In function ‘uv_fs_event_init’:
01:56:35  <bnoordhuis>../src/unix/linux.c:161: error: ‘flags’ redeclared as different kind of symbol
01:56:35  <bnoordhuis>../src/unix/linux.c:160: note: previous definition of ‘flags’ was here
01:56:37  <bnoordhuis>piscisaureus: ^
01:57:04  <bnoordhuis>hmm, i can fix that
01:57:11  <piscisaureus>call it flags2 :-)
01:57:13  <piscisaureus>sorry btw
01:57:18  <piscisaureus>I didn't test on all platforms
01:58:04  <bnoordhuis>../test/test-fs.c:1438: error: ‘_O_RDWR’ undeclared (first use in this function) <- ffs
01:59:18  <bnoordhuis>piscisaureus: ^ how do i solve that?
01:59:27  <bnoordhuis>does windows have O_RDWR?
02:03:19  <igorzi>bnoordhuis: yes, sorry - that should be O_RDWR
02:03:32  <bnoordhuis>okay, i'll fix it
02:03:33  <piscisaureus>hmm
02:03:49  <piscisaureus>even more complicated
02:04:14  <piscisaureus>if I fs.watch "c:\a\b\c" then I can safely delete and rename c and everything works fine
02:04:20  <piscisaureus>however c:\a and c:\a\b are locked
02:04:21  <piscisaureus>:-/
02:04:35  <igorzi>piscisaureus: hmm
02:05:02  <piscisaureus>igorzi: you do however specifiy full sharing when you open the directory handle
02:05:07  <piscisaureus>that's pretty funky
02:09:24  <piscisaureus>I also get an error when I delete the watched directory
02:09:33  <piscisaureus>Error: watch Unknown system errno 5
02:09:33  <piscisaureus> at errnoException (fs.js:604:11)
02:09:33  <piscisaureus> at FSEvent.onchange (fs.js:618:26)
02:09:37  <CIA-95>libuv: Ben Noordhuis master * rcee56c9 / src/unix/linux.c : unix: unbreak linux build, broken in 1997e10 - http://git.io/5AJvmg
02:09:37  <CIA-95>libuv: Ben Noordhuis master * r9dc67f5 / test/test-fs.c : test: don't use _O_RDWR, windows-ism - http://git.io/uykrow
02:09:37  <CIA-95>libuv: Ben Noordhuis master * rc468e2a / test/test-fs.c : test: fix memory buffer comparison - http://git.io/5eMjiw
02:09:54  <piscisaureus>with `rd /r/s` that is
02:10:07  <piscisaureus>probably related to comparing long/short names
02:10:07  <bnoordhuis>piscisaureus, take note of that last one
02:10:55  <piscisaureus>bnoordhuis: what about?
02:11:14  <bnoordhuis>piscisaureus: sizeof(buf) == 32 but the string to compare against was 26 bytes long
02:11:16  * piscisaureusquit (Read error: Connection reset by peer)
02:11:17  <igorzi>bnoordhuis: that's my bad
02:11:29  <bnoordhuis>oh, okay
02:11:37  <bnoordhuis>sorry, piscisaureus_
02:11:53  * piscisaureusjoined
02:15:35  <CIA-95>node: Ben Noordhuis master * r10edbbb / (deps/uv/src/unix/linux.c deps/uv/test/test-fs.c): uv: upgrade to c468e2a - http://git.io/4vVr3A
02:16:17  <piscisaureus>pretty funny ... explorer.exe exhibits the same behaviour
02:16:26  <piscisaureus>if I open c:\a\b\c in explorer
02:16:37  <piscisaureus>and then try to rename c:\a\b\c from cmd, that works fine
02:17:03  <piscisaureus>however if I try to rename c:\a, it fails w/ access denied
02:32:36  * piscisaureusquit (Quit: ~ Trillian Astra - www.trillian.im ~)
03:13:31  * AvianFlu_changed nick to AvianFlu
03:22:27  * koichikjoined
03:23:36  * AvianFluquit (Quit: Leaving)
03:36:30  <CIA-95>node: koichik master * r96fe504 / doc/api/child_processes.markdown : docs: fix typo - http://git.io/fPlsSw
04:14:36  * jesusabdullahpart
04:32:54  * bnoordhuisquit (Read error: Operation timed out)
04:41:54  * AvianFlujoined
06:23:08  * bnoordhuisjoined
06:23:22  <bnoordhuis>ryah: i'll be here in 10
06:40:14  <ryah>yo
06:43:57  <bnoordhuis>ryah: k, atk - keep those rc's coming
06:50:57  <ryah>yep - one sec
06:53:10  * mikealjoined
06:58:50  <ryah>http://nodejs.org/dist/v0.6.0/node-v0.6.0rc2.tar.gz
06:59:20  <indutny>ryah: evening
06:59:29  <indutny>where are we now with 0.6.0 ?
06:59:36  <indutny>can I help you?
07:00:11  <bnoordhuis>indutny: sure, by testing the rc tarball
07:00:30  <bnoordhuis>download, ./configure --debug && make, make test-all
07:04:43  * raggiquit (Read error: Connection reset by peer)
07:04:49  * raggijoined
07:05:27  <indutny>ok
07:09:52  <ryah>its looking good
07:21:36  <indutny>tests are sooo slow in debug mode
07:21:57  <indutny>test-dgram-ping-pong runs for about 1 minute
07:22:06  <indutny>is it ok?
07:22:12  <indutny>ah, well - not
07:22:16  <indutny>it's timeouted
07:25:24  * mikealquit (Quit: Leaving.)
07:25:48  <ryah>Command: out/Release/node /home/ryan/node-v0.6.0/test/pummel/test-regress-GH-892.js
07:25:51  <ryah>[13:01|% 96|+ 601|- 9]: release test-regress-GH-814_2
07:25:54  <ryah>Traceback (most recent call last):
07:25:57  <ryah> File "tools/test.py", line 1440, in <module>
07:25:59  <ryah> sys.exit(Main())
07:26:01  <ryah>er
07:26:03  <ryah>[13:01|% 96|+ 601|- 9]: release test-regress-GH-814_2
07:26:03  <ryah>Traceback (most recent call last):
07:26:05  <ryah> File "tool
07:26:08  <ryah> File "tools/test.py", line 1440, in <module>
07:26:11  <ryah> sys.exit(Main())
07:26:13  <ryah> File "tools/test.py", line 1414, in Main
07:26:16  <ryah> if RunTestCases(cases_to_run, options.progress, options.j):
07:26:18  <ryah> File "tools/test.py", line 696, in RunTestCases
07:26:20  <ryah> return progress.Run(tasks)
07:26:23  <ryah> File "tools/test.py", line 93, in Run
07:26:26  <ryah> self.RunSingle()
07:26:28  <ryah> File "tools/test.py", line 119, in RunSingle
07:26:30  <ryah> output = case.Run()
07:26:33  <ryah> File "/home/ryan/node-v0.6.0/tools/test.py", line 380, in Run
07:26:35  <ryah> self.AfterRun(result)
07:26:38  <ryah> File "/home/ryan/node-v0.6.0/test/pummel/testcfg.py", line 58, in AfterRun
07:26:40  <ryah> mkdir(self.tmpdir)
07:26:43  <ryah>OSError: [Errno 17] File exists: '/home/ryan/node-v0.6.0/test/tmp'
07:26:45  <ryah>gmake: *** [test-all] Error 1
07:26:48  <ryah>^-- sunos
07:27:15  <ryah>sunos:
07:27:18  <ryah>% make install
07:27:18  <ryah>Waf: Entering directory `/home/ryan/node-v0.6.0/out'
07:27:18  <ryah>DEST_OS: sunos
07:27:18  <ryah>DEST_CPU: ia32
07:27:20  <ryah>Parallel Jobs: 2
07:27:23  <ryah>Product type: program
07:27:25  <ryah>* installing deps/uv/include/ares.h as /home/ryan/local/node/include/node/ares.h
07:27:28  <ryah>Waf: Leaving directory `/home/ryan/node-v0.6.0/out'
07:27:30  <ryah>Could not install the file '/home/ryan/local/node/include/node/ares.h'
07:27:33  <ryah>gmake: *** [install] Error 1
07:27:44  * mikealjoined
07:29:52  <indutny>test-net-server-max-connections timeout candidate (running about 1minute)
07:30:07  <indutny>yep
07:30:08  <indutny>error 199: Error: connect EMFILE
07:30:08  <indutny>closed 199
07:30:56  <bnoordhuis>indutny: what's your `ulimit -n` set to?
07:31:18  <indutny>256
07:31:24  <indutny>ok, I'll try again
07:31:42  <indutny>1024 should be enough, right?
07:31:56  <bnoordhuis>indutny: yes
07:32:24  <indutny>as I can see debugger-repl is not failining anymore
07:32:29  <indutny>right?
07:32:41  <bnoordhuis>yep, works now - good work
07:32:57  <bnoordhuis>[18:46|% 100|+ 626|- 6]: Done <- sunos, and test-regress-GH-814_2 passes
07:34:03  <bnoordhuis>[18:46|% 100|+ 626|- 6]: Done <- linux, mostly timing related but test-net-pingpong-delay.js actually crashed node...
07:35:26  <ryah>Command: out/Debug/node /home/ryan/node-v0.6.0/test/pummel/test-tls-throttle.js
07:35:26  <ryah>--- TIMEOUT ---
07:35:30  <ryah>:/
07:35:59  <bnoordhuis>same here
07:36:35  <bnoordhuis>that pummel/test-net-pingpong-delay crash is that weird phantom error from last night
07:36:41  <ryah>windows is looking good:
07:36:43  <ryah>[02:20|% 100|+ 280|- 9]: Done
07:36:48  <bnoordhuis>good
07:36:51  <ryah>that's just simple/message
07:36:52  <indutny>https://gist.github.com/c564eeb352dcf6a7d09f
07:37:12  <bnoordhuis>indutny: what os?
07:37:17  <indutny>osx
07:37:24  <bnoordhuis>weird
07:37:30  <indutny>https://gist.github.com/2094f6e6c5d9cd517f04
07:37:47  <bnoordhuis>yeah, that one is known broken
07:38:07  <ryah>cant repeat the test-readfloat.js problem
07:38:21  <ryah>nevermind
07:38:25  <ryah>% ./node_g test/simple/test-readfloat.js
07:38:25  <ryah>node.js:201
07:38:25  <ryah> throw e; // process.nextTick error, or 'error' event on first tick
07:38:25  <ryah> ^
07:38:25  <ryah>AssertionError: true == false
07:38:27  <ryah> at test (/Users/ryan/projects/node/test/simple/test-readfloat.js:51:10)
07:38:30  <ryah> at Object.<anonymous> (/Users/ryan/projects/node/test/simple/test-readfloat.js:69:1)
07:38:33  <ryah> at Module._compile (module.js:432:26)
07:38:35  <ryah> at Object..js (module.js:450:10)
07:38:37  <ryah> at Module.load (module.js:351:31)
07:38:40  <ryah> at Function._load (module.js:310:12)
07:38:43  <ryah> at Array.0 (module.js:470:10)
07:38:45  <ryah> at EventEmitter._tickCallback (node.js:192:40)
07:38:48  <ryah>wtf
07:39:21  <ryah>i dont see how that one can sometimes fail...
07:39:41  <indutny>https://gist.github.com/f68368316413a923af05
07:39:50  <indutny>hehe
07:39:55  <indutny>debugger-repl fails sometimes
07:40:11  <ryah>man
07:40:17  <ryah>failing all over the place
07:40:21  <ryah>we need to hammer this shit down
07:40:34  <indutny>ok, I'll try to figure it out
07:40:35  <indutny>https://gist.github.com/42da79835234c46179ba
07:40:50  <indutny>it's just a stupid writing to child's stdin
07:41:07  <indutny>https://gist.github.com/aaf811b047db9ee67398
07:41:59  <bnoordhuis>https://gist.github.com/515c42e2dc9b19b5fec2 <- sunos and linux failures
07:42:28  <bnoordhuis>ryah: i think we're still running into v8 bugs
07:42:59  <bnoordhuis>https://gist.github.com/1341235 <- that one's strange too
07:43:13  <ryah>valgrind through test-readfloat is clean
07:44:28  <indutny>https://gist.github.com/413448dc9180961a8606
07:44:54  <bnoordhuis>https://gist.github.com/1341249 <- wtf? probably a build environment issue
07:45:28  <indutny>ryah: is 'drain' always emitting on file?
07:45:47  <indutny>bnoordhuis: definitely
07:46:17  <indutny>bnoordhuis: I'm sitting on 10.6.8 too
07:46:59  <indutny>ryah: I think I fixed it, pushing update
07:47:09  <bnoordhuis>indutny: he just added a gdb backtrace in that gist, does that look sane to you?
07:47:19  <bnoordhuis>triggers an assert in v8 for some reason
07:47:56  <indutny>one sec
07:48:28  <indutny>looking
07:48:57  <indutny>osx: [13:41|% 100|+ 622|- 10]: Done
07:49:13  <bnoordhuis>i should say that the assert triggers a NULL pointer dereference, not that the assert itself triggers
07:49:31  <indutny>great
07:49:32  <indutny>:D
07:50:24  <indutny>strange
07:50:40  * ryahlooks for mraleph
07:50:57  <indutny>I'll ping him
07:50:58  <indutny>one sec
07:51:19  <indutny>send him a message
07:51:20  <bnoordhuis>you russians all know each other?
07:51:23  <indutny>emmm
07:51:24  <indutny>sent
07:51:25  <indutny>hehe
07:52:26  <ryah>did he do a "distclean" ?
07:53:07  <indutny>bnoordhuis: looks like Isolate::Current() returns undefined value
07:53:17  <bnoordhuis>clean build from the tarball
07:53:17  <indutny>when we're creating HandleScope
07:53:33  <indutny>ryah: bnoordhuis: https://github.com/joyent/node/pull/2018
07:53:38  <indutny>wfm ^
07:53:55  <bnoordhuis>wow, we're up to #2018 already? things move so fast
07:54:16  <bnoordhuis>indutny: that patch already got merged
07:54:25  <indutny>hehe
07:54:31  <indutny>really?
07:54:41  <bnoordhuis>oh wait, no - the inverse of that patch got merged
07:54:42  <ryah>solaris:
07:54:43  <ryah>=== release test-fs-watch ===
07:54:43  <ryah>Path: simple/test-fs-watch
07:54:43  <ryah>assert.js:104
07:54:43  <ryah> throw new assert.AssertionError({
07:54:45  <ryah> ^
07:54:48  <ryah>AssertionError: "rename" == "change"
07:54:50  <ryah> at FSWatcher.<anonymous> (/home/ryan/node-v0.6.0/test/simple/test-fs-watch.js:128:16)
07:54:54  <ryah> at FSWatcher.emit (events.js:70:17)
07:54:56  <ryah> at FSEvent.onchange (fs.js:620:12)
07:54:59  <ryah>Command: out/Release/node /home/ryan/node-v0.6.0/test/simple/test-fs-watch.js
07:55:16  <ryah>i dont want to hold the release on this test fix
07:55:39  <bnoordhuis>^ known bug, solaris reports it in such a way that you can't detect it as a rename
07:55:40  <ryah>er - i dont want to do another RC i should say
07:55:46  <ryah>bnoordhuis: ok
07:55:50  <bnoordhuis>there's a test in libuv that demonstrates the same behaviour
07:57:09  <bnoordhuis>ryah: btw, did simple/test-http-dns-error fail for you on sunos?
07:57:22  <indutny>bnoordhuis: most interesting is that isolate_ is a pointer (Isolate*)
07:57:26  <ryah>bnoordhuis: yes
07:57:26  <ryah>AssertionError: "EADDRINFO" == "ENOTFOUND"
07:57:31  <indutny>I don't understand how can it crash
07:57:38  <indutny>on ASSERT(pointer != NULL)
07:57:42  <ryah>let's wait for him to make distclean
07:57:48  <bnoordhuis>right, so it's not an issue with the version of sunos i'm testing it on
07:57:48  <ryah>maybe it's just some strange linking problem
07:57:58  <indutny>mralpeh is not responding
07:58:03  <indutny>mraleph*
07:58:07  <indutny>ryah: looks like so
07:58:25  * piscisaureus_quit (Ping timeout: 252 seconds)
07:58:55  <AvianFlu>9 failed on debian 6.02 with rc2 https://gist.github.com/1341254
07:59:26  <ryah>man.. what's with this test-readfloat
08:00:06  <ryah>bnoordhuis: somehow we were down to 2 failures a few days ago
08:00:10  <ryah>bnoordhuis: what happened?
08:00:28  <indutny>when have we changed v8 version?
08:00:30  <bnoordhuis>ryah: on linux you mean?
08:00:33  <ryah>yeah
08:00:44  <ryah>indutny: yesterday
08:00:46  <indutny>what if we try that test on latest
08:01:17  <ryah>nope
08:01:24  <bnoordhuis>ryah: most of the failures are timing related, i.e. they don't fail if the load isn't so high
08:01:27  <ryah>latests is also messed up
08:01:48  <indutny>ryah: I mean just this test
08:02:09  <indutny>probably we can pull some fixes from bleeding_edge if mraleph appear online
08:02:16  <bnoordhuis>i.e. pummel/test-timers <- bad test, expects to complete in 200 ms or so
08:02:41  <bnoordhuis>simple/test-net-server-max-connections <- another bad test, makes assumptions about close order
08:04:29  <bnoordhuis>i think we're mostly good on linux, spurious crashes aside...
08:05:22  <indutny>ryah: can I ask you to email me before posting about release?
08:05:41  <indutny>I'm going to translate and publish it on http://habrahabr.ru/
08:06:19  <ryah>indutny: yes
08:06:58  <indutny>ok, readfloat fails on latest v8
08:07:08  <indutny>same as on current version
08:11:05  <indutny>bnoordhuis: can you please pull my patch?
08:11:12  <indutny>at least we fix one failing test :D
08:12:30  <bnoordhuis>indutny: Error: Timeout. Expected: /connecting... ok/
08:12:52  <indutny>errm
08:12:55  <indutny>fck )
08:15:42  <indutny>em... that's not a test problem
08:16:02  <indutny>debugger is not connecting
08:16:11  <bnoordhuis>indutny: i applied your test, then ran `python tools/test.py --mode=debug,release simple/test-debugger-repl`
08:16:44  <bnoordhuis>debug passes, release times out
08:17:07  <indutny>yep, I understand
08:17:10  <indutny>but ./node debug lib/fs.sj
08:17:13  <indutny>is not working
08:17:19  <indutny>f*ck
08:17:28  <bnoordhuis>not working how?
08:17:42  * piscisaureusjoined
08:18:33  <indutny>testing...
08:18:51  <indutny>Remote debugging session already active
08:18:58  <indutny>that's what v8 is saying
08:19:13  <indutny>wtf
08:19:17  * piscisaureus_joined
08:19:19  <bnoordhuis>oh hah, there's probably stray processes sitting on my machine
08:19:22  <bnoordhuis>`pkill node`
08:19:36  <indutny>aaaah
08:19:38  <indutny>yeah
08:20:01  * piscisaureus_quit (Read error: Connection reset by peer)
08:20:22  * piscisaureus_joined
08:20:29  <bnoordhuis>the debug test leaves a process sitting there, so the release test times out
08:20:45  <indutny>ohhhh
08:21:18  <indutny>i'll fix that
08:22:14  * piscisaureusquit (Ping timeout: 252 seconds)
08:29:03  <indutny>bnoordhuis: https://github.com/joyent/node/pull/2018
08:29:21  <indutny>this one should be better
08:33:00  <indutny>bnoordhuis: yt?
08:33:08  <bnoordhuis>indutny: yes, better
08:33:19  <indutny>commands w/o output are evil
08:33:37  <indutny>I think sometimes multiple commands were merged
08:33:48  <CIA-95>node: Fedor Indutny master * r18267d0 / test/simple/test-debugger-repl.js : test: debugger-repl should wait for 'drain' event - http://git.io/WC3GFw
08:33:54  <indutny>great
08:34:33  <indutny>-1
08:35:11  <ryah>hm
08:36:16  <bnoordhuis>ryah: what's the plan? release or not?
08:36:23  <bnoordhuis>i ask because i want to get croissants :)
08:36:46  <ryah>is it possible that DTrejo is hitting something without handlescope?
08:36:52  <indutny>ryah: nope
08:36:58  <indutny>it's created in Stat
08:37:16  <indutny>is still failing for him after distclean?
08:37:20  <ryah>yes
08:37:39  <indutny>what version of XCode does he have?
08:39:52  <ryah>bnoordhuis: http://blog.nodejs.org/?p=340&preview=true
08:42:19  <ryah>yeah.
08:42:20  <ryah>so.
08:42:26  <ryah>do we release or not?
08:42:30  <indutny>+1
08:42:32  <indutny>ryah: cc me
08:42:36  <indutny>please
08:42:38  <indutny>;)
08:42:52  <ryah>i think we release
08:42:55  <ryah>because, fuck it
08:42:59  <indutny>hahaha
08:43:04  <ryah>there's always v0.6.1
08:43:06  <indutny>if you waited for release for too long
08:43:12  <indutny>:D
08:43:13  <bnoordhuis>nicely downplayed the /bytes/102400 benchmark :)
08:43:22  <bnoordhuis>yeah, let's go for it
08:43:26  <ryah>bnoordhuis: selective benchmarking
08:43:34  <bnoordhuis>we'll fix it in 0.6.1
08:44:02  <indutny>yep, that's what 0.6.1 is for
08:44:08  <ryah>indutny: im going to push over your commit
08:44:12  <ryah>i dont want to build a new rc
08:44:38  <indutny>ryah: ok, it's harmless
08:45:00  <indutny>oh, do you mean not pushing it into 0.6.x?
08:45:12  <indutny>np, anyway
08:45:46  <indutny>if only I can see that blog post... ;)
08:45:49  <indutny>hehe
08:45:57  <indutny>I need some time to translate it
08:53:02  <ryah>indutny: still working on it
08:53:07  <indutny>k
08:53:15  <indutny>writing some common words now
08:54:35  <CIA-95>node: Ryan Dahl master * r865b077 / (5 files in 3 dirs): Bump version to v0.6.0 - http://git.io/gFF1rA
08:55:00  <ryah>indutny: can you see this: http://blog.nodejs.org/?p=340&preview=true
08:55:07  <indutny>nope
08:56:18  <CIA-95>node: Ryan Dahl master * r9e00b7d / src/node_version.h : Now working on v0.6.1 - http://git.io/nupoLw
08:57:22  <ryah>i just want to make sure i can run this binary in win 2k3
08:57:22  <indutny>:)
08:57:27  <indutny>ok, np
08:57:28  <ryah>before i make the post
08:58:16  <ryah>indutny: https://gist.github.com/4080a3ab4144895b43cb
08:58:23  <indutny>thanks
08:59:07  <indutny>I think better post link for 0.4.x - 0.6.0 migration
08:59:20  <ryah>indutny: oh good idea
09:06:56  <indutny>50% of translation is done
09:19:41  <indutny>ryah: http://habrahabr.ru/blogs/nodejs/131944/
09:24:16  <indutny>ryah: I think v8 upgrade should be noted too: upgrade v8 from 3.1.8.25 to 3.6.6.6
09:24:25  <indutny>ah
09:24:32  <indutny>we have downgrade to 3.6.6.6 line
09:24:50  <ryah>i'll note that in the main features
09:37:12  <koichik>congrats!
09:38:09  <bnoordhuis>hey koichik
09:39:25  <koichik>bnoordhuis: hey!
09:39:34  <indutny>congrats!
09:39:41  <indutny>I owe you a beer guys
09:39:45  <indutny>come to Omsk
09:39:46  <indutny>:D
09:40:17  <indutny>ryah++ bnoordhuis++ piscisaureus++ igorzi++ koichik++
09:40:31  <bnoordhuis>heh, where is that beer bot when you need him?
09:41:45  <indutny>:)
09:42:12  <CIA-95>node: Eric Lovett master * r8f2b032 / doc/api/child_processes.markdown : docs: minor typo fix in child process docs - http://git.io/yg0MEg
09:44:57  <CIA-95>node: Ben Noordhuis master * r099c717 / doc/index.html : docs: fix copy/paste error, 0.6.0 is a stable release - http://git.io/BcWCSA
09:51:49  <koichik>ryah: can I translate the blog into Japanese?
09:52:28  <koichik>indtny: you already finished, too fast!
09:53:05  <koichik>indutny: oops, not indtny
09:54:59  * bnoordhuisis afk for a bit
09:57:43  <indutny>:)
09:58:10  <indutny>ryah: http://habrahabr.ru/ <- on main page
09:58:20  <indutny>;)
09:59:28  <indutny>ooops
09:59:35  <indutny>forgot to insert links to downloads
10:02:15  <indutny>whoa
10:02:17  <indutny>added
10:06:06  <bnoordhuis>is http://habrahabr.ru/ like the russian hacker news?
10:08:25  <indutny>yep
10:08:29  <indutny>but more hard-weight
10:08:32  <indutny>:D
10:08:38  <indutny>a lot of banners, images and etc
10:08:52  <indutny>but yep, that's most popular hacker site in russia
10:21:43  <indutny>aah
10:21:51  <indutny>it's visible only for registered users
10:21:52  <indutny>right now
11:54:16  * Marakquit (Remote host closed the connection)
11:54:17  * indutnyquit (Read error: Connection reset by peer)
12:01:04  <CIA-95>node: Eric Lovett master * rfebe5c4 / doc/api/zlib.markdown : docs: use markdown for link, not html - http://git.io/t51CYw
12:14:48  * indutnyjoined
12:49:39  * kuebk^joined
13:37:34  * kuebk^quit
14:26:02  <CIA-95>node: Fedor Indutny master * rda82daf / test/simple/test-debugger-repl.js : test: debugger-repl should wait for 'drain' event - http://git.io/o23y7w
14:28:35  <indutny>em...
14:29:03  <indutny>ah
14:29:04  <indutny>ok
14:39:58  * bnoordhuisquit (Ping timeout: 245 seconds)
15:01:54  * AvianFluquit (Quit: Leaving)
15:24:35  * mikealquit (Quit: Leaving.)
15:25:58  * mikealjoined
15:30:35  * mikealquit (Ping timeout: 258 seconds)
15:32:50  * mikealjoined
15:37:07  * mikealquit (Ping timeout: 252 seconds)
15:40:00  * mikealjoined
15:44:27  * mikealquit (Ping timeout: 252 seconds)
15:47:08  * mikealjoined
15:50:47  * mikealquit (Client Quit)
16:07:38  * kuebk^joined
16:27:38  <CIA-95>node: koichik master * r1001cf4 / benchmark/static_http_server.js :
16:27:38  <CIA-95>node: bench: update static_http_server benchmark to new API
16:27:38  <CIA-95>node: Fixes #2016. - http://git.io/Bdpe2Q
16:43:28  * mikealjoined
16:46:45  <mikeal>umn….
16:46:49  <mikeal>you removed the resume event
16:46:58  <mikeal>how does resume propogate?
16:47:13  <indutny>mikeal: we haven't removed it
16:47:14  <indutny>afaik
16:47:15  <mikeal>cause you didn't replace it with drain event propogation
16:47:19  <mikeal>it's in the release notes
16:47:24  <indutny>really ? :D
16:47:25  <indutny>hehe
16:47:44  <indutny>ah, you're talking about stream.pipe
16:47:52  <mikeal>yeah
16:52:20  <mikeal>god dammit
16:52:35  <mikeal>this totally broke resume in pipe chains between non-core objects
16:53:08  <mikeal>even better, it throws!
16:53:43  <mikeal>no, nevermind, it doesn't throw, it just silently never resues
16:53:45  <mikeal>er resumes
16:53:48  <indutny>:)
16:54:33  <indutny>hmm
16:54:39  <indutny>correct me if I wrong
16:54:50  <indutny>but it was emitting 'resume' only if stream doesn't have a .resume method
16:54:51  <indutny>right?
16:56:06  <mikeal>it added it if it didnt' exist
16:56:16  <mikeal>it doesn't need to emit resume, ryah is right about that, it can just emit drain
16:56:49  <mikeal>but it needs to emit drain if it doesn't have a resume method or else it never makes it back to the file handler
16:57:55  <indutny>drain on source?
16:58:02  <indutny>I think that is inconsistent
17:00:50  <mikeal>why?
17:00:58  <mikeal>source is readable/writeable
17:01:01  <indutny>yep
17:01:11  <indutny>but drain should be emitted only after .write() will return false
17:01:15  <mikeal>so emitting "drain" is expected
17:01:25  <mikeal>right
17:01:30  <mikeal>write() returns false
17:01:34  <indutny>btw, why source should be writable?
17:01:42  <mikeal>think about this
17:01:46  <indutny>it definitely shouldn't be
17:01:58  <mikeal>streamA <-> streamB <-> streamC
17:02:09  <indutny>fs.createReadStream
17:02:14  <indutny>fs.createReadStream -> streamB
17:02:16  <mikeal>streamC returns false, that returns all the way to the source and pauses
17:02:24  <mikeal>so it's paused
17:02:30  <mikeal>paused emits "drain"
17:02:37  <mikeal>how does streamA get that?
17:02:37  <indutny>aah
17:02:42  <mikeal>write() will never be called again
17:02:47  <mikeal>the pipe chain is paused
17:03:06  <indutny>hm....
17:03:32  <indutny>yep, agree with you
17:03:33  <mikeal>this is why me and isaacs said it was a bad idea to merge this in at the last minute
17:10:24  <mikeal>pull request sent
17:10:51  <mikeal>and an email was sent to the list
17:12:37  * mikealquit (Quit: Leaving.)
18:10:58  * piscisaureus__joined
18:11:15  * piscisaureus__changed nick to piscisaureus
18:14:59  * ericktjoined
18:27:13  <indutny>https://lh4.googleusercontent.com/-OWVxR1wEvLw/TrVrj_xHc5I/AAAAAAAABF0/afSafHY7Wcw/s619/header.png
18:27:14  <indutny>lol
18:31:44  * mikealjoined
18:52:05  * mikealquit (Quit: Leaving.)
19:12:32  * piscisaureusquit (Quit: ~ Trillian Astra - www.trillian.im ~)
19:17:09  * mikealjoined
19:23:05  * piscisaureusjoined
19:37:51  * ericktquit (Quit: erickt)
19:44:40  * brsonjoined
19:49:45  * igorzi_joined
19:51:03  * igorzi_quit (Client Quit)
19:51:59  * AvianFlujoined
19:53:49  <pquerna>https://github.com/racker/virgo/commit/4153f58c0f2d53c371fe485370bd258a61459a99
19:53:53  <pquerna>gyp for openssl 1.0.0e
19:54:01  <pquerna>dunno what the intention is for the bundled openssl
19:56:16  * mikealquit (Quit: Leaving.)
21:16:55  <pquerna>where is the best place to ask about gyp things on irc? trying use make_global_settings :-/
21:38:14  * igorziquit (Ping timeout: 265 seconds)
21:49:08  * isaacsjoined
22:22:07  * mafintoshjoined
22:47:02  * mafintosjoined
22:47:02  * mafintoshquit (Read error: Connection reset by peer)
23:09:04  * AvianFluquit (Ping timeout: 255 seconds)
23:21:57  * AvianFlujoined