00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:07  * ircretaryjoined
00:04:45  * mikealquit (Ping timeout: 276 seconds)
00:08:16  * bnoordhu1sjoined
00:12:36  * bnoordhu1squit (Ping timeout: 248 seconds)
00:23:57  * bnoordhuisquit (Ping timeout: 276 seconds)
00:25:44  * Ralt_joined
00:30:48  * mikealjoined
00:35:01  * mikealquit (Ping timeout: 245 seconds)
00:41:55  * shigekijoined
00:43:40  * Ralt_quit (Remote host closed the connection)
01:01:31  <isaacs>man, this benchmark compare script is already proving its worth
01:01:31  * mikealjoined
01:05:37  * felixgequit (Quit: felixge)
01:19:36  * perezdjoined
01:24:11  * mikealquit (Ping timeout: 245 seconds)
01:28:55  * c4miloquit (Remote host closed the connection)
01:28:59  * perezdquit (Quit: perezd)
01:51:19  * mikealjoined
01:56:00  * mikealquit (Ping timeout: 264 seconds)
01:58:34  <shigeki>ircretary: tell piscisaureus_ I reopen the PR so as to use timer_counter. Please review my patch.
01:58:34  <ircretary>shigeki: I'll be sure to tell piscisaureus_
01:58:47  * shigekiquit (Quit: Page closed)
02:20:14  * txdvjoined
02:22:06  * mikealjoined
02:26:36  * mikealquit (Ping timeout: 264 seconds)
02:36:23  * hzquit
02:53:05  * mikealjoined
02:57:23  * mikealquit (Ping timeout: 240 seconds)
03:21:39  * indexzerojoined
03:23:53  * mikealjoined
03:28:20  * mikealquit (Ping timeout: 248 seconds)
03:31:22  * Raynosquit
03:36:00  * Raynosjoined
03:51:47  * jmar777quit (Remote host closed the connection)
03:52:22  * TheJHquit (Ping timeout: 240 seconds)
03:54:34  * mikealjoined
03:58:53  * mikealquit (Ping timeout: 240 seconds)
04:05:02  * indexzeroquit (Quit: indexzero)
04:23:04  * trevnorrisjoined
04:25:15  * mikealjoined
04:29:51  * rje`macquit (Quit: Leaving...)
04:30:17  * rjejoined
04:34:34  * rjequit (Quit: Leaving...)
04:39:20  * rjejoined
04:47:19  * mikealquit (Ping timeout: 260 seconds)
04:53:19  * rjequit (Quit: Leaving...)
04:56:22  * rjejoined
05:01:59  * bradleymeckquit (Quit: bradleymeck)
05:14:08  * mikealjoined
05:19:21  * mikealquit (Ping timeout: 276 seconds)
05:26:51  * stagasjoined
05:44:54  * mikealjoined
05:49:26  * mikealquit (Ping timeout: 255 seconds)
05:57:42  <trevnorris>any libuv experts up?
06:15:41  * mikealjoined
06:19:59  * mikealquit (Ping timeout: 244 seconds)
06:20:27  * perezdjoined
06:46:30  * mikealjoined
06:58:09  * mikealquit (Read error: Connection reset by peer)
07:10:13  * mikealjoined
07:10:15  * mikealquit (Client Quit)
07:10:37  * mikealjoined
07:30:55  * AvianFluquit (Remote host closed the connection)
08:02:25  * rendarjoined
08:24:34  * stagas_joined
08:25:38  * loladiroquit (Quit: loladiro)
08:26:08  * stagasquit (Ping timeout: 255 seconds)
08:26:14  * stagas_changed nick to stagas
08:35:59  * stagasquit (Ping timeout: 260 seconds)
08:58:05  * paddybyersjoined
09:08:57  <indutny>morning
09:09:17  <trevnorris>indutny: sup
09:09:30  <indutny>you have libuv questions?
09:10:19  <trevnorris>yeah. newb one. i see uv_idle_start declared, but can't find where it's defined.
09:10:57  <indutny>ahhaha
09:11:00  <indutny>use the search
09:12:29  <trevnorris>practically grep'd my entire hard drive. `grep -r "\<uv_idle_start\>" *` and only found it in include/uv.h and several tests.
09:12:36  <trevnorris>that what you meant?
09:17:08  <indutny>trevnorris: well, you seriously want to know answer?
09:17:09  <indutny>:)
09:17:24  <indutny>its in src/unix/loop-watcher.c
09:18:35  <trevnorris>oh, son of a #@$%. didn't expect a define to use a partial name.
09:18:37  <trevnorris>thanks.
09:19:48  <indutny>:)
09:19:48  <indutny>np
09:20:04  <indutny>basically, that's because check, idle, and prepare share all code
09:20:20  <trevnorris>ah, makes it simple.
09:28:20  * paddybyersquit (Ping timeout: 248 seconds)
09:35:32  * felixgejoined
09:35:32  * felixgequit (Changing host)
09:35:32  * felixgejoined
09:37:01  * `3rdEdenjoined
09:39:18  * felixgequit (Client Quit)
10:01:42  * Ralt_joined
10:20:30  * paddybyersjoined
10:26:39  * paddybyersquit (Ping timeout: 256 seconds)
10:33:17  * trevnorrisquit (Quit: Leaving)
10:38:53  * Ralt_quit (Remote host closed the connection)
10:45:12  * Ralt_joined
10:56:53  * bnoordhuisjoined
11:17:55  * bnoordhuisquit (Ping timeout: 260 seconds)
11:21:58  * bnoordhuisjoined
11:55:00  * bnoordhuisquit (Ping timeout: 248 seconds)
11:57:49  * `3rdEdenchanged nick to `3E|AFK
12:01:23  * TheJHjoined
12:04:53  * CoverSlide&
12:04:54  <LOUDBOT>I'M GONNA LAY YOU DOWN WO-MAN
12:11:59  * felixgejoined
12:12:00  * felixgequit (Changing host)
12:12:00  * felixgejoined
12:13:04  * `3E|AFKquit (Remote host closed the connection)
12:43:21  * bnoordhuisjoined
12:54:36  * TheJHquit (Ping timeout: 245 seconds)
12:57:39  * Ralt_quit (Remote host closed the connection)
12:57:54  * `3rdEdenjoined
12:58:01  <mmalecki>bnoordhuis: hey
12:58:19  <mmalecki>bnoordhuis: is there any word on making node's DNS JS?
12:58:44  <bnoordhuis>mmalecki: none so far
12:58:48  <bnoordhuis>why do you ask?
12:59:25  <mmalecki>bnoordhuis: cares doesn't feel configurable. would be good to be able to change name servers, for example
12:59:50  <mmalecki>bnoordhuis: I'm doing something DNS-heavy and I'm afraid that C-JS boundary will be a bottleneck
13:05:49  <indutny>bnoordhuis: hi
13:13:57  * TheJHjoined
13:23:52  * TheJHquit (Ping timeout: 240 seconds)
13:26:47  <saghul>mmalecki you can change nameserver in c-ares, maybe that is not exposed to JS?
13:26:55  <saghul>*nameservers
13:27:55  <mmalecki>it's not
13:30:10  <saghul>mmalecki right. Also AFAIS there is a single ares channel being used, so you can't have multiple queries in parallel with different nameservers
13:30:19  <saghul>not use if someone would need that though
13:30:43  <mmalecki>yeah, that kind of sucks
13:31:02  <mmalecki>we don't want one library to be able to mess something up
13:37:03  <`3rdEden>mmalecki: do you happen to know a way to figure out if a connection is closed by server you connect to, or if it's done by a .end/destroy call that is initiated by a user?
13:37:28  <`3rdEden>The only horrible hack I can come up with is call stack parsing =/
13:37:42  <`3rdEden>and overriding the end/destroy methods
13:37:55  <indutny>.end should emit 'finish'
13:38:14  <indutny>and no difference between .destroy and when server closes connection
13:39:54  <mmalecki>`3rdEden: you mean, on('end') ?
13:40:59  <`3rdEden>mmalecki: on(end) is always emitted, when the server closes the connection or when the you manually connection.end()
13:41:23  * Ralt_joined
13:41:53  <`3rdEden>indutny: I know there's no difference, but there's a different reason why connection got closed
13:43:11  <indutny>well
13:43:12  <indutny>I mean
13:43:16  <indutny>you asked - I answered :)
13:43:21  <indutny>you can't tell it from APIs
13:43:21  * Ralt_quit (Remote host closed the connection)
13:43:23  <indutny>afaik
13:43:54  <`3rdEden>indutny: so stack parsing is the only solution
13:44:07  <indutny>can you open github issue?
13:44:14  <`3rdEden>indutny: sure
13:44:38  <indutny>oh
13:44:40  <indutny>there is a way
13:44:49  <indutny>you can try checking .readable .writable state
13:44:59  <`3rdEden>hms
13:45:59  <`3rdEden>indutny: no difference, they are false in all cases
13:46:07  <indutny>when are you checking?
13:46:09  <indutny>on 'close' event?
13:46:17  <indutny>also you'll probably need to set allowHalfOpen to true
13:46:27  <indutny>and close your side manually after it
13:47:45  <`3rdEden>indutny: yes, i'm listening for the close event
13:47:59  <indutny>what about half-open?
13:50:33  <`3rdEden>indutny: when you allowHalfOpen you don't receive an `end` event
13:50:36  * felixgequit (Ping timeout: 276 seconds)
13:50:40  <indutny>well
13:50:45  <indutny>you should just call .destroySoon()
13:50:48  <indutny>when received 'close'
13:50:52  <indutny>it should be generally the same
13:51:41  <`3rdEden>err, I mean it didn't emit a close event
13:52:08  * felixgejoined
13:52:08  * felixgequit (Changing host)
13:52:08  * felixgejoined
13:52:43  <mmalecki>`3rdEden: maybe set a property on a socket when you end it yourself?
13:53:00  <mmalecki>sock._ended = true; sock.end();
13:53:03  <`3rdEden>mmalecki: I can't expect users to set a property ._.
13:53:13  <indutny>`3rdEden: yes, you're probably right
13:53:13  <`3rdEden>that's just horrible lol
13:53:19  <indutny>`3rdEden: open an issue
13:53:22  <indutny>we'll figure out something
13:53:23  <indutny>in 0.10
13:53:37  <mmalecki>`3rdEden: I mean, I'm giving you a walkaround
13:53:45  <mmalecki>I'm not actually expecting people to do that
13:53:47  <`3rdEden>mmalecki: yeah iknow :p
14:03:12  * felixgequit (Read error: Connection reset by peer)
14:03:17  * felixge_joined
14:03:17  * felixge_quit (Changing host)
14:03:17  * felixge_joined
14:03:29  * hzjoined
14:08:03  <bnoordhuis>mmalecki: sorry, i don't get irc notifications on this machine
14:08:24  <bnoordhuis>mmalecki: re dns, don't worry about the js->c++ boundary, that's probably the least of your worries
14:08:34  <bnoordhuis>we're talking microseconds here at worst
14:09:02  <indutny>bnoordhuis: benchmark? :)
14:09:14  <indutny>I guess it could be almost 300-400us
14:09:18  <bnoordhuis>bertje benchmarked it a while ago
14:09:23  <indutny>and?
14:09:31  <bnoordhuis>i forgot the exact numbers but the actual switch is noise
14:09:31  <indutny>results?
14:09:56  <bnoordhuis>the thing that hurts is that you usually have to marshall data in and out of js land
14:10:22  <indutny>well
14:10:26  <indutny>it hurts much more
14:10:26  <indutny>I agree
14:11:01  <`3rdEden>indutny: logged
14:11:04  <`3rdEden>https://github.com/joyent/node/issues/4739
14:17:36  <bnoordhuis>btw, i figured out how to use EV_CLEAR to approximate edge-triggered i/o with kqueue
14:17:57  <bnoordhuis>but it's less than useful because you need to rearm the EVFILT_* manually
14:18:27  <bnoordhuis>so it doesn't really cut down on the number of syscalls but at least it stops the event loop from waking up all the time
14:18:40  <bnoordhuis>if you're not immediately consuming the event, i mean
14:19:37  <indutny>bnoordhuis: yep
14:19:48  <indutny>I think its not worth it
14:19:51  <indutny>(my assumption)
14:20:59  <bnoordhuis>yeah, i don't really see an advantage here
14:23:28  <MI6>joyent/node: Ben Noordhuis master * fe10335 : typed arrays: make DataView throw on non-ArrayBuffer Make the DataView c (+3 more commits) - http://git.io/LzZX7g
14:26:25  * `3rdEdenquit (Remote host closed the connection)
14:30:09  <saghul>bnoordhuis Thanks for sharing your findings :-)
14:37:08  * bnoordhuisquit (Ping timeout: 248 seconds)
14:42:40  * TheJHjoined
14:56:54  * `3rdEdenjoined
14:57:08  <roxlu>hi guys, I'm experiencing that wierd non-stopping loop again in another project. I send data on a sockets and my on_written callback keeps getting called
14:57:24  <roxlu>uv_write(..) does not return an error
14:58:05  * roxlugetting a backtrace
15:05:18  * `3rdEdenquit (Ping timeout: 256 seconds)
15:06:32  <roxlu>ok got a backtrace here: https://gist.github.com/roxlu/aefc788b622f7d88a9ef
15:07:13  <roxlu>how can I figure out why libuv comes into a endless loop?
15:17:13  <roxlu>ah, I think I got it
15:17:33  <roxlu>I'm using a "client" struct which has a uv_write_t which I'm using for all my uv_write() calls
15:17:53  <roxlu>it seems that, when reusing this member it fails
15:18:38  <roxlu>it would be awesome if this could be described somewhere in the docs/source code (or the online 'book')
15:42:35  * `3rdEdenjoined
15:43:29  * bnoordhuisjoined
15:47:31  * jmar777joined
15:48:54  * bnoordhuisquit (Ping timeout: 276 seconds)
15:55:27  * loladirojoined
16:06:35  * bnoordhuisjoined
16:07:49  * TheJHquit (Ping timeout: 246 seconds)
16:09:16  * AvianFlujoined
16:13:56  <bnoordhuis>saghul: sorry, missed your comment but np :)
16:14:13  <bnoordhuis>i guess i should set up growl on this machine
16:18:08  * `3rdEdenquit (Remote host closed the connection)
16:27:21  <mmalecki>bnoordhuis: would you accept a pull request for changing DNS servers?
16:34:28  <bnoordhuis>mmalecki: for changing the ares dns servers? probably
16:34:35  <bnoordhuis>i think there already is one (a PR that is)
16:38:13  * toothrotquit (Read error: Connection reset by peer)
16:40:43  * toothrjoined
16:41:32  * dscapechanged nick to dscape2
16:41:47  * dscape2changed nick to dscape
16:47:35  <MI6>joyent/libuv: Shigeki Ohtsu master * fadfeaf : unix,windows: fix timer order in case of same timeout Compare start_id o - http://git.io/Krg7Dg
16:48:39  * `3rdEdenjoined
16:50:32  <MI6>joyent/libuv: Ben Noordhuis master * da71649 : unix, windows: make uv_fs_t.statbuf public Make the statbuf field public - http://git.io/bnRRgg
16:51:55  * piscisaureus_joined
16:52:04  <bnoordhuis>piscisaureus_: olla bertje
16:52:05  <piscisaureus_>ircretary: notes
16:52:15  <piscisaureus_>hey bennetje
16:52:20  <piscisaureus_>how's it hanging?
16:52:35  <bnoordhuis>to the left, most of the times
16:52:48  <bnoordhuis>when are you flying? tuesday or wednesday?
16:52:53  <piscisaureus_>wednesday
16:53:25  <piscisaureus_>bnoordhuis: do you think I should implement st_dev and st_ino now?
16:53:40  <bnoordhuis>is that feasible on windows?
16:53:49  <piscisaureus_>I can now do so by defining my own uv_statbuf_t to make these fields bigger
16:53:49  <bnoordhuis>i think a lot of people would be happy with st_ino
16:54:05  <piscisaureus_>The only problem is that "inodes" on windows are 128-bit values
16:54:25  <bnoordhuis>well, at least that's future proof
16:55:06  <piscisaureus_>oh wait it's actually 64-bit
16:55:14  <piscisaureus_>http://msdn.microsoft.com/en-us/library/windows/hardware/ff540318(v=vs.85).aspx
16:56:08  <bnoordhuis>no problem then, they're 64 bits on most unices as well
16:57:05  * `3rdEdenquit (Ping timeout: 256 seconds)
16:57:13  <piscisaureus_>yes so they dont' actually fit in a js number right?
16:57:21  <bnoordhuis>no, indeed
16:57:22  <piscisaureus_>btw st_dev would be 128-bit
16:57:23  <piscisaureus_>http://msdn.microsoft.com/en-us/library/windows/hardware/ff540274(v=vs.85).aspx
16:57:40  <bnoordhuis>but in practice they easily fit in 2**53
16:57:47  * c4milojoined
16:58:38  <bnoordhuis>2**53 is still 9 million billion files
16:58:50  <bnoordhuis>okay, dinner time. biab
16:59:10  <piscisaureus_>it depens of course whether the id is opaque or monotonically increasing
16:59:36  <piscisaureus_>ok eat smeakelike
17:03:30  * bnoordhuisquit (Ping timeout: 252 seconds)
17:06:44  * felixge_quit (Quit: felixge_)
17:19:22  <roxlu>FYI: small type, https://github.com/joyent/libuv/blob/master/include/uv.h#L541 (twice "several several")
17:19:59  <roxlu>FYI: small typO, https://github.com/joyent/libuv/blob/master/include/uv.h#L541 (twice "several several")
17:23:09  * TheJHjoined
17:23:23  * mikealquit (Quit: Leaving.)
17:27:03  * paddybyersjoined
17:36:24  <roxlu>hi guys, the alloc callback asks for 65536 bytes, event if it needs to read just a couple of bytes. Therefore I'm continuosly allocating/deallocating .. isnt' there a smarty way to reuse previously allocated data
17:59:05  * mikealjoined
18:03:42  * hzquit
18:09:15  * bnoordhuisjoined
18:13:21  * bnoordhuisquit (Ping timeout: 240 seconds)
18:26:14  * mikealquit (Quit: Leaving.)
18:35:20  * bnoordhuisjoined
18:36:38  * `3rdEdenjoined
18:40:03  * `3rdEdenquit (Remote host closed the connection)
18:47:52  * c4miloquit (Remote host closed the connection)
18:49:52  <piscisaureus_>roxlu: if you *know* you are only going to receive some bytes then you can igore the hint
18:51:01  * `3rdEdenjoined
18:51:20  * c4milojoined
18:51:34  <piscisaureus_>roxlu: what node does btw is allocate a big slab (1mb) and it keeps track of the last part that was returned by alloc_cb. If a subsequent read_cb returns the same chunk it can move the start position for the next chunk backwards.
18:56:28  * mikealjoined
19:17:52  <bnoordhuis>piscisaureus_: https://github.com/joyent/node/issues/4736#issuecomment-13345187 <- seen that? can't reproduce it on unices with v0.8
19:21:48  <piscisaureus_>bnoordhuis: yes, although I haven't dug into it
19:40:51  * toothrquit (Read error: Connection reset by peer)
19:44:39  * toothrjoined
20:25:14  * `3rdEdenquit (Remote host closed the connection)
20:29:11  * hzjoined
20:30:51  * qmx|awaychanged nick to qmx
20:47:29  * stagasjoined
20:53:37  * `3rdEdenjoined
20:58:38  <MI6>joyent/node: Ben Noordhuis master * 30b0bc4 : doc: update buffer/typed array documentation Clarify that typed array co (+1 more commits) - http://git.io/G5v5Ng
20:59:33  <bnoordhuis>i hate typed arrays >:(
21:04:08  * loladiroquit (Quit: loladiro)
21:07:39  * trevnorrisjoined
21:07:41  * hzquit
21:07:50  * brsonjoined
21:11:39  * loladirojoined
21:12:31  * stagas_joined
21:14:38  * stagasquit (Ping timeout: 255 seconds)
21:16:19  * stagasjoined
21:16:46  * stagasquit (Remote host closed the connection)
21:17:07  * stagasjoined
21:17:53  * stagas_quit (Ping timeout: 255 seconds)
21:19:27  * paddybyersquit (Ping timeout: 256 seconds)
21:22:30  <trevnorris>bnoordhuis: you around?
21:23:17  <bnoordhuis>trevnorris: i am
21:23:56  <trevnorris>bnoordhuis: one problem with the DataView change. part of your argument was that it could be accessed via .buffer. all buffers of typed arrays can be accessed that way.
21:24:13  <trevnorris>(new Uint32Array(12)).buffer
21:24:36  <bnoordhuis>trevnorris: all .buffer properties are ArrayBuffers now
21:25:13  <bnoordhuis>actually, if we changed Buffer#slice to accept negative indices, ArrayBuffers and Buffers would be pretty much interchangeable
21:25:19  <trevnorris>bnoordhuis: um... (new Uint32Array(new Buffer(12))).buffer?
21:25:29  <bnoordhuis>the buffer is cloned
21:25:42  <bnoordhuis>into an ArrayBuffer, that is
21:25:44  <trevnorris>ah, forgot to build after pulling. thanks.
21:25:58  <bnoordhuis>i'm not at all happy with these changes btw
21:26:06  <bnoordhuis>but correctness before performance (usually)
21:26:33  <trevnorris>yeah. i understand.
21:27:56  <bnoordhuis>i'll open an issue and call in some people
21:28:01  <trevnorris>bnoordhuis: fwiw there's another non-spec specific we have. the data backing the ArrayBuffer should be a hidden property. non-enumerable.
21:28:29  <bnoordhuis>you mean non-indexable?
21:28:34  <trevnorris>um. yeah.
21:28:39  <bnoordhuis>yeah, i know
21:29:01  <bnoordhuis>i'm undecided if that's something we should ax
21:29:23  <trevnorris>bnoordhuis: like the negative slice idea. wasn't that something you wanted?
21:29:25  <bnoordhuis>it's not directly harmful in the way that the other infidelities were
21:29:30  <bnoordhuis>yes, i did :)
21:29:39  <bnoordhuis>how forward thinking of me, eh?
21:29:46  <trevnorris>lol, yeah.
21:30:08  <trevnorris>i like it. and cross compatibility between buffers and arraybuffers is very helpful.
21:31:24  * mikealquit (Quit: Leaving.)
21:35:27  * indexzerojoined
21:37:09  * paddybyersjoined
21:41:11  <bnoordhuis>trevnorris: https://github.com/joyent/node/issues/4742
21:41:31  <bnoordhuis>paddybyers: so i hear android has a working fork() syscall now
21:41:40  * stagas_joined
21:42:21  * stagasquit (Ping timeout: 240 seconds)
21:42:35  * stagas_changed nick to stagas
21:42:51  <paddybyers>bnoordhuis: I hadn't seen that; I'll check it out
21:43:31  <trevnorris>bnoordhuis: awesome, thanks.
21:44:35  <bnoordhuis>paddybyers: only in newer releases though (forgot which one exactly). but that would remove the need for isolates for you, right?
21:45:06  <paddybyers>maybe yes. It depends on how it integrates with the Android application layer
21:45:35  <paddybyers>we didn't really need fork(), just the ability to run more than a single process belonging to a given application
21:45:48  <paddybyers>they don't have to be forks of one another
21:50:20  * wolfeidauquit (Remote host closed the connection)
22:01:04  <paddybyers>bnoordhuis: I can't find a reference to it - got a link?
22:01:09  * joshthecoder_changed nick to joshthecoder
22:01:10  <paddybyers>I'll keep looking
22:02:17  * mikealjoined
22:08:29  * wolfeidaujoined
22:09:35  * toothrchanged nick to toothrot
22:11:06  * rendarquit
22:27:08  <bnoordhuis>paddybyers: hm, google doesn't turn up anything. i heard it from a guy that works on android
22:27:51  <paddybyers>bnoordhuis: ok, thanks for looking
22:28:01  * c4miloquit (Ping timeout: 256 seconds)
22:28:13  * c4milojoined
22:34:49  * trevnorrisquit (Quit: Leaving)
22:46:28  <paddybyers>bnoordhuis: (another topic) ever had a problem with chrome taking forever to parse heapdump?
22:46:46  <paddybyers>node 0.6.x
22:46:57  * indexzeroquit (Quit: indexzero)
22:50:41  * TheJHquit (Ping timeout: 252 seconds)
22:55:36  * `3rdEdenquit (Remote host closed the connection)
23:03:15  * TheJHjoined
23:03:22  * mikealquit (Quit: Leaving.)
23:04:06  * mikealjoined
23:07:07  * mikealquit (Client Quit)
23:10:31  * stagasquit (Ping timeout: 256 seconds)
23:14:51  * piscisaureus_quit (Quit: ~ Trillian Astra - www.trillian.im ~)
23:24:17  * TheJHquit (Read error: Operation timed out)
23:28:02  * loladiroquit (Quit: loladiro)
23:29:28  * mikealjoined
23:35:29  * piscisaureus_joined
23:36:02  * bnoordhuisquit (Ping timeout: 255 seconds)
23:38:46  * c4miloquit (Remote host closed the connection)
23:49:06  * qmxchanged nick to qmx|away
23:50:22  * piscisaureus_quit (Ping timeout: 244 seconds)
23:51:19  * paddybyersquit (Ping timeout: 256 seconds)
23:52:13  <rvagg>isaacs: npm's broke, you around?
23:55:53  * travis-cijoined
23:55:53  <travis-ci>[travis-ci] hissohathair/http-parser#1 (master - fa74550 : Corey Richardson): The build passed.
23:55:53  <travis-ci>[travis-ci] Change view : https://github.com/hissohathair/http-parser/compare/0938fe599f7e...fa7455081a53
23:55:53  <travis-ci>[travis-ci] Build details : http://travis-ci.org/hissohathair/http-parser/builds/4712560
23:55:53  * travis-cipart