00:10:38  * brsonquit (Ping timeout: 246 seconds)
00:21:51  * TooTallNatequit (Quit: Computer has gone to sleep.)
00:30:43  * bnoordhuisquit (Ping timeout: 260 seconds)
00:30:49  * loladiroquit (Quit: loladiro)
00:40:26  <piscisaureus_>ok
00:40:28  <piscisaureus_>time to sleep
00:41:01  <piscisaureus_>I see bnoordhuis already snuck out of here even.
00:41:26  <tjfontaine>sneaky bastard
00:42:18  <piscisaureus_>you bet, mister
00:54:38  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
01:16:15  * piscisaureus_joined
01:37:10  * abraxasjoined
01:49:49  * piscisaureus_quit (Ping timeout: 276 seconds)
02:41:57  * loladirojoined
02:57:38  * avalanche123quit (Quit: Computer has gone to sleep.)
03:18:23  * avalanche123joined
03:23:21  * TooTallNatejoined
03:24:44  * TooTallNatequit (Client Quit)
04:09:51  * ericktquit (Quit: erickt)
04:10:08  * joshthecoderjoined
04:17:59  * mmaleckijoined
04:26:03  * TheJHjoined
04:31:02  * mmaleckiquit (Ping timeout: 260 seconds)
04:36:39  * TheJHquit (Ping timeout: 268 seconds)
05:23:08  * loladiroquit (Quit: loladiro)
05:27:43  * joshthecoderquit (Quit: Linkinus - http://linkinus.com)
05:29:03  * loladirojoined
05:34:47  * loladiroquit (Quit: loladiro)
05:37:41  * mmaleckijoined
05:38:03  * paddybyersjoined
05:42:53  * mmaleckiquit (Ping timeout: 244 seconds)
05:44:38  * mmaleckijoined
05:45:54  * AvianFluquit (Quit: AvianFlu)
06:02:12  * avalanche123quit (Quit: Computer has gone to sleep.)
06:25:54  * ibobrikjoined
06:26:22  <ibobrik>hi there. can anyone explain this to me? https://gist.github.com/3617558
06:31:00  <indutny>ibobrik: spagetti code?
06:31:16  <ibobrik>this is just an example
06:31:23  <indutny>meh
06:31:39  <indutny>downloading
06:33:46  <indutny>ibobrik: do you see WTF?!
06:34:02  <ibobrik>yep
06:34:09  <ibobrik>from time to time
06:34:12  <indutny>ibobrik: can't reproduce it on osx
06:34:31  <indutny>ibobrik: what if you'll do fs.writeSync?
06:34:40  <mmalecki>8 spaces?
06:34:51  <ibobrik>stupid textmate :)
06:34:53  <mmalecki>actually, those are tabs
06:35:40  <ibobrik>i can't reproduce on osx too, but linux box shows wtfs
06:36:16  <ibobrik>indutny: do you have linux to check it?
06:36:22  <indutny>ibobrik: yeah, in VM
06:36:34  <indutny>one sec
06:37:18  <indutny>ibobrik: no wtfs for me
06:37:20  <indutny>ibobrik: on ubuntu
06:37:22  <indutny>ibobrik: in vbox
06:37:32  <indutny>ibobrik: are you on SSD drive?
06:37:40  <ibobrik>no, spinning disks
06:37:59  <ibobrik>i tried 2 gentoo servers and 1 debian - all affected
06:38:11  <ibobrik>at leas after 20 tries
06:38:12  <indutny>ibobrik: ok, so one thing that we can check
06:38:20  <indutny>ibobrik: can you .fill('\0') your buffers
06:38:31  <indutny>ibobrik: and paste what WTF will print
06:38:58  <indutny>and use bigger slice
06:39:02  <indutny>like (0, 40)
06:40:12  <ibobrik>this will not work. how can i compare buffers then?\
06:40:32  <indutny>ibobrik: well, just use slices when logging
06:40:39  <indutny>ibobrik: I want to see what happens
06:40:40  <ibobrik>1kb of \0 is equal to another 1kb of \0
06:40:45  <ibobrik>always
06:40:47  <ibobrik>i suppose
06:40:50  <indutny>ibobrik: well it should not be
06:40:55  <indutny>according to your example
06:41:01  <ibobrik>test.toString("base64") != buf(size).toString("base64"))
06:41:17  <indutny>and?
06:41:21  <indutny>that's what I told
06:41:28  <indutny>just fill your buffers before read and write
06:41:31  <ibobrik>no wtfs so far
06:41:34  <indutny>ah
06:41:54  <indutny>oh, I see now
06:41:54  <indutny>ok
06:44:53  <indutny>ibobrik: but only on ubuntu
06:45:27  <ibobrik>i have gentoo and debian, same results
06:46:18  <indutny>i.e. linuxes
06:48:33  <ibobrik>yep. is this kind of bug?
06:49:22  <indutny>it's hard to tell
06:49:28  <indutny>probably
06:49:53  <indutny>well
06:50:08  <indutny>actually, it it's not a bug when read is called w/o setTimeout
06:50:39  <indutny>and setTimeout doesn't guarantee that all executed writes was finished
06:51:02  <ibobrik>strafe output says that all pwrites finished before preads
06:51:05  <ibobrik>strace*
06:51:24  <indutny>yeah, I see it too
06:51:25  <indutny>hm...
07:08:09  <ibobrik>should i make an issue at github?
07:13:19  * safdsfasdfasdfasjoined
07:13:41  * safdsfasdfasdfaschanged nick to `3rdEden
07:13:57  <indutny>ibobrik: yeah
07:14:02  <indutny>ibobrik: cc bnoordhuis there
07:20:08  <ibobrik>should i make nodes or libuv issue?
07:20:12  <ibobrik>nodejs*
07:22:24  <ibobrik>https://github.com/joyent/libuv/issues/544
07:30:35  * rendarjoined
07:35:14  <indutny>ibobrik: thanks
07:35:34  <indutny>ibobrik: btw
07:37:23  <indutny>ibobrik: it seems to be happening only with uninitialized buffer
07:37:28  <indutny>ibobrik: I think there's something with node.js
07:37:41  <indutny>ibobrik: so probably it would be better to move issue to it
07:42:28  <indutny>oooh
07:42:43  <indutny>ibobrik: also node seems to be pwriting from 2 thread simultaneously
07:42:48  <indutny>ibobrik: this is definitely bad
07:44:29  <indutny>ircretary: tell bnoordhuis to ping me
07:44:29  <ircretary>indutny: I'll be sure to tell bnoordhuis
07:45:47  * ibobrikquit (Read error: Connection reset by peer)
07:46:06  * ibobrikjoined
07:51:32  <indutny>ibobrik: yt?
07:51:46  <indutny>ibobrik: what if you'll try to write 4096 bytes maximum?
08:03:47  <ibobrik>same results
08:11:24  <ibobrik>indutny: but buffer initialization helped
08:11:34  <ibobrik>indutny: as far as i can see. this is weird
08:15:50  <ibobrik>indutny: i have no idea how to "initialize" buffers that came from http request body btw
08:16:50  <indutny>ibobrik: they should be already initialized I guess
08:16:54  <indutny>but that's definitely a bug
08:17:00  <indutny>at least as far as I can see
08:18:58  <ibobrik>indutny: i don't understand why pwrite even bother about calculating offsets when i give offset explicitly
08:19:13  <indutny>ibobrik: that's not the case
08:19:22  <indutny>you're writing more than PIPE_BUF data
08:19:28  <indutny>and when doing so pwrite is not atomic
08:25:04  <indutny>so that seems to be a libuv bug
08:25:09  <indutny>even eio bug
08:26:11  <ibobrik>indutny: hm, this is buggy too: https://gist.github.com/3618478
08:26:29  <ibobrik>indutny: 100 writes < 4096 - same result
08:26:38  <indutny>ok
08:26:43  <indutny>something I'm missing there
08:26:45  <indutny>definitely
09:26:05  * piscisaureus_joined
09:56:14  * rendarquit
09:58:16  * rendarjoined
10:03:48  * bnoordhuisjoined
10:05:11  * stagasjoined
10:28:34  <bnoordhuis>indutny: what's up?
10:34:30  <indutny>bnoordhuis: hey man
10:34:36  <indutny>bnoordhuis: writes are not overlapping
10:34:42  <indutny>bnoordhuis: and more interestingly
10:34:49  <indutny>bnoordhuis: filling buffers with data helps
10:34:54  <indutny>bnoordhuis: even with a random data
10:35:46  <bnoordhuis>indutny: looking at the strace output, they seem to overlap
10:36:16  <indutny>bnoordhuis: they should not
10:36:26  <indutny>bnoordhuis: offset is increased by buffer length
10:39:16  <bnoordhuis>he's writing at the end of the file right?
10:39:50  <bnoordhuis>wait, i'll explain it in the issue
10:40:31  <indutny>ok
10:44:53  <bnoordhuis>indutny: https://github.com/joyent/libuv/issues/544#issuecomment-8258839
10:45:05  <bnoordhuis>i.e. it's not a bug
10:45:08  <bnoordhuis>or rather, not a bug in libuv
10:45:26  <indutny>bnoordhuis: oviously
10:45:30  <indutny>obviously
10:45:39  <indutny>the thing is that we're doing parallel pwrites
10:45:57  <indutny>while we surely know that pwrite won't work correctly when called from multiple threads
10:46:16  <bnoordhuis>oviously... copiously egg-like?
10:46:41  <bnoordhuis>at worst it's a documentation issue
10:46:50  <bnoordhuis>i think we document it for node, maybe not libuv
10:48:03  <indutny>ok
10:48:21  <indutny>it's just odd that it happens concurrently
10:48:27  <indutny>because it should not
10:48:49  <ibobrik>i see 2 solutions: 1. pre-allocating the whole big file before writing, 2. sticking fd to one io thread that will make linear pwrite calls one-after-another
10:52:14  <ibobrik>and 3. make write queue for every file in my own node.js code
10:54:56  * piscisaureus_quit (Ping timeout: 272 seconds)
11:10:49  <indutny>bnoordhuis: Assertion failed: (handle->flags & UV_CLOSING), function uv__finish_close, file ../deps/uv/src/unix/core.c, line 129.
11:10:55  <indutny>I like this! :)
11:11:37  * abraxasquit (Remote host closed the connection)
11:12:34  * abraxasjoined
11:13:27  * stagasquit (Quit: ChatZilla 0.9.88-rdmsoft [XULRunner 1.9.0.17/2009122204])
11:17:10  * abraxasquit (Ping timeout: 244 seconds)
11:26:12  <indutny>bnoordhuis: why is this happening?
11:34:18  * piscisaureus_joined
11:34:39  <piscisaureus_>bnoordhuis: pwrite from multiple threads *should* be safe... we're doing it in node too
11:35:19  <indutny>piscisaureus_: it isn't
11:35:21  <piscisaureus_>oh - we're not doing it in node
11:35:29  <piscisaureus_>indutny: so what's happening?
11:35:35  <piscisaureus_>indutny: data gets written at the wrong place?
11:35:38  <indutny>piscisaureus_: it's writing junk :)
11:35:43  <indutny>piscisaureus_: yeah, sort of
11:35:59  <piscisaureus_>indutny: so what it is - junk, or at the wrong place?
11:36:09  <indutny>idk
11:36:18  <indutny>but when you initalize buffers
11:36:21  <indutny>everything seems to be fine
11:36:28  <piscisaureus_>huh
11:36:35  <piscisaureus_>indutny: which buffers?
11:36:58  <piscisaureus_>indutny: so you're writing uninitialized memory and complaining that junk ends up in the file?
11:37:01  <indutny>https://gist.github.com/3617558
11:37:09  <indutny>piscisaureus_: well, not me
11:37:20  <indutny>but the thing is I comparing read data to what was written
11:37:29  <indutny>and I expect it to be equal
11:48:34  * CIA-130quit (Ping timeout: 265 seconds)
11:49:47  <bnoordhuis>CIA-130 doesn't even say bye? the nerve
11:54:18  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
11:59:32  <indutny>bnoordhuis: meh
11:59:35  <indutny>bunch of xml stuff
11:59:56  <bnoordhuis>indutny: xml? that's the new json, right?
12:00:17  <indutny>oh, do not remind me about it
12:00:30  <ibobrik>bnoordhuis, indutny: https://gist.github.com/3620592 sequential writes, corrupted file from time to time :(
12:01:04  <indutny>ha
12:01:06  <indutny>I knew it!
12:07:37  <ibobrik>i've updated libuv issue #544
12:21:52  * piscisaureus_joined
12:21:55  * piscisaureus_quit (Client Quit)
12:22:30  * `3rdEdenquit (Quit: Leaving...)
12:23:17  * piscisaureus_joined
12:28:10  * piscisaureusjoined
12:29:07  * CIA-129joined
12:30:08  * safdsfasdfasdfasjoined
12:31:01  * safdsfasdfasdfaschanged nick to `3rdEden
12:40:42  * loladirojoined
12:43:10  <CIA-129>node: Ben Noordhuis master * r83b1dda / (src/node.cc test/simple/test-cli-eval.js): cli: make argument to -p optional - http://git.io/_ff9Og
12:43:11  <CIA-129>node: Ben Noordhuis master * r19a4322 / test/simple/test-cli-eval.js : test: add extra checks in simple/test-cli-eval - http://git.io/r7sx8g
13:09:24  * ArmyOfBrucequit (Excess Flood)
13:09:55  * ArmyOfBrucejoined
13:13:00  * loladiroquit (Quit: loladiro)
13:13:06  <CIA-129>node: Ben Noordhuis master * r2efa3ae / tools/install.py : installer: reapply b21c8e0b, honor --without-npm (+17 more commits...) - http://git.io/xhZiiA
13:17:16  <CIA-129>node: Bert Belder issue3964 * r9236230 / (56 files in 5 dirs): doc: don't use ' - http://git.io/ORYVNg
13:18:46  <bnoordhuis>piscisaureus: is the company meeting this friday?
13:19:01  <piscisaureus_>bnoordhuis: yup
13:23:14  <CIA-129>node: Bert Belder issue3964 * r35d1da1 / (15 files in 2 dirs): doc: don't use ' - http://git.io/XWOdHA
13:25:42  * AvianFlujoined
13:26:40  <bnoordhuis>^ that guy
13:26:48  <bnoordhuis>he didn't say where exactly he ran into '
13:27:00  <bnoordhuis>i assume it's the blog but who knows
13:27:03  <piscisaureus_>yeah
13:27:07  <piscisaureus_>I don't know either
13:27:16  <bnoordhuis>also, IE
13:27:18  <piscisaureus_>It was a poor bug report
13:28:03  <piscisaureus_>bnoordhuis: BUT &#39 is smaller than &apos
13:28:21  <piscisaureus_>LESS IS MOAR
13:28:51  <piscisaureus_>CAPSLOCKBOT is really stoic today
13:29:05  <piscisaureus_>HELLO CAPSLOCKBOT HOW ARE WE DOING TODAY?
13:29:42  * piscisaureuschanged nick to NUMLOCKBOT
13:29:58  <NUMLOCKBOT>1 4M F1N3
13:44:06  * hzjoined
13:48:42  * loladirojoined
13:52:20  * loladiroquit (Client Quit)
13:53:03  * bentkusjoined
13:53:38  <piscisaureus_>bnoordhuis: how do you feel about that &apos patch btw? throw away or land?
13:57:47  <bentkus>Who wants to write an irc server in C? xD
13:59:52  <tjfontaine>bentkus: btdt
14:04:31  <bentkus>btdt?
14:04:52  <bentkus>with libuv?\
14:05:16  <CIA-129>node: Timothy J Fontaine master * rd3135e0 / (configure tools/gyp_node): build: add configure option to build with ninja - http://git.io/Ylh98g
14:05:16  <CIA-129>node: Ben Noordhuis master * r7b6d3ce / (Makefile configure): build: add ninja support to Makefile - http://git.io/afPQnA
14:06:27  <tjfontaine>bentkus: homegrown event loop, libevent, and we're currently doing on based on libuv
14:06:47  <bentkus>github link plz?
14:07:03  <tjfontaine>bentkus: still quite young http://github.com/oftc/oftc-ircd
14:08:02  <bentkus>is it a branch of the oftc server?
14:08:15  <bnoordhuis>piscisaureus_: land, doesn't hurt
14:08:25  <tjfontaine>bentkus: no oftc currently runs on oftc-hybrid
14:09:06  <bnoordhuis>ninja is nice
14:09:06  <bentkus>beafy server
14:09:22  <bnoordhuis>the build system, that is, not the killers for hire
14:09:40  <tjfontaine>killers are pretty awesome too, so long as they're not after you
14:10:07  <bnoordhuis>i don't know, i'd be worried about mixups
14:10:48  <bnoordhuis>i mean "oh sorry, wrong bloke - won't happen again" after the fact is little consolation
14:11:22  <tjfontaine>quite
14:11:54  <bnoordhuis>okay, time to take the wife out for a walk
14:14:47  * loladirojoined
14:19:35  * bentkuschanged nick to txdv2
14:25:40  <CIA-129>node: Bert Belder issue3964 * r12e327d / (18 files in 4 dirs): doc: don't use ' - http://git.io/EEDYtA
14:45:28  * hzquit (Ping timeout: 272 seconds)
14:47:04  <ibobrik>indutny: i finally found it. "a+" is evil
14:47:20  <indutny>oh
14:47:43  <piscisaureus_>still weird tho
14:47:47  <piscisaureus_>what flags does it translate to
14:47:57  <piscisaureus_>O_RDWR | O_APPEND ?
14:48:02  <indutny>I think so
14:48:36  <piscisaureus_>looks like a linux bug to me to be honest
14:48:44  <ibobrik>wait a minute
14:48:48  <ibobrik>linux for sure
14:49:11  * AndreasMadsenjoined
14:50:23  <indutny>piscisaureus_: sure, if they used kqueue this bug wouldn't happen!
14:50:31  <piscisaureus_>har har
14:50:43  <indutny>s/r//g
14:51:05  <ibobrik>https://gist.github.com/3621892
14:51:54  <ibobrik>with r+ everything is okay
14:54:21  * TheJHjoined
14:56:57  <ibobrik>indutny: this should not happen, should it? i mean "a+" behavior
15:09:20  * bnoordhuisquit (Ping timeout: 268 seconds)
15:12:43  * ericktjoined
15:16:37  * hzjoined
15:27:48  * loladiroquit (Quit: loladiro)
15:28:00  * `3rdEdenquit (Quit: Leaving...)
15:28:41  * tomshredsjoined
15:51:05  * AndreasMadsenquit (Remote host closed the connection)
16:07:18  * TheJHquit (Ping timeout: 260 seconds)
16:07:37  * brsonjoined
16:11:01  * DrPizzaquit (Quit: alice.)
16:11:24  * c4milojoined
16:13:42  <piscisaureus_>https://github.com/blog/1227-status-api <--
16:13:46  <piscisaureus_>wanted
16:14:01  <piscisaureus_>for both CLA and Travis
16:14:16  <piscisaureus_>the current Travis comments are kinda noisy
16:15:04  <tjfontaine>seems like travis is already configured to use it
16:16:16  * tomshredsquit (Ping timeout: 276 seconds)
16:18:50  * dapjoined
16:21:32  <piscisaureus_>https://github.com/joyent/libuv/pull/546 <-- we'll find out soon
16:30:53  <NUMLOCKBOT>cd /media/
16:30:54  <NUMLOCKBOT>ls
16:31:13  * NUMLOCKBOTquit (Quit: leaving)
16:31:15  <tjfontaine>NUMLOCKBOT: by the way that terminal has irssi running
16:31:17  <tjfontaine>oh damn.
16:31:54  * loladirojoined
16:33:07  <piscisaureus_>tjfontaine: ya that was just me. sorry
16:33:13  <tjfontaine>I know :)
16:34:28  * piscisaureusjoined
16:34:28  * ericktquit (Quit: erickt)
16:34:37  * loladiroquit (Client Quit)
16:35:07  <piscisaureus>tjfontaine: irssi should just print a big warning:
16:35:14  <piscisaureus>"noooooo this is not bash:
16:35:41  <tjfontaine>heh, there's scripts/plugins so that you can have a terminal window in your irssi
16:35:50  <piscisaureus>ghe
16:35:57  <piscisaureus>how incredibly backwards
16:36:18  <tjfontaine>welcome to FOSS :)
17:07:27  * TooTallNatejoined
17:11:40  * DrPizzajoined
17:11:41  * DrPizzaquit (Read error: Connection reset by peer)
17:13:10  * DrPizzajoined
17:14:57  * loladirojoined
17:20:32  * hzquit (Disconnected by services)
17:20:34  * hzjoined
17:25:48  * loladiroquit (Quit: loladiro)
17:27:38  * joshthecoderjoined
17:30:01  * AvianFluquit (Quit: AvianFlu)
17:42:43  * ericktjoined
17:47:05  * loladirojoined
17:47:28  * loladiroquit (Client Quit)
17:49:53  * TheJHjoined
18:00:55  * loladirojoined
18:01:09  * loladiroquit (Client Quit)
18:02:36  * loladirojoined
18:03:07  * loladiroquit (Client Quit)
18:05:00  * loladirojoined
18:07:39  * c4miloquit (Remote host closed the connection)
18:08:33  * c4milojoined
18:16:12  * beachdogjoined
18:26:26  * bnoordhuisjoined
18:30:12  * loladiroquit (Quit: loladiro)
18:31:55  * joshthecoderquit (Quit: Linkinus - http://linkinus.com)
18:32:03  * loladirojoined
18:33:52  * loladiroquit (Client Quit)
18:49:49  * hzquit (Disconnected by services)
18:49:53  * hzjoined
19:03:23  * tomshredsjoined
19:07:32  * joshthecoderjoined
19:09:47  <indutny>bnoordhuis: ok man
19:09:50  <indutny>fuck openssl patching
19:09:57  <indutny>better rewrite it
19:09:57  <indutny>meanwhile
19:10:03  <indutny>lets pull that async tls session stuff in :)
19:17:15  <CIA-129>node: Bert Belder v0.8 * r6174ea6 / (16 files in 3 dirs): doc: don't use ' - http://git.io/QHUt6w
19:17:34  <bnoordhuis>indutny: i like the idea of rewriting openssl
19:17:40  <bnoordhuis>can you have it finished by four?
19:17:44  <indutny>bnoordhuis: yeah, I've already started it
19:17:54  <indutny>bnoordhuis: four what?
19:17:57  <indutny>July?
19:17:59  <bnoordhuis>four am?
19:17:59  <tjfontaine>oclock
19:18:07  <indutny>only July 4th
19:18:20  <bnoordhuis>pquerna was working on that
19:18:44  <bnoordhuis>using openssl for crypto but doing everything else async
19:18:46  <indutny>bnoordhuis: no, he wasn't
19:18:48  <indutny>yeah
19:19:13  <indutny>only async stuff
19:26:28  <indutny>I want to say
19:26:32  <indutny>I love you guys
19:26:36  <indutny>you're so awesome
19:27:56  <bnoordhuis>hah, where does that come from?
19:28:24  <TooTallNate>indutny: you are loved back
19:31:25  * beachdog_joined
19:35:27  <piscisaureus_>maybe polarssl?
19:36:26  <indutny>oh, yeah
19:36:30  <indutny>I remember it!
19:36:48  <indutny>but unfortunatelly it's not async
19:37:52  * theColejoined
19:38:53  <indutny>actually, I think I may repeat that off-loading-to-threads tls handshake experiment
19:39:39  <indutny>bnoordhuis: https://github.com/joyent/node/pull/3661
19:39:40  <indutny>updated
19:41:07  * beachdog_quit (Remote host closed the connection)
19:45:09  * beachdogquit (Remote host closed the connection)
19:48:33  <indutny>bnoordhuis: ?
19:49:31  * loladirojoined
19:52:44  * loladiroquit (Client Quit)
19:57:10  * ibobrikquit (Quit: ibobrik)
19:59:52  * hzquit (Disconnected by services)
19:59:57  * hzjoined
20:09:12  <bnoordhuis>indutny: ?
20:09:27  <CIA-129>node: Ben Noordhuis master * r790d651 / (3 files in 3 dirs): http: make http.ServerResponse emit 'end' - http://git.io/N8GP1A
20:09:42  <pquerna>indutny: on that patch, clientHello always comes first, if you see anything else, shouldn't it just stop/finish() ?
20:10:27  <pquerna>indutny: hrm
20:12:35  <pquerna>indutny: what would happen on an session size of 254 say, and then bogus padding data in the extensions area
20:13:02  <pquerna>indutny: in practice openssl session_size is always.. 32 bytes iirc (should double check)
20:13:43  <pquerna>indutny: The length of the session id is 16 bytes for SSLv2 sessions and between 1 and 32 bytes for SSLv3/TLSv1
20:16:45  <indutny>pquerna: well, I think it's ok to limit it there
20:17:08  <indutny>pquerna: not only client hello may come first
20:17:24  <indutny>bnoordhuis: review?
20:17:37  <indutny>pquerna: like alert protocol
20:17:39  <indutny>pquerna: or anything else
20:17:45  <indutny>pquerna: this is surely not the case for https stuff
20:18:07  <bnoordhuis>indutny: my GP advised me to cut back on the number of reviews
20:18:07  <pquerna>indutny: sure, but in those cases, we should just hand of to openssl?
20:18:34  <pquerna>like cover the 99% case in a paranoid way
20:18:41  <pquerna>but don't try to cover it all imo
20:18:44  <pquerna>tls is a bitch (tm)
20:18:51  <indutny>pquerna: hm...
20:19:09  <pquerna>a client sending a tls alert in the first frame is already F'ed up tbh
20:19:17  <pquerna>let openssl deal :)
20:19:43  <indutny>pquerna: ok
20:20:08  <piscisaureus>bnoordhuis: hey
20:20:20  <piscisaureus>bnoordhuis: is there any way I can make valgrind stack traces longer?
20:20:48  <pquerna>indutny: its a neat patch though, i want to port it to apcahe now :)
20:20:54  <indutny>pquerna: hahaha
20:20:57  <indutny>thanks
20:21:06  <indutny>pquerna: what's a use for it in httpd?
20:21:14  <indutny>pquerna: I thought you're using thread pool
20:21:27  <pquerna>indutny: in th event mpm, we could do async memcache for the sessionc ache
20:21:33  <indutny>oh
20:21:34  <indutny>great
20:21:40  <pquerna>like keep the socket in accepting in the event loop
20:21:43  <pquerna>just like in node really :)
20:21:43  <indutny>pquerna: sad thing is that tls tickets are widely adopted too
20:21:53  <pquerna>until IE does it....
20:21:56  <indutny>hahaha
20:22:11  <indutny>well, with tls tickets we don't need this stuff at al
20:22:14  <indutny>s/al/all
20:22:15  <pquerna>yeah
20:22:20  <pquerna>its great :)
20:22:30  <indutny>yeah, sure
20:22:50  <pquerna>need to get like, Python using tls tickets
20:22:53  <pquerna>for all our api clients :(
20:24:02  <indutny>haha
20:24:04  <pquerna>hrm, actually, that would be interesting. I should get a pcap of our inbound API servers TLS connections, analyze what support numbers are for tls session tickets, etc
20:24:10  <pquerna>its pretty different mix that consumer browsers
20:24:15  <indutny>yeah
20:24:17  <indutny>that would be good
20:24:27  <indutny>it should not be hard to parse this
20:24:30  <pquerna>yeah
20:24:34  <pquerna>todo+=
20:24:38  <bnoordhuis>piscisaureus: yes, --num-callers=32
20:24:39  <indutny>haha
20:24:54  <indutny>so, what about APIs for async session storage?
20:25:04  <indutny>I don't really like camel case resumeSession
20:25:06  <indutny>and newSession
20:25:16  <indutny>may be just 'session'
20:25:28  <indutny>and a boolean argument
20:25:39  <bnoordhuis>vetoed
20:25:47  <indutny>bnoordhuis: so what?
20:25:51  <bnoordhuis>so there
20:25:52  <indutny>:)
20:25:59  <indutny>ok, what's your proposal?
20:26:10  <indutny>resumeTlsSession is definitely not shortest thing to type
20:26:13  <indutny>and looks awful
20:26:21  <bnoordhuis>who cares? C-n ftw
20:26:33  <bnoordhuis>resumeSession is okay
20:26:39  <indutny>ok
20:26:45  <indutny>will remove Tls from it
20:28:03  <indutny>bnoordhuis: are you ok with merging it?
20:28:46  <bnoordhuis>let me check it one more time
20:28:55  <bnoordhuis>that's like review round 6, i think?
20:29:39  <bnoordhuis>indutny: you haven't added any tests
20:29:50  <indutny>bnoordhuis: heh
20:29:52  <indutny>bnoordhuis: oooook
20:29:56  <indutny>lam
20:36:17  <txdv2>HMMM HAAA
20:36:41  <indutny>txdv2: hi
20:42:22  * TheJHquit (Ping timeout: 248 seconds)
20:47:33  <indutny>bnoordhuis: added documentation and test
20:49:35  * AvianFlujoined
20:52:09  <bnoordhuis>what's a decent vnc client for linux these days?
20:56:08  <tjfontaine>are you looking for something with a pretty gui, or just quality vnc interaction? I mostly still use tight
20:57:16  <bnoordhuis>oh, just basic vnc functionality, it doesn't have to be pretty
20:57:24  <bnoordhuis>just installed vinagre, seems to work okay
20:57:47  <bnoordhuis>tightvnc was my second option though :)
20:57:53  <mmalecki>I use vinagre
20:57:55  <tjfontaine>I'm old school
21:00:18  <piscisaureus>any nodeconf attendees here?
21:00:50  <piscisaureus>er, summercamp
21:01:00  <AvianFlu>piscisaureus: I'm headed there shortly, but not yet at the camp
21:01:17  <piscisaureus>AvianFlu: do you happen to have Mikeal's phone number?
21:01:22  <AvianFlu>maybe? let me check
21:01:30  <indutny>so
21:01:37  <indutny>bnoordhuis: lets land it?
21:02:37  <bnoordhuis>indutny: i haven't reviewed it yet, will do later tonight
21:03:11  * AvianFluquit (Read error: Connection reset by peer)
21:03:45  * AvianFlujoined
21:14:10  * tomshredsquit (Quit: Linkinus - http://linkinus.com)
21:19:51  * paddybyersquit (Quit: paddybyers)
21:20:20  * AvianFluquit (Quit: AvianFlu)
21:28:56  * TooTallNatequit (Ping timeout: 240 seconds)
21:30:53  * paddybyersjoined
21:33:05  * TooTallNatejoined
21:33:11  <indutny>bnoordhuis: ok
21:46:02  <indutny>bnoordhuis: I'm thinking about piping inside libuv
21:46:32  <indutny>bnoordhuis: like creating a (sort of) socketpair from two streams and processing function
21:46:59  <indutny>bnoordhuis: this looks like an API, not a conceptual change
21:47:09  <indutny>though may have interesting impacts on how we deal with SSL in node
21:47:45  <indutny>for example, we may have both cleartext and encrypted streams in uv and expose only sockets to node
21:47:56  <indutny>which sounds really reasonable for me
21:48:02  <indutny>bnoordhuis: what do you think?
21:59:49  * loladirojoined
22:01:42  <txdv2>ui is such a pain in the ass that nobody is doing it for fun
22:02:42  <indutny>bnoordhuis: removed that loop
22:02:44  <indutny>bnoordhuis: pushing
22:03:05  <CIA-129>node: Fedor Indutny master * r8e0c830 / (5 files in 4 dirs): tls: async session storage - http://git.io/0Ungvg
22:03:59  <indutny>bnoordhuis: yt?
22:24:54  * paddybyersquit (Quit: paddybyers)
22:27:19  * rendarquit
23:00:34  * loladiroquit (Quit: loladiro)
23:05:54  * txdv2quit (Quit: Lost terminal)
23:43:36  * hzquit
23:45:38  * lohkeyjoined
23:48:07  * loladirojoined
23:49:12  <bnoordhuis>indutny: ih