00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:07  * rmgjoined
00:00:09  * ircretaryjoined
00:00:09  <tjfontaine>at the site of WriteWrap's new you can just use the current child's provider
00:00:37  <trevnorris>yeah, exactly
00:00:41  <trevnorris>that's what I had in mind
00:00:47  <tjfontaine>that's the right path
00:00:57  <tjfontaine>make it a required argument to the constructor, should be fine
00:02:01  <tjfontaine>oh I did that before with modifying the template class for ReqWrap
00:02:05  <tjfontaine>wasn't I clever
00:02:15  <trevnorris>heh
00:02:47  <tjfontaine>anyway, ReqWrap having an explicit and thus WriteWrap having an explicit seems to be the best way to indicate what you want
00:03:24  * brsonquit (Ping timeout: 245 seconds)
00:04:25  * daviddiasquit (Remote host closed the connection)
00:04:43  <trevnorris>yeah. ah, guess I just mostly took care of that, but didn't take care of the places where reqwrap is called directly.
00:04:44  * brsonjoined
00:04:55  * daviddiasjoined
00:05:03  <trevnorris>i'll fix that too
00:05:56  * AvianFluquit (Remote host closed the connection)
00:09:17  * daviddiasquit (Ping timeout: 260 seconds)
00:09:34  * AWintermanquit (Remote host closed the connection)
00:11:11  <trevnorris>tjfontaine: c++ best practices question. AsyncWrap::ProviderType is the enum. should the storage value also be ProviderType, or just like an int32_t?
00:12:10  <tjfontaine>because you're going to be doing bitwise it should be int based, and probably uint32_t even
00:12:52  * mikealjoined
00:13:11  <trevnorris>well, ok. so uint32_t instead. but still. should it be stored and passed as ProviderType or uint32_t? just asking because had it as ProviderType but got compilation errors because AsyncWrap::provider_type() returns the storage value of uint32_t
00:13:33  <trevnorris>so basically you can't just pass wrap->provider_type() as an argument
00:13:56  <tjfontaine>because it's going to be bitwise it should be int based, i.e. not ProviderType
00:14:03  * brson_joined
00:15:15  <trevnorris>well, take for example v8's IndexedProperties methods. SetIndexedPropertiesToExternalArrayData() accepts a ExternalArrayType, and GetIndexedPropertiesExternalArrayDataType() returns the same.
00:15:47  <tjfontaine>they are not subsequently used as bitwise flags storage though?
00:16:13  <trevnorris>GetPropertyAttributes() does, and it returns a PropertyAttribute enum type
00:17:11  * hzquit
00:17:19  * brsonquit (Ping timeout: 250 seconds)
00:18:21  <tjfontaine>storage on the AW should be the ProviderType, but storage for watched_flags and the type for methods should be uint32_t
00:20:45  * c4milojoined
00:21:12  <trevnorris>ok. so from AsyncWrap::provider_type() I just return static_cast<ProviderType>(provider_type_) ?
00:22:30  <tjfontaine>I'm confused, why is the cast necessary? AW::provider_type_ isn't ProviderType?
00:23:52  <trevnorris>ah, misread your comment. got it. :)
00:24:53  <trevnorris>tjfontaine: fyi, there's a comment in fs_event_wrap.cc in FSEventWrap::OnEvent() about something that should be fixed before v1.0
00:28:07  * paulfryzeljoined
00:29:18  * Kakeraquit (Read error: Operation timed out)
00:30:37  * c4miloquit (Remote host closed the connection)
00:30:44  <trevnorris>wow, that's a lot of code just for fs.watch()
00:31:04  * mikolalysenkoquit (Ping timeout: 246 seconds)
00:32:29  * paulfryzelquit (Ping timeout: 250 seconds)
00:33:39  * mikealquit (Quit: Leaving.)
00:36:25  <trevnorris>tjfontaine: think the provider should delineate between TCP connections and servers? or should it all just be TCP?
00:37:06  * zz_karupanerurachanged nick to karupanerura
00:38:07  <tjfontaine>all tcp, the server doesn't really do read/write, but you care about connection, error, close
00:38:24  <tjfontaine>but there's no reason for them to be separate, imo
00:38:49  * octetcloudquit (Quit: WeeChat 0.4.2)
00:39:02  <trevnorris>great. makes my life much easier.
00:39:20  <trevnorris>awesome. feeling good about this. it'll be fun to play with. :)
00:40:07  <trevnorris>tjfontaine: but just to confirm, you don't think that GetAddrInfo and QueryWrap should be combined into one CARES provider?
00:40:27  <tjfontaine>that's correct, I'd like to be able to eventually have THREADPOOL
00:40:35  <tjfontaine>which is getaddr|fs
00:40:50  * c4milojoined
00:41:01  <trevnorris>ah, cool. does that also mean I should keep FSEventWrap and FSReqWrap separate?
00:41:23  <tjfontaine>ya, EventWrap doesn't run in the threadpool (unless it's a stat watcher)
00:41:41  * dshaw_joined
00:42:13  <isaacs>rvagg: I just touched all the docs that you are having problems with
00:42:39  <rvagg>isaacs: thanks, do you think that would cause this kind of pause in replication?
00:42:52  <isaacs>rvagg: not sure.
00:42:52  <trevnorris>tjfontaine: doesn't FSEventWrap only handle fs.watch() ?
00:42:57  <rvagg>isaacs: I don't think this is unique to fullfatdb fwiw, I have a cron job to restart couch every night just for this kind of thing
00:43:17  <isaacs>rvagg: how are you replicating? a POST to /_replicate or a doc in the /_replicator db?
00:43:17  <rvagg>isaacs: I'm thinking of putting a 2 hourly cron job to delete and reinsert the _replicator entry just to give it a kick
00:43:32  <rvagg>isaacs: new _replicator stuff
00:43:36  <isaacs>hm. weird.
00:43:40  <isaacs>thta totlaly has been working for me
00:44:08  <rvagg>isaacs: still struggling to catch up: Checkpointed source sequence 88307, current source sequence 89317, progress 98%
00:44:32  <rvagg>but at least I have beam at 99% now so it's doing *something*
00:46:32  <rvagg>isaacs: btw, if you ever want npmjs.org.au for npm inc just give me a holler
00:46:54  <rvagg>I imagine tho if you ever do official mirrors then it'd be a bit more intelligent than using dns
00:48:25  * kpdeckerjoined
00:49:25  * janjongboomjoined
00:49:34  * __rockbot__quit (Quit: __rockbot__)
00:51:11  * dshaw_quit (Ping timeout: 265 seconds)
00:52:28  <isaacs>rvagg: yeah, i think eventually it'd be cool to have local mirrors that are still using fastly, but shielded by a different POP or something
00:53:35  * __rockbot__joined
00:53:59  <isaacs>rvagg: and smart DNS that routes you based on your origin IP
00:54:27  <isaacs>rvagg: also, then we could still send PUTs to the "real" write-master
00:54:31  <isaacs>so a publish from AU would still be hecka slow.
00:54:43  <isaacs>but GETs would be cached locally
00:54:47  <othiym23>isaacs: does the current architecture use edge caching?
00:54:52  <isaacs>and perhaps have a read-only replica that's local
00:54:56  <isaacs>othiym23: yeah, fastly
00:55:11  <othiym23>yeah, I didn't know if that's what Fastly was doing
00:55:12  <isaacs>othiym23:
00:55:13  <isaacs>$ dig +short registry.npmjs.org
00:55:13  <isaacs>a.sni.fastly.net.
00:55:13  <isaacs>199.27.79.162
00:55:17  <isaacs>yep
00:55:24  <othiym23>( o_o)-b
00:55:28  <trevnorris>tjfontaine: i'm sure you already realize this, but using bitwise operators in js we're stuck to 2^31 since they do int32 math.
00:55:37  <isaacs>try a few curl -v's. you'll see some interesting header info there.
00:55:42  <trevnorris>ok, except for >>> which for some reason does uint32 math
00:55:44  <isaacs>like, cache miss, where it was cached, etc.
00:55:51  <tjfontaine>yes, if we reach that level we can figure something else
00:56:01  <trevnorris>heh. hopefully we don't :P
00:56:17  <tjfontaine>the number of providers in our c++ should be graciously tiny
00:56:30  <tjfontaine>we're always better off relying on the JIT
00:58:20  <MI6>joyent/node: Timothy J Fontaine execSync-wip * d76d01d : add spawnsync input test case (+21 more commits) - http://git.io/ixUhMw
00:59:19  <trevnorris>mother of commits. 21?
00:59:26  <tjfontaine>it'll be rebased before then
00:59:28  <tjfontaine>fear not
00:59:35  <tjfontaine>rebase and squashed
00:59:46  <trevnorris>ah, didn't see it was a topic branch.
00:59:57  <tjfontaine>just getting it out there again, maybe I can get groundwater to write some more tests
01:00:25  <groundwater>tests for what?
01:00:45  <groundwater>i'm always game for trying to break things
01:00:49  <tjfontaine>spawnSync
01:00:57  <groundwater>oh, sure i could try
01:01:09  <tjfontaine>I need to finish some of the documentation
01:01:16  <tjfontaine>but I cleaned up a bunch of the logic and deduplicated stuff
01:01:17  <groundwater>which PR?
01:01:32  <tjfontaine>6148 I think
01:02:17  <trevnorris>wtf. so StatWatcher is for fs.watchFile() and FSEventWrap is for fs.watch() then FSReqWrap is for pretty much everything else in fs.
01:02:20  <trevnorris>that's not confusing at all...
01:02:45  <tjfontaine>and mostly everyone hates our fs.watch* interface
01:02:50  * AvianFlujoined
01:02:50  <trevnorris>heh
01:03:36  <othiym23>it was pretty ambitious to think that a fs watcher would work across platforms
01:03:43  <tjfontaine>yes
01:03:44  <othiym23>given that nobody else has ever managed to pull that off
01:03:58  <tjfontaine>as a result, we have something that works basically nowhere ;)
01:04:02  <othiym23>except maybe Dropbox, and their implementation occasionally kills everybody's CPU
01:04:04  <trevnorris>which one? watching a file or watching an entire directory structure?
01:04:21  <othiym23>trevnorris: either / both
01:04:26  <tjfontaine>trevnorris: take your pick, it's actually a really difficult problem, and every os does it differently
01:04:49  <tjfontaine>it's one of those pieces that just can't find its stratification
01:04:53  * vigith_changed nick to vigith
01:04:57  <trevnorris>oy. well... i'm going to have fun explaining all those differences in the docs
01:05:29  <tjfontaine>fs watching is inconsistent acrosss all platforms, caveat emptor
01:05:31  <trevnorris>ooh. cool word.
01:05:35  * kazuponjoined
01:05:47  * c4miloquit (Remote host closed the connection)
01:05:48  <trevnorris>stratification, that's a fun one.
01:07:39  <tjfontaine>internal compiler errors, damn you ancient centos
01:07:53  <trevnorris>heh
01:07:53  <tjfontaine>I need to find time to build a gcc 4.7 toolchain for that SoB
01:08:01  <othiym23>yeah I was gonna say
01:08:19  <tjfontaine>it wouldn't be so bad if we didn't have people wanting to run on ancient glibcs
01:08:23  * Ralithquit (Ping timeout: 272 seconds)
01:08:28  <othiym23>how dependent is gcc on libc features?
01:08:42  <tjfontaine>gcc isn't per se
01:08:51  <tjfontaine>but if they're available for certain ops it'll use them
01:08:58  <othiym23>got it
01:09:08  <othiym23>kinda ironic given libc's name
01:09:12  <tjfontaine>and you'll end up with unresolved symbols on those platforms with older glibcs
01:09:16  <tjfontaine>well
01:09:28  <tjfontaine>it's this whole backward/forward compatibility thing :)
01:09:50  <othiym23>right
01:09:51  <tjfontaine>you can guarantee backwards compatibility, and some people try and do forwards, but it's not really tennable
01:09:57  <tjfontaine>libuv sometimes can get away with it
01:10:08  <othiym23>I used to know more about that, but then I burnt out on Debian and started writing more Java instead
01:10:32  <tjfontaine>basically idea is you have to build on the oldest platform you want to support
01:10:43  <tjfontaine>unless the toolchain supports the concept of targeting
01:10:55  <tjfontaine>(like osx/xcode and vs)
01:11:13  <othiym23>can you cross-compile for old versions of libc?
01:11:46  * calvinfoquit (Quit: Leaving.)
01:11:47  <tjfontaine>yes, but that's a path that may be difficult as well, you may miss a piece
01:12:09  <othiym23>yeah, cross-compiling always feels a little janky to me
01:12:12  <tjfontaine>but I could potentially grab the libc and related compiler portions from ancient centos onto new ubuntu
01:12:22  <othiym23>doing anything weird with gcc scares me
01:12:34  <othiym23>brings back bad memories of bootstrapping old, old versions on Unixware
01:12:39  <tjfontaine>llvm/clang is getting a universal driver -- things will get better
01:19:07  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
01:19:26  * indexzerojoined
01:20:56  * AWintermanjoined
01:21:11  * mikolalysenkojoined
01:24:38  <isaacs>rvagg: ok, i re-touched all the docs that were on your list
01:24:44  <tjfontaine>groundwater: hah.
01:24:48  <isaacs>rvagg: and went through and re-touched all the docs that had conflicts as well, and then deleted the conflicts.
01:25:50  <groundwater>tjfontaine should i just make notes on the PR?
01:26:06  * AWintermanquit (Ping timeout: 245 seconds)
01:26:11  * kpdeckerquit (Quit: Leaving.)
01:26:12  <tjfontaine>groundwater: seems reasonable, yes
01:26:38  <isaacs>rvagg: also, we should probably take that to #npm :)
01:26:47  <tjfontaine>what, then I'll miss all the fun
01:26:55  <tjfontaine>and then how will I know izs is alive? ;)
01:27:13  <groundwater>tjfontaine any reason why SIGTERM is used on timeout, rather than SIGKILL?
01:27:53  <tjfontaine>groundwater: historical default for `killSignal`
01:28:35  <tjfontaine>also, generally a nicer value
01:28:48  <groundwater>only problem with that, you completely lose access to your child on timeout
01:28:54  * paulfryzeljoined
01:29:00  <groundwater>SIGTERM can be caught
01:29:40  <tjfontaine>right, KILL is the mean one, it's overridable but generally you do want to give the process a chance to cleanup on its own
01:30:24  <tjfontaine>groundwater: fwiw kill(1) defaults to TERM as well
01:31:19  * dshaw_joined
01:33:10  * paulfryzelquit (Ping timeout: 250 seconds)
01:34:47  <groundwater>tjfontaine left my 2c on the PR
01:36:04  * Ralithjoined
01:36:08  * dshaw_quit (Ping timeout: 265 seconds)
01:38:21  * abraxasjoined
01:39:08  <tjfontaine>groundwater: ya
01:39:29  * abraxasquit (Read error: Connection reset by peer)
01:39:43  * abraxasjoined
01:43:33  * kpdeckerjoined
01:46:51  <trevnorris>othiym23 / tjfontaine: so the before/after/create callbacks I can understand to filter. but should I also filter calls to the error handler and let it propagate if an error occurs in a call stack that's being watched, but the provider wasn't passed?
01:47:23  * WalrusPony1joined
01:47:38  <othiym23>wasn't passed, or was '*"?
01:48:57  <trevnorris>i'm not doing string based, instead bitwise. and the provider argument is optional. if not passed that's pretty much the same as '*'.
01:49:57  <trevnorris>and sorry, by wasn't passed I mean like an FS event errors, but the user only passed TCP
01:50:03  <othiym23>the error handler is essentially an all-seeing observer of everything that gets thrown in the runtime, and it's pretty tough to provide context at all times
01:50:16  <trevnorris>but say the FS event occurred in the call chain of a TCP event
01:50:33  * WalrusPonyquit (Ping timeout: 260 seconds)
01:50:35  <othiym23>in the polyfill, for instance, I quite frequently don't have access to the listener data for a given continuation chain
01:50:50  <othiym23>I think the error handler is just different from the others for that reason
01:50:53  <trevnorris>e.g. net.createServer(fn() { fs.write*(fn() { throw Error()); })
01:50:58  * brson_quit (Quit: leaving)
01:51:02  <othiym23>you want to pass all the info you have and let the handler figure out what to do with it
01:51:12  <othiym23>not sure that the filters make sense there at all, is what I'm saying
01:51:34  <trevnorris>ok
01:52:02  <othiym23>trevnorris: that filtering stuff isn't going in 0.12, is it?
01:52:04  <othiym23>(please say no)
01:53:13  <trevnorris>hm. should I go against all that's good and do Object.prototype._async* = undefined so v8 doesn't make a bunch of copies of the object structure internally?
01:54:02  <trevnorris>othiym23: yeah it is. the api is 100% backwards compatible and totally optional. but i'm trying to wrap it up before I leave for the next 2 weeks. I just really really want this off my plate.
01:54:35  <othiym23>I really wish it weren't
01:54:37  <othiym23>that's all I'm going to say
01:56:37  <trevnorris>one thing that hammers AL's performance is because it fires so much. i don't see it a viable production debugger with how much noise is going through that channel right now.
01:57:14  <othiym23>the API is very complex for what the functionality does
01:57:34  <trevnorris>how do you mean?
01:57:47  <othiym23>were I to try to incorporate this stuff into the polyfill (and I still might, when I have time), getting it adequately tested would be very hard
01:58:23  <trevnorris>yeah. I can understand your concern.
01:59:23  * austo_joined
01:59:56  <trevnorris>but i'm not going to prevent doable features from being released because a polyfill can't be made.
02:00:15  <trevnorris>i'm going to try and include plenty of tests in core for this though.
02:01:03  * austoquit (Read error: Operation timed out)
02:01:03  * austo_changed nick to austo
02:01:27  * rosskquit
02:01:34  * janjongboomjoined
02:05:19  * trevnorris&
02:05:19  <LOUDBOT>ACHIEVEMENT UNLOCKED: URANIUM MINE
02:07:20  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
02:13:27  * TooTallNatequit (Quit: Computer has gone to sleep.)
02:15:13  * __rockbot__quit (Quit: __rockbot__)
02:29:40  * paulfryzeljoined
02:30:49  * stagasjoined
02:31:50  * abraxasquit (Remote host closed the connection)
02:32:08  * dshaw_joined
02:33:49  * paulfryzelquit (Ping timeout: 250 seconds)
02:37:02  * dshaw_quit (Ping timeout: 265 seconds)
02:38:05  * rmgquit (Remote host closed the connection)
02:48:47  * kpdeckerquit (Quit: Leaving.)
02:54:31  * c4milojoined
02:57:08  * kpdeckerjoined
02:58:56  * c4miloquit (Ping timeout: 245 seconds)
03:00:31  * kpdeckerquit (Client Quit)
03:05:53  * indexzeroquit (Quit: indexzero)
03:07:59  * stagasquit (Remote host closed the connection)
03:08:33  * stagasjoined
03:08:44  * rmgjoined
03:14:32  * indexzerojoined
03:30:15  * paulfryzeljoined
03:32:42  * dshaw_joined
03:34:29  * paulfryzelquit (Ping timeout: 250 seconds)
03:37:27  * dshaw_quit (Ping timeout: 265 seconds)
03:44:37  * Benviequit (Ping timeout: 248 seconds)
04:06:14  * kazuponquit (Remote host closed the connection)
04:08:03  * thlorenzjoined
04:08:14  * austoquit (Quit: austo)
04:08:33  * stagasquit (Read error: Connection reset by peer)
04:16:09  * thlorenzquit (Remote host closed the connection)
04:31:07  * paulfryzeljoined
04:35:35  * paulfryzelquit (Ping timeout: 250 seconds)
04:41:25  * kazuponjoined
04:43:38  * c4milojoined
04:48:11  * c4miloquit (Ping timeout: 260 seconds)
04:48:48  * kpdeckerjoined
04:57:35  * kpdeckerquit (Quit: Leaving.)
04:57:56  * kpdeckerjoined
05:00:11  * janjongboomjoined
05:05:37  * __rockbot__joined
05:05:42  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
05:15:03  * c4milojoined
05:16:26  * c4milo_joined
05:16:31  * c4miloquit (Read error: Connection reset by peer)
05:31:50  * paulfryzeljoined
05:33:50  * __rockbot__quit (Quit: __rockbot__)
05:34:17  * dshaw_joined
05:34:37  * __rockbot__joined
05:36:15  * paulfryzelquit (Ping timeout: 250 seconds)
05:38:00  * __rockbot__quit (Client Quit)
05:38:40  * mikolalysenkoquit (Quit: Lost terminal)
05:39:15  * dshaw_quit (Ping timeout: 265 seconds)
05:43:57  * __rockbot__joined
05:47:04  * c4milo_quit (Remote host closed the connection)
05:51:32  * Benviejoined
05:56:15  * c4milojoined
06:01:15  * c4miloquit (Ping timeout: 265 seconds)
06:15:10  * Benviequit (Remote host closed the connection)
06:15:29  * Benviejoined
06:20:48  * __rockbot__quit (Quit: __rockbot__)
06:32:33  * paulfryzeljoined
06:36:56  * paulfryzelquit (Ping timeout: 245 seconds)
06:46:09  * mikealjoined
06:47:05  * janjongboomjoined
06:49:34  * AvianFluquit (Remote host closed the connection)
07:12:45  * bajtosjoined
07:13:38  * m76joined
07:20:30  * kpdeckerquit (Quit: Leaving.)
07:21:15  * rendarjoined
07:32:10  <othiym23>I finally made it all the way through the latest set of TC39 meeting minutes, and there, at the very end of the last day, is the discussion of the changes to ES promises
07:32:31  <othiym23>I'm sure it wasn't meant that way, but it sure looks like an attempt to do an end-run around the monadic promises camp
07:32:39  <othiym23>no wonder everybody's so irritable about it on es-discuss
07:33:20  * paulfryzeljoined
07:33:57  * abraxasjoined
07:35:53  * dshaw_joined
07:37:35  * paulfryzelquit (Ping timeout: 250 seconds)
07:40:34  * dshaw_quit (Ping timeout: 265 seconds)
07:45:02  * c4milojoined
07:49:57  * c4miloquit (Ping timeout: 248 seconds)
08:18:24  * abrknquit (Excess Flood)
08:18:38  * abrknjoined
08:28:08  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
08:34:11  * paulfryzeljoined
08:34:34  <MI6>joyent/libuv: Austin Foxley master * 451de61 : unix, win: add uv_udp_set_multicast_interface() - http://git.io/aHHVHw
08:36:39  * dshaw_joined
08:37:19  * markmmmjoined
08:38:41  * paulfryzelquit (Ping timeout: 250 seconds)
08:39:26  * janjongboomjoined
08:39:35  <MI6>joyent/libuv: Sam Roberts master * a3c0e48 : doc: describe signal send emulation on windows - http://git.io/eawM7g
08:41:28  * dshaw_quit (Ping timeout: 265 seconds)
08:47:27  * indexzeroquit (Quit: indexzero)
08:52:12  * markmmmquit (Quit: Konversation terminated!)
08:53:33  * markmmjoined
09:05:28  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
09:25:02  * hzjoined
09:30:08  * janjongboomjoined
09:31:51  * stagasjoined
09:33:39  * karupanerurachanged nick to zz_karupanerura
09:34:55  * paulfryzeljoined
09:35:14  * abraxasquit (Remote host closed the connection)
09:39:21  * paulfryzelquit (Ping timeout: 250 seconds)
09:42:58  * abraxasjoined
10:04:17  * bajtosquit (Quit: bajtos)
10:05:38  * kpdeckerjoined
10:13:52  * sinclair|workquit (Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131205075310])
10:20:57  * abraxasquit (Remote host closed the connection)
10:35:41  * paulfryzeljoined
10:38:23  * dshaw_joined
10:40:01  * paulfryzelquit (Ping timeout: 250 seconds)
10:42:48  * dshaw_quit (Ping timeout: 265 seconds)
10:48:07  * kpdeckerquit (Read error: Connection reset by peer)
10:48:25  * kpdeckerjoined
10:51:30  * kazuponquit (Remote host closed the connection)
10:51:57  * kazuponjoined
10:56:23  * kazuponquit (Ping timeout: 260 seconds)
11:00:45  * daviddiasjoined
11:03:43  * rmgquit (Remote host closed the connection)
11:03:59  * rmgjoined
11:07:00  * mralephquit (Read error: Connection reset by peer)
11:10:05  * kpdeckerquit (Quit: Leaving.)
11:10:23  * kpdeckerjoined
11:10:59  * rmgquit (Remote host closed the connection)
11:23:53  * m76quit (Read error: Connection reset by peer)
11:36:25  * paulfryzeljoined
11:40:32  * kpdeckerquit (Quit: Leaving.)
11:40:41  * paulfryzelquit (Ping timeout: 250 seconds)
12:02:22  * stagasquit (Read error: Connection reset by peer)
12:13:04  * daviddiasquit (Read error: Connection reset by peer)
12:37:12  * paulfryzeljoined
12:40:04  * zotjoined
12:41:47  * paulfryzelquit (Ping timeout: 250 seconds)
12:45:44  <zot>just got a libuv assert failure; was using coffee (executable) in continuous watch/compile mode. there is a core file, but it appears to be corrupted. seems random, as i've been using this the last 3 days, so probably not reproducible. submit to github libuv issues?
12:45:55  * daviddiasjoined
12:47:06  <mmalecki>zot: please
12:47:29  <zot>i'll include as much of my screencap as possible, but there's not much to go on. and i'm baffled as to why the core gives me nothing :/
12:48:50  * daviddiasquit (Read error: Connection reset by peer)
12:48:55  <zot>if i get the core to load nicely, any particular things you would want me to run from lldb on it?
12:48:56  * daviddia_joined
12:50:43  <mmalecki>zot: bt, of course
12:50:50  * Kakerajoined
12:50:55  <mmalecki>and report back :)
12:50:58  <zot>yeah, that one i got :)
12:51:02  <mmalecki>zot: can you upload the core perhaps?
12:51:21  <zot>i'll have to check; i don't think anything sensitive could be in there, but permission required.
12:51:26  * daviddiasjoined
12:51:47  <zot>i'll get the bt and the rest up shortly tho
12:55:28  * daviddia_quit (Ping timeout: 252 seconds)
13:11:41  * thepumpkinquit (Ping timeout: 250 seconds)
13:16:23  * dshaw_joined
13:21:15  * dshaw_quit (Ping timeout: 272 seconds)
13:24:43  * hzquit (Ping timeout: 260 seconds)
13:33:58  * AvianFlujoined
13:37:58  * paulfryzeljoined
13:42:27  * paulfryzelquit (Ping timeout: 250 seconds)
13:53:02  * austojoined
14:00:10  * austo_joined
14:00:29  * austoquit (Quit: austo)
14:01:09  * austo_quit (Client Quit)
14:01:48  * m76joined
14:01:50  * austojoined
14:02:53  * bajtosjoined
14:14:49  * thlorenzjoined
14:20:35  * austo_joined
14:22:17  * hzjoined
14:22:43  * abraxasjoined
14:23:51  * austoquit (Ping timeout: 272 seconds)
14:25:08  * austo_quit (Ping timeout: 265 seconds)
14:27:39  * abraxasquit (Ping timeout: 272 seconds)
14:33:11  * piscisaureusjoined
14:33:27  <piscisaureus>mmalecki: hey maciej
14:33:41  <piscisaureus>mmalecki: rumor has it that you scored yourself a house with a pool
14:34:02  <piscisaureus>mmalecki: how t f did you do that?
14:34:34  <mmalecki>piscisaureus: hey!
14:34:51  <mmalecki>piscisaureus: yes I did! you're invited for a housewarming party btw! not sure if you got the message
14:35:08  <piscisaureus>mmalecki: I didn't but jan told me
14:35:17  <piscisaureus>mmalecki: is it tomorrow?
14:35:20  <mmalecki>piscisaureus: I sent you a DM yesterday I think
14:35:25  <mmalecki>piscisaureus: yeah, tomorrow 8 PM
14:35:29  <piscisaureus>ok twitter ah
14:35:32  <piscisaureus>I suck at twitter ...
14:36:27  <piscisaureus>mmalecki: actually, I didn't get it
14:36:41  <mmalecki>piscisaureus: curious... I also suck at spelling your nick...
14:37:01  <piscisaureus>mmalecki: hah! blame my nick :-p
14:37:13  <mmalecki>piscisaureus: Driekoningstraat 10 is the address btw
14:37:29  <mmalecki>I asked Ben also but he has a family over
14:37:47  <piscisaureus>mmalecki: what time do you think will the fun start?
14:38:41  <piscisaureus>mmalecki: yeah, get used to it - it's not easy to drag Ben to 020. He's a family man
14:38:45  * paulfryzeljoined
14:42:17  <mmalecki>piscisaureus: party starts around 8 PM. fun probably a bit later ;)
14:42:31  <mmalecki>piscisaureus: bring your swimming shorts if you want to swim!
14:42:46  <piscisaureus>mmalecki: no shit :)
14:42:52  <piscisaureus>mmalecki: I guess the fun starts when I arrive
14:43:07  * paulfryzelquit (Ping timeout: 250 seconds)
14:43:12  <piscisaureus>mmalecki: I'll wear my mankini
14:43:35  <mmalecki>oh god this'll give me a thaijs flashback
14:44:11  <piscisaureus>haha
14:44:38  * SquirrelCZECH_quit
14:45:20  * SquirrelCZECHjoined
14:46:07  <piscisaureus>mmalecki: I thought we agreed - what happens in เทศบาลนครภูเก็ต stays in เทศบาลนครภูเก็ต ?
14:53:40  <mmalecki>piscisaureus: I still have that video somewhere
14:54:28  <piscisaureus>mmalecki: ha! maybe you can show it tomorrow?
14:54:29  * Kakeraquit (Ping timeout: 248 seconds)
15:00:41  * hueniversequit (Ping timeout: 245 seconds)
15:02:34  * jmar777joined
15:10:15  * markmmquit (Ping timeout: 260 seconds)
15:10:24  * markmmjoined
15:15:04  * kazuponjoined
15:17:17  * dshaw_joined
15:20:37  * AvianFluquit (Remote host closed the connection)
15:21:26  * AvianFlujoined
15:21:59  * hueniversejoined
15:22:10  * dshaw_quit (Ping timeout: 265 seconds)
15:26:16  * AvianFluquit (Ping timeout: 256 seconds)
15:27:52  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:38:05  * Kakerajoined
15:38:47  * janjongboomjoined
15:39:28  * paulfryzeljoined
15:39:39  * markmmquit (Quit: Konversation terminated!)
15:40:43  * markmmjoined
15:43:47  * paulfryzelquit (Ping timeout: 250 seconds)
15:51:53  * bajtosquit (Quit: bajtos)
16:02:18  * mikealquit (Quit: Leaving.)
16:02:59  * c4milojoined
16:12:21  * WalrusPony1changed nick to WalrusPony
16:19:09  * AvianFlujoined
16:23:48  * abraxasjoined
16:28:21  * abraxasquit (Ping timeout: 248 seconds)
16:36:10  * AWinterm_joined
16:38:14  * rendarquit (Quit: reboot)
16:39:53  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
16:40:16  * paulfryzeljoined
16:44:22  * rendarjoined
16:44:27  * paulfryzelquit (Ping timeout: 250 seconds)
16:44:46  * bajtosjoined
16:50:01  * stagasjoined
16:50:20  * rmgjoined
16:50:55  * zotpart
16:53:50  * calvinfojoined
16:59:36  * kpdeckerjoined
17:03:31  * daviddiasquit (Ping timeout: 245 seconds)
17:05:48  * mikealjoined
17:06:37  * daviddiasjoined
17:07:03  * kpdeckerquit (Quit: Leaving.)
17:09:12  * mikealquit (Client Quit)
17:15:04  * AWinterm_quit (Remote host closed the connection)
17:17:52  * AWinterm_joined
17:18:52  * dshaw_joined
17:23:29  * dshaw_quit (Ping timeout: 265 seconds)
17:26:52  * __rockbot__joined
17:28:58  * __rockbot___joined
17:29:35  * stagasquit (Read error: Connection reset by peer)
17:30:53  * __rockbot__quit (Client Quit)
17:30:53  * __rockbot___changed nick to __rockbot__
17:32:18  * __rockbot___joined
17:35:36  * __rockbot___quit (Client Quit)
17:36:27  * __rockbot__quit (Quit: __rockbot__)
17:37:59  * __rockbot__joined
17:41:02  * paulfryzeljoined
17:41:56  * piscisaureusquit (Ping timeout: 245 seconds)
17:42:08  * WalrusPony1joined
17:44:15  * hzquit
17:44:15  * WalrusPonyquit (Ping timeout: 250 seconds)
17:45:33  * paulfryzelquit (Ping timeout: 250 seconds)
17:48:20  * piscisaureusjoined
17:51:00  * c4miloquit (Remote host closed the connection)
17:51:37  * sblomjoined
17:53:36  * mcavagequit (Remote host closed the connection)
17:57:14  * mcavagejoined
17:58:12  * c4milojoined
17:58:49  * mcavagequit (Remote host closed the connection)
18:01:41  * Ralithquit (Ping timeout: 248 seconds)
18:03:30  * __rockbot__quit (Quit: __rockbot__)
18:03:46  * __rockbot__joined
18:04:18  * dshaw_joined
18:05:55  * c4miloquit (Remote host closed the connection)
18:06:34  * thlorenzquit (Remote host closed the connection)
18:07:25  * __rockbot__quit (Client Quit)
18:14:19  * rosskjoined
18:17:14  * janjongboomjoined
18:17:51  * rmgquit (Ping timeout: 260 seconds)
18:19:25  * rmgjoined
18:20:51  * kpdeckerjoined
18:22:28  * kazuponquit (Remote host closed the connection)
18:22:54  * kazuponjoined
18:23:54  * Ralithjoined
18:24:40  * abraxasjoined
18:27:16  * kazuponquit (Ping timeout: 245 seconds)
18:29:13  * abraxasquit (Ping timeout: 260 seconds)
18:40:01  * mikealjoined
18:41:42  * daviddiasquit (Remote host closed the connection)
18:41:49  * paulfryzeljoined
18:42:16  * janjongboomquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:42:54  * mcavagejoined
18:43:59  * jmar777quit (Read error: Connection reset by peer)
18:44:16  * thlorenzjoined
18:44:26  * jmar777joined
18:44:51  * daviddiasjoined
18:46:13  * paulfryzelquit (Ping timeout: 250 seconds)
19:03:29  * piscisaureusquit (Quit: ~ Trillian Astra - www.trillian.im ~)
19:03:57  * kenperkins_changed nick to kenperkins
19:16:29  * kpdeckerquit (Read error: Connection reset by peer)
19:16:32  * kpdecker1joined
19:18:21  <MI6>joyent/node: Timothy J Fontaine v0.10 * e3d8359 : website: update cla email address - http://git.io/DtalaA
19:25:49  * bajtosquit (Quit: bajtos)
19:30:44  * mikealquit (Quit: Leaving.)
19:31:02  * mikealjoined
19:32:57  * hzjoined
19:33:41  * kazuponjoined
19:38:11  * kazuponquit (Ping timeout: 245 seconds)
19:38:18  * mikealquit (Quit: Leaving.)
19:39:39  * Kakeraquit (Ping timeout: 245 seconds)
19:42:33  * paulfryzeljoined
19:46:53  * paulfryzelquit (Ping timeout: 250 seconds)
19:54:24  * mikealjoined
19:55:24  * WalrusPony1changed nick to CPlusPlusPony
20:00:05  * paulfryzeljoined
20:01:51  * jmar777quit (Remote host closed the connection)
20:03:00  * paulfryzelquit (Read error: Connection reset by peer)
20:03:19  * paulfryzeljoined
20:06:16  * mikealquit (Quit: Leaving.)
20:06:20  * paulfryzelquit (Read error: Connection reset by peer)
20:06:41  * mikealjoined
20:13:22  * mikealquit (Quit: Leaving.)
20:15:56  * andrewrkjoined
20:16:50  * mikealjoined
20:18:48  * daviddiasquit (Remote host closed the connection)
20:19:10  * mikealquit (Client Quit)
20:19:31  * c4milojoined
20:20:29  <MI6>joyent/node: Austin Moran master * 4b77bd3 : headers: fix spelling error - http://git.io/ffXAqA
20:22:58  * m76quit (Read error: Connection reset by peer)
20:25:31  * abraxasjoined
20:28:20  * dsantiagoquit (Ping timeout: 265 seconds)
20:28:52  * dsantiagojoined
20:29:57  * abraxasquit (Ping timeout: 248 seconds)
20:31:36  * dsantiagoquit (Client Quit)
20:34:13  * mikealjoined
20:36:08  * AWintermanjoined
20:39:14  * AWinterm_quit (Ping timeout: 245 seconds)
20:39:21  * dshaw_quit (Read error: Connection reset by peer)
20:39:43  * dshaw_joined
20:42:43  * daviddiasjoined
20:44:23  * markmmquit (Ping timeout: 260 seconds)
20:45:44  * jmar777joined
20:46:59  * daviddiasquit (Ping timeout: 246 seconds)
20:47:36  * dshaw_quit (Read error: Connection reset by peer)
20:47:59  * dshaw_joined
20:48:18  * markmmjoined
20:50:46  * mikolalysenkojoined
20:54:35  * defunctzombie_zzchanged nick to defunctzombie
20:54:40  * markmmquit (Quit: Konversation terminated!)
20:54:59  * mikealquit (Quit: Leaving.)
20:57:18  * mikealjoined
20:58:37  * thlorenzquit (Remote host closed the connection)
20:58:51  * thlorenzjoined
21:03:38  * txdvquit (Read error: Operation timed out)
21:07:07  * paulfryzeljoined
21:08:00  * txdvjoined
21:09:11  * daviddiasjoined
21:09:54  * defunctzombiechanged nick to defunctzombie_zz
21:11:23  * paulfryzelquit (Ping timeout: 250 seconds)
21:13:52  * defunctzombie_zzchanged nick to defunctzombie
21:16:54  * defunctzombiechanged nick to defunctzombie_zz
21:18:04  * brsonjoined
21:18:45  * defunctzombie_zzchanged nick to defunctzombie
21:25:29  * AWintermanquit (Remote host closed the connection)
21:28:52  * dshaw_quit (Read error: Connection reset by peer)
21:29:11  * dshaw_joined
21:30:47  * Kakerajoined
21:31:59  <tjfontaine>groundwater: hey man
21:32:07  <groundwater>tjfontaine ahoy!
21:32:23  <tjfontaine>so your timeout and throw, I didn't get a chance to talk to you abou tit
21:33:03  <groundwater>sure
21:33:21  <tjfontaine>I'm going to put the pid in the error object, which you could then do process.kill() with
21:33:22  <groundwater>did i articulate the issue?
21:33:28  <tjfontaine>does that make sense?
21:33:42  <groundwater>ahh, didn't know process.kill() could do that
21:33:53  <tjfontaine>indeed it's (pid, signal)
21:34:11  <tjfontaine>the question is about waitpid
21:34:28  <groundwater>and, is there a way to verify if the child has exiteD?
21:34:41  <tjfontaine>halting problem?
21:34:58  <groundwater>i don't think it's that bad
21:34:59  <tjfontaine>http://linux.die.net/man/2/waitpid
21:35:05  <tjfontaine>is the real answer
21:35:14  <groundwater>i assumed libuv handled that magic :D
21:36:58  * mikealquit (Quit: Leaving.)
21:37:00  * rosskquit
21:37:04  <groundwater>does calling kill(pid) error if pid doesn't exist?
21:38:21  <tjfontaine>it should ESEARCH I thiink
21:38:37  <tjfontaine>ESRCH
21:38:38  <tjfontaine>but
21:38:45  <tjfontaine>it can be racey
21:39:42  * dshaw_quit (Read error: Connection reset by peer)
21:41:47  * rosskjoined
21:42:24  * janjongboomjoined
21:42:40  * m76joined
21:43:43  * jmar777quit (Remote host closed the connection)
21:45:44  * dshaw_joined
21:45:54  * mikolalysenkoquit (Ping timeout: 245 seconds)
21:47:02  * janjongboomquit (Client Quit)
21:50:21  * c4miloquit (Ping timeout: 272 seconds)
21:51:58  * daviddia_joined
21:52:13  <groundwater>tjfontaine does that throw?
21:52:22  <groundwater>i guess i could find that out in like 2 min
21:52:34  * dshaw_quit (Quit: Leaving.)
21:52:41  <tjfontaine>I just had more conversations, and I'm not sure what the right path is
21:52:49  <tjfontaine>damn confusing part of this
21:53:05  <tjfontaine>some agree with you, we should default to -9
21:53:22  <groundwater>yes, yes it does
21:53:55  <groundwater>i think it should be -9, but i'm okay with not being -9, as long as there isn't an "information loss"
21:54:21  * daviddiasquit (Ping timeout: 245 seconds)
21:54:45  <tjfontaine>I mean, it defaults to term, you can set it to kill, but either way we should inform you of something you could use with it
21:58:13  <groundwater>maybe it shouldn't throw on timeout
21:58:17  <groundwater>just 'throwing' that out there
21:58:34  <tjfontaine>*groan*
21:59:39  * mikolalysenkojoined
21:59:50  * c4milojoined
22:00:10  * dsantiagojoined
22:00:11  <tjfontaine>throwing seems reasonable here though
22:00:21  <groundwater>so, assuming the child catches SIGTERM, you need to wrap process.kill(..) in another try-catch
22:00:37  <groundwater>because if it did quit, it might be off the pid table by then
22:00:52  <tjfontaine>I need to look and see wha thappens here
22:00:54  <groundwater>and that try-catch would be within the catch block of the first try-catch
22:01:08  <groundwater>starting to look gross
22:01:21  <tjfontaine>pfft who cares what it looks like ;)
22:02:20  <groundwater>and that's just boilerplate, unless you don't mind the risk of having wild processes wandering your system
22:02:21  <groundwater>:)
22:02:34  <tjfontaine>ya, but that's just like, what happens man
22:02:47  <groundwater>from an ops perspective, -9 is comforting because you know what happened
22:03:35  <tjfontaine>ah cute, uv_process_t->pid is public
22:04:48  <tjfontaine>ok, as I recall it, execSync was allowed to throw, but spawnSync probably shouldn't throw
22:04:57  <tjfontaine>because execSync is just supposed to return the buffer for stdout
22:06:29  <groundwater>makes sense
22:06:47  * dsantiagoquit (Ping timeout: 246 seconds)
22:07:16  <groundwater>hmm... no then how would timeout work?
22:07:31  <groundwater>oh, yah maybe it returns the proc object regardless
22:07:56  * paulfryzeljoined
22:08:11  <tjfontaine>ya, so in spawnSync *you* are responsible for checking result.error and result.status
22:08:36  <MI6>joyent/node: Kenan Sulayman v0.10 * 56e80a3 : dns: validate arguments in resolve - http://git.io/I6C6bw
22:10:33  <groundwater>so does result have a .kill? or .pid?
22:10:46  <tjfontaine>it will have a .pid
22:11:02  <MI6>joyent/node: Kenan Sulayman v0.10 * 2ee86c6 : dns: verify argument is valid function in resolve - http://git.io/Xnf7tQ
22:11:11  <groundwater>process.kill(child.pid) still needs to be wrapped in a try-catch then
22:11:25  <tjfontaine>ya I can't fix that
22:11:40  <tjfontaine>it's also potentially racey
22:11:43  <groundwater>okay, crazy time, here me out
22:12:19  <groundwater>spawSync( CMD, [], opts, function onTimeout(child){ child.kill('SIGKILL') })
22:12:28  <groundwater>or something like that
22:12:30  * paulfryzelquit (Ping timeout: 250 seconds)
22:12:32  <tjfontaine>that's a painful interface
22:12:41  <tjfontaine>which part is actually sync here?
22:12:54  <tjfontaine>it's just not that we have any other interface that's sync that takes a cb
22:12:59  * dshaw_joined
22:13:11  <groundwater>heh
22:13:31  * daviddia_quit (Remote host closed the connection)
22:14:02  * daviddiasjoined
22:14:24  <indutny>oh gosh
22:14:28  <indutny>made a mistake
22:14:38  <tjfontaine>what kind of mistake?
22:14:39  <indutny>tjfontaine: I'd like to revert last two patches
22:14:44  <indutny>would you mind?
22:14:53  <indutny>I could do force push
22:14:53  <tjfontaine>I don't mind, but make them real reverts?
22:15:05  * hueniversequit (Ping timeout: 260 seconds)
22:15:07  * hueniverse1joined
22:15:09  <indutny>ok
22:15:10  <tjfontaine>I'm ok with it being noisey here
22:15:22  <tjfontaine>what was the mistake
22:15:26  <tjfontaine>I haven't looked at it yet
22:15:46  <MI6>joyent/node: Fedor Indutny v0.10 * d10a687 : Revert "dns: validate arguments in resolve" (+1 more commits) - http://git.io/U-Pmww
22:15:50  <indutny>nah, incorrect git am
22:15:58  <indutny>i.e. merge problems
22:16:00  <tjfontaine>ok
22:17:17  * rmgquit (Remote host closed the connection)
22:25:03  * hzquit
22:26:26  * abraxasjoined
22:30:54  * abraxasquit (Ping timeout: 245 seconds)
22:31:07  <groundwater>tjfontaine anyways, i think everyone agrees that there needs to be enough information to kill a child in pathalogical cases
22:31:23  <groundwater>whether that information is "elegant" or not, i don't care too much
22:32:57  <groundwater>using -9 lets you side-step needing to provide any information about the child
22:33:02  <groundwater>but it's not flexible
22:33:55  <groundwater>the alternative is making sure to provide the pid on timeout, either by throwing or returning
22:34:24  <tjfontaine>there are times where you don't want to use -9, I think we can acknolwedge that
22:34:57  <tjfontaine>so killSignal being configurable and returning the pid in the result object seems about the best node is going to do in this regard
22:35:07  <tjfontaine>if you want something more robust, you probably don't want synchronous spawn
22:36:01  * AWintermanjoined
22:36:18  <MI6>joyent/node: Timothy J Fontaine execSync-wip * 819fde3 : handle stdio inherit more crisply (+2 more commits) - http://git.io/koE9EA
22:36:33  <tjfontaine>groundwater: I think that addresses most of the initial complaints you had
22:37:01  <tjfontaine>I'll do the execSync part now
22:37:09  <tjfontaine>should be relatively trivial to add that
22:37:44  <groundwater>trivial
22:37:46  <groundwater>you said it
22:37:51  <tjfontaine>:)
22:38:16  <groundwater>execSync is left as an exercise for the reader
22:38:28  <tjfontaine>technically first is execFileSync
22:38:42  <tjfontaine>then execSync which just does sh -c ""
22:38:43  <tjfontaine>or whatever
22:40:37  * AWintermanquit (Ping timeout: 248 seconds)
22:41:12  <tjfontaine>hmm actually, execFileSync and spawnSync are not any different
22:42:58  * sblomquit (Read error: Connection reset by peer)
22:44:35  * sblomjoined
22:44:41  * AWinterm_joined
22:45:31  * sblomquit (Read error: Connection reset by peer)
22:45:44  * sblomjoined
22:46:48  * sblomquit (Read error: Connection reset by peer)
22:46:59  * sblomjoined
22:47:17  * sblomquit (Read error: Connection reset by peer)
22:47:27  * sblomjoined
22:51:04  * rmgjoined
22:51:16  * rendarquit
22:52:53  * hueniverse1quit (Quit: Leaving.)
22:53:04  * hueniversejoined
22:53:12  * thlorenzquit (Remote host closed the connection)
22:54:15  * dsantiagojoined
22:54:57  <groundwater>so whatever the next iteration is, i'm happy to try breaking it
22:55:15  * rmgquit (Remote host closed the connection)
22:55:30  * rmgjoined
22:55:35  <tjfontaine>I'm just about done with the execSync one
22:58:27  * Damn3d_quit (Ping timeout: 276 seconds)
23:00:25  * paulfryzeljoined
23:00:32  * stagasjoined
23:04:29  * paulfryzelquit (Ping timeout: 250 seconds)
23:04:45  * defunctzombiechanged nick to defunctzombie_zz
23:06:09  * Damn3djoined
23:07:49  * dsantiagoquit (Ping timeout: 248 seconds)
23:08:38  * c4miloquit (Remote host closed the connection)
23:08:51  * paulfryzeljoined
23:10:08  * paulfryzelquit (Read error: Connection reset by peer)
23:10:39  * paulfryzeljoined
23:14:53  * paulfryzelquit (Ping timeout: 250 seconds)
23:15:30  <MI6>joyent/node: Timothy J Fontaine execSync-wip * 87c6e1d : add execSync interface - http://git.io/Yuo0Gg
23:15:45  <tjfontaine>groundwater: ^
23:16:41  <groundwater>tjfontaine sweet, i'll have to take a look at this later though
23:16:48  <tjfontaine>no problemo
23:25:01  * wolfeidauquit (Remote host closed the connection)
23:27:39  * m76quit (Read error: Connection reset by peer)
23:37:34  * AvianFluquit (Ping timeout: 256 seconds)
23:41:24  * jmar777joined
23:42:01  * defunctzombie_zzchanged nick to defunctzombie
23:44:21  * daviddiasquit (Remote host closed the connection)
23:52:17  * sinclair|workjoined
23:57:23  * thlorenzjoined