00:00:01  * ircretaryquit (Remote host closed the connection)
00:00:06  * bzoojoined
00:00:09  * ircretaryjoined
00:00:27  * bzooquit (Remote host closed the connection)
00:01:03  * bzoojoined
00:01:38  * Slaytors_quit (Remote host closed the connection)
00:02:08  <henrikhodne>Ah, I see now, you have to give an absolute path or it is considered relative to ~.
00:05:08  * bzooquit (Ping timeout: 240 seconds)
00:06:46  * indexzeroquit (Quit: indexzero)
00:07:13  * st_lukejoined
00:15:00  * jklbquit (Remote host closed the connection)
00:15:36  * jklbjoined
00:19:51  * Slaytorsonjoined
00:20:05  * jklbquit (Ping timeout: 272 seconds)
00:22:02  * DTrejojoined
00:24:11  * st_lukequit (Remote host closed the connection)
00:24:46  * st_lukejoined
00:25:36  * st_luke_joined
00:27:35  * sberrymanjoined
00:29:02  * st_lukequit (Ping timeout: 240 seconds)
00:40:46  * tobiequit (Quit: tobie)
00:41:48  * jklbjoined
00:49:47  * st_luke_quit (Remote host closed the connection)
00:52:43  * Slaytorsonquit (Remote host closed the connection)
00:53:15  * Slaytorsonjoined
00:54:13  * jcrugzzjoined
00:54:26  * Slaytorsonquit (Read error: Connection reset by peer)
00:54:48  * Slaytorsonjoined
00:58:20  * jcrugzzquit (Ping timeout: 245 seconds)
01:11:32  * DTrejoquit (Remote host closed the connection)
01:11:58  * DTrejojoined
01:14:41  * Slaytorsonquit (Remote host closed the connection)
01:16:21  * DTrejoquit (Ping timeout: 248 seconds)
01:18:22  * Slaytors_joined
01:18:42  * defunctzombie_zzchanged nick to defunctzombie
01:19:24  * defunctzombiechanged nick to defunctzombie_zz
01:29:07  * Slaytors_quit (Remote host closed the connection)
01:29:39  * Slaytorsonjoined
01:31:27  * Slaytors_joined
01:31:37  * Slaytors_quit (Remote host closed the connection)
01:31:54  * Slaytorsonquit (Read error: Connection reset by peer)
01:43:20  * jklbquit (Remote host closed the connection)
01:43:54  * jklbjoined
01:48:23  * jklbquit (Ping timeout: 272 seconds)
01:58:07  * jklbjoined
02:17:59  * joshsmithquit (Quit: joshsmith)
02:31:53  * jklbquit (Remote host closed the connection)
02:32:29  * jklbjoined
02:34:53  * themgtquit (Ping timeout: 272 seconds)
02:36:22  * themgtjoined
02:36:40  * jklbquit (Ping timeout: 245 seconds)
02:37:08  * _yoy_quit (Ping timeout: 240 seconds)
02:38:43  * _yoy_joined
02:40:32  * jklbjoined
03:14:17  * jklbquit (Remote host closed the connection)
03:14:49  * jklbjoined
03:17:00  * jklbquit (Read error: Connection reset by peer)
03:17:29  * jklbjoined
03:19:00  * jcrugzzjoined
03:20:40  * indexzerojoined
03:24:21  * wesbosquit (Ping timeout: 248 seconds)
03:24:21  * robmozartquit (Ping timeout: 248 seconds)
03:24:49  * wesbosjoined
03:25:57  * robmozartjoined
03:27:37  * jmar777quit (Remote host closed the connection)
03:28:15  * jmar777joined
03:32:53  * jmar777quit (Ping timeout: 272 seconds)
03:34:37  * jklbquit (Remote host closed the connection)
03:35:10  * jklbjoined
03:40:13  * jklbquit (Ping timeout: 272 seconds)
03:53:06  * cronopiojoined
04:17:57  * sreeixjoined
04:28:28  * Proditorquit (Ping timeout: 240 seconds)
04:29:38  * Proditorjoined
05:12:14  * DTrejojoined
05:16:45  * DTrejoquit (Ping timeout: 272 seconds)
05:18:34  * themgtquit (Quit: themgt)
05:22:21  * sreeixquit (Quit: sreeix)
05:25:58  * topwobblejoined
05:39:55  * DTrejojoined
05:48:11  * standooquit (Ping timeout: 248 seconds)
05:48:28  * standoo1joined
05:49:33  * DTrejoquit (Remote host closed the connection)
05:55:15  * thirdknife__joined
05:58:03  * mesoquit (Read error: Connection reset by peer)
05:58:09  * meso_joined
06:04:05  * RORgasmquit (Read error: Connection reset by peer)
06:05:02  * RORgasmjoined
06:06:16  * sreeixjoined
06:13:47  * sportoquit (Quit: Computer has gone to sleep.)
06:19:17  * mdedetrichquit (Quit: Computer has gone to sleep.)
06:22:25  * mdedetrichjoined
06:43:55  * Baastrupjoined
06:45:47  * standoo1quit (Ping timeout: 248 seconds)
06:48:32  * standoojoined
06:56:11  * sreeixquit (Ping timeout: 272 seconds)
06:56:46  * sreeixjoined
07:06:30  * jonykrausejoined
07:07:59  * meso_quit (Read error: Connection reset by peer)
07:08:00  * mesojoined
07:08:38  * jonykrausequit (Remote host closed the connection)
07:11:49  * frenchto1stjoined
07:12:46  * tobiejoined
07:13:12  * Baastrupquit (Quit: Leaving.)
07:13:37  * Baastrupjoined
07:25:13  * mdedetrichquit (Quit: Computer has gone to sleep.)
07:32:59  * sportojoined
07:37:30  * LuckySMackquit (Remote host closed the connection)
07:39:24  * jbprosjoined
07:43:45  * jonykrausejoined
07:44:35  * frenchto1stquit (Ping timeout: 245 seconds)
07:45:34  * frenchto1stjoined
07:55:04  * sreeixquit (Quit: sreeix)
08:13:29  * lpinjoined
08:14:14  * hallasjoined
08:14:43  * ChrisMathesonjoined
08:26:03  * benjaminbenbenjoined
08:36:18  * mesoquit (Remote host closed the connection)
08:36:53  * mesojoined
08:40:33  * meso_joined
08:41:13  * mesoquit (Read error: Connection reset by peer)
08:43:42  * hallasquit (Quit: Textual IRC Client: www.textualapp.com)
08:46:05  * atomlessjoined
08:48:54  * sportoquit (Quit: Computer has gone to sleep.)
08:49:48  * andreypoppjoined
08:52:28  * lpinquit (Quit: Textual IRC Client: www.textualapp.com)
08:53:07  * lpinjoined
08:58:03  * Nodejitsu-Githubjoined
08:58:03  <Nodejitsu-Github>[node-http-proxy] cronopio pushed 4 new commits to caronte: http://git.io/ijUomQ
08:58:03  <Nodejitsu-Github>node-http-proxy/caronte 1d1ee88 cronopio: [tests] the options got a problem and this test probe that timeout is not being set
08:58:03  <Nodejitsu-Github>node-http-proxy/caronte 90fb01d cronopio: [fix] fixed options and server reference to can access them from passes functions
08:58:03  <Nodejitsu-Github>node-http-proxy/caronte 9b3e1eb cronopio: [fix] fixed passes functions, now 'this' can be used and options are stored on 'this.options'
08:58:03  * Nodejitsu-Githubpart
08:59:26  * travis-cijoined
08:59:26  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#279 (caronte - 52ecd52 : cronopio): The build passed.
08:59:26  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/e4450132e2c1...52ecd52ee5aa
08:59:26  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/12816136
08:59:26  * travis-cipart
09:01:15  * mesojoined
09:05:23  * meso_quit (Ping timeout: 272 seconds)
09:09:06  * thirdknife__quit (Ping timeout: 256 seconds)
09:10:02  * salmaksimjoined
09:15:10  * topwobblequit (Quit: topwobble)
09:22:17  * jon_starcountjoined
09:22:22  * thirdknife__joined
09:25:05  * johnny_starcountjoined
09:26:08  <johnny_starcount>Hey. I'm trying to deploy but failing. Deploy worked fine, but app is stopped (it said it started). I've tried jitsu apps start, again successful, site is still stopped.
09:26:23  <johnny_starcount>starcount/worker-production
09:26:26  * sreeixjoined
09:26:49  <johnny_starcount>Can't start it now, either from cli or from webops. Logs say it started ok.
09:33:54  <johnny_starcount>It's up now.
09:38:11  * johnny_starcountquit (Ping timeout: 250 seconds)
09:39:42  * thirdknife__quit (Ping timeout: 256 seconds)
09:43:38  * thanpolasjoined
09:51:47  * thirdknife__joined
09:52:59  * chrisdotcodequit (Ping timeout: 248 seconds)
09:54:30  * cronopioquit (Quit: leaving)
09:56:41  * thirdknife__quit (Ping timeout: 272 seconds)
10:01:34  * tonistjoined
10:02:48  * jbprosquit (Quit: jbpros)
10:09:15  * thirdknife__joined
10:18:18  * hallasjoined
10:18:20  * thanpola_joined
10:20:59  * thanpolasquit (Ping timeout: 265 seconds)
10:21:24  * themgtjoined
10:21:29  * themgtquit (Remote host closed the connection)
10:26:18  * ChrisMathesonquit
10:51:31  * ChrisMathesonjoined
10:54:31  * trygvejoined
10:55:00  * tonistquit (Quit: tonist)
11:10:22  * Hounddogjoined
11:14:04  * davidmackjoined
11:14:16  * Nodejitsu-Githubjoined
11:14:16  <Nodejitsu-Github>[node-http-proxy] Swaagie pushed 1 new commit to caronte: http://git.io/nRqiTQ
11:14:16  <Nodejitsu-Github>node-http-proxy/caronte f23bbba Swaagie: [fix] remove odd utf-8 char, whitespace cleared automatically
11:14:16  * Nodejitsu-Githubpart
11:14:28  * frenchto1stquit (Ping timeout: 240 seconds)
11:15:48  * aj_joined
11:15:56  * travis-cijoined
11:15:57  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#280 (caronte - f23bbba : Swaagie): The build passed.
11:15:57  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/52ecd52ee5aa...f23bbbaf0ddd
11:15:57  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/12820856
11:15:57  * travis-cipart
11:16:39  * thanpola_changed nick to thanpolas
11:17:50  <thanpolas>sooooo, when will you be at capacity again?
11:19:44  * thirdknife__quit (Quit: Leaving)
11:23:29  * aj_quit (Quit: Page closed)
11:26:57  * davidmackquit (Ping timeout: 250 seconds)
11:39:14  * lpinquit (Quit: Textual IRC Client: www.textualapp.com)
11:40:24  * mdedetrichjoined
11:41:40  * thirdknifejoined
11:42:20  * thirdknifequit (Max SendQ exceeded)
11:42:45  * thirdknifejoined
11:46:12  * thirdknifequit (Client Quit)
11:46:44  * frenchto1stjoined
11:51:01  * frenchto1stquit (Ping timeout: 248 seconds)
11:52:12  * _yoy_quit (Quit: Leaving...)
11:53:50  * rcombsquit (Ping timeout: 240 seconds)
11:54:51  * _yoy_joined
11:57:23  * tonistjoined
11:57:48  * sreeixquit (Quit: sreeix)
12:09:17  * rcombsjoined
12:09:37  * thirdknifejoined
12:16:31  <indexzero>thanpolas: https://twitter.com/nodejitsu/status/392241636190609408
12:16:57  <thanpolas>thanks indexzero
12:18:38  * jklbjoined
12:19:37  * thealanwattsriotjoined
12:19:41  * thealanwattsriotquit (Max SendQ exceeded)
12:20:17  * thealanwattsriotjoined
12:21:49  * thomas84joined
12:24:17  * dorphjoined
12:24:53  <dorph>Was there a notice about the maintenance?
12:25:33  * themgtjoined
12:26:53  * duckboxjoined
12:29:23  <thomas84>Any predictions to complete the maintenance?
12:31:01  * basvankuijckjoined
12:32:09  * kaspertidemannjoined
12:33:01  * basvankuijckquit (Client Quit)
12:37:24  * andreypoppquit (Quit: andreypopp)
12:38:23  * blahjoined
12:38:36  <blah>what's going on with node jitsu
12:38:37  <blah>?
12:40:19  <blah>hey, anybody here?
12:40:32  <dorph>No admins anyway..
12:40:48  <thanpolas>folks >> indexzero: thanpolas: https://twitter.com/nodejitsu/status/392241636190609408
12:41:13  <dorph>ahh okay thank you
12:41:28  <indexzero>blah dorph ^^ we are ~60% done with the maintenance
12:41:45  <dorph>hah :b awesome !
12:47:47  * oliland_changed nick to oliland
12:48:10  <Tox>this must be this new dos issue of node...
12:48:48  * wylie1joined
12:48:54  * eferniejoined
12:49:21  <wylie1>The Nodejitsu cloud is currently at capacity. (trying to confirm a new user)
12:49:25  * mdedetrichquit (Quit: Computer has gone to sleep.)
12:49:54  <jklb>wylie1: https://twitter.com/nodejitsu/status/392241636190609408
12:50:19  <wylie1>ah ha. well okay then.
12:50:27  <wylie1>thanx!
12:50:32  * wylie1quit (Client Quit)
12:51:54  <jklb>wylie1 np
12:52:17  * benjaminbenbenquit (Quit: benjaminbenben)
12:59:22  * thomas84quit (Quit: thomas84)
13:04:01  * blahquit (Ping timeout: 250 seconds)
13:04:14  * dorphquit (Quit: dorph)
13:08:25  * thomas84joined
13:09:00  * kaspertidemannquit (Quit: Free soup for everybody!)
13:09:26  * kaspertidemannjoined
13:10:02  * RubenGuerrerojoined
13:10:14  <RubenGuerrero>Hi
13:11:17  * RubenGuerreroquit (Client Quit)
13:12:24  * npmbrojoined
13:13:14  * sreeixjoined
13:14:06  * indexzeroquit (Quit: indexzero)
13:14:49  * standooquit (Quit: standoo)
13:15:22  * jmar777joined
13:19:47  * jbprosjoined
13:19:51  * frenchto1stjoined
13:26:15  * sreeixquit (Quit: sreeix)
13:28:16  * benjaminbenbenjoined
13:30:47  * sreeixjoined
13:30:52  * ggoodmanjoined
13:37:32  * devdazedjoined
13:41:55  * efernie_joined
13:43:23  <efernie_>hello, anyone available to help?
13:45:11  * eferniequit (Ping timeout: 250 seconds)
13:45:11  * efernie_changed nick to efernie
13:51:14  <ggoodman>argh, this maintenance broke one of my servers
13:55:49  * Slaytorsonjoined
14:03:09  * npmbroquit (Remote host closed the connection)
14:03:21  * npmbrojoined
14:03:58  * ChrisMathesonquit
14:13:11  <efernie>anyone?
14:13:49  * jcrugzzquit (Ping timeout: 272 seconds)
14:17:21  * ChrisMathesonjoined
14:21:02  * Baastrup1joined
14:23:14  * Baastrupquit (Read error: Connection reset by peer)
14:23:55  <duckbox>Everything is working for me
14:24:03  * jbprosquit (Quit: jbpros)
14:24:06  * atomlessquit (Quit: My iMac has gone to sleep. ZZZzzz…)
14:25:15  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
14:27:03  * thealanwattsriotjoined
14:27:06  * thealanwattsriotquit (Max SendQ exceeded)
14:27:45  * thealanwattsriotjoined
14:40:51  <jklb>anybody know anything about 'solenoid exited with code 1'?
14:48:52  * spacenickjoined
14:54:27  * sreeixquit (Quit: sreeix)
14:59:07  * kenperkinsjoined
15:00:24  * spacenickquit (Remote host closed the connection)
15:00:34  * joshsmithjoined
15:00:58  * spacenickjoined
15:01:17  * spacenickquit (Read error: Connection reset by peer)
15:01:32  * spacenickjoined
15:06:38  <thomas84>Hi! Timezone on my drone. jitsu env set TZ America/Los_Angeles. Is this enough? I've done it but did not reflect the change.
15:07:23  <thomas84>Does anyone here know how to change the timezone on my drone?
15:10:29  * rosskjoined
15:12:24  <Slaytorson>http://npmjs.org isn't responding. Just me here?
15:12:33  <Slaytorson>It's hosted at nodejitsu right?
15:12:38  * sreeixjoined
15:12:59  * tonistquit (Quit: tonist)
15:16:11  * espiralquit (Ping timeout: 248 seconds)
15:16:15  * ohamaquit (Ping timeout: 272 seconds)
15:16:16  * xymoxquit (Ping timeout: 245 seconds)
15:19:25  * duckboxquit (Quit: duckbox)
15:23:54  * Hounddogquit (Remote host closed the connection)
15:26:56  * InconceivableBjoined
15:27:44  * hallasquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:29:23  * bzoojoined
15:29:43  <Sly>Slaytorson: the website is not hosted with us. It's nginx.
15:31:27  <Sly>jklb: solenoid code 1 means that solenoid exited with an error.
15:31:48  <Sly>thomas84: what are you trying to accomplish with the TZ variable?
15:32:07  <jklb>Sly: is that usually due to user error?
15:32:31  <Sly>jklb: it can be. Package too large or something along those lines.
15:32:44  <Sly>Whether that's the case with solenoid exiting on you, idk.
15:33:08  <jklb>Sly: https://gist.github.com/jakeleboeuf/a852116a5dd659e249f4
15:33:24  * duckboxjoined
15:33:26  <jklb>Sly: Wouldn't be surprised :)
15:33:42  <Sly>jklb: is that still happening right now?
15:34:25  <jklb>Running deploy again...
15:34:30  <Sly>Whoa, whoa.
15:34:34  <Sly>I was going to try to fix that server.
15:34:39  <jklb>oh, haha
15:34:39  <jklb>sorry
15:34:56  <Sly>Well, you'll probably run into again.
15:34:56  <thomas84>Sly: I would like the Date objects respect the following timezone: America /Sao_Paulo. My application is working with the incorrect time.
15:35:11  * TooTallNatejoined
15:35:23  <Sly>thomas84: you can always set the timezone in the Date object itself.
15:35:51  <Sly>thomas84: I know we used to support the TZ variable, but I'm not sure that we do anymore since the drones handle logging and such.
15:37:25  * ggoodmanquit (Ping timeout: 250 seconds)
15:37:45  * sreeixquit (Quit: sreeix)
15:37:49  * wesbosquit (Changing host)
15:37:49  * wesbosjoined
15:37:53  <thomas84>Sly: I can not change the timezone of the drone? I really have to change the application? Does not exist something to default timezone?
15:38:05  <thomas84>as*
15:39:04  <Sly>thomas84: since the new infrastructure change, I'm not sure that we support TZ anymore because now the drone handles logging in a completely different way than it used to.
15:39:27  <Sly>thomas84: however, did you try running a `jitsu start` after setting TZ to see if that would help?
15:40:03  <jklb>Sly: yep, still getting that error
15:40:19  <Sly>jklb: one second. Don't deploy again please.
15:40:34  <jklb>Sly: k
15:40:44  <thomas84>Sly: jitsu app start? yes… restart, stop start…
15:41:09  * sreeixjoined
15:41:43  <Sly>thomas84: hm... not sure. That should have definitely set the TZ environment variable.
15:43:02  <thomas84>yea
15:43:26  * tonistjoined
15:45:14  <thomas84>Sly: It was supposed to be a simple thing to do, right? Change the default timezone on drone.
15:45:22  <Sly>thomas84: I just texted one of our devops. Hopefully he will be online soon.
15:45:29  <Sly>thomas84: yeah. TZ should set it. I'm not sure why it's not.
15:45:30  * ChrisMathesonquit
15:46:21  * standoojoined
15:47:08  <Sly>jklb: also not sure what's happening with yours. O_o
15:48:07  * tonistquit (Client Quit)
15:48:14  <jklb>Sly :) I just started using express-cdn, which some people said was having Image optimization issues on nodejitsu
15:48:49  <Sly>I mean, it looks like your app is started...
15:48:52  <jklb>But I forked that repo and removed the image opti stuff and pulled from that repo on the last deploy. No boats.
15:49:17  <Sly>I'm seeing socket.io logs going through `jitsu logs tail`, so it's definitely started.
15:49:37  <Sly>Please send a ticket into [email protected] for me so I can let you know what I find out if you leave.
15:49:58  <Sly>Also, mention your username and app name in the ticket so I don't forget.
15:49:59  <jklb>I can see it is running at beta.unitedpursuit.com, but I don' think that is the most recent deploy, is it?
15:50:12  <jklb>Sly: k
15:50:17  <Sly>jklb: as far as I can see, it is the latest deploy.
15:50:27  <jklb>oh, straange
15:50:37  <Sly>Right. So, not sure what's going on with that log error.
15:51:01  <jklb>Sly: this is what you get when you have a designer to do smart people things.
15:51:15  <Sly>rofl
15:51:24  <Sly>Not so sure it's something to do with your app specifically.
15:51:50  <jklb>Sly: good to know :) I'll get that ticket sent over. Thanks for your help as always.
15:52:07  <Sly>No problem. I'll let you know as soon as I find something out. :)
15:52:13  * themgtquit (Quit: themgt)
15:52:25  <jklb>You just want that gist in an email to [email protected]?
15:52:31  <Sly>Please. :D
15:52:58  <jklb>Sly: deal
15:53:17  <Slaytorson>Sly, I thought I read a few weeks back that nodejitsu had taken over hosting the public repos.
15:53:37  <Sly>Slaytorson: we did take over the registry hosting. Not the website hosting, though.
15:54:06  * sreeixquit (Quit: sreeix)
15:54:26  * joshsmithquit (Quit: joshsmith)
15:58:48  * _yoy_quit (Ping timeout: 240 seconds)
16:01:03  <Sly>jklb: looks like we did have a maintenance window last night that I wasn't aware of. So that could have been what caused this to happen today.
16:01:09  <Sly>Still waiting to find out for sure what's going on.
16:01:24  * jonykrausequit (Remote host closed the connection)
16:01:32  <jklb>Sly: K, thanks
16:01:54  * _yoy_joined
16:01:56  * jonykrausejoined
16:02:35  <Sly>Er, actually this morning. lol.
16:03:02  <Slaytorson>Sly: Ahh that's right
16:03:04  <Slaytorson>thanks
16:03:17  <Sly>Slaytorson: no problem. :)
16:06:44  * jonykrausequit (Ping timeout: 256 seconds)
16:07:18  * kaspertidemannquit (Quit: Free soup for everybody!)
16:08:54  * hallasjoined
16:11:27  * jbasdfjoined
16:14:56  * indexzerojoined
16:19:52  * sreeixjoined
16:26:28  * tonistjoined
16:28:19  * ohamajoined
16:28:23  * julianduquejoined
16:29:35  * xymoxjoined
16:32:52  * jbprosjoined
16:36:31  * edmackjoined
16:36:52  * jbprosquit (Client Quit)
16:37:15  <edmack>Hi, has Nodejitsu been failing (Error 500 / Capacity full) on demo plans for everyone else?
16:37:46  <thomas84>Sly: Thank you! I am eagerly awaiting.
16:43:43  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
16:45:47  * jmar777quit (Remote host closed the connection)
16:46:27  <Sly>edmack: I haven't heard of it happening.
16:46:29  * frenchto1stquit (Ping timeout: 248 seconds)
16:46:33  <Sly>I've actually never heard of that error.
16:50:18  <Sly>edmack: have you tried again in the last little bit? We were in maintenance mode earlier, so it could have been that.
16:51:50  * booyaa|fooquit (Ping timeout: 240 seconds)
16:59:01  * booyaa|foojoined
16:59:29  * jonykrausejoined
17:04:06  * sreeixquit (Quit: sreeix)
17:04:31  * jon_starcountquit (Ping timeout: 250 seconds)
17:11:05  * andreypoppjoined
17:16:13  * edmackquit (Ping timeout: 250 seconds)
17:16:18  * DTrejojoined
17:16:25  * DTrejoquit (Read error: Connection reset by peer)
17:17:03  * Baastrup1quit (Quit: Leaving.)
17:25:23  * benjaminbenbenquit (Quit: benjaminbenben)
17:27:35  * benjaminbenbenjoined
17:31:16  * sreeixjoined
17:32:23  * duckboxquit (Quit: duckbox)
17:37:31  * jdp23joined
17:38:44  * st_lukejoined
17:38:51  <jdp23>good morning all ... i'm having some weird behavior with environment variables. jitsu env tells me that NODE_ENV is set the way I want it to be, but it's not getting picked up by my app
17:39:29  <jdp23>this appears to be new behavior since Friday
17:40:18  <Sly>jdp23: we're actually looking into this problem and hope to have a solution soon.
17:40:23  <Sly>Apologies for any inconvenience.
17:40:44  <jdp23>ok thanks!
17:43:16  <jdp23>it would be great to update status.nodejitsu.com with this info
17:43:28  * benjaminbenben_joined
17:43:31  <Sly>jdp23: will do.
17:44:41  <Sly>jdp23: updatd.
17:44:43  <Sly>*updated
17:46:34  * defunctzombie_zzchanged nick to defunctzombie
17:47:20  * st_lukequit (Read error: Connection reset by peer)
17:48:12  * kaspertidemannjoined
17:52:32  <jdp23>thanks
17:56:21  * spacenickquit (Remote host closed the connection)
17:56:51  * chrisdotcodejoined
17:56:56  * spacenickjoined
17:58:10  * Baastrupjoined
17:59:14  * atomlessjoined
18:01:02  * spacenickquit (Ping timeout: 240 seconds)
18:01:15  * spacenickjoined
18:05:46  * DTrejojoined
18:05:48  * _discoveryjoined
18:05:51  * DTrejoquit (Remote host closed the connection)
18:06:26  * DTrejojoined
18:06:37  <_discovery>is there some where best to report bugs/suggestions for webops?
18:07:13  <Sly>_discovery: [email protected] is the best place, so that we have a way to get up with you when you're not on IRC.
18:07:42  <Sly>_discovery: if you want to explain the issue, swaagie may be able to help.
18:08:00  <_discovery>thanks Sly, it's mainly simple things, multi select on the snapshots (removing old snapshots is tedious as heck right now)
18:08:21  <swaagie>_discovery: gotcha goog suggestion
18:08:22  <Sly>_discovery: ah. Okay. There's no way to delete a range right now, but that has been suggested for jitsu.
18:08:25  <_discovery>and secondly I broke the list of snapshots by middle clicking the delete button with one selected (i.e new tab)
18:08:35  <_discovery>it removes the snapshot but
18:08:38  <Sly>Once that's in the master API, it should be a lot easier to implement it on webops.
18:08:40  <_discovery>the list on the original page never updates
18:08:48  <_discovery>and subsequent removes say rackspace error 404
18:09:01  <_discovery>so it DID remove it, it's still just listed in the snapshot list on the webops page
18:09:13  <swaagie>also if you reload that old page
18:09:22  <_discovery>yep, hard reset, log in and out, restart app etc
18:09:39  <_discovery>tried various combinations, still showing 3 i deleted with middle click (trying to solve above issue one, hehe)
18:10:20  <swaagie>_discovery: they are still in the cache of webops probably, as soon as we would restart it they would be gone, I assume if you jitsu snapshots list on the CLI they are gone?
18:10:33  <_discovery>will check quick
18:10:46  <swaagie>anyways that is something that is being worked (cache in general) for the next iteration of webops
18:11:01  * Baastrupquit (Quit: Leaving.)
18:11:06  <_discovery>they still show on CLI swaagie
18:11:26  <_discovery>but i will try remove em from the command line, and see
18:11:50  <_discovery>hmm oh, no real option for that it seems
18:13:15  * st_lukejoined
18:13:43  * ChrisMathesonjoined
18:14:49  <_discovery>Is there a concept like gitignore for a deploy, I sometimes accidentally forget an /uploads/tmp folder full of images and it bloats things up.
18:15:30  * asdjoined
18:15:55  * st_lukequit (Remote host closed the connection)
18:15:59  <swaagie>_discovery: .npmignore sec getting useful link
18:16:18  <_discovery>i've used that before, didn't think of it though for some reason, thanks
18:16:32  * st_lukejoined
18:16:39  <_discovery>"If there's no .npmignore file, but there is a .gitignore file, then npm will ignore the stuff matched by the .gitignore file."
18:17:25  <swaagie>_discovery: see https://www.nodejitsu.com/documentation/faq/#why-is-the-subdirectory-or-its-content-not-deployed-to-nodejitsu
18:17:48  <swaagie>and/or https://www.nodejitsu.com/documentation/faq/#how-do-i-specify-which-files-not-to-bundle-how-do-i-know-what-files-are-getting-bundled
18:18:17  <_discovery>cool, yea thanks, I wanted to be certain, the npm pack is a good idea
18:19:47  <_discovery>lastly, is there any reason why only certain users would be seeing 502 socket hang ups on the app but not others?
18:20:38  * st_lukequit (Ping timeout: 240 seconds)
18:20:51  <swaagie>have you checked your logs for any specific errors? like users hitting a specific path
18:21:00  <_discovery>yep, logs are clean
18:21:32  <_discovery>a bit earlier on there was some ENOMEM errors when deploying, and then some mad long tail errors repeated a whole bunch ( on deploy )
18:21:42  <_discovery>which...i just got again so I can paste!
18:22:17  <swaagie>please do :)
18:22:21  * chjjquit (Ping timeout: 272 seconds)
18:22:48  <_discovery>can you see this gist swaagie? https://gist.github.com/underscorediscovery/758e7a11948d931ca868
18:23:50  * chjjjoined
18:24:12  <_discovery>hmm, i tried to deploy right after and got
18:24:18  <_discovery>error: Error: No servers available
18:24:30  <Sly>_discovery: are you on an individual plan?
18:24:46  <_discovery>I am on a dev sandbox evaluating if nodejitsu will work for me
18:24:54  <_discovery>So whatever that entails
18:25:19  <_discovery>so far it's been hella good. Faster on live than localhost, even at times. But since last night having some peculiar things like this
18:25:51  <_discovery>502 via the custom domain but not via the subdomain (jit.su link), stuff like the tail log errors, stuff like ENOMEM errors
18:26:02  <Sly>_discovery: alright. One minute. Looking at servers.
18:26:04  <_discovery>that's why I was trying to remove older snapshots in the first place
18:26:22  <_discovery>As i figured I want to keep my footprint down as much as I can before bumping any limits on the dev sandbox by accident :)
18:27:24  * jonykrau_joined
18:27:40  <Sly>_discovery: try again for me.
18:27:45  * stevemanueljoined
18:27:48  <_discovery>trying
18:27:59  * benjaminbenbenquit (Quit: benjaminbenben)
18:27:59  * benjaminbenben_changed nick to benjaminbenben
18:28:10  <stevemanuel>(sorry if repeat, disconnected) I can't deploy an update: https://gist.github.com/stevemanuel/adf20b97b9d37607caa9
18:29:00  * ChrisMathesonquit
18:29:07  <_discovery>deploy succeeded Sly, will test the 502 thing as well
18:29:25  <Sly>stevemanuel: this is a known issue. Your application is most likely started.
18:29:39  <Sly>Apologies for the inconvenience. We're working on a fix. :)
18:29:44  <_discovery>actually if you get the tail error it archives that deploy
18:29:50  <_discovery>but you can manually activate it
18:29:52  * cronopiojoined
18:30:04  <Sly>_discovery: ah, thanks for that.
18:30:24  <stevemanuel>@Sly it's started, but not on the version Ive deployed.. would definitely be seeing the update on my side if it was active
18:30:51  * jonykrausequit (Ping timeout: 248 seconds)
18:31:18  <Sly>stevemanuel: try `jitsu snapshots activate` and make sure that your latest snapshot is activated. _discovery pointed out something that I wasn't thinking of. If it's declared a failure, it won't activate the snapshot and will revert back to the previous working snapshot.
18:31:19  <_discovery>stevemanuel: it should be in the webops list of snapshots though, it just doesn't auto switch because of return 1 from deploy
18:31:33  <_discovery>yea that ^^
18:31:51  * themgtjoined
18:32:00  * ChrisMathesonjoined
18:32:46  * indexzeroquit (Quit: indexzero)
18:33:12  <stevemanuel>_discovery @Sly ya I'm seeing my active snapshot (v 2.3) and an archived v 2.4 which I want active.. I've tried to activate within the webops web gui as well - all errors
18:33:57  <Sly>stevemanuel: hm. I apologize for this inconvenience. :\
18:34:10  <Sly>We had a maintenance window this morning, and I'm not sure what all took place during the maintenance as I wasn't around.
18:34:46  <stevemanuel>its ok, at least we're still running :) not a critical update, appreciate your attention on it though
18:34:47  * chjjquit (Quit: leaving)
18:35:00  <_discovery>hmm, still getting timeouts from specific users but only via custom url it seems
18:35:36  * ChrisMathesonquit (Client Quit)
18:36:02  <stevemanuel>@Sly _discovery ok, we're up!
18:36:12  <_discovery>neat
18:36:16  <Sly>stevemanuel: awesome. Sorry about that. We hope to have it solved *very* soon.
18:36:28  <stevemanuel>no worries. thank you!
18:36:48  * themgt_joined
18:36:53  <Sly>_discovery: rolling out a restart on the balancers. Going to have you try again in just a minute.
18:37:00  <_discovery>sure Sly
18:38:17  * spacenickquit (Remote host closed the connection)
18:38:20  <Sly>_discovery: try again for me?
18:38:53  * spacenickjoined
18:39:10  <_discovery>waiting for tester, i should add that it works perfectly for me (and a couple of testers that previously used the page..)
18:39:24  * themgtquit (Ping timeout: 252 seconds)
18:39:24  * themgt_changed nick to themgt
18:39:24  * benjaminbenben_joined
18:39:26  <Sly>Yeah. May have been the balancer he was getting.
18:39:31  <Sly>Our balancers do have sticky sessions.
18:39:53  <_discovery>so a first time user might just get a weird balancer ?
18:41:02  * indexzerojoined
18:42:03  <Sly>_discovery: it looked like one of the balancers was being a little slow with its response time, so I ran a restart across all of them to make sure they're all in the same state.
18:42:58  * spacenic_joined
18:43:06  * spacenickquit (Read error: Connection reset by peer)
18:44:19  * jcrugzzjoined
18:45:37  <_discovery>still no luck Sly
18:45:57  <Sly>_discovery: hm... what domain are you having trouble with?
18:46:22  <_discovery>pm'ed
18:46:31  <_discovery>as i want to keep it out of logs for now
18:46:41  <Sly>Cool.
18:47:58  * st_lukejoined
18:48:47  * Chris____joined
18:49:37  * julianduquequit (Quit: leaving)
18:50:16  <Chris____>I'm interested in hosting my node app with jitsu. Can someone tell me whether there is support for full-text indexing and search by nodejitsu or 3rd party addons? Thanks.
18:53:18  <Chris____>Anyone home??
18:53:22  <swaagie>Chris____: hey there
18:53:44  <Chris____>I'm interested in hosting my node app with jitsu. Can someone tell me whether there is support for full-text indexing and search by nodejitsu or 3rd party addons? Thanks.
18:53:52  <swaagie>we don't support the service natively but there are some good API's out there, like solr services or you could use lunr.js
18:54:01  <swaagie>http://lunrjs.com/
18:54:30  <swaagie>https://opensolr.com/ not sure how they perform though
18:54:30  <Chris____>OK. I will check out lunr.js and other solr/lucene hosts.
18:54:50  * RORgasmquit (Read error: Connection reset by peer)
18:54:59  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
18:55:23  <Chris____>If you have a lot of docs, then lunr.js is not a good fit.
18:55:26  * RORgasmjoined
18:56:34  * andreypoppquit (Quit: andreypopp)
18:57:29  <swaagie>agree
18:57:39  <swaagie>it seems opensolr has a rest APi though
18:57:47  <swaagie>but then again I don't know your exact requirements
18:58:05  * spacenic_quit (Remote host closed the connection)
18:58:57  * npmbroquit (Remote host closed the connection)
18:59:12  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:59:38  * npmbrojoined
19:00:19  * stevemanueljoined
19:01:17  <Chris____>OK. In chat with opensolr. Will find out shortly what they support. Thanks for pointing me in some direction.
19:05:14  * jdp23quit (Quit: Page closed)
19:05:47  * cronopioquit (Quit: Bye)
19:06:22  * cronopiojoined
19:07:35  * asdquit (Ping timeout: 250 seconds)
19:11:01  * Hebojoined
19:13:33  * TooTallNatejoined
19:16:04  * Baastrupjoined
19:16:34  <_discovery>Sly: they don't even hit the app itself (not a single console.log comes through from those two testers :<)
19:17:27  <Sly>_discovery: that's.... weird.
19:17:35  <Sly>I really don't have any clue what could be happening. o_o
19:17:38  <Sly>It works absolutely fine for me.
19:17:46  <_discovery>yea, trying to get a concrete reason like a code
19:17:52  <Sly>Ask them to try this...
19:18:19  <Sly>for ip in $(dig nodejitsu.com a +short); do echo "Testing balancer: $ip"; curl -I $ip -H "Host: yourdomain.com"; done
19:18:30  <Sly>And then paste that output to a gist so I can see the results
19:18:38  <Sly>Just change yourdomain.com to your domain. :D
19:18:45  <Sly>That'll test all the balancers.
19:25:59  * benjaminbenben_quit (Quit: benjaminbenben_)
19:28:43  * DTrejoquit (Remote host closed the connection)
19:29:17  * DTrejojoined
19:29:23  <_discovery>Sly: there was some miscommunication from his end, tester1 could see the site (but my site prints "this site is unavailable" and he thought I meant that...so I changed that message but AFTER he logs in (and the oauth provider redirects him) it stops responding, and for his browser from that point on the site refuses to load haha, really trippy
19:29:38  <_discovery>and tester2 it doesn't even load at all
19:29:54  * jonykrausejoined
19:29:54  * st_lukequit (Read error: Connection reset by peer)
19:33:00  * jonykrau_quit (Ping timeout: 256 seconds)
19:33:34  * DTrejoquit (Ping timeout: 256 seconds)
19:33:58  * topwobblejoined
19:36:29  * julianduquejoined
19:41:24  * Baastrupquit (Quit: Leaving.)
19:45:02  * jbasdfquit (Quit: jbasdf)
19:48:10  * mark___joined
19:48:57  <mark___>Hey, can anyone give me a hand with some npm/nodejitsu packaging?
19:49:45  * natebjoined
19:50:04  * InconceivableBquit (Read error: Connection reset by peer)
19:50:20  * DTrejojoined
19:50:26  <nateb>Hello. I'm having some trouble with continuous deployment from github.
19:50:32  * DTrejoquit (Remote host closed the connection)
19:50:52  * Nodejitsu-Githubjoined
19:50:52  <Nodejitsu-Github>[node-http-proxy] cronopio force-pushed caronte from f23bbba to 5d66ce1: http://git.io/8XMXAw
19:50:52  <Nodejitsu-Github>node-http-proxy/caronte 2bf20d6 cronopio: Revert "[tests] fix test to use the new way to pass options"...
19:50:52  <Nodejitsu-Github>node-http-proxy/caronte babdf53 cronopio: Revert "[fix] fixed options and server reference to can access them from passes functions"...
19:50:52  <Nodejitsu-Github>node-http-proxy/caronte 5e130de cronopio: Revert "[fix] fixed passes functions, now 'this' can be used and options are stored on 'this.options'"...
19:50:52  * Nodejitsu-Githubpart
19:51:05  * DTrejojoined
19:53:09  * jbasdfjoined
19:53:31  * mark___quit (Quit: Page closed)
19:54:32  * julianduquequit (Ping timeout: 246 seconds)
19:55:50  * eirikbpart ("WeeChat 0.4.2")
19:57:14  * travis-cijoined
19:57:14  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#282 (caronte - 5d66ce1 : cronopio): The build passed.
19:57:14  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/f23bbbaf0ddd...5d66ce11bb7e
19:57:14  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/12844638
19:57:14  * travis-cipart
19:57:21  * indexzeroquit (Quit: indexzero)
20:00:55  * cronopioquit (Ping timeout: 260 seconds)
20:00:56  * jcrugzzquit (Ping timeout: 260 seconds)
20:01:04  <stevemanuel>@Sly: is this a lot to ask? https://twitter.com/stevemanuel/status/392379666608046080 would be SO useful
20:01:43  <Sly>swaagie: `3rdEden: ^ doable?
20:01:48  <Sly>Looks like it would indeed be useful.
20:04:22  <swaagie>Sly: pretty useful indeed, could you issue this at the proper places, not sure if anything needs to change in jitsu CLI as well, like adding a message to jitsu deploy 'add your custom message here'
20:04:35  <swaagie>basically update the package.json with that message
20:06:57  <stevemanuel>swaagie: same way jitsu deploy versions itself, or recognizes manual version change would be great.. i always add my new version number manually, so i'd probably add the comment the same way. support for both would be awesome
20:07:05  <`3rdEden>Sly: stevemanuel but why introduce another package.json field? Why not just use the description
20:07:20  <`3rdEden>also as far as I know, we don't store the package.json for each version
20:08:09  * sreeixquit (Quit: sreeix)
20:08:17  <stevemanuel>`3rdEden, i suppose that works fine - just didn't realize that would be specific to the version #
20:08:21  * thomas84quit (Quit: thomas84)
20:09:14  <stevemanuel>basically i just want to pin a message to a app version. keeps me from digging thru git logs..
20:10:21  * andreypoppjoined
20:11:18  <swaagie>`3rdEden: description wouldn't work as it would be mostly static
20:11:34  * jonykrausequit (Remote host closed the connection)
20:13:21  <`3rdEden>Anyways changing the package.json everytime you deploy isnt that productive and user friendly, maybe a cli arg makes more sense here
20:13:54  <`3rdEden>Jitsu deploy --as description
20:14:04  <`3rdEden>Or what ever
20:14:07  <swaagie>new package.json is not stored automatically
20:14:14  <swaagie>just do commit style tbh
20:14:19  <swaagie>like jitsu deploy ''
20:14:40  <swaagie>it would require some additional engineering to store that message with snapshot
20:17:40  <`3rdEden>anyways, a feature request can be made at our uservoice forums
20:17:48  * `3rdEden( http://sso.nodejitsu.com/ )
20:17:49  * indexzerojoined
20:20:23  * natebquit (Quit: Page closed)
20:21:21  <stevemanuel>great, thanks guys
20:22:11  * atomlessquit (Ping timeout: 246 seconds)
20:24:35  * thealanwattsriotjoined
20:26:44  * huevosdeorojoined
20:27:28  <huevosdeoro>hi - I experienced an error while deploying
20:27:29  <huevosdeoro>Error: spawn ENOMEM error: at errnoException (child_process.js:855:11) error: at ChildProcess.spawn (child_process.js:802:11) error: at exports.spawn (child_process.js:626:9) error: at tailLog (/opt/local/lib/node_modules/solenoid/lib/solenoid.js:471:18) error: at Object._onTimeout (/opt/local/lib/node_modules/solenoid/lib/solenoid.js:462:17) error: at Timer.list.ontimeout (timers.js:101:19
20:27:42  * daviddiasjoined
20:27:59  <huevosdeoro>I then restarted my server from the admin panel and it did not restart successfully
20:29:23  * themgtquit (Ping timeout: 260 seconds)
20:30:37  * themgtjoined
20:34:00  <chovy>did you guys just raise your prices?
20:38:02  * chjjjoined
20:41:52  * huevosdeoroquit (Quit: Page closed)
20:47:07  * ChrisMathesonjoined
20:47:12  * ChrisMathesonquit (Client Quit)
20:51:32  * alangrtusjoined
20:52:12  * alangrtuspart
20:53:30  * alangrusjoined
20:55:11  * sportojoined
20:58:27  * indexzeroquit (Quit: indexzero)
21:03:23  <alangrus>I am working to try to add resiliant error handling to my existing Node/Express app. I found domain-cluster-example.js at https://gist.github.com/isaacs/5264418. This works nicely for killing a errored process and freshly starting another. Now, I need to have my Node/Express app connected to this feature, as everything in my App runs through the Express "app" object. I am looking for good advice on how to adapt the domain-clus
21:06:41  * tonistquit (Quit: tonist)
21:14:28  * ChrisMathesonjoined
21:15:51  * Chris____quit (Ping timeout: 250 seconds)
21:22:49  * DTrejoquit (Remote host closed the connection)
21:24:25  * indexzerojoined
21:29:10  * themgtquit (Quit: themgt)
21:29:56  * stevemanuelquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:30:14  * bzooquit (Remote host closed the connection)
21:30:29  * ChrisMathesonquit
21:30:50  * bzoojoined
21:34:13  * daviddiasquit (Remote host closed the connection)
21:34:42  * daviddiasjoined
21:35:49  * bzooquit (Ping timeout: 268 seconds)
21:39:02  * daviddiasquit (Ping timeout: 240 seconds)
21:42:00  * xymoxquit (Ping timeout: 265 seconds)
21:44:46  * eferniequit (Quit: efernie)
21:45:20  * jcrugzzjoined
21:46:33  * cronopiojoined
21:49:09  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
21:49:27  * Toxchanged nick to Gottox
21:51:59  * tobiequit (Ping timeout: 272 seconds)
21:54:36  * thealanwattsriotjoined
21:54:41  * thealanwattsriotquit (Max SendQ exceeded)
21:55:14  * thealanwattsriotjoined
21:55:44  * DTrejojoined
21:55:52  * DTrejoquit (Remote host closed the connection)
21:56:28  * DTrejojoined
22:07:28  <chovy>is there a guide somewhere about supporting user image iuploads>
22:07:30  <chovy>?
22:07:45  <chovy>i'm creating a service where people can post images.
22:07:54  * stevemanueljoined
22:08:01  <chovy>I want to use imagemagick to scale the image down, and then persist it on disk.
22:08:49  * frenchto1stjoined
22:09:25  * Heboquit
22:10:34  * Hebojoined
22:15:44  * defunctzombiechanged nick to defunctzombie_zz
22:17:26  * natebjoined
22:18:52  <nateb>Hi guys. I could use some help with continuous deployment from github.
22:21:37  * bzoojoined
22:27:48  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
22:29:34  <_discovery>chovy: it's fairly standard but be aware that files are dropped with each snapshot (so you should be storing them on a CDN not on the node host)
22:30:13  <_discovery>for example , http://aws.amazon.com/sdkfornodejs/
22:30:33  * thealanwattsriotjoined
22:30:37  * thealanwattsriotquit (Max SendQ exceeded)
22:31:13  * thealanwattsriotjoined
22:36:56  * kaspertidemannquit (Quit: Free soup for everybody!)
22:38:19  * thirdknifequit (Ping timeout: 272 seconds)
22:39:49  * Slaytors_joined
22:43:24  * Slaytorsonquit (Ping timeout: 256 seconds)
22:44:17  * Slaytors_quit (Ping timeout: 246 seconds)
22:45:52  * tobiejoined
22:45:56  <jcrugzz>chovy: you want to use a service like a CDN to store the images, but you can do the encodings and such with imagemagick using gm(https://npmjs.org/package/gm)
22:50:33  * indexzeroquit (Quit: indexzero)
22:50:48  * jbasdfquit (Quit: jbasdf)
22:51:10  * thirdknifejoined
22:52:35  * thirdknifequit (Max SendQ exceeded)
22:53:05  * thirdknifejoined
22:59:14  * jbasdfjoined
23:00:35  * c4milojoined
23:01:41  * jbasdfquit (Client Quit)
23:04:42  * natebquit (Quit: Page closed)
23:06:37  * topwobblequit (Quit: topwobble)
23:06:48  * thomas84joined
23:06:55  * Heboquit
23:08:00  * Hebojoined
23:10:01  * joshonthewebquit (Quit: Computer has gone to sleep.)
23:10:33  * thirdknifequit (Ping timeout: 251 seconds)
23:11:26  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
23:17:55  * c4miloquit (Remote host closed the connection)
23:23:38  * thirdknifejoined
23:26:01  * jcrugzzquit (Ping timeout: 245 seconds)
23:26:28  * cronopioquit (Ping timeout: 256 seconds)
23:28:36  * mdedetrichjoined
23:28:58  * jbasdfjoined
23:38:01  * hallasquit (Quit: Textual IRC Client: www.textualapp.com)
23:39:46  * jbasdfquit (Ping timeout: 268 seconds)
23:41:05  * jbasdfjoined
23:41:52  * topwobblejoined
23:41:58  * ChrisMathesonjoined
23:42:08  * ChrisMathesonquit (Client Quit)
23:42:34  * tobiequit (Quit: tobie)
23:44:19  * mdedetrichquit (Quit: Computer has gone to sleep.)
23:50:39  * npmbroquit (Remote host closed the connection)
23:51:10  * npmbrojoined