00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:00:44  * joshonthewebjoined
00:02:40  * mokesjoined
00:04:07  * joshonthewebquit (Client Quit)
00:04:07  * mokesquit (Read error: Connection reset by peer)
00:05:57  * isoddquit (Ping timeout: 240 seconds)
00:06:55  * robmozartquit (Remote host closed the connection)
00:08:42  * st_lukequit (Remote host closed the connection)
00:10:07  * xobbobquit (Quit: xobbob)
00:14:21  * mokesjoined
00:16:33  * mokesquit (Read error: Connection reset by peer)
00:24:14  * st_lukejoined
00:25:54  * defunctzombiechanged nick to defunctzombie_zz
00:26:19  * frenchtoastquit (Ping timeout: 268 seconds)
00:27:38  * mokesjoined
00:27:49  * michaelhemesathjoined
00:27:53  * mokesquit (Read error: Connection reset by peer)
00:31:47  * frenchtoastjoined
00:32:30  * mdedetrichjoined
00:32:36  * ProLoserquit (Quit: ProLoser)
00:39:33  * ProLoserjoined
00:41:41  * mokesjoined
00:41:52  * mokesquit (Read error: Connection reset by peer)
00:41:56  * michaelhemesathquit (Remote host closed the connection)
00:53:32  * jaridmargolinquit (Remote host closed the connection)
00:54:42  * joshonthewebjoined
00:55:18  * mokesjoined
00:57:31  * mokesquit (Read error: Connection reset by peer)
00:58:15  * DavidDia_quit (Remote host closed the connection)
00:58:35  * st_lukequit (Remote host closed the connection)
00:58:51  * DavidDiasjoined
01:01:02  * Samuel_Roldanquit (Quit: Samuel_Roldan)
01:03:02  * DavidDiasquit (Ping timeout: 240 seconds)
01:05:25  * isoddjoined
01:05:32  * Nodejitsu-Githubjoined
01:05:33  <Nodejitsu-Github>[nodejitsu-api] mmalecki pushed 1 new commit to master: http://git.io/KG_atA
01:05:33  <Nodejitsu-Github>nodejitsu-api/master 93c2cc5 Maciej MaƂecki: Merge pull request #25 from nodejitsu/fix-databases-superuser...
01:05:33  * Nodejitsu-Githubpart
01:05:41  <mmalecki>Sly: ^ thanks
01:05:52  <Sly>np :)
01:06:01  * Nodejitsu-Githubjoined
01:06:01  <Nodejitsu-Github>[nodejitsu-api] mmalecki deleted fix-databases-superuser at 01e4ea1: http://git.io/FJFVxA
01:06:01  * Nodejitsu-Githubpart
01:07:03  <mmalecki>Sly: I just added you to npm on this one so feel free to release
01:07:14  <Sly>Cool deal. :)
01:08:55  * mokesjoined
01:09:43  * mokesquit (Read error: Connection reset by peer)
01:12:55  * michaelhemesathjoined
01:17:32  * mokesjoined
01:17:46  * mokesquit (Read error: Connection reset by peer)
01:25:20  * mokesjoined
01:25:34  * mokesquit (Read error: Connection reset by peer)
01:27:10  * joshonthewebquit (Quit: Computer has gone to sleep.)
01:30:53  * isoddquit (Remote host closed the connection)
01:31:31  * isoddjoined
01:32:32  * isodd_joined
01:32:33  * isoddquit (Read error: Connection reset by peer)
01:33:06  * ProLoserpart
01:34:33  * Samuel_Roldanjoined
01:35:40  * admcquit (Quit: Leaving.)
01:37:05  * therealkoopaquit (Remote host closed the connection)
01:38:31  * mokesjoined
01:41:09  * mokesquit (Read error: Connection reset by peer)
01:43:12  * joshonthewebjoined
01:43:22  * joshonthewebquit (Client Quit)
01:45:33  * mokesjoined
01:45:49  * mdedetrichquit (Quit: Computer has gone to sleep.)
01:45:50  * mokesquit (Read error: Connection reset by peer)
01:48:51  * therealkoopajoined
01:50:05  * Samuel_Roldanquit (Quit: Samuel_Roldan)
01:54:48  * admcjoined
01:55:39  * mokesjoined
01:56:17  * mokesquit (Read error: Connection reset by peer)
01:58:04  * michaelhemesathquit (Remote host closed the connection)
01:58:59  * therealkoopaquit (Remote host closed the connection)
01:59:57  * mdedetrichjoined
02:00:51  * isodd_quit (Remote host closed the connection)
02:04:11  * jbasdfjoined
02:08:10  * mokesjoined
02:08:27  * mokesquit (Read error: Connection reset by peer)
02:13:05  * defunctzombie_zzchanged nick to defunctzombie
02:14:14  * henrikhodnequit (Ping timeout: 268 seconds)
02:17:15  * isoddjoined
02:19:18  * jbasdfquit (Quit: jbasdf)
02:21:21  * mokesjoined
02:23:42  * mokesquit (Read error: Connection reset by peer)
02:26:10  * isoddquit (Remote host closed the connection)
02:27:59  * henrikhodnejoined
02:29:29  * mdedetrichquit (Quit: Computer has gone to sleep.)
02:30:43  * mokesjoined
02:31:01  * mokesquit (Read error: Connection reset by peer)
02:31:56  * st_lukejoined
02:38:07  * mokesjoined
02:38:55  * mokesquit (Read error: Connection reset by peer)
02:44:13  * defunctzombiechanged nick to defunctzombie_zz
02:44:33  * jmar777quit (Remote host closed the connection)
02:45:33  * mokesjoined
02:45:42  * mokesquit (Read error: Connection reset by peer)
02:48:20  * frenchtoastquit (Ping timeout: 246 seconds)
02:54:30  * mokesjoined
02:54:42  * mokesquit (Read error: Connection reset by peer)
02:56:09  * admcquit (Quit: Leaving.)
03:05:24  * mokesjoined
03:07:40  * mokesquit (Read error: Connection reset by peer)
03:08:40  * michaelhemesathjoined
03:10:04  * joeybakerjoined
03:12:00  * mokesjoined
03:13:21  * michaelhemesathquit (Ping timeout: 264 seconds)
03:13:25  * mokesquit (Read error: Connection reset by peer)
03:18:14  * joeybakerquit (Quit: Computer has gone to sleep.)
03:18:15  * joshonthewebjoined
03:20:44  * isoddjoined
03:26:21  * cendrizziquit (Remote host closed the connection)
03:27:11  * mokesjoined
03:29:43  * mokesquit (Read error: Connection reset by peer)
03:37:43  * mokesjoined
03:39:52  * joshonthewebquit (Quit: Computer has gone to sleep.)
03:39:53  * mokesquit (Read error: Connection reset by peer)
03:42:22  * st_lukequit (Remote host closed the connection)
03:48:40  * mokesjoined
03:49:01  * mokesquit (Read error: Connection reset by peer)
03:53:24  * joshonthewebjoined
03:56:11  * isoddquit (Remote host closed the connection)
03:57:02  * isoddjoined
03:59:58  * mokesjoined
04:00:48  * bzoojoined
04:00:54  * mokesquit (Read error: Connection reset by peer)
04:01:28  * bzooquit (Remote host closed the connection)
04:02:01  * bzoojoined
04:04:03  * Popjoined
04:04:34  * Popquit (Client Quit)
04:06:14  * bzooquit (Ping timeout: 240 seconds)
04:07:44  * mokesjoined
04:10:03  * mokesquit (Read error: Connection reset by peer)
04:16:42  * mokesjoined
04:18:14  * bzoojoined
04:18:15  * mokesquit (Read error: Connection reset by peer)
04:27:37  * mokesjoined
04:27:55  * mokesquit (Read error: Connection reset by peer)
04:30:00  * jbasdfjoined
04:31:59  * isoddquit (Remote host closed the connection)
04:33:07  * isoddjoined
04:34:18  * bzooquit (Remote host closed the connection)
04:34:52  * bzoojoined
04:35:17  * mokesjoined
04:39:46  * bzooquit (Ping timeout: 268 seconds)
04:42:04  * isoddquit (Remote host closed the connection)
04:42:07  * jbasdfquit (Quit: jbasdf)
04:43:11  * isoddjoined
04:44:39  * isoddquit (Remote host closed the connection)
04:49:44  * cendrizzijoined
05:03:25  * chrisdotcodequit (Ping timeout: 246 seconds)
05:03:26  * chrisdotcode_joined
05:03:34  * chrisdotcode_quit (Read error: Connection reset by peer)
05:04:21  * mokesquit (Remote host closed the connection)
05:11:48  * mdedetrichjoined
05:17:31  * Guest88898joined
05:34:29  * defunctzombie_zzchanged nick to defunctzombie
05:35:25  * defunctzombiechanged nick to defunctzombie_zz
05:52:45  * st_lukejoined
06:00:08  * _kirbysayshiquit (Quit: _kirbysayshi)
06:01:31  * admcjoined
06:07:53  * mokesjoined
06:20:44  * thealanwattsriotjoined
06:20:52  * _yoy_quit (Quit: Leaving...)
06:23:23  * _yoy_joined
06:24:02  * zaracquit (Quit: WeeChat 0.4.1)
06:24:22  * mokesquit (Remote host closed the connection)
06:25:46  * thealanwattsriotquit (Ping timeout: 276 seconds)
06:35:49  * _yoy_quit (Ping timeout: 248 seconds)
06:37:05  * zaracjoined
06:42:44  * _yoy_joined
07:09:28  * fnumpjoined
07:12:24  * spolujoined
07:14:58  * tobiejoined
07:18:30  * mokesjoined
07:19:30  * fnumpquit (Ping timeout: 240 seconds)
07:20:13  * sreeixjoined
07:20:29  * defunctzombie_zzchanged nick to defunctzombie
07:25:12  * topwobblequit (Quit: topwobble)
07:26:32  * fnumpjoined
07:26:59  * mdedetrichquit (Quit: Computer has gone to sleep.)
07:29:44  * tobiequit (Quit: tobie)
07:34:45  * mokesquit (Remote host closed the connection)
07:38:47  * `3E|Zzzchanged nick to `3E
07:40:18  * _yoy_quit (Quit: Leaving...)
07:40:19  * mdedetrichjoined
07:58:17  * andreypoppjoined
08:06:10  * jbprosjoined
08:12:51  * mokesjoined
08:16:52  * sreeixquit (Ping timeout: 256 seconds)
08:19:42  * sreeixjoined
08:25:50  * spoluquit (Ping timeout: 240 seconds)
08:29:03  * andreypoppquit (Quit: andreypopp)
08:30:29  * Guest88898quit (Ping timeout: 248 seconds)
08:34:02  * benjaminbenbenjoined
08:34:43  * andreypoppjoined
08:37:14  * defunctzombiechanged nick to defunctzombie_zz
08:43:36  * jetiennejoined
08:46:10  * spolujoined
08:47:28  * jetiennequit (Client Quit)
08:49:33  * jetiennejoined
08:55:39  * andreypoppquit (Quit: andreypopp)
08:56:20  * andreypoppjoined
08:59:22  * andreypoppquit (Client Quit)
09:12:03  * mdedetrichquit (Quit: Computer has gone to sleep.)
09:21:01  * andreypoppjoined
09:26:14  * sreeixquit (Ping timeout: 240 seconds)
09:30:03  * mdedetrichjoined
09:30:06  * sreeixjoined
09:31:40  * andreypoppquit (Ping timeout: 276 seconds)
09:32:45  * ericguojoined
09:35:00  <ericguo>I try to figure out the ip addresses of jitsu. But I accidentally type 'jitsu host myapp.jit.su' Then jitsu seems broken even I reinstall. Any help?
09:36:03  <ericguo>always see 'error: getaddrinfo ENOTFOUND'
09:37:31  * sreeixquit (Ping timeout: 276 seconds)
09:40:59  * Caliginousjoined
09:41:04  <`3E>As far as I know, we don't have a `jitsu host` comand ericguo
09:41:22  <`3E>could it be that you meant to just do `host myapp.jit.su` ?
09:41:54  <Caliginous>Hey People, Is there a plan for NodeJitsu to support node 0.10.x in the future? Having problems with a auth plugin
09:42:27  <ericguo>i just fixed it with jitsu host api.nodejitsu.com
09:43:22  <ericguo>thanks. jitsu host is stand for jitsu config set remoteHost somedomain.com
09:44:18  <ericguo>It is not in the help document. That is why it was killing me to figure out the default domain.
09:44:29  <`3E>damned aliases ;)
09:44:52  <Caliginous>Its related to non-RSA verification failures
09:46:00  * sreeixjoined
09:46:40  * admcquit (Quit: Leaving.)
09:46:43  <Caliginous>Anyone?
09:47:31  <Caliginous>node engine 0.10.x anytime soon for node jitsu
09:47:34  <Caliginous>??
09:48:06  <`3E>Caliginous: it will be supported once we release our infrastructure revamp
09:48:22  <Caliginous>is there a roadmap for this?
09:49:22  <`3E>There isn't a public road map for it as far as i'm aware. But we're currently testing out the new infrastructure on our staging servers so it shouldn't that long before we migrate the public cloud to it
09:50:53  <Caliginous>Nice. In the mean time do you know of any work around for issue https://github.com/joyent/node/pull/4827
09:50:57  * ericguoquit (Ping timeout: 250 seconds)
09:51:00  * mesojoined
09:52:05  <`3E>I have no idea unfortunately
09:52:24  <Caliginous>No worries, it was worth a try. Cheers
10:00:55  * Caliginousquit (Ping timeout: 250 seconds)
10:16:59  * admcjoined
10:18:22  * tobiejoined
10:25:50  * admcquit (Ping timeout: 240 seconds)
10:27:17  * jbprosquit (Quit: jbpros)
10:42:57  * dchquit (Quit: Connection closed for inactivity)
10:44:53  * Samuel_Roldanjoined
10:48:56  * robmozartjoined
11:04:42  * Samuel_Roldanquit (Quit: Samuel_Roldan)
11:05:15  * andreypoppjoined
11:13:39  * zaracquit (Quit: WeeChat 0.4.1)
11:17:32  * admcjoined
11:20:58  * spoluquit (Ping timeout: 240 seconds)
11:22:21  * admcquit (Ping timeout: 264 seconds)
11:34:01  * mokesquit (Remote host closed the connection)
11:34:53  * mokesjoined
11:39:10  * mokesquit (Remote host closed the connection)
11:40:40  * d_d_dquit (Quit: Computer has gone to sleep.)
11:48:13  * fnumpquit (Remote host closed the connection)
11:57:48  * jbprosjoined
12:08:58  * st_lukequit (Remote host closed the connection)
12:16:17  * st_lukejoined
12:17:57  * admcjoined
12:22:37  * admcquit (Ping timeout: 276 seconds)
12:26:11  * therealkoopajoined
12:26:59  * d_d_djoined
12:27:35  * spolujoined
12:32:18  * therealkoopaquit (Remote host closed the connection)
12:37:23  * st_lukequit (Remote host closed the connection)
12:40:38  * sreeixquit (Ping timeout: 240 seconds)
12:41:40  * sreeixjoined
12:46:54  * mokesjoined
12:48:26  * admcjoined
12:52:16  * therealkoopajoined
12:52:38  * admcquit (Ping timeout: 240 seconds)
12:55:53  * hourbackquit (Quit: Leaving.)
13:01:27  * isodd_joined
13:04:40  * kevino80joined
13:05:47  * hourbackjoined
13:15:09  * kwhinneryjoined
13:17:26  * isodd_quit (Ping timeout: 240 seconds)
13:21:48  * futbolpaljoined
13:22:41  * jbprosquit (Quit: jbpros)
13:26:17  * kirbysayshijoined
13:27:48  * jmar777joined
13:27:54  * kirbysayshiquit (Client Quit)
13:32:00  * devdazedjoined
13:38:42  * devdazedquit (Quit: Bye)
13:41:23  * devdazedjoined
13:46:56  * starcountjoined
13:47:18  <starcount>Hey. What's the current situation with node 0.10 support?
13:48:36  * jgablejoined
13:48:54  * admcjoined
13:49:49  * isoddjoined
13:50:36  * Samuel_Roldanjoined
13:50:53  * isoddquit (Remote host closed the connection)
13:51:06  * robertkowalskiquit (Ping timeout: 264 seconds)
13:51:20  * sreeixquit (Quit: sreeix)
13:52:13  * kevino80quit (Remote host closed the connection)
13:52:54  * kevino80joined
13:53:02  * admcquit (Ping timeout: 240 seconds)
14:11:23  * starcountquit (Ping timeout: 250 seconds)
14:19:08  * robertkowalskijoined
14:19:23  * admcjoined
14:19:56  * bzoojoined
14:24:10  * admcquit (Ping timeout: 276 seconds)
14:26:43  * frenchtoastjoined
14:28:40  * anoemijoined
14:29:45  * brvjoined
14:30:24  * brvpart
14:30:55  * brandonrvaughanjoined
14:32:10  * paralleljoined
14:33:57  <brandonrvaughan>Howdy, I keep getting Error: Redis connection to 127.0.0.1:6379 failed even though I have added in my iris couch db port and host. Any ideas
14:36:53  * janingequit (Ping timeout: 240 seconds)
14:37:32  * janingejoined
14:39:36  * Wedgybojoined
14:40:18  <Sly>brandonrvaughan: you're trying to connect to local host.
14:40:56  * andreypoppquit (Quit: andreypopp)
14:41:16  <brandonrvaughan>I don't understand why if I add redis.createClient(port, host)
14:41:35  <brandonrvaughan>why would it try localhost?
14:42:02  * DavidDiasjoined
14:43:30  * DavidDia_joined
14:43:33  <Sly>Probably has a fall back for empty arguments. If you didn't define port or host, it's probably hitting the fall back.
14:43:44  <Sly>socket.io does the same thing.
14:43:58  <brandonrvaughan>I am passing in redis.createClient(6379, 'nodejitsudb7590710418.redis.irstack.com')
14:44:07  <Sly>Ah. Not sure, then.
14:44:55  <Sly>What's your username and app name?
14:45:01  <brandonrvaughan>ok i think u hit it with the sockets I forgot about that I will check that the connections are correct there
14:45:15  * c4milojoined
14:45:19  * robmozartquit (Remote host closed the connection)
14:46:15  * DavidDiasquit (Ping timeout: 245 seconds)
14:47:15  * mdedetrichquit (Quit: Computer has gone to sleep.)
14:49:54  * kwhinneryquit (Quit: kwhinnery)
14:50:57  * diogogmtjoined
14:51:17  * kwhinneryjoined
14:54:50  * brandonrvaughanquit (Quit: brandonrvaughan)
15:01:22  * bzooquit (Remote host closed the connection)
15:01:35  * satishjoined
15:01:58  * bzoojoined
15:02:46  <satish>Hello nodejitsu! Is there a recommended way of handling exceptions in nodejitsu apps? As an example I tested my app by trying to connect to a non-existent DB and that throws an error in the console and shows the default nodejitsu 'socket hang up' page.
15:02:55  <satish>instead is there a way to show an app specific status page?
15:03:56  <satish>(i read about process.on('uncaughtException', cb) and wonder if that is the way to go)
15:04:18  <Sly>satish: try {} catch () {} blocks would be recommended over uncaughtException.
15:05:19  <Sly>If you catch uncaughtException and have a fatal error, you may leave your app in a nonfunctional state.
15:06:01  * jetiennequit (Quit: jetienne)
15:06:24  * brandonrvaughanjoined
15:06:28  * bzooquit (Ping timeout: 264 seconds)
15:06:54  <satish>@Sly: ok. i noticed though the error and call stack was printed in the log the app still kept running. does nodejitsu restart it automatically?
15:07:08  <brandonrvaughan>Sly: that was it! thanks for much for your help
15:07:10  * kevino80quit (Remote host closed the connection)
15:07:11  <Sly>Yup. If the program exits, it'll restart it.
15:07:20  <Sly>brandonrvaughan: no problem. :)
15:08:37  * cronopiojoined
15:09:22  <satish>@Sly: ok, so the try/catch block could just emit an app specific status page and let the default happen then? i.e. let node kill the app and restart
15:09:31  * brianloveswordsquit (Excess Flood)
15:09:36  <Sly>That depends on what all you do in the catch block.
15:09:44  <Sly>If you want it to exit, just throw a process.exit() in.
15:10:06  <Sly>If you want to catch all the errors in uncaughtException, you can... just make sure it exits, or you can be left with a bad app if it had a fatal error.
15:10:21  * parallelquit (Remote host closed the connection)
15:11:02  * brianloveswordsjoined
15:12:51  * satishquit (Changing host)
15:12:51  * satishjoined
15:16:25  * DavidDia_quit (Read error: Connection reset by peer)
15:16:49  * diogogmtquit (Ping timeout: 276 seconds)
15:17:02  * Guest88898joined
15:18:36  * bzoojoined
15:19:51  * admcjoined
15:23:50  <satish>@Sly: does the connect error handler (the handler with 4 parameters) not get invoked when an exception happens?
15:23:58  <satish>sorry if this is a really lame question :/
15:24:10  <Sly>Connect, like the connect module?
15:24:34  <satish>connect framework (i use express & connect in my node app)
15:24:45  * admcquit (Ping timeout: 264 seconds)
15:24:56  <Sly>To be honest, I have no idea how connect works on the inside. x_x;
15:25:00  <Sly>Never had to use it.
15:26:11  * joeybakerjoined
15:28:38  * henrikhodnequit (Ping timeout: 240 seconds)
15:29:52  * spoluquit (Ping timeout: 264 seconds)
15:30:34  * DavidDiasjoined
15:31:23  * paralleljoined
15:31:42  * mokesquit (Remote host closed the connection)
15:32:47  * pbab_13joined
15:33:11  * jethedgehogjoined
15:33:45  <pbab_13>Good afternoons, I'm having issues deploying/starting an app, I have a gist to PM the first wonderful helper that responds :-)
15:34:05  <Sly>pbab_13: what's up?
15:34:08  * c4miloquit (Remote host closed the connection)
15:34:34  * c4milojoined
15:35:08  * jbasdfjoined
15:36:08  <pbab_13>Sly: I PM'd you, thanks!
15:37:16  * satishquit
15:37:39  * Guest88898quit (Ping timeout: 257 seconds)
15:39:02  * topwobblejoined
15:39:14  * anoemiquit (Quit: anoemi)
15:39:34  * c4miloquit (Ping timeout: 276 seconds)
15:43:37  * DavidDia_joined
15:44:08  * c4milojoined
15:44:42  * joeybakerquit (Quit: Quit)
15:46:03  * armi_joined
15:46:40  * DavidDiasquit (Ping timeout: 245 seconds)
15:48:27  * pbab_13quit (Ping timeout: 250 seconds)
15:49:31  * joeybakerjoined
15:49:37  * parallelquit (Remote host closed the connection)
15:50:13  * topwobblequit (Quit: topwobble)
15:50:20  * admcjoined
15:50:23  * anoemijoined
15:51:35  * topwobblejoined
15:53:08  * diogogmtjoined
15:54:47  * admcquit (Ping timeout: 246 seconds)
15:58:10  * Nodejitsu-Githubjoined
15:58:10  <Nodejitsu-Github>[nodejitsu-api] Southern tagged v0.4.7 at 5bc53b5: http://git.io/fXshuA
15:58:10  * Nodejitsu-Githubpart
16:00:00  <jethedgehog>connections to nodejitsu drones are awfully slow today... what happened to latency?
16:00:22  <mmalecki>are they? everything looks fine on our side. which app is that?
16:00:38  <jethedgehog>lifecoding-imperium
16:00:54  <jethedgehog>seems that first connection takes >10 seconds
16:01:05  * hourbackpart ("PART #solr :PONG :adams.freenode.net")
16:01:17  <jethedgehog>further request happens quicker
16:01:41  <mmalecki>are you using iriscouch, per chance?
16:01:43  * jbasdfquit (Quit: jbasdf)
16:01:54  <jethedgehog>nope. MongoHQ
16:02:08  <jethedgehog>it initializes once during start
16:02:31  <mmalecki>oh, okay. so it might be that MongoHQ shuts down your database if it's not being used
16:02:44  * kevino80joined
16:02:45  <jethedgehog>request processing doesn't depend on mongo, though
16:03:01  * joeybakerquit (Quit: Computer has gone to sleep.)
16:03:01  <mmalecki>anything in logs?
16:03:14  <mmalecki>let me give it a try
16:03:15  * andreypoppjoined
16:03:18  <mmalecki>what's your username?
16:03:19  <jethedgehog>I use this drone to do specific url-redirects... it should answer immediatly (all data cached in memory)
16:03:31  <jethedgehog>username: lifecoder
16:04:23  * jbasdfjoined
16:04:35  <mmalecki>I got mine 'Method not allowed' back immediately
16:05:32  <jethedgehog>also, I've seen again deployment prombles due to cloudfiles down... 3rd time for 3 months6, regular... why did you choose that platform and not S3, for example, etc? I have bad luck to 'catch' deployment fails once per month
16:05:42  * Nodejitsu-Githubjoined
16:05:42  <Nodejitsu-Github>[jitsu] Southern tagged v0.12.15 at 27710f3: http://git.io/GjcenQ
16:05:42  <Nodejitsu-Github>jitsu/v0.12.15 60acfdd Colton Baker: [dist] Bump nodejitsu-api dependency version: 0.4.7
16:05:42  <Nodejitsu-Github>jitsu/v0.12.15 ecf374c Colton Baker: [dist] Bump version: 0.12.15
16:05:42  * Nodejitsu-Githubpart
16:05:43  <jethedgehog>> <@mmalecki> I got mine 'Method not allowed' back immediately
16:05:56  <Sly>Argh.
16:06:07  <jethedgehog>immediate answer is ok... could you try opening crm.lifecoding.ru/click/tobeornottobe ?
16:06:16  <Sly>argh..
16:06:22  <jethedgehog>http://crm.lifecoding.ru/click/tobeornottobe
16:06:25  <Sly>Outdated branch >:O
16:07:15  <mmalecki>jethedgehog: can you try doing chrome's network profiling next time you see this?
16:07:31  <mmalecki>this site isn't hosted at nodejitsu
16:07:33  <jethedgehog>ok. right now it took ~50 seconds to open for me
16:07:50  * Nodejitsu-Githubjoined
16:07:50  <Nodejitsu-Github>[jitsu] Southern pushed 2 new commits to master: http://git.io/UFbtVA
16:07:50  <Nodejitsu-Github>jitsu/master 121e2c7 Colton Baker: [dist] Bump nodejitsu-api dependency version: 0.4.7
16:07:50  <Nodejitsu-Github>jitsu/master 5ee65b1 Colton Baker: [dist] Bump version: 0.12.15
16:07:50  * Nodejitsu-Githubpart
16:07:53  <Sly>There we go.
16:08:00  * Nodejitsu-Githubjoined
16:08:00  <Nodejitsu-Github>[jitsu] Southern force-pushed v0.12.15 from 27710f3 to fb7e8d4: http://git.io/AIFG1A
16:08:00  * Nodejitsu-Githubpart
16:08:04  <jethedgehog>crm.lifecoding.ru dns records points to nodejitsu balancers
16:08:13  <mmalecki>right, this one does, info doesn't
16:08:39  <jethedgehog>it opens quickly
16:08:47  <jethedgehog>if I open it directly
16:08:54  <mmalecki>jethedgehog: crm took 129 ms for me
16:08:58  <jethedgehog>my app should do 302 redirect... and it takes forever
16:09:05  * paralleljoined
16:09:29  <jethedgehog>thank you. I'll try to use Chrome's networking tools
16:09:32  <mmalecki>yup, this is what took 129 ms for me
16:09:37  <mmalecki>let me give you a screenshot
16:09:44  <mmalecki>might give you some insight
16:09:52  <mmalecki>http://i.imgur.com/K7kC8ki.png
16:10:03  <mmalecki>can you reproduce the slowness now?
16:10:20  * travis-cijoined
16:10:20  <travis-ci>[travis-ci] nodejitsu/jitsu#453 (v0.12.15 - ecf374c : Colton Baker): The build has errored.
16:10:20  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/60acfdd10c9a^...ecf374c8312c
16:10:20  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/9610421
16:10:20  * travis-cipart
16:10:26  <Sly>O_O
16:10:42  <jethedgehog>yes i can. will send you screen in a minute
16:10:57  <Sly>Oh, it's a git fail.
16:10:58  <Sly>That's nice.
16:11:10  * Nodejitsu-Githubjoined
16:11:11  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 2 new commits to 0.10.x: http://git.io/3KmSBw
16:11:11  <Nodejitsu-Github>node-http-proxy/0.10.x f9c5777 yawnt: [fix] error
16:11:11  <Nodejitsu-Github>node-http-proxy/0.10.x 7480c11 yawnt: Merge branch '0.10.x' of github.com:nodejitsu/node-http-proxy into 0.10.x
16:11:11  * Nodejitsu-Githubpart
16:12:15  * jbprosjoined
16:12:24  * Nodejitsu-Githubjoined
16:12:24  <Nodejitsu-Github>[node-http-proxy] yawnt pushed 1 new commit to 0.10.x: http://git.io/M_JpdQ
16:12:24  <Nodejitsu-Github>node-http-proxy/0.10.x f6495e5 yawnt: [minor] remove comments
16:12:24  * Nodejitsu-Githubpart
16:12:27  * jbprosquit (Client Quit)
16:14:29  * Nodejitsu-Githubjoined
16:14:30  <Nodejitsu-Github>[node-http-proxy] yawnt force-pushed 0.10.x from f6495e5 to da6f345: http://git.io/xdsRpw
16:14:30  <Nodejitsu-Github>node-http-proxy/0.10.x da6f345 yawnt: [minor] remove comments
16:14:30  * Nodejitsu-Githubpart
16:14:34  * travis-cijoined
16:14:34  <travis-ci>[travis-ci] nodejitsu/jitsu#454 (master - 5ee65b1 : Colton Baker): The build passed.
16:14:34  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/jitsu/compare/3656bdcf54cf...5ee65b1c3af2
16:14:34  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/jitsu/builds/9610523
16:14:34  * travis-cipart
16:15:01  <jethedgehog>http://monosnap.com/image/v3fkxqVfkPMgQrC8A0aDUhN19.png
16:15:07  <jethedgehog>Connecting: 1.3 min
16:15:30  * DavidDia_changed nick to daviddias
16:15:44  <mmalecki>okay, this is really intersting. can you reproduce it with curl? I'm wondering if cookies or something are involved
16:15:50  <mmalecki>sup daviddias
16:16:00  * travis-cijoined
16:16:01  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#194 (0.10.x - 7480c11 : yawnt): The build is still failing.
16:16:01  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/781214fda054...7480c1102050
16:16:01  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/9610671
16:16:01  * travis-cipart
16:17:01  * travis-cijoined
16:17:01  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#195 (0.10.x - f6495e5 : yawnt): The build has errored.
16:17:01  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/7480c1102050...f6495e5a43a5
16:17:01  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/9610741
16:17:01  * travis-cipart
16:17:39  <jethedgehog>@mmalecki could you please give right command for curl?
16:17:50  <jethedgehog>to run it and send output
16:18:42  <mmalecki>try doing `time curl http://crm.lifecoding.ru/click/tobeornottobe`
16:18:50  * travis-cijoined
16:18:50  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#196 (0.10.x - da6f345 : yawnt): The build is still failing.
16:18:50  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/f6495e5a43a5...da6f345b3663
16:18:50  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/9610833
16:18:50  * travis-cipart
16:19:01  <mmalecki>this should give you the time it takes for curl to fetch it
16:19:24  <jethedgehog>ok, it happens
16:19:36  <jethedgehog>slow requests pops out randomly
16:19:41  <jethedgehog>50/50
16:20:06  <jethedgehog>http://monosnap.com/image/ecLUBHFY8WWbCipMWOlHdJ2nV.png
16:20:56  <mmalecki>ohhh, I think I just managed to reproduce it. let me look more
16:21:42  * jbasdfquit (Quit: jbasdf)
16:22:19  <jethedgehog>i'm here as long as t takes, cause this problem makes my soul cry)
16:23:06  * parallelquit (Remote host closed the connection)
16:24:57  * paralleljoined
16:25:34  <mmalecki>jethedgehog: you seem to be able to reproduce this easier, can you give me output of `time curl -v http://crm.lifecoding.ru/click/tobeornottobe` (note the `-v`)
16:26:28  * andreypoppquit (Quit: andreypopp)
16:27:32  <jethedgehog>surely, in minute
16:28:25  * motiooonjoined
16:28:48  <jethedgehog>that's it: http://monosnap.com/image/knpoONlbSk7Ljhw2stWYjkVQb.png
16:30:13  <jethedgehog>165.225.130.253 timeout
16:31:22  * andreypoppjoined
16:31:22  <jethedgehog>it happens each 2nd time. I don't know, why 2nd request goes to .253, then to .5 (ok), then .235, then .5, etc
16:31:35  <mmalecki>right, those balancers look fine. I looked at the drone and it's not logging at all. adding some logs would surely help
16:31:48  <mmalecki>like, log what you do during those requests, preferably with some timestamps
16:31:58  <mmalecki>console.time() and console.timeEnd() comes to mind
16:32:12  * brandonrvaughanquit (Quit: brandonrvaughan)
16:33:22  * bzoo_joined
16:33:24  <jethedgehog>how it can happen only if do request throw only one of the balancers?
16:34:38  * bzooquit (Read error: Connection reset by peer)
16:34:47  <jethedgehog>problem only with this IP: 165.225.130.253
16:35:31  <jethedgehog>165.225.131.4 works fine all day long
16:35:34  <jethedgehog>instantly
16:35:44  <jethedgehog>165.225.130.253 timeouts every time
16:36:07  <jethedgehog>for me it's clear that something is wrong with DNS/balancers, isn't it?
16:36:11  * henrikhodnejoined
16:36:47  <mmalecki>I can give them a kick, let's see if it helps
16:36:53  <jethedgehog>no, wait
16:37:00  <jethedgehog>it definitely wrong DNS entry
16:37:07  <mmalecki>OHH
16:37:11  <jethedgehog>host dns.kit.su hasn't this ip in list
16:37:36  <mmalecki>damn, I missed that
16:37:41  <jethedgehog>it should be .129.253, so error is on my side
16:37:51  <jethedgehog>sorry)
16:38:32  <mmalecki>heh, my fault for not noticing that the first time, it's all good
16:38:37  * Samuel_Roldanquit (Quit: Samuel_Roldan)
16:38:49  <jethedgehog>shouldn't nodejitsu send some magic commands to chrome to 'tie' user to one balancer?
16:39:06  <mmalecki>we can't do that, unfortunately. you have to set it up yourself
16:39:11  <mmalecki>but we can add a test for sure!
16:39:18  <jethedgehog>I wonder why curl and chrome 'round-robin' request to one or another ip
16:39:28  <mmalecki>oh, it's supposed to do that
16:39:37  <mmalecki>it's a load balancing technique
16:39:54  <jethedgehog>why not all N addresses? I wrote them all...
16:40:54  <jethedgehog>and it would be shurely great to write a tool to test DNS records :) maybe jitsu could handle it in future? ;)
16:41:04  <mmalecki>totally, that's a great idea
16:41:09  <mmalecki>I'll pass that along
16:42:16  * mokesjoined
16:42:24  * topwobblequit (Quit: topwobble)
16:44:42  <jethedgehog>thank you for support
16:45:09  <jethedgehog>It's truly great, as always
16:46:28  * mokesquit (Ping timeout: 240 seconds)
16:47:55  * joeybakerjoined
16:50:24  * jethedgehogquit (Quit: Page closed)
16:50:49  * admcjoined
16:53:30  * joeybakerquit (Quit: Computer has gone to sleep.)
16:55:08  * admcquit (Ping timeout: 245 seconds)
16:55:27  * bobbybuilderjoined
16:56:07  * joeybakerjoined
16:57:34  <bobbybuilder>hi, i need to send out a reminder email to users of my app, at 1 day before a scheduled event. I'm not sure if I should be using cron or node-cron. But I definitely need the reminders to be sent even if I redeploy my app (so I think I'll need some type of db backing)
17:00:31  * alchimis_joined
17:01:20  * daviddiasquit (Remote host closed the connection)
17:10:23  * jbasdfjoined
17:13:08  * andreypoppquit (Quit: andreypopp)
17:14:05  * Samuel_Roldanjoined
17:14:52  * rosskjoined
17:15:28  <bobbybuilder>anybody there?
17:16:53  <Sly>bobbybuilder: sorry. Didn't see your message. :)
17:20:03  <Sly>bobbybuilder: node-cron would probably be best. Not sure. Probably better to ask in #node.js.
17:20:15  <Sly>Someone there might know something better than node-cron.
17:20:48  <jcrugzz>bobbybuilder: there is something like https://npmjs.org/package/node-schedule that may work as well
17:21:00  <bobbybuilder>thanks, i will
17:21:13  * admcjoined
17:21:21  * Wedgyboquit (Ping timeout: 268 seconds)
17:21:31  * anoemiquit (Quit: anoemi)
17:21:40  <bobbybuilder>and @jcrugzz, node-schedule is only for in process scheduling, it won't persist over restarts
17:22:35  * jbasdfquit (Ping timeout: 268 seconds)
17:22:41  <jcrugzz>bobbybuilder: yea you probably want db records for a scheduled task
17:22:48  <jcrugzz>that get loaded on startup
17:24:00  <jcrugzz>so it would load a filtered list of tasks to then be scheduled in some manner
17:24:29  <bobbybuilder>gotchya
17:24:36  <bobbybuilder>thanks for the advice
17:25:23  * admcquit (Ping timeout: 240 seconds)
17:25:39  <jcrugzz>no problem :)
17:26:48  * c4miloquit (Remote host closed the connection)
17:27:14  * c4milojoined
17:27:22  * jbasdfjoined
17:31:40  * c4miloquit (Ping timeout: 245 seconds)
17:33:12  * kwhinneryquit (Quit: kwhinnery)
17:33:24  * mokesjoined
17:36:33  * joshonthewebquit (Quit: Computer has gone to sleep.)
17:37:29  * admcjoined
17:38:06  * joeybakerquit (Quit: Computer has gone to sleep.)
17:39:12  * andreypoppjoined
17:39:13  * joeybakerjoined
17:39:36  * rossk_joined
17:41:58  * alchimis_quit (Remote host closed the connection)
17:42:48  * anoemijoined
17:42:55  * rosskquit (Ping timeout: 245 seconds)
17:44:03  * almostobsoletejoined
17:44:04  <almostobsolete>gb
17:44:13  <almostobsolete>sorry! fat fingers :p
17:44:14  * jbasdfquit (Quit: jbasdf)
17:44:25  <almostobsolete>I'm getting "No free servers available. Please visit #nodejitsu on irc.freenode.net or email [email protected] for further information."
17:44:37  * cendrizziquit (Remote host closed the connection)
17:44:40  * c4milojoined
17:44:42  * kwhinneryjoined
17:45:11  <Sly>almostobsolete: one minute.
17:45:57  <Sly>almostobsolete: can you give it another shot for me?
17:45:59  <almostobsolete>ah, working again
17:46:06  <Sly>Good deal. :)
17:48:29  * bobbybuilderquit (Ping timeout: 250 seconds)
17:49:07  * gkobergerjoined
17:49:51  * joshonthewebjoined
17:51:17  * rossk_changed nick to rossk
17:54:20  * parallelquit (Remote host closed the connection)
17:59:33  * ranglejoined
18:01:54  * paralleljoined
18:03:52  * motiooonquit (Quit: motiooon)
18:04:32  * julianduquejoined
18:12:39  * defunctzombie_zzchanged nick to defunctzombie
18:13:58  * andreypoppquit (Quit: andreypopp)
18:16:03  * sreeixjoined
18:24:31  * silv3rwindjoined
18:28:40  * andreypoppjoined
18:28:55  * jetiennejoined
18:29:32  * parallelquit (Remote host closed the connection)
18:36:21  * Lipathorjoined
18:36:32  <Lipathor>Hi
18:36:58  * d_d_dquit (Quit: Computer has gone to sleep.)
18:37:30  * julianduquequit (Quit: leaving)
18:37:40  * julianduquejoined
18:39:23  <Lipathor>@Sly i have another problem with flatiron/director :/
18:39:42  <Sly>Lipathor: what's up?
18:39:45  * upshootjoined
18:40:24  <Lipathor>@Sly: I don't know if You remember, i've reported bug with #! in routes, and You repaired it
18:40:32  <Sly>Yup, I remember. :)
18:40:37  <Lipathor>then i reported the same bug with nested routes
18:40:51  <Lipathor>and You didn't have time
18:41:00  <Lipathor>but i workarounded it
18:41:17  <Lipathor>and now i think it's similar bug
18:41:27  <Lipathor>if i declare '!/' route
18:41:32  <Lipathor>nothing is fired
18:42:47  <Sly>Lipathor: yeah, we've been busy changing some things around and getting 0.10.x out.
18:43:58  <Sly>Lipathor: can you point me to the issue you filed in flatiron/director? I'm not seeing it.
18:44:05  <Sly>For the nested one?
18:44:16  <Lipathor>well
18:44:23  <Lipathor>give me one minute
18:46:52  <Lipathor>@Sly: just simple example http://pastebin.com/k40LiwgS
18:47:04  * joeybakerquit (Quit: Computer has gone to sleep.)
18:47:18  * rene_joined
18:47:40  <Sly>Lipathor: can you file this as an issue under https://gist.github.com/flatiron/director/issues?
18:47:48  <Lipathor>yep
18:49:01  * Samuel_Roldanquit (Quit: Samuel_Roldan)
18:50:37  * joeybakerjoined
18:50:43  <Sly>Lipathor: thanks. :)
18:50:57  <Lipathor>Sly: no problem ;)
18:51:04  * arushjoined
18:51:14  <arush>hello guys
18:51:21  <arush>got a deployment issue
18:51:25  <arush>can't deploy
18:51:39  <arush>https://gist.github.com/arush/548887164a885d6807b7
18:51:47  * Samuel_Roldanjoined
18:52:03  <Sly>arush: looks like Rackspace is just being a pain today. You're probably the 3rd person that's had this today.
18:52:13  <Sly>arush: check out http://errors.jit.su/Rackspace%20Error%20(404):%20Item%20not%20found
18:52:14  * brandonrvaughanjoined
18:52:15  <kenperkins>Which problem?
18:52:37  <Sly>kenperkins: 404
18:52:47  <kenperkins>Sly: seriously, you guys should migrate off of cloudfiles
18:52:51  <kenperkins>it's ancient and not maintained
18:53:04  <kenperkins>and I'm seriously suspect of that code and not rackspace proper
18:53:18  <kenperkins>I've tried to reproduce your problems for multiple days with not one
18:53:51  * gkobergerquit (Quit: Leaving...)
18:54:07  <kenperkins>secondly, even if we do have a problem, given that it appears to happen daily, why not wrap it and automatically retry at least once
18:54:17  <kenperkins>not cloudfiles from rackspace
18:54:21  <kenperkins>but the cloudfiles package
18:55:32  <Sly>kenperkins: what would you recommend instead of cloudfiles? I can't say that it'll change, but it's at least worth mentioning.
18:55:39  <kenperkins>pkgcloud.
18:55:42  <kenperkins>obviously
18:56:02  <Sly>Oh, I thought you meant Rackspace cloud files. Not the cloudfile package, literally.
18:56:05  <kenperkins>no
18:56:06  * Lipathorquit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
18:56:22  <kenperkins>i'm convinced the problem is not rackspace cloudfiles, but rather some edge case in the code
18:57:24  <Sly>kenperkins: wouldn't surprise me.
18:58:26  * admcquit (Quit: Leaving.)
18:58:43  <arush>this sucks
18:58:46  <arush>it won't work
18:59:37  * gkobergerjoined
19:01:15  <arush>activate doesn't even work, same error
19:02:36  * jbprosjoined
19:04:03  * andreypoppquit (Quit: andreypopp)
19:04:20  * jcrugzzquit (Ping timeout: 268 seconds)
19:04:50  * rene_quit (Remote host closed the connection)
19:05:36  <Sly>arush: if the activate didn't work, then it probably failed to upload correctly. We're working on rolling out some new things that should solve bugs like this.
19:06:05  * kwhinneryquit (Quit: kwhinnery)
19:07:58  * andreypoppjoined
19:08:14  * kscully27joined
19:08:20  * cendrizzijoined
19:09:22  * topwobblejoined
19:11:00  * jcrugzzjoined
19:11:07  * almostobsoletequit (Ping timeout: 268 seconds)
19:17:39  * mokesquit (Remote host closed the connection)
19:19:47  * arushquit (Quit: This computer has gone to sleep)
19:27:24  * arushjoined
19:29:25  * joeybakerquit (Quit: Computer has gone to sleep.)
19:29:39  * tobie_joined
19:30:17  * niftylettucequit (Ping timeout: 246 seconds)
19:30:44  * tobiequit (Ping timeout: 246 seconds)
19:30:44  * tobie_changed nick to tobie
19:33:01  <kscully27>is there a nodejitsu support rep online?
19:33:09  * chjjquit (Ping timeout: 246 seconds)
19:33:15  <Sly>kscully27: yup. What's up?
19:33:59  * hourbackjoined
19:34:20  * chjjjoined
19:36:33  * rene_joined
19:37:06  * niftylettucejoined
19:39:07  * henrikhodnequit (Ping timeout: 246 seconds)
19:39:51  * henrikhodnejoined
19:40:00  * paralleljoined
19:40:00  * kwhinneryjoined
19:41:52  * benjaminbenbenquit (Quit: benjaminbenben)
19:42:59  * joeybakerjoined
19:44:55  * parallelquit (Ping timeout: 264 seconds)
19:48:08  * mokesjoined
19:49:07  * julianduquequit (Ping timeout: 264 seconds)
19:51:41  * julianduquejoined
19:52:13  * anoemiquit (Ping timeout: 245 seconds)
19:52:18  * anoemi_joined
19:52:44  * cronopioquit (Ping timeout: 256 seconds)
19:53:06  * cronopiojoined
19:57:30  * mokesquit (Ping timeout: 245 seconds)
19:59:22  * spolujoined
20:02:44  * st_lukejoined
20:03:32  * admcjoined
20:05:35  * jbasdfjoined
20:07:21  * jbasdfquit (Client Quit)
20:10:31  * jbasdfjoined
20:10:31  * jbasdfquit (Client Quit)
20:16:50  * paralleljoined
20:21:39  * jbasdfjoined
20:21:43  * rene_quit (Remote host closed the connection)
20:22:59  * arushquit (Quit: This computer has gone to sleep)
20:25:36  * rene_joined
20:27:02  * jcrugzzquit (Ping timeout: 240 seconds)
20:27:41  * gkobergerquit (Quit: Leaving...)
20:28:31  * bobbybuilderjoined
20:29:08  <bobbybuilder>hi, when i try to deploy after upgrading to node v0.10.15 I get the following error: error: Error running command deploy error: Nodejitsu Error (500): Internal Server Error error: No matching versions found
20:32:15  * johnmartyjoined
20:32:29  <julianduque>bobbybuilder: we don't support 0.10.x yet, use 0.8.x instead in your package.json
20:33:26  * anoemijoined
20:33:40  * anoemiquit (Client Quit)
20:34:06  * fnumpjoined
20:34:33  <bobbybuilder>now i get a new error
20:34:54  <bobbybuilder>https://gist.github.com/paintzen/6107573
20:34:55  * jmar777quit (Remote host closed the connection)
20:35:25  * anoemi_quit (Ping timeout: 245 seconds)
20:36:34  <julianduque>bobbybuilder: let me check
20:36:44  <bobbybuilder>k, thanks
20:37:45  <fnump>I'm seeing this error when activating snapshots: https://gist.github.com/MarcDiethelm/22db5f4b193434e37794
20:38:35  <julianduque>ok, let me check if Rackspace is down
20:39:13  <julianduque>fnump, bobbybuilder: execute `jitsu start` on app folder and let me know if still same error
20:39:32  * Wedgybojoined
20:40:13  <fnump>julianduque: I'm getting the same error.
20:40:24  * silv3rwindquit (Read error: Connection reset by peer)
20:40:26  <julianduque>ok, give me a couple minutes, investigating
20:41:30  <bobbybuilder>@julianduque: yup same error
20:48:59  * anoemijoined
20:53:40  * brandonrvaughanquit (Quit: brandonrvaughan)
20:54:31  <fnump>julianduque: I can try re-deploying instead of snapshots activate... Should I?
20:54:59  <julianduque>fnump: yes, try a new deploy with `jitsu deploy --debug` and let me know the output in a gist if something goes wrong
20:55:07  <julianduque>bobbybuilder: same to you ^
20:55:28  <fnump>I'm stuck here in the office anyway until my deployment is successful. (At 22:55 local) :)
20:55:37  <julianduque>fnump: :o
20:56:19  * anoemiquit (Quit: anoemi)
20:57:55  * anoemijoined
20:58:33  <jesusabdullah>anoemi: sup dawg ltns
20:58:45  <fnump>julianduque: That worked partially. Now my assets are missing. o_0 I will re-try. It happens from time to time.
20:59:59  * rene_quit (Remote host closed the connection)
21:02:01  <julianduque>fnump: what is your username/appname?
21:03:27  <fnump>julianduque: I just created another snapshot and activated it. It's working now.
21:03:29  <fnump>Still want my username/appname?
21:04:18  <julianduque>fnump: sure, want to take a look
21:04:28  * st_lukequit (Remote host closed the connection)
21:04:53  <fnump>namics/orange-frontend-stage
21:04:55  * rene_joined
21:05:10  <bobbybuilder>@julianduque: all is good again
21:05:28  <fnump>julianduque: namics/orange-frontend-stage
21:06:12  <julianduque>bobbybuilder: a hiccup in Rackspace client, sorry for the inconveniences :)
21:06:38  <julianduque>fnump: thanks
21:07:07  <bobbybuilder>no worries, it happens
21:07:45  <fnump>julianduque: do you still need me? else i'll be on my way.
21:08:15  * julianduquequit (Quit: leaving)
21:08:26  * julianduquejoined
21:09:55  <fnump>julianduque: do you still need me? else i'll be on my way. (bump. seems you were offline just now)
21:11:04  * frenchtoastquit (Ping timeout: 276 seconds)
21:12:32  * julian_duquejoined
21:12:34  * julian_duquequit (Changing host)
21:12:34  * julian_duquejoined
21:12:56  * julianduquequit (Disconnected by services)
21:13:06  * julian_duquechanged nick to julianduque
21:13:32  <julianduque>damn internetz :/
21:14:27  <kscully27>haha no worries
21:15:13  <fnump>yo julianduque, still need me? probably not, right?
21:15:46  <julianduque>fnump: no, was trying to figure out the problem but i'm not seeing anything useful in the logs, so
21:16:05  <julianduque>if it's working it's ok :)
21:16:42  <fnump>julianduque: KTHXBAI :D
21:17:04  * fnumpquit (Quit: ChatZilla 0.9.90.1 [Firefox 22.0/20130618035212])
21:18:13  * bobbybuilderquit (Ping timeout: 250 seconds)
21:19:54  * itzmjauzquit (Ping timeout: 264 seconds)
21:20:03  * itzmjauzjoined
21:20:41  * jbprosquit (Quit: jbpros)
21:20:43  * anoemiquit (Quit: anoemi)
21:22:59  * jbasdfquit (Quit: jbasdf)
21:26:38  * tobiequit (Quit: tobie)
21:28:04  * gkobergerjoined
21:31:37  * kevino80quit (Remote host closed the connection)
21:32:04  * Samuel_Roldan_joined
21:34:41  * jgablequit (Quit: Computer has gone to sleep.)
21:35:50  * Samuel_Roldanquit (Ping timeout: 240 seconds)
21:36:17  * alchimis_joined
21:36:39  * Samuel_Roldan_quit (Ping timeout: 268 seconds)
21:36:51  * Nodejitsu-Githubjoined
21:36:51  <Nodejitsu-Github>[node-http-proxy] cronopio pushed 1 new commit to 0.10.x: http://git.io/nX1kQQ
21:36:51  <Nodejitsu-Github>node-http-proxy/0.10.x 45c874e cronopio: [fix] hack to call .end() explicitly, enable error handler, at this point the test/http/http-test.js all passed
21:36:51  * Nodejitsu-Githubpart
21:38:44  * jbasdfjoined
21:39:22  * Guest88898joined
21:39:49  * jlinesjoined
21:40:43  * travis-cijoined
21:40:43  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#197 (0.10.x - 45c874e : cronopio): The build is still failing.
21:40:43  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/da6f345b3663...45c874e36fe6
21:40:43  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/9623316
21:40:43  * travis-cipart
21:40:45  <jlines>i have a bin folder in my app that holds files that are uploaded to the server through my app, i want this folder to remain unchanged when I deploy a new version of my app, right now the folder gets blown out each time
21:44:13  * Guest88898quit (Ping timeout: 276 seconds)
21:45:22  <julianduque>jlines: we don't have permament storeage, so if you deploy your files will be replaced by the new snapshot
21:45:23  * topwobblequit (Quit: topwobble)
21:45:54  * rene_part
21:53:01  * anoemijoined
21:58:57  * anoemiquit (Ping timeout: 264 seconds)
21:59:55  * Guest88898joined
22:00:42  * d_d_djoined
22:01:03  * d_d_dquit (Max SendQ exceeded)
22:01:36  * d_d_djoined
22:02:30  * Nodejitsu-Githubjoined
22:02:30  <Nodejitsu-Github>[node-http-proxy] cronopio force-pushed 0.10.x from 45c874e to 52defcb: http://git.io/xdsRpw
22:02:30  <Nodejitsu-Github>node-http-proxy/0.10.x a56ae94 yawnt: [fix] refactor
22:02:30  <Nodejitsu-Github>node-http-proxy/0.10.x c8d9e0f yawnt: [refactor] start working on forwardStream
22:02:30  <Nodejitsu-Github>node-http-proxy/0.10.x bd62a68 yawnt: [fix] now you can pipe()
22:02:30  * Nodejitsu-Githubpart
22:04:36  * Nodejitsu-Githubjoined
22:04:36  <Nodejitsu-Github>[nodejitsu-api] Southern pushed 1 new commit to master: http://git.io/kIX3hw
22:04:36  <Nodejitsu-Github>nodejitsu-api/master 86108c0 Colton Baker: [minor] Refactor helpers.defaultUser into Client....
22:04:36  * Nodejitsu-Githubpart
22:04:43  * anoemijoined
22:04:57  * gkobergerquit (Quit: Leaving...)
22:05:11  * arushjoined
22:05:40  * travis-cijoined
22:05:40  <travis-ci>[travis-ci] nodejitsu/node-http-proxy#198 (0.10.x - 52defcb : cronopio): The build is still failing.
22:05:40  <travis-ci>[travis-ci] Change view : https://github.com/nodejitsu/node-http-proxy/compare/45c874e36fe6...52defcb3f262
22:05:40  <travis-ci>[travis-ci] Build details : http://travis-ci.org/nodejitsu/node-http-proxy/builds/9624199
22:05:40  * travis-cipart
22:07:07  * st_lukejoined
22:08:38  * Nodejitsu-Githubjoined
22:08:38  <Nodejitsu-Github>[node-http-proxy] cronopio pushed 1 new commit to 0.10.x: http://git.io/gxTwxA
22:08:38  <Nodejitsu-Github>node-http-proxy/0.10.x 77f3723 cronopio: [fix] getting rid of try..catch, as @mmalecki suggested
22:08:38  * Nodejitsu-Githubpart
22:09:00  * papachanjoined
22:11:10  * anoemiquit (Quit: anoemi)
22:12:23  * spoluquit (Ping timeout: 240 seconds)
22:15:51  * joshonthewebquit (Quit: Computer has gone to sleep.)
22:16:07  * topwobblejoined
22:16:26  * joshonthewebjoined
22:17:46  * topwobblequit (Client Quit)
22:17:50  * futbolpalquit (Quit: futbolpal)
22:18:32  * frenchtoastjoined
22:19:20  * topwobblejoined
22:21:51  * c4miloquit (Remote host closed the connection)
22:22:17  * c4milojoined
22:25:10  * drewjoined
22:25:19  * jbasdfquit (Quit: jbasdf)
22:25:34  * drewchanged nick to Guest5755
22:26:40  * c4miloquit (Ping timeout: 245 seconds)
22:27:18  <Guest5755>hi, does nodejitsu support something like the `bcrypt` npm package or an alternative I can use for one way password crypt?
22:28:08  * papachanquit (Quit: Saliendo)
22:29:15  <mmalecki>we do support bcrypt
22:30:54  <Guest5755>great. anything specific I need to do to configure?
22:31:39  <mmalecki>nope, just add it to your dependencies :-)
22:32:21  <Guest5755>thanks. will give it a go :)
22:32:47  <mmalecki>pleasure :)
22:33:23  * jbasdfjoined
22:35:13  * jgablejoined
22:35:35  * thealanwattsriotjoined
22:41:26  * Guest88898quit (Ping timeout: 240 seconds)
22:45:45  * jlinesquit (Ping timeout: 250 seconds)
22:46:18  * cronopioquit (Quit: leaving)
22:49:52  * gkobergerjoined
22:50:56  * jbasdfquit (Quit: jbasdf)
22:51:16  * Guest5755part
22:51:59  * mokesjoined
22:56:07  * armi_quit (Quit: Page closed)
22:56:33  * mokesquit (Ping timeout: 264 seconds)
22:58:57  * kwhinneryquit (Quit: kwhinnery)
22:59:03  * joshonthewebquit (Quit: Computer has gone to sleep.)
23:04:00  * jmar777joined
23:06:42  * jmar777quit (Remote host closed the connection)
23:07:10  <kscully27>is there a support rep online?
23:11:36  <julianduque>kscully27: I'm and talking with you on privat
23:11:39  <julianduque>private*
23:18:23  * alchimis_quit (Read error: Connection reset by peer)
23:18:57  * alchimis_joined
23:26:12  * topwobblequit (Quit: topwobble)
23:29:12  * jmar777joined
23:32:25  * alchimis_quit (Remote host closed the connection)
23:38:24  * jmar777quit (Remote host closed the connection)
23:40:33  * upshootquit (Ping timeout: 245 seconds)
23:44:23  * andreypoppquit (Quit: andreypopp)
23:48:25  * jcrugzzjoined
23:48:25  * jcrugzzquit (Client Quit)
23:48:28  * henrikhodnequit (Ping timeout: 264 seconds)
23:49:39  * jcrugzzjoined
23:55:18  * thealanwattsriotquit (Quit: Computer has gone to sleep.)
23:55:24  * d_d_dquit (Quit: Computer has gone to sleep.)
23:59:00  * mokesjoined