00:01:25  * derpopsjoined
00:01:52  * jmar777joined
00:03:51  * `3rdEdenjoined
00:07:38  * blakmatrixquit (Remote host closed the connection)
00:07:57  * RabidFirejoined
00:08:33  * Leeoljoined
00:09:18  * jmoyersquit (Quit: Computer has gone to sleep.)
00:09:43  <jesusabdullah>dangit pallinder
00:11:51  * `3rdEdenquit (Ping timeout: 244 seconds)
00:12:36  * garrettwilkinjoined
00:12:41  * therealk_quit (Remote host closed the connection)
00:16:48  * jmar777quit (Remote host closed the connection)
00:20:11  * appsunitedjoined
00:20:59  * jgomez_joined
00:21:37  * tonymilnejoined
00:22:14  * garrettwilkinquit (Quit: garrettwilkin)
00:25:09  * jmar777joined
00:25:15  <appsunited>jesusabdullah: Thanks for your kind advice. Unfortunately I didn't get it work. A simple Meteor example app doesn't run on Nodejitsu. I have created a package.json as you said. But to be honest: I don't understand, why it's so complicated to deploy it on Nodejitsu. At Heroku it's really simple without any problems. Maybe we need a build plugin like this? https://github.com/jordansissel/heroku-buildpack-meteor
00:27:14  * benlowerjoined
00:27:29  * therealkoopajoined
00:27:43  <appsunited>But I love Nodejitsu and Heroku doesn't support Websockets. So I am really interessted to find a better solution! :)
00:29:49  * jgomez_quit (Quit: Leaving)
00:32:11  <jesusabdullah>appsunited: it's because meteor refuses to use the package.json format
00:32:16  <jesusabdullah>and leverage npm
00:32:25  <jesusabdullah>they actively decided to work against the grain and do their own thing
00:32:30  * RabidFirequit (Quit: RabidFire)
00:32:30  * blakmatrixjoined
00:32:37  * hotchquit (Quit: hotch)
00:32:53  * therealkoopaquit (Remote host closed the connection)
00:36:19  * slloyd_quit (Quit: Leaving...)
00:37:10  * c4milojoined
00:41:09  * c4miloquit (Ping timeout: 240 seconds)
00:44:38  <appsunited>:jesusabullah: Hm, I understand... so we have to go to Heroku, if developers need to use Meteor?
00:46:22  <appsunited>http://meteor-leaderboard.herokuapp.com/
00:47:56  * RabidFirejoined
00:48:00  * coen-hydequit (Quit: coen-hyde)
00:50:00  <admc>jitsu databases create redis blah <- appears to be broken, anyone have thoughts?
00:51:37  * blakmatrixquit (Read error: Connection reset by peer)
00:52:14  * blakmatrixjoined
00:52:38  <torvalde>hi mmalecki, do I need to upgrade the node version in my module also, from 0.8.6, or is it enough to restart my app to fix the timezone thing?
00:53:12  * derpopsquit
00:53:54  <mmalecki>torvalde: they didn't release the fix yet, but if your app specifies 0.8.x as the node version, restart should be enough
00:54:25  <torvalde>great, thanks!
00:56:03  * RabidFirequit (Quit: RabidFire)
00:58:50  * blakmatrixquit (Read error: Connection reset by peer)
00:59:26  * blakmatrixjoined
01:00:32  * ccowanquit (Quit: Leaving.)
01:01:29  * derpopsjoined
01:03:15  * `3rdEdenjoined
01:03:26  * ccowanjoined
01:05:13  * anoemijoined
01:06:09  * benvquit (Quit: Computer has gone to sleep.)
01:10:22  * niftylettucequit (Remote host closed the connection)
01:10:22  * BruNeXquit (Read error: Connection reset by peer)
01:10:22  * jkarsrudquit (Remote host closed the connection)
01:10:23  * Raynosquit (Remote host closed the connection)
01:10:23  * dscapequit (Read error: Connection reset by peer)
01:10:23  * lmjabreuquit (Remote host closed the connection)
01:10:23  * cmwelshquit (Remote host closed the connection)
01:10:23  * Lemminkainen_quit (Remote host closed the connection)
01:10:23  * owenbquit (Remote host closed the connection)
01:10:23  * indutnyquit (Read error: Connection reset by peer)
01:10:23  * JasonSmithquit (Remote host closed the connection)
01:10:23  * pksunkaraquit (Remote host closed the connection)
01:10:23  * Fabryzquit (Read error: Connection reset by peer)
01:10:23  * teritequit (Remote host closed the connection)
01:10:23  * romainhuetquit (Remote host closed the connection)
01:10:25  * duncanbeeversquit (Remote host closed the connection)
01:10:29  * remysharpquit (Remote host closed the connection)
01:11:08  * duncanbeeversjoined
01:11:56  * appsunitedquit (Ping timeout: 245 seconds)
01:12:18  * ferloresjoined
01:12:35  * ArxPoeticajoined
01:13:37  * jkarsrudjoined
01:15:21  * romainhuetjoined
01:15:30  * jmar777quit (Remote host closed the connection)
01:15:35  * Sly[Tablet]quit (Ping timeout: 260 seconds)
01:16:24  * Sly[Tablet]joined
01:16:28  * remysharpjoined
01:17:43  * niftylettucejoined
01:18:58  * lmjabreujoined
01:20:23  * teritejoined
01:21:22  * ArxPoeticaquit (Quit: Leaving.)
01:22:04  * admcquit (Quit: Leaving.)
01:22:32  * JasonSmithjoined
01:22:37  * owenbjoined
01:22:58  * indutnyjoined
01:25:10  * joshonthewebquit (Quit: Computer has gone to sleep.)
01:25:54  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
01:26:00  * anoemiquit (Quit: anoemi)
01:26:10  * derpopsquit
01:27:10  * benlowerquit (Remote host closed the connection)
01:29:39  * jmar777joined
01:32:46  * jmar777quit (Remote host closed the connection)
01:39:50  * therealkoopajoined
01:40:47  * Fabryzjoined
01:42:40  * `3rdEdenquit (Remote host closed the connection)
01:42:47  <ferlores>hi guys, I cannot deploy there's some issue? https://gist.github.com/3942405
01:42:49  * bardujoined
01:45:16  * torvaldequit (Ping timeout: 245 seconds)
01:49:01  <bardu>as long as I was on a free account I usually didn't need more than 3 attempts to get a deployment through, now on a paid account I need 7 to 12 attemps
01:49:08  <bardu>this sucks
01:50:06  * Lemminkainen_joined
01:50:15  * dscapejoined
01:55:09  <jesusabdullah>bardu: that's certainly not due to any change in service. Perhaps I can help you figure out why?
01:55:31  <jesusabdullah>ferlores: what is your username and app name?
01:56:01  <bardu>bardu yxyapp
01:56:24  <jesusabdullah>bardu: you should start by showing me jitsu's output from when you try to deploy
01:56:31  <jesusabdullah>ferlores: a look at your package.json would also be helpful
01:56:56  * mdedetrichjoined
01:58:12  <bardu>sorry I have to run now, when I'm deploying again again I will be here and gist all output, but usually it is : socket hang up
01:58:51  * derpopsjoined
01:59:12  <jesusabdullah>bardu: you'll have to catch up with me then, I can't debug with just that
01:59:23  <jesusabdullah>ferlores: I'm still here to give you a hand
02:00:55  * cmwelshjoined
02:01:23  * BruNeXjoined
02:01:48  * `3rdEdenjoined
02:02:10  * Raynosjoined
02:02:11  * bardupart
02:03:34  * jgomezquit (Quit: Leaving)
02:03:41  * ArxPoeticajoined
02:12:19  <ferlores>jesusabdullah, sorry, had to go, but now I'm back
02:12:24  <jesusabdullah>word
02:12:26  <ferlores>user: ferlores
02:13:00  <ferlores>app-name: npm-status
02:13:05  * coen-hydejoined
02:13:16  * pksunkarajoined
02:13:48  * coen-hydequit (Client Quit)
02:14:03  <ferlores>here is the output : https://gist.github.com/3942405
02:14:31  <ferlores>and I will add the package.json there too
02:15:47  <ferlores>jesusabdullah, what else can I send you?
02:16:19  <jesusabdullah>unsure
02:24:05  * TooTallNatejoined
02:24:09  * TooTallNatequit (Client Quit)
02:25:24  <ferlores>do you think I have any chance recreating the app?
02:28:20  * derpopsquit
02:29:27  * coderarityjoined
02:30:32  * `3rdEdenquit
02:48:23  <jesusabdullah>ferlores: I believe mmalecki is investigating, this is a new error for me
02:48:46  * jahaquit (Quit: Leaving.)
02:48:48  <jesusabdullah>ferlores: sorry needed food
02:49:32  * ArxPoeticaquit (Quit: Leaving.)
02:49:50  <ferlores>jesusabdullah, np, thanks for working on it
02:51:11  <mdedetrich>hi everybody!
02:52:41  <ferlores>jesusabdullah, I'm going to sleep, please tweet me if you got a solution @ferlores. Thanks!
02:52:42  * marshall_afkchanged nick to marshall_law
02:53:00  <mdedetrich>ferlores: gnight
02:53:29  <ferlores>gn mdedetrich
02:55:17  * bengourleyquit (Quit: bengourley)
02:55:25  * jahajoined
02:56:24  <jaha>ive been getting a lot of socket hang up errors lately, anything more i can do to debug, id like to get the deployment more stable
02:56:54  <jaha>not THAT many dependencies
02:56:56  <jesusabdullah>jaha: you can tell me more about the errors you're running into
02:57:03  <jesusabdullah>jaha: are these hangups on deploy?
02:57:28  <jaha>yes
02:57:33  <jaha>jesusabdullah: ^
02:57:36  <jesusabdullah>okay
02:57:54  <jesusabdullah>so, can you show me the output of jitsu, and your package.json, in a gist? http://gist.github.com
02:58:58  <jaha>jesusabdullah: https://gist.github.com/3950187
03:00:06  <jaha>its says the snapshot is created but it isnt actually "live"
03:00:30  <jesusabdullah>interesting
03:01:33  <jaha>heres another issue… every so often (like now) it deploys but I get no response back from the server, just hangs
03:01:58  <jaha>tried to debug and problem in the code but couldnt replicate it locally or find it
03:02:26  <jaha>plus no helpful errors or logs which makes it that much more enjoyable
03:04:03  <jesusabdullah>I understand your frustration
03:04:10  <jesusabdullah>did you try typing 'jitsu logs app' ?
03:04:58  <jesusabdullah>jaha: it looks like on that last machine, it ran out of memory, then rebooted running your app
03:05:02  <jesusabdullah>jaha: that's what it looks like
03:05:33  <jesusabdullah>jaha: doesn't necessarily look like your fault
03:06:25  <jaha>phew ;), but http://ualc.jit.su/ is still not sending a response
03:06:45  <jaha>jesusabdullah: and yea, nothing in logs
03:07:24  * derpopsjoined
03:08:23  <jesusabdullah>jaha: can you do me a favor and deploy while I watch?
03:09:36  <jaha>jesusabdullah: sounds dirty…. ok
03:10:15  <jaha>v0.0.10-0 coming at ya
03:10:30  <jesusabdullah>aight
03:10:39  <jesusabdullah>how big is your snapshot?
03:10:58  <jesusabdullah>If it's big (think 20mb or more) unpacking the tarball can choke the mini-machines
03:12:30  <jesusabdullah>looks like it reached deploy stage
03:12:40  <jesusabdullah>that is, pushing it to a haibu
03:14:47  * ferloresquit (Remote host closed the connection)
03:15:10  <jaha>npm pack puts it at 6m
03:15:22  <jesusabdullah>okay so maybe that's not it
03:15:27  <jesusabdullah>and you have deps but not a fuckton
03:16:37  <jaha>i seem to have this problem with socket.io and mongoose deploys… well thats what it seems like anyway
03:16:50  <jesusabdullah>hmm
03:17:00  <jesusabdullah>didn't some versions of mongoose have giganticness?
03:17:39  <jaha>this one is 20m i think
03:17:44  <jaha>latest
03:17:51  <jaha>i think
03:18:01  <jesusabdullah>I see it jaha
03:18:08  <jesusabdullah>how long does it take your server to listen on a socket?
03:18:16  <jesusabdullah>Also, are you trying to use the cluster module (be honest)
03:18:41  <jaha>wouldnt even know how… yet
03:18:48  <jesusabdullah>good
03:18:53  <jesusabdullah>don't use cluster with nodejitsu XD
03:19:10  <jesusabdullah>but yeah, the error I see is, "took too long to listen on a socket", in these logs
03:19:39  <jesusabdullah>but that's also on the reboot of the haibu which looked like it choked on something
03:20:07  <jaha>is that on your side or are you saying my client machine might have the problem
03:20:33  <jesusabdullah>I'm saying your app might not be starting an http server in a "reasonable timeframe"
03:20:47  <jesusabdullah>how long does it take to start serving webpages from `npm start`?
03:21:34  <jesusabdullah>oh christ jaha
03:21:38  <jesusabdullah>I found it
03:21:57  <jesusabdullah>jaha: the version of mongoose you're using requires a version of mongodb that has like 15MB of coverage data
03:22:12  <jesusabdullah>jaha: which causes 50mb of total app to unpack
03:22:20  <jesusabdullah>jaha: which kills the micro-server
03:22:49  <jesusabdullah>jaha: I believe later versions of mongodb and/or mongoose fixed this; either way tweaking versions will help you a lot here
03:23:38  <jaha>.. that should be all at latest, my rules are still pretty loose atm
03:23:42  <jaha>hmm
03:24:45  <jaha>also I have that app on the "large" account (along with others), how exactly does that work, also want to know cause i did the math the other day and it doesnt work out to a price break compared to the 5 pack
03:25:10  <jesusabdullah>jaha: all the "individual" accounts have the same size machines
03:25:22  <jesusabdullah>jaha: it sounds like you might want the one that lets you pay $3/drone?
03:26:44  * harbhubjoined
03:26:46  <harbhub>hey
03:26:53  <jaha>how do I manage that with multiple apps, i am going to have 20 some deployed apps eventually, most will only need 1 drone but others may need to scale
03:26:55  <harbhub>my package.json is returning an error
03:27:12  <jesusabdullah>jaha: you should be able to spread out a given plan across any amount of apps
03:27:33  <harbhub>hey jesus
03:27:37  <jesusabdullah>jaha: I do understand that the ux is a bit funky around that, I need to arrange to experiment with it myself so I can figure stuff out
03:27:41  <harbhub>been a while
03:27:42  <jesusabdullah>harbhub: hey, what kind of error?
03:27:53  <harbhub>https://gist.github.com/3950252
03:28:08  <harbhub>error: Nodejitsu Error (404): Item not found error: Could not find path: /apps/harbhub/shout%20work/snapshots/0.0.1-2
03:28:34  <harbhub>i'm guessing my package.json folder is wrong
03:28:35  <jesusabdullah>harbhub: can you try an app name without a space in it?
03:28:45  <jesusabdullah>I think that's the issue
03:28:46  <jesusabdullah>personally
03:28:48  <jaha>jesusabdullah: so what is the large giving me now? if I buy a 3/month it wouldnt let me attach more than one app to it last time i tried
03:29:10  <harbhub>that might work, it is attempting deploy
03:29:17  <jesusabdullah>harbhub: cool
03:29:39  <harbhub>:)
03:29:43  <jesusabdullah>jaha: supposedly there's a way to get it to attach to multiple apps, but like I said I need to see this first-hand
03:30:11  <mmalecki>jaha: hm, I can say that it worked for me
03:30:16  <harbhub>new error: subscription limit reached
03:30:17  <harbhub>o.0
03:30:25  <mmalecki>jaha: let me give it a try now
03:30:30  <jesusabdullah>jaha: I'm going to talk to the front-end guys as soon as I can to try and figure out wtf, I've had too many people tlell me they're getting confused
03:31:30  <jesusabdullah>harbhub: dev sandbox has a max of one drone now
03:31:40  <jaha>mmalecki: thanks, yea i just really need to figure this out, i have a couple apps id like to put into production but im not even sure how i am going to be billed ;)
03:31:42  <harbhub>never had that before lol
03:31:45  <jesusabdullah>harbhub: try destroying the old app
03:31:53  <harbhub>i am doing that :)
03:32:05  <jesusabdullah>harbhub: yeah, it's pretty new, we just opened up billing like a week ago, maybe two?
03:32:10  <mmalecki>jaha: the 11/month (large) is letting me attach more than one app
03:32:20  <mmalecki>also, 3/month is for one app only
03:32:25  <jesusabdullah>mmalecki: it is?
03:32:34  <mmalecki>jesusabdullah: yeah
03:32:34  <jesusabdullah>when did that happen /o\
03:32:36  <jesusabdullah>uuugh
03:33:15  <harbhub>whoa
03:33:20  <harbhub>you guys integrated with mongohq
03:33:29  <jaha>mmalecki: yea so thats what i thought, hence why ive got like 5 on the LARGE plan now, how can I control the drones on it?
03:33:30  <harbhub>i can create a mongohq database from the UI
03:33:32  <harbhub>o.0
03:34:00  * standoojoined
03:34:23  <jaha>harbhub: yea you can, but might i suggest creating one on the mongohq site first then hooking it up into your app, their DB admin UI is amazing
03:34:41  <harbhub>you can suggest that
03:34:57  <harbhub>i will look at both options, thanks for your input
03:35:29  <jaha>harbhub: unless you can figure out how to get that UI with the jitsu created DB, then please let me know ;)
03:36:03  <harbhub>that is more up to the jitsu team than me lol
03:36:17  <harbhub>but sure, i'll let you know how i approach it
03:36:31  * st_lukejoined
03:40:11  * derpopsquit
03:41:37  <harbhub>lol
03:43:30  * admcjoined
03:49:46  * chrisdotcodejoined
03:52:56  * coen-hydejoined
04:02:13  * bradleymeckjoined
04:04:51  * davidbanhamjoined
04:07:39  * RabidFirejoined
04:09:42  * marshall_lawchanged nick to marshall_afk
04:13:49  * coderarityquit (Ping timeout: 252 seconds)
04:14:00  * TheJHquit (Ping timeout: 245 seconds)
04:21:31  * harbhubquit (Ping timeout: 245 seconds)
04:22:01  * jahaquit (Quit: Leaving.)
04:29:15  * AvianFlujoined
04:36:54  * coderarityjoined
04:38:13  * _ddgbotquit (Remote host closed the connection)
04:39:39  * coderarityquit (Client Quit)
04:40:01  * _ddgbotjoined
04:40:34  * _ddgbotquit (Remote host closed the connection)
04:41:33  * _ddgbotjoined
04:43:52  * cjmquit (Ping timeout: 245 seconds)
04:43:56  * cjm_joined
04:49:33  * derpopsjoined
04:56:22  * cjm_quit (Remote host closed the connection)
04:56:38  * Frippejoined
05:02:14  * yawnt[out]changed nick to yawnt
05:04:17  * Frippequit (Quit: ^D)
05:04:20  * taurenjoined
05:04:27  * taurenquit (Client Quit)
05:08:45  * shykeschanged nick to zz_shykes
05:09:40  * sreeixjoined
05:12:45  * AvianFluquit (Remote host closed the connection)
05:16:09  * hpe1joined
05:18:39  * sreeixquit (Quit: sreeix)
05:25:16  * sreeixjoined
05:30:24  * bradleymeckquit (Quit: bradleymeck)
05:31:34  * hpe1quit (Quit: Leaving.)
05:41:14  * sreeixquit (Quit: sreeix)
05:41:38  * mmaleckichanged nick to mmalecki[zzz]
05:47:24  * joshonthewebjoined
05:49:17  * admcquit (Ping timeout: 255 seconds)
05:50:38  * admcjoined
05:54:31  * coen-hydequit (Quit: coen-hyde)
05:59:09  * derpopsquit
06:05:11  * doubletapquit (Quit: Leaving.)
06:05:35  * st_lukequit (Remote host closed the connection)
06:06:55  * graeme_fjoined
06:12:04  * tonymilnequit (Quit: tonymilne)
06:12:13  * joshsmithjoined
06:13:17  * RabidFirequit (Quit: RabidFire)
06:13:37  * sreeixjoined
06:24:22  * st_lukejoined
06:24:30  * ccowanquit (Quit: Leaving.)
06:25:42  * timoxley_joined
06:33:23  * admcquit (Quit: Leaving.)
06:36:47  * marciopugaquit (Remote host closed the connection)
06:41:44  * timoxley_quit (Quit: Computer has gone to sleep.)
06:41:44  * toonketelsjoined
06:46:38  * chrisdotcodequit (Ping timeout: 240 seconds)
06:48:18  * mdedetrichquit (Ping timeout: 240 seconds)
06:51:02  * thepumpkinquit (Remote host closed the connection)
06:56:48  * st_lukequit (Remote host closed the connection)
07:00:48  * joshsmithquit (Quit: joshsmith)
07:01:43  * dob_joined
07:04:46  * zz_shykeschanged nick to shykes
07:04:48  * sreeixquit (Quit: sreeix)
07:10:04  * admcjoined
07:15:14  * stagasjoined
07:18:03  * sreeixjoined
07:22:49  * sorensojoined
07:26:37  * ktkNAchanged nick to ktk
07:34:06  * blakmatrixquit (Remote host closed the connection)
08:01:12  * davidbanhamquit (Remote host closed the connection)
08:02:46  * davidbanhamjoined
08:08:33  * graeme_fquit (Quit: Computer has gone to sleep.)
08:12:48  * yawntchanged nick to yawnt[away]
08:18:20  * sorensoquit (Ping timeout: 265 seconds)
08:18:51  * standoopart
08:21:18  * admcquit (Quit: Leaving.)
08:23:12  * admcjoined
08:24:12  * davidbanhamquit (Remote host closed the connection)
08:25:57  * graeme_fjoined
08:32:17  * bengourleyjoined
08:37:11  * graeme_fquit (Quit: Computer has gone to sleep.)
08:48:44  * yawnt[away]changed nick to yawnt
08:49:44  * cjmjoined
08:49:54  * sreeixquit (Quit: sreeix)
08:58:18  * stagasquit (Quit: ChatZilla 0.9.89-rdmsoft [XULRunner 1.9.0.17/2009122204])
09:14:33  * shykeschanged nick to zz_shykes
09:20:04  * ebrightjoined
09:25:27  * TheJHjoined
09:28:06  * admcquit (Quit: Leaving.)
09:29:29  * eldiosjoined
09:30:27  * dob_quit (Remote host closed the connection)
09:36:42  * YoYquit (Quit: Leaving...)
09:38:09  * YoYjoined
09:39:43  * TheJHquit (Read error: Operation timed out)
09:40:12  * sorensojoined
09:42:54  * sreeixjoined
09:56:26  * mappumquit (Ping timeout: 246 seconds)
10:01:08  * davidbanhamjoined
10:18:09  * graeme_fjoined
10:22:42  * yawntchanged nick to yawnt[eatah]
10:23:46  * RabidFirejoined
10:23:49  * ohamajoined
10:27:00  * robhawkesjoined
10:47:44  * mmalecki[zzz]changed nick to mmalecki
10:55:05  * tm_joined
11:05:41  * tm_quit (Ping timeout: 245 seconds)
11:06:22  * pooriaazimijoined
11:11:16  * thepumpkinjoined
11:13:47  * sorensoquit (Ping timeout: 265 seconds)
11:14:52  * Gergelyjoined
11:14:59  <Gergely>hello,
11:15:16  <Gergely>i have an interesting error while deloying
11:15:22  <Gergely>can anyone help me ?
11:27:58  * sorensojoined
11:28:08  <lmjabreu>hey guys, I've been having some issues with jitsu cli -> https://gist.github.com/3952078
11:29:03  <lmjabreu>latest node, jitsu. already reinstalled and etc, works fine on another machine so it's not an issue with the package.json or project
11:29:42  * pgtejoined
11:31:49  * pooriaazimjoined
11:31:49  * pooriaazimquit (Client Quit)
11:33:51  * ArxPoeticajoined
11:34:22  <mmalecki>Gergely: hey, what's up?
11:34:26  * Gergelyquit (Ping timeout: 245 seconds)
11:34:26  * mdedetrichjoined
11:34:34  * pooriaazimiquit (Ping timeout: 255 seconds)
11:34:49  <mmalecki>lmjabreu: that's weird, did you try removing and installing it again?
11:34:57  <mmalecki>also, what's your node version?
11:36:20  * graeme_fquit (Quit: Computer has gone to sleep.)
11:37:47  * hallasjoined
11:39:36  * pooriaazimijoined
11:42:59  * sorensoquit (Quit: Computer has gone to sleep.)
11:43:18  <ArxPoetica>civicseed-testing <— anybody feel like giving that a kick start?
11:43:28  <ArxPoetica>I keep getting socket hang ups...
11:44:06  <ArxPoetica>(It was running last night, but I needed to restart to test something.)
11:44:37  * ArxPoeticapart
11:44:38  * ArxPoeticajoined
11:45:41  <ArxPoetica>yesterday jesusabdullah did something magical to get it running
11:46:12  <mmalecki>ArxPoetica: looking
11:46:13  <lmjabreu>mmalecki: yeah I have. node 0.8.12
11:47:50  <ArxPoetica>ope…it looks like a redis prob
11:47:56  <ArxPoetica>the logs are working today :P
11:48:12  <ArxPoetica>(weren't working yesterday)
11:48:24  <ArxPoetica>Error: Auth error: ERR max number of clients reached
11:48:24  <ArxPoetica>at Command.RedisClient.do_auth.self.send_anyway [as callback]
11:48:55  <mmalecki>lmjabreu: can you try doing `sudo rm -rf /usr/local/lib/node_modules/jitsu && sudo npm -g i jitsu`?
11:49:17  <ArxPoetica>I know you were having AWS service outage...
11:49:27  <lmjabreu>that's what I'm doing, just noticed there was something else wrong
11:49:30  <ArxPoetica>I might just turn off redis for now
11:49:46  <mmalecki>ArxPoetica: redis to go has been having problems for days now :(
11:49:55  <mmalecki>their API still doesn't let us create databases
11:50:04  <ArxPoetica>yeah
11:50:09  <mmalecki>we're working on a permanent solution tho
11:50:11  <ArxPoetica>I'm just going to turn it off
11:50:17  <ArxPoetica>I don't need it *quite yet*
11:50:23  <ArxPoetica>that's good
11:52:13  * garrettwilkinjoined
11:52:36  * yawnt[eatah]changed nick to yawnt
11:53:44  * sreeixquit (Quit: sreeix)
11:54:35  * graeme_fjoined
11:56:10  <lmjabreu>mmalecki: yeah that fixed it thanks. Have a PATH issue though, or something, where should npm be storing -g modules?
11:56:30  * sorensojoined
11:57:09  <lmjabreu>nvm
11:58:09  * ferloresjoined
11:58:34  <ArxPoetica>it's running now (with Redis turned off)
11:59:42  * standoojoined
11:59:50  * standooquit (Client Quit)
12:02:31  * hallasquit (Quit: ["Textual IRC Client: www.textualapp.com"])
12:09:24  <mmalecki>ferlores: oh, hey, didn't realize you were here
12:09:42  <mmalecki>I'm getting "Script took too long to listen on a socket"
12:09:46  <mmalecki>but creating snapshot worked
12:09:48  * AvianFlujoined
12:09:55  <mmalecki>so removing node_modules2 was a good call
12:10:33  <mmalecki>ferlores: what port are you listening on?
12:14:24  <ferlores>mmalecki, 8080
12:14:44  <ferlores>yes, now I can see an snapshot :D
12:15:10  <ferlores>would be nice to document somewhere that we cannot have a folder called node_module2 :D
12:15:45  <mmalecki>well, you can, but your folder was so big we couldn't upload it to the build server reliably
12:17:08  <mmalecki>ferlores: okay, looks like we had some slow servers in the pool, next time you start the app everything should be fine
12:18:22  <bengourley>Hi AvianFlu: did you get anywhere with my EAGAIN …etc errors yesterday?
12:25:37  <AvianFlu>bengourley: so, have you seen your app fail to load from this, or has it just turned up in your logs?
12:25:40  * sorensoquit (Quit: ["Textual IRC Client: www.textualapp.com"])
12:25:55  <AvianFlu>it seems like it's just some poorly handled file descriptor closing, but I wasn't actually seeing it make requests fail
12:26:04  <AvianFlu>it's like, it fails closing the fd after it's already done
12:26:11  <bengourley>Well sometimes the assets 404 or 500, and sometimes the wrong asset gets served
12:26:24  <bengourley>e.g request a js file, get back 200 OK and the contents of a .gif
12:30:00  <ferlores>mmalecki, I've deployed again, the snapshot was created and i cann access to the app but the jitsu command always says socket hangup
12:30:09  <ferlores>can*
12:30:36  <AvianFlu>bengourley: okay, wow, that's probably a bug in all this heavy caching that st does
12:30:52  <AvianFlu>I'll have to keep watching it
12:30:59  <AvianFlu>the fails I saw yesterday never actually caused failures
12:31:25  <AvianFlu>ferlores: that's a client-side timeout
12:31:31  <AvianFlu>you can raise the timeout value in your .jitsuconf
12:32:32  <ferlores>AvianFlu, I will do, thanks
12:32:33  * mmaleckichanged nick to mmalecki[away]
12:32:34  <bengourley>AvianFlu: If you can look back in the logs, it was serving the wrong asset at 12.20am this morning, uk time
12:34:14  * hpe1joined
12:35:18  <AvianFlu>okay, cool
12:35:32  <AvianFlu>actually, I can't retroactively trace syscalls
12:35:42  <bengourley>bugger
12:35:46  <AvianFlu>I'll set up a probe this morning so I can keep them around
12:35:51  <AvianFlu>log it to disk and all that
12:36:01  <bengourley>what timezone are you in?
12:36:08  <AvianFlu>NY
12:37:18  <bengourley>Ok, so it's 8.30am for you?
12:37:24  <AvianFlu>yeah
12:41:07  <bengourley>AvianFlu: it's happening now…
12:41:10  <bengourley>http://iowmcc.jit.su/static/javascripts/navigation.js
12:41:19  <bengourley>serving a PNG!
12:41:52  * ArxPoeticaquit (Quit: Leaving.)
12:45:09  * hpe1quit (Quit: Leaving.)
12:47:42  <AvianFlu>I saw the .js file just now
12:48:06  <bengourley>As well as the png?
12:51:32  <AvianFlu>well when I clicked that link to the .js file you pasted
12:51:34  <AvianFlu>I saw .js code
12:51:47  <AvianFlu>make a few requests, I'm watching the calls now
12:58:25  * sreeixjoined
12:58:26  * hpe1joined
12:58:49  * davidbanhamquit (Remote host closed the connection)
13:11:04  * pgtequit (Remote host closed the connection)
13:11:34  <AvianFlu>bengourley: I've got it logging them to disk, when I get to the office we'll take a look at the output
13:11:51  * AvianFluquit (Remote host closed the connection)
13:12:25  * VLijoined
13:18:40  * hpe1quit (Quit: Leaving.)
13:18:58  * cronopioquit (Quit: leaving)
13:21:15  * pooriaazimiquit (Remote host closed the connection)
13:22:01  * pooriaazimijoined
13:24:46  * testingjoined
13:28:49  * cronopiojoined
13:31:44  * pooriaazimjoined
13:33:10  * pooriaazimquit (Client Quit)
13:34:07  * pooriaazimiquit (Ping timeout: 260 seconds)
13:34:25  * derpopsjoined
13:35:12  * derpopsquit (Client Quit)
13:37:31  * ramitosquit (Read error: Operation timed out)
13:38:07  * Killixjoined
13:39:01  * derpopsjoined
13:41:16  <Killix>hi all
13:45:13  * thurmda2joined
13:48:02  * coderarityjoined
13:49:04  <Killix>i try to use this route : https://gist.github.com/e0c2559e148f6876d209, but firts don't work, any idea ?
13:51:45  * ramitosjoined
13:53:01  * ArxPoeticajoined
13:53:42  * hpe1joined
13:54:29  * mdedetrichquit (Quit: Computer has gone to sleep.)
13:54:50  * thl0joined
13:56:41  * jcrugzzquit (Remote host closed the connection)
13:57:05  * mdedetrichjoined
14:00:05  * bradleymeckjoined
14:06:47  * thurmda2quit (Quit: Leaving.)
14:13:05  * hpe1quit (Quit: Leaving.)
14:14:26  * sorensojoined
14:15:54  * papachanjoined
14:16:17  * mdedetrichquit (Quit: Computer has gone to sleep.)
14:18:08  * sppericatjoined
14:19:40  * TheJHjoined
14:23:08  * cronopioquit (Ping timeout: 246 seconds)
14:24:26  * redir_joined
14:28:24  * VLipart
14:33:00  * redirquit (Quit: Textual IRC Client: www.textualapp.com)
14:33:01  * redir_changed nick to redir
14:35:17  * hofbraujoined
14:35:28  * garrettwilkinquit (Quit: garrettwilkin)
14:35:42  * hofbrauquit (Client Quit)
14:36:51  * hofbraujoined
14:37:06  <hofbrau>hello
14:37:15  <hofbrau>anyone here from the support team ?
14:37:31  <bradleymeck>hofbrau: whats up
14:38:43  <hofbrau>most of the time i got an error : 'socket hagn up' while deploying, about 1 out of 10 times
14:39:35  * doubletapjoined
14:40:03  <hofbrau>do you have any idea what can be the cause ?
14:41:47  * thurmda2joined
14:42:08  <bradleymeck>hofbrau it may be memory consumption. we are working on a fix so we can reduce the npm startup that blows up memory usage somewhat inconsistently
14:42:52  <bradleymeck>but memory bugs are tough fixes, the alternative is to resize vms after startup which we are not really keen on due to some stability issues
14:43:16  <hofbrau>any tips/tricks how can i avoid this problem ?
14:43:22  * cronopiojoined
14:44:46  <bradleymeck>hofbrau: for now the problem is known but no easy sure fire workarounds, you can use a bash script to redeploy really fast, run a deploy and if it fails activate the snapshot and start the app in a loop
14:47:07  * marshall_afkchanged nick to marshall_law
14:47:08  <hofbrau>what do you think, can you fix this issue soon ? we are in the process of starting something new, but we need a stable platform on which we can build
14:47:45  <hofbrau>now, we try to deploy to your free plan, but if i change to a dedicated plan, is it still a problem ?
14:48:16  <bradleymeck>hofbrau: the platform is stable, the memory consumption in dynamic languages is the issue, we will probably have a workaround in place on our side this weekend and it fixed next week
14:49:44  * jahajoined
14:49:59  * alucardXjoined
14:50:01  * CRONOPIO_joined
14:50:54  * anoemijoined
14:52:51  * cronopioquit (Ping timeout: 268 seconds)
14:53:18  <hofbrau>so is it a problem in bigger plans as well ?
14:53:19  * loktarpart
14:54:31  <ArxPoetica>I was having socket hang ups too...
14:54:42  * CRONOPIO_quit (Ping timeout: 268 seconds)
14:54:45  <ArxPoetica>but then figured out it was related more to the AWS and redis outages
14:55:05  <bradleymeck>hofbrau: it is a problem in all plans, we have sliced vms to 256mb and npm sometimes blows up to 200~MB when starting up
14:56:03  <ArxPoetica>hofbrau — do you have any redis in your sockets app?
14:56:07  <ArxPoetica>check your connections
14:56:17  <bradleymeck>so we are remaking npm's functionality but stripped down to just starting stuff with much less memory usage
14:56:50  <hofbrau>okay
14:57:02  <hofbrau>yes, i use redis
14:57:19  <bradleymeck>we can start apps in a bootstrap under 2mb it looks like consistently, but we cannot roll that out until some testing is finished
14:57:44  * thurmda2quit (Quit: Leaving.)
14:57:59  <ArxPoetica>yeah, I turned off Redis in mine and stopped getting hang ups — it's another issue Nodejitsu is working on.
14:58:06  <ArxPoetica>Since there's been AWS outage.
14:58:21  <ArxPoetica>Unfortunately, that might not be an option for everyone.
14:58:22  <bradleymeck>plenty of work :)
14:58:39  * doubletapquit (Quit: Leaving.)
14:58:39  <bradleymeck>eventually we will just read your mind for when to deploy haha
14:58:45  <ArxPoetica>ha
14:59:30  <ArxPoetica>What are the blue stars as opposed to the gold shields with stars? :P
14:59:57  * indexzerojoined
15:00:00  <bradleymeck>?
15:00:36  <Killix>anyone for my issue route : https://gist.github.com/e0c2559e148f6876d209, please ? i use flatiron
15:02:15  * sreeixquit (Read error: Connection reset by peer)
15:02:32  * sreeixjoined
15:02:32  <bradleymeck>killfill: var statements arent shared between functions, what does the error say?
15:04:44  <Killix>bradleymeck: killfill or killix ? ;)
15:04:55  * hofbrauquit (Quit: Page closed)
15:04:56  <bradleymeck>killix* sorry :)
15:06:09  <Killix>in the first case, the next function isn't work for do that i need to user the custom callback passport
15:06:22  <Killix>s/work/run
15:06:42  <Killix>s/user/use (sorry)
15:08:58  <bradleymeck>Killix I would need to see how you are adding these middleware for more info, https://github.com/travist/flatiron-passport may ease things for you though
15:09:37  <Killix>and I just discovered that there is the only basic strategy is executed, then nothing, it would seem that the next function does not work in passport ...
15:09:43  <Killix>i use flatiron-passport
15:09:48  <Killix>for adding middle where
15:09:58  <Killix>grmbl
15:10:04  <Killix>middleware
15:12:50  * thurmda2joined
15:13:08  * sppericatquit (Quit: sppericat)
15:14:16  * _pantsjoined
15:14:51  <_pants>Trying to deploy my app on nodejitsu for the first time and it's failing with https://gist.github.com/3953257
15:14:53  * st_lukejoined
15:15:07  <_pants>Anyone have a sec to take a look?
15:17:38  <bradleymeck>_pants: have you tried to redeploy, there is an npm memory consumption bug we are trying to iron out right now, until we replace npm with a shim deploys will have a chance of failure
15:17:42  * mmalecki[away]changed nick to mmalecki
15:18:12  * bardujoined
15:18:35  <_pants>bradleymeck: Thanks for the update, I figured it might be something like that but didn't see anything at https://twitter.com/statjitsu. I've tried redeploying 3 times with the same result
15:18:40  * fatjonnyjoined
15:20:34  <bradleymeck>_pants: it may be something else ill take a look one second
15:20:49  <_pants>bradleymeck: hey, thanks so much
15:21:30  <_pants>the repo is on github at github.com/getlantern/lantern-ui
15:21:35  <_pants>start script is https://github.com/getlantern/lantern-ui/blob/master/scripts/web-server.js
15:22:34  <bradleymeck>_pants: try now
15:23:18  <_pants>trying
15:23:24  * barduquit (Read error: Connection reset by peer)
15:24:02  <_pants>bradleymeck: same result. but took a lot less time for the socket to time out this time.
15:26:23  <bradleymeck>mmmm
15:26:27  <ebright>hi guys, I'm unsure about something. Does Winston have a CouchDB transport out of the box, or do I need to npm install & require winston-couchdb?
15:28:58  * cpjolicoeurjoined
15:29:18  * AvianFlujoined
15:29:30  <cpjolicoeur>I have not been able to successfully "jitsu deploy" all morning
15:29:36  <cpjolicoeur>constant socket hang up errors
15:30:07  <AvianFlu>cpjolicoeur: are they local timeouts or remote hangups? please gist the output you get
15:30:22  * graeme_fquit (Quit: Computer has gone to sleep.)
15:30:38  <cpjolicoeur>how can I tell? https://gist.github.com/3953357
15:31:25  <AvianFlu>cpjolicoeur: if it were remote, it would say "error returned from nodejitsu"
15:31:31  <AvianFlu>that's just you hitting the 8-minute upload timeout
15:31:37  <AvianFlu>the app may have started successfully after that message
15:31:47  <AvianFlu>how big is the app directory?
15:32:22  <cpjolicoeur>so how can I tell if it was successful and the app started, if it tells me it failed?
15:32:47  <AvianFlu>check the subdomain right after - you can also change the timeout in jitsu
15:32:54  <groovecoder>I'm still getting https://gist.github.com/3918723 which I was told was a problem with hiredis.
15:33:02  <groovecoder>but the hiredis is part of socket.io
15:33:04  <cpjolicoeur>so the timeout is a local config setting you are saying?
15:33:15  <AvianFlu>cpjolicoeur: yeah, in your .jitsuconf
15:33:20  <AvianFlu>try `jitsu config list`
15:33:22  * coderarityquit (Ping timeout: 245 seconds)
15:33:31  * c4milojoined
15:33:40  <AvianFlu>groovecoder: use a newer socket.io version
15:33:45  <AvianFlu>or master from git
15:33:50  <cpjolicoeur>sure, i'm familiar with my local config, is there a place describing available config options
15:34:33  <AvianFlu>cpjolicoeur: https://github.com/nodejitsu/jitsu#jitsuconf-file
15:34:59  <cpjolicoeur>the default is 8 minutes you are saying? my deploy reuqests are ending in more like 2-3 minutes, not 8, just FYI if that matters
15:36:13  <AvianFlu>what's it set to for you locally?
15:36:18  <AvianFlu>try `time jitsu deploy` next time
15:36:25  <cpjolicoeur>its not even in my config at all
15:36:31  <cpjolicoeur>i have never overridden it
15:36:36  * vekexasiajoined
15:36:40  <vekexasia>hello all
15:36:44  <vekexasia>I'm having a problem with hiredis
15:36:45  <AvianFlu>so, `jitsu config set timeout 12000`
15:37:02  <vekexasia>jitsu deploy does not install it
15:37:04  <cpjolicoeur>ok, i'll keep playing with it. thx
15:37:22  <cpjolicoeur>its in milliseconds i assume?
15:37:28  <AvianFlu>cpjolicoeur: yeah
15:37:30  <cpjolicoeur>k
15:37:40  <AvianFlu>so that value I gave you is terrible actually, lol
15:37:45  <vekexasia>can someone help me with hiredis & nodejitsu ?
15:37:51  <AvianFlu>vekexasia: try to use the version of socket.io from master
15:37:52  <cpjolicoeur>AvianFlu: sure, I get the idea tho
15:37:59  <cpjolicoeur>i'll keep playing around
15:38:00  <vekexasia>AvianFlu it's not socket.io
15:38:10  <AvianFlu>vekexasia: use newer redis
15:38:14  * thurmda2quit (Quit: Leaving.)
15:38:16  <vekexasia>it's hiredis ?
15:38:17  <AvianFlu>hiredis won't work on SmartOS, period
15:38:25  <_pants>bradleymeck: Any other ideas?
15:38:39  <vekexasia>So what am i suppoused to use?
15:38:44  <bradleymeck>_pants: someone is looking at it, may be working now
15:39:02  <bradleymeck>vekexasia: 'redis' has a JS parser thats equivilant in perf
15:39:08  * garrettwilkinjoined
15:39:18  <vekexasia>bradleymeck apparently it does not work
15:39:28  <vekexasia>i'm having troubles with multi
15:39:32  <bradleymeck>vekexasia: hiredis does not
15:39:36  <bradleymeck>redis should
15:39:38  <vekexasia>using hiredis
15:39:44  <vekexasia>it works
15:42:02  <groovecoder>AvianFlu: I'm using latest socket.io in npm. what's the easiest way to update it to github's master?
15:42:56  <AvianFlu>groovecoder: in your package.json, replace "socket.io": "x.y.z" with "socket.io": "https://github.com/LearnBoost/socket.io/tarball/master"
15:43:06  <AvianFlu>you can tell it to grab from a tarball like that, instead of the npm registry
15:43:31  * generalissimojoined
15:43:52  <vekexasia>indeed
15:43:54  <vekexasia>it does not work
15:44:19  <vekexasia>using the javascript parser of redis with "MULTI + EXEC"
15:44:22  <vekexasia>causes issues
15:44:28  <vekexasia>using hiredis => works
15:44:33  <vekexasia>so I cant use hiredis
15:44:54  <AvianFlu>not on SmartOS
15:44:59  <AvianFlu>it very simply won't run
15:45:07  <AvianFlu>it forces itself to compile for the wrong arch
15:45:15  <vekexasia>AvianFlu: I suppouse nodejitsu is on SmartOS
15:45:19  <AvianFlu>yeah
15:45:25  <vekexasia>so what am i suppoused to do ?
15:45:42  <AvianFlu>for starters, look through the issue trackers for redis and hiredis
15:45:44  <vekexasia>i cannot leverage the multi + exec stuff ?
15:45:50  <AvianFlu>there might be better info
15:46:03  <AvianFlu>but I mean, what's wrong with the multi + exec stuff?
15:46:11  <AvianFlu>what issues do you get? what are you trying to do?
15:48:47  * sorensoquit (Ping timeout: 265 seconds)
15:49:34  <groovecoder>AvianFlu: new "socket hang up" error using socket.io master tarbal: https://gist.github.com/3918723
15:49:46  * papachanquit (Ping timeout: 244 seconds)
15:49:49  <AvianFlu>that's a local timeout
15:49:55  <AvianFlu>you should wait a few minutes and check the subdomain
15:50:02  <groovecoder>AvianFlu: k
15:50:03  <AvianFlu>you should also add a `timeout` to your jitsu config
15:50:06  <AvianFlu>make it big
15:50:13  <AvianFlu>12 minutes worth of milliseconds, or something
15:50:47  * cronopiojoined
15:51:00  <vekexasia>AvianFlu: it's rather simple I do Multi + hmset + zadd
15:51:05  <vekexasia> + exec.
15:51:18  <vekexasia>then I do smembers of the zadd
15:51:25  <vekexasia>and 40% of the members are "null"
15:51:37  <vekexasia>if i use hiredis
15:51:43  <vekexasia>the error goes away
15:52:13  <mmalecki>vekexasia: did you open an issue/find one?
15:52:29  <mmalecki>I'm willing to help with solving it
15:52:41  * mappumjoined
15:52:46  <groovecoder>AvianFlu: do I need to redeploy with the new timeout value? or just wait for the first deploy?
15:53:03  <AvianFlu>wait for the first, change the timeout for future deploys
15:53:04  <AvianFlu>that's the idea
15:53:11  <groovecoder>AvianFlu: got it. waiting.
15:54:01  <AvianFlu>check the url, though, it should be good by now
15:54:06  <AvianFlu>if not try again and I'll watch the logs
15:54:47  * toonketelsquit (Remote host closed the connection)
15:55:41  <_pants>bradleymeck: Still no dice. Any way I can get some more help with this?
15:56:03  <bradleymeck>_pants: sec, got side tracked with a db issue
15:56:34  <cpjolicoeur>AvianFlu: even after setting my timeout to 480000 (8 minutes), the deploys still fail and only run for under 3 minutes. You can see the log and time results here: https://gist.github.com/3953613
15:57:12  <AvianFlu>cpjolicoeur: what jitsu version?
15:57:17  * mappumquit (Ping timeout: 246 seconds)
15:57:34  <cpjolicoeur>0.9.8
15:58:11  * slloydjoined
15:58:48  <groovecoder>AvianFlu: works now after re-deploying. thanks
15:58:51  * Nodejitsu-Githubjoined
15:58:51  <Nodejitsu-Github>[jitsu] AvianFlu pushed 1 new commit to master: http://git.io/7Izc-Q
15:58:51  <Nodejitsu-Github>[jitsu/master] [dist] Version bump, v0.10.0 - Charlie McConnell
15:58:51  * Nodejitsu-Githubpart
15:58:59  <AvianFlu>cpjolicoeur: I was mistaken
15:59:03  <AvianFlu>we didn't release the timeout fix
15:59:08  <AvianFlu>please install the new one and then try it again
15:59:13  <AvianFlu>it's now published
15:59:20  <AvianFlu>maybe `npm cache clear` first to be sure
15:59:39  * sreeixquit (Quit: sreeix)
15:59:50  <cpjolicoeur>ok, will do
16:00:01  <vekexasia>https://gist.github.com/cb6563d10389cb9a5754 AvianFlu
16:00:04  <vekexasia>can you test this ?
16:00:16  <vekexasia>mmalecki:
16:00:35  <vekexasia>if you launch this
16:00:44  <vekexasia>most of the times
16:00:52  <vekexasia>the last smembers result are "null"
16:00:57  <vekexasia>while sometimes are not
16:01:20  <mmalecki>vekexasia: hold up
16:01:27  <vekexasia>yes
16:01:37  * bradleymeckquit (Read error: Connection reset by peer)
16:01:43  <mmalecki>you shouldn't be sendind commands before db authenticates
16:01:56  * bradleymeckjoined
16:01:59  <mmalecki>n line 14 you start authenticating
16:02:12  * ramitosquit (Read error: Connection reset by peer)
16:02:13  <vekexasia>hmm yes sorry. But mine is not auth
16:02:18  <vekexasia>so that's not the issue.
16:02:36  <mmalecki>okay, let me set it up and run locally
16:02:53  <jaha>Error I havent seen yet: https://gist.github.com/3953656
16:03:09  <vekexasia>https://gist.github.com/cb6563d10389cb9a5754
16:03:17  <vekexasia>mmalecki: try that one
16:03:43  <jaha>also how do you assign more than 1 drone to an app?
16:06:35  <cpjolicoeur>AvianFlu: I updated to 0.10.0 - deploy fails (much quicker this time) with different log output: https://gist.github.com/3953675
16:07:04  <AvianFlu>cpjolicoeur: yeah that's something new, just give us a moment
16:07:14  <cpjolicoeur>sure, no worries. just pasting for your info
16:07:39  * chrisdotcodejoined
16:08:52  * ramitosjoined
16:09:58  * YoYquit (Ping timeout: 260 seconds)
16:11:54  <vekexasia>are you there?
16:11:58  <vekexasia>mmalecki:
16:12:08  * YoYjoined
16:13:00  <mmalecki>vekexasia: sec epicly busy
16:13:09  <vekexasia>ok
16:13:36  * RabidFirequit (Quit: RabidFire)
16:13:42  * Tam2joined
16:14:01  <bradleymeck>always forget who storifi is on irc… /me wishes names always were the same
16:14:19  <Tam2>storifi is one of mine
16:15:42  <Tam2>It's what i came on to ask about, the deploy's are still failing alot
16:15:48  * c4miloquit (Remote host closed the connection)
16:16:05  <AvianFlu>cpjolicoeur: you should try again
16:16:10  <AvianFlu>that specific error should now be gone
16:16:43  * graeme_fjoined
16:16:46  <cpjolicoeur>ok, trying now
16:16:50  * c4milojoined
16:18:18  * c4miloquit (Remote host closed the connection)
16:18:23  * Nodejitsu-Githubjoined
16:18:23  <Nodejitsu-Github>[jitsu] AvianFlu pushed 2 new commits to master: http://git.io/6u9rVw
16:18:23  <Nodejitsu-Github>[jitsu/master] [fix] _bytesDispatched sometimes is bigger than packages for small packages.. that crashes the progressBar - yawnt
16:18:23  <Nodejitsu-Github>[jitsu/master] [dist] Version bump, v0.10.1 - Charlie McConnell
16:18:23  * Nodejitsu-Githubpart
16:18:59  * c4milojoined
16:19:48  * wookiehangoverquit (Ping timeout: 268 seconds)
16:20:40  * sreeixjoined
16:20:43  <cpjolicoeur>AvianFlu: no dice. gets to "Starting app" for a while, then error'd with this new mssage: https://gist.github.com/3953777
16:21:00  <cpjolicoeur>definitely not waiting 8 minutes like is set in my config either.
16:21:17  <AvianFlu>cpjolicoeur: that's new copy for the exact same local timeout
16:21:21  <AvianFlu>is your timeout set?
16:21:28  <AvianFlu>the update might have overridden it, though I hope not
16:21:29  <cpjolicoeur>yes, its at the end of that recent jist
16:21:37  <cpjolicoeur>i put it there for reference
16:21:55  <AvianFlu>cpjolicoeur: can you `npm ls -g | grep nodejitsu-api` and show me the output?
16:22:13  <cpjolicoeur>cpjolicoeur $ npm ls -g | grep nodejitsu-api
16:22:14  <cpjolicoeur>│ ├── nodejitsu-api@0.3.4
16:22:58  <AvianFlu>cpjolicoeur: your deploy actually still hasn't finished, it's in progress
16:23:06  * cpjolicoeurquit (Remote host closed the connection)
16:23:24  * cpjolicoeurjoined
16:23:49  <cpjolicoeur>hmm. so what is the expected outcome? How can I know when the deploy finished and why does it take so long now when they didnt before?
16:24:16  <AvianFlu>cpjolicoeur: how recently was it faster
16:24:21  <AvianFlu>when did this change for you
16:24:31  * wompratjoined
16:24:36  <cpjolicoeur>i was deploying with no issues last week
16:24:41  <cpjolicoeur>(thursday , friday)
16:24:46  <cpjolicoeur>this is the first I've tried to deploy this week
16:25:17  <AvianFlu>what have you changed
16:25:29  <AvianFlu>try to think of any and all changes, it'll help track things down
16:25:47  <cpjolicoeur>in the app, nothing has changed. today I just added a 1 new file and altered one other
16:25:54  <AvianFlu>what was the new file for?
16:25:58  <cpjolicoeur>i didnt change any npm setup other than you having me upgrade jus tnow
16:26:16  <cpjolicoeur>its a zip file for download. but its just a new one. we have had others the past month
16:26:56  <cpjolicoeur>I guess I'm still curious how I can know from the client side when the app is deployed if the deploy scripts can terminate early
16:27:04  <cpjolicoeur>you mentioned it was still deploying?
16:27:07  <_pants>bradleymeck: Just tried again and finally get a more informative error: https://gist.github.com/3953257. Any idea why it couldn't find faye-websocket? It's right there at https://github.com/getlantern/lantern-ui/tree/master/mock/node_modules/faye/node_modules/faye-websocket
16:27:11  <_pants>works locally of coure
16:27:13  <_pants>course
16:29:16  <vekexasia>AvianFlu: did you take a moment to test that piece of code?
16:29:39  <bradleymeck>_pants: download your snapshot, run npm rebuild inside it and see if there is something missing
16:30:07  <yawnt>_pants: hey :)
16:30:11  <bradleymeck>also if you have done anything after installing an npm module like installing websocket plugin modules inside fay i would use bundledDependencies in your package.json
16:30:19  <bradleymeck>_pants ^
16:30:37  <yawnt>_pants: if you want apps to deploy remotely, you need to specify dependencies in package.json
16:30:42  <yawnt>_pants: like here -> http://package.json.jit.su/
16:31:09  <yawnt>_pants: so in your case you'd have to add "dependencies": {"faye-websocket": "*"}
16:31:15  <yawnt>_pants: to your package.json :)
16:31:28  <_pants>bradleymeck, yawnt: But my dependencies are just vendored inside my own repo.
16:33:03  <_pants>still looking for a way to download the snapshot. it's not linked from https://webops.nodejitsu.com/apps/lantern-ui
16:33:21  <yawnt>_pants: jitsu snapshots fetch <appName>
16:33:26  <_pants>thanks
16:34:14  <yawnt>_pants: if you want deps to be bundled, you have to add "bundledDependencies": ["faye-websocket"] to your package.json :)
16:34:40  <_pants>yawnt: thanks, i'll try it
16:34:56  <yawnt>_pants: you're welcome :)
16:35:57  * indexzeroquit (Quit: indexzero)
16:36:26  <_pants>yawnt: shoot, still got that same error
16:37:39  * coderarityjoined
16:38:09  <yawnt>_pants: add "faye-websocket" to "dependencies" and re-deploy
16:39:57  <_pants>yawnt: https://gist.github.com/3953908
16:40:24  <yawnt>_pants: the syntax is "dependencies": {"faye-websocket": "*"}
16:40:32  <_pants>oh, sorry
16:40:38  <yawnt>it's okay ;)
16:40:45  <jaha>jesusabdullah: I think I figured out what the app hanging from yesterday is https://github.com/LearnBoost/mongoose/issues/1033#issuecomment-7452727 apparently it is connect-mongodb causing all the headache
16:43:06  <_pants>yawnt: ok, this time is it still my fault? https://gist.github.com/3953929
16:43:47  * Sly[Tablet]quit (Ping timeout: 245 seconds)
16:44:16  * TooTallNatejoined
16:44:32  <yawnt>_pants: how big is your app?
16:45:20  <_pants>yawnt: ok, tried again and now got https://gist.github.com/3953945. should i add cookiejar to dependencies?
16:45:31  <yawnt>_pants: yes
16:45:36  <yawnt>_pants: how big is your application?
16:46:20  * clarkfischerjoined
16:47:28  <_pants>yawnt: the github zipball is 9.1 megs. unzipped it's 18. what's the max?
16:48:02  <yawnt>_pants: why is it so big?
16:50:42  <_pants>yawnt: it's an AngularJS app built from github.com/angular/angular-seed, as recommended. Angular-seed alone is over 12 megs
16:51:03  <CoverSlide>holy fuck
16:51:18  <CoverSlide>oh its a boilerplate
16:51:21  <CoverSlide>makes sense
16:51:30  <cpjolicoeur>when you all ask "how big is the app" what does that mean? uncompressed?
16:51:42  <cpjolicoeur>is there some kind of nodejitsu app limit for directory size?
16:52:17  <_pants>yawnt: ^
16:52:21  * anoemiquit (Quit: anoemi)
16:52:31  <yawnt>cpjolicoeur: well, it takes memory to decompress snapshots
16:52:32  * AvianFluquit (Remote host closed the connection)
16:52:50  <yawnt>if your app is too big, you're going to hit the memory limit and deploy fails
16:52:53  <cpjolicoeur>sure, but what is "too big"
16:53:03  <_pants>hey, it's running!
16:53:04  * RabidFirejoined
16:53:07  <_pants>wheeee!!!
16:53:12  <_pants>thanks for your help, yawnt
16:53:18  <yawnt>_pants: you're welcome
16:53:59  <_pants>yawnt: do i still need bundledDependencies as well as dependencies?
16:54:06  <yawnt>_pants: dependencies yes
16:54:23  <_pants>yawnt: i mean, just dependencies, i can take out bundled?
16:54:23  <yawnt>bundledDependencies only when you need your changes to faye-websockets to persist when you deploy
16:54:37  <yawnt>in your case.. no, you can just leave the dependencies and take out "bundledDependencies"
16:54:41  <_pants>thanks
16:55:11  <yawnt>cpjolicoeur: _pants anyway usually.. < 30 mega uncompressed should be okay
16:55:20  <_pants>great
16:56:33  * Sly[Tablet]joined
16:57:15  * lwicksjoined
16:59:41  * sreeix_joined
17:01:04  * sreeixquit (Ping timeout: 244 seconds)
17:01:05  * sreeix_changed nick to sreeix
17:04:10  * Tam2quit
17:05:25  * toonketelsjoined
17:05:28  <coderarity>!mdn Function.apply
17:05:28  <_ddgbot>https://developer.mozilla.org/search?q=Function.apply
17:06:14  * thl0quit (Ping timeout: 260 seconds)
17:09:42  * hpe1joined
17:09:44  * toonketelsquit (Ping timeout: 246 seconds)
17:10:15  * indexzerojoined
17:10:16  * indexzeroquit (Client Quit)
17:14:20  * clarkfischerquit (Ping timeout: 252 seconds)
17:15:44  * sorensojoined
17:16:32  * blakmatrixjoined
17:16:52  * sreeix_joined
17:17:22  * clarkfischerjoined
17:17:40  * hpe1quit (Ping timeout: 248 seconds)
17:17:57  * sreeixquit (Ping timeout: 245 seconds)
17:18:10  * sreeix_changed nick to sreeix
17:18:14  * hpe1joined
17:20:13  * benvjoined
17:21:21  <coderarity>!mdn setTimeout
17:21:22  <_ddgbot>https://developer.mozilla.org/search?q=setTimeout
17:21:27  * _pantspart
17:22:03  * ArxPoeticaquit (Quit: Leaving.)
17:32:20  * garrettwilkinquit (Quit: garrettwilkin)
17:34:04  * zz_shykeschanged nick to shykes
17:34:39  * Avastoujoined
17:35:25  * eldiosquit (Quit: bye =))
17:36:03  * Killixquit (Ping timeout: 260 seconds)
17:37:39  <vekexasia>someone here?
17:37:53  <yawnt>yes?
17:38:00  <vekexasia>eh ma se sei impegnato :)
17:38:10  <yawnt>eh c'est la vie
17:38:16  <yawnt>se è per nodejitsu posso aiutarti
17:38:19  <yawnt>altrimenti mi spiace :P
17:38:29  <vekexasia>nope è per redis. Ma mi basterebbe che lanciassi un test :(
17:38:42  <yawnt>english please ;)
17:38:57  <vekexasia>Nope it's for redis. I just need you to launch a test
17:39:01  <vekexasia>LOL
17:39:03  <vekexasia>:)
17:39:56  * joshonthewebquit (Quit: Computer has gone to sleep.)
17:40:02  * blakmatrixquit (Read error: Connection reset by peer)
17:40:37  * blakmatrixjoined
17:41:14  * bradleymeckquit (Quit: bradleymeck)
17:43:24  * bengourleyquit (Quit: bengourley)
17:44:05  * hpe1quit (Quit: Leaving.)
17:47:35  * st_lukequit (Remote host closed the connection)
17:48:05  * blissGonechanged nick to blissdev
17:48:07  * bengourleyjoined
17:48:43  * ArxPoeticajoined
17:51:11  * sreeixquit (Ping timeout: 244 seconds)
17:52:01  * sreeixjoined
17:53:06  * Sly[Tablet]quit (Quit: Bye)
17:54:33  * ArxPoeticaquit (Ping timeout: 264 seconds)
17:57:00  * hpe1joined
17:57:26  * njh__joined
17:57:43  * joshonthewebjoined
17:58:17  * sorensoquit (Quit: Computer has gone to sleep.)
17:58:54  * ArxPoeticajoined
18:00:53  * Heisenberg_joined
18:01:04  <Heisenberg_>hello
18:01:45  <yawnt>hi :)
18:01:49  <Heisenberg_>i am using express, and ran int oa problem.. i try to upload a picture to cloudinary using req.files
18:02:07  <Heisenberg_>but I get an error, that express cannot access the temporary file
18:02:47  <yawnt>Heisenberg_: can i see the error you're getting?
18:03:21  <Heisenberg_>sure
18:03:51  <Heisenberg_>i use : app.use(express.bodyParser({uploadDir:'./uploads'}));
18:03:56  <Heisenberg_>and the error msg is
18:03:58  * AvianFlujoined
18:04:01  * anoemijoined
18:04:04  <Heisenberg_>Error: ENOENT, open 'uploads/99a86d8caab5ee374167b0b41a9aa991' [10/25 15:23:28 GMT+0200] warn: error raised: Error: listen EADDRINUSE
18:05:07  * papachanjoined
18:05:10  <yawnt>can you try to change the path to ./uploads ?
18:06:19  * cronopioquit (Quit: leaving)
18:07:31  * cronopiojoined
18:09:23  <Heisenberg_>okay
18:09:29  <Heisenberg_>tryiing it ouy
18:09:31  <Heisenberg_>thanks
18:09:42  <Heisenberg_>by the way, do you want some meth ?
18:09:57  <Heisenberg_>sorry, to much breaking bad :D
18:10:31  * testingquit (Quit: Page closed)
18:12:39  * thepumpkinquit (Remote host closed the connection)
18:14:38  * Sly[Tablet]joined
18:16:24  * thl0joined
18:18:28  * chrisdotcodequit (Ping timeout: 248 seconds)
18:19:33  * evangenieurjoined
18:20:11  * Nodejitsu-Githubjoined
18:20:11  <Nodejitsu-Github>[nodejitsu-api] mmalecki pushed 3 new commits to master: http://git.io/eJfy5g
18:20:11  <Nodejitsu-Github>[nodejitsu-api/master] [fix] _bytesDispatched in node 0.9.x - yawnt
18:20:11  <Nodejitsu-Github>[nodejitsu-api/master] [fix] issue that sometimes caused the bar to behave wrongly - yawnt
18:20:11  <Nodejitsu-Github>[nodejitsu-api/master] Merge pull request #19 from yawnt/master - Maciej Małecki
18:20:11  * Nodejitsu-Githubpart
18:23:17  * hpe1quit (Quit: Leaving.)
18:24:11  * TooTallNatequit (Ping timeout: 245 seconds)
18:24:50  * c4miloquit (Remote host closed the connection)
18:26:04  * TooTallNatejoined
18:27:36  * njh__quit (Remote host closed the connection)
18:28:11  * njh__joined
18:31:05  * c4milojoined
18:32:09  * njh__quit (Ping timeout: 240 seconds)
18:35:26  * bradleymeckjoined
18:41:19  * jipiboilyquit (Read error: Connection reset by peer)
18:41:47  * lwicksquit (Ping timeout: 246 seconds)
18:43:38  * admcjoined
18:45:06  * garrettwilkinjoined
18:46:04  * hpe1joined
18:46:05  * sreeix_joined
18:46:23  * sreeixquit (Ping timeout: 255 seconds)
18:46:24  * sreeix_changed nick to sreeix
18:48:17  * shamajoined
18:49:53  * wesbosjoined
18:51:40  <Heisenberg_>hello again
18:52:02  <yawnt>hey ;)
18:52:04  <Heisenberg_>so i did that little tweak that you suggested me about req,files upload path
18:52:17  <Heisenberg_>but i get an error again
18:52:18  <Heisenberg_>An error has occurred: {"code":"ECONNRESET"}
18:52:29  <Heisenberg_>i think it is coming from mongo
18:52:30  <Heisenberg_>but
18:52:40  <Heisenberg_>every other funcion of the site works well
18:52:54  <Heisenberg_>i only get it when accessing that file
18:53:00  <Heisenberg_>so i have no idea :S
18:53:10  <yawnt>could you show me the logss?
18:53:18  <yawnt>`jitsu logs app <appName>`
18:54:02  * sorensojoined
18:54:12  <Heisenberg_>there is no new entry in there
18:54:23  <Heisenberg_>only the file access error from 2 hours ago
18:54:59  * st_lukejoined
18:55:28  * st_lukequit (Read error: Connection reset by peer)
18:55:47  * cronopioquit (Quit: Bye)
18:56:53  <yawnt>Heisenberg_: i see
18:57:00  <yawnt>could you give me your appname and username? thanks
18:57:20  * cronopiojoined
18:59:06  * Nodejitsu-Githubjoined
18:59:06  <Nodejitsu-Github>[jitsu] blakmatrix pushed 1 new commit to master: http://git.io/fQ4Ugg
18:59:06  <Nodejitsu-Github>[jitsu/master] [dist] bump for flatiron #343 - Farrin Reid
18:59:06  * Nodejitsu-Githubpart
19:01:09  * alucardX_joined
19:02:01  * cpjolicoeurchanged nick to twistshow
19:02:28  * jeffrgjoined
19:02:34  * twistshowchanged nick to cpjolicoeur
19:02:45  * cpjolicoeurquit (Quit: cpjolicoeur)
19:02:59  * cpjolicoeurjoined
19:03:30  * kenperkinsjoined
19:03:42  * cpjolicoeurpart
19:03:50  * cpjolicoeurjoined
19:04:21  * st_lukejoined
19:06:32  * wompratquit (Quit: Page closed)
19:07:21  * alucardXquit (Quit: leaving)
19:07:33  * wookiehangoverjoined
19:07:36  * alucardX_quit (Quit: leaving)
19:07:46  * kenperkinsquit (Client Quit)
19:09:25  * Nodejitsu-Githubjoined
19:09:25  <Nodejitsu-Github>[nodejitsu-api] blakmatrix pushed 1 new commit to master: http://git.io/eM3dEg
19:09:25  <Nodejitsu-Github>[nodejitsu-api/master] [dist] bump version for release adresses nodejitsu/jitsu#346 - Farrin Reid
19:09:25  * Nodejitsu-Githubpart
19:12:56  * Heisenberg_quit (Quit: Page closed)
19:15:56  * kevindentejoined
19:21:19  * papachanquit (Quit: Leaving)
19:22:10  <kevindente>Does Nodejitsu support scheduled background jobs?
19:22:21  * Nodejitsu-Githubjoined
19:22:21  <Nodejitsu-Github>[jitsu] blakmatrix pushed 1 new commit to master: http://git.io/_osObg
19:22:21  <Nodejitsu-Github>[jitsu/master] [dist] bump version of nodejitsu-api adresses nodejitsu/jitsu#346 - Farrin Reid
19:22:21  * Nodejitsu-Githubpart
19:31:57  * evangeni_joined
19:32:31  <yawnt>kevindente: not natively, but you can use 3rd party service or userland modules to achieve that :)
19:33:09  * thurmda1joined
19:34:41  <kevindente>yawnt: which modules?
19:35:17  <yawnt>https://github.com/ncb000gt/node-cron this is one that comes to my mind
19:35:33  * evangenieurquit (Ping timeout: 244 seconds)
19:36:55  * Nodejitsu-Githubjoined
19:36:56  <Nodejitsu-Github>[jitsu] blakmatrix pushed 2 new commits to master: http://git.io/4dMH4A
19:36:56  <Nodejitsu-Github>[jitsu/master] [feature] added yes to be the default option when writing package.json - yawnt
19:36:56  <Nodejitsu-Github>[jitsu/master] Merge pull request #343 from yawnt/fix-default-yes - Farrin Reid
19:36:56  * Nodejitsu-Githubpart
19:37:24  <kevindente>yawnt: interesting, I'll check it out. Thanks. But would my app be shut down if it goes idle, preventing userland code from triggering?
19:37:31  * thurmda1quit (Ping timeout: 245 seconds)
19:37:50  <yawnt>no, it's a webserver, so it'll just keep running
19:38:15  <kevindente>yawnt: OK, sweet. Thanks for the info!
19:38:55  <yawnt>kevindente: anytime ;)
19:40:06  * pspeter3joined
19:40:55  <yawnt>pspeter3: awesome!
19:40:56  * hpe1quit (Quit: Leaving.)
19:42:00  <pspeter3>yawnt: I really like nodejitsu. It seems way easier than heroku. I have an application that I'm building and I don't want to pay too much money for so I'm just deciding between MongoHQ and Heroku Postgres for what will be the better experience. I can model my app in both databases
19:43:15  * jeffrgquit (Quit: jeffrg)
19:43:49  * cronopioquit (Quit: leaving)
19:44:48  <yawnt>mh probably mongo has a better support
19:44:51  * cronopiojoined
19:45:07  <yawnt>but my app was full of relations and so i went with postgres :P
19:45:09  <yawnt>pspeter3: ^
19:45:25  * jmoyersjoined
19:45:41  * yawntchanged nick to feiert
19:45:45  * feiertchanged nick to yawnt
19:46:48  <pspeter3>yawnt: Alright, thanks for the advice
19:46:58  <yawnt>pspeter3: you're welcome
19:50:17  * YoYquit (Ping timeout: 255 seconds)
19:50:40  * Nodejitsu-Githubjoined
19:50:40  <Nodejitsu-Github>[jitsu] blakmatrix pushed 1 new commit to master: http://git.io/_js2mw
19:50:40  <Nodejitsu-Github>[jitsu/master] [dist] Version bump, v0.10.2 - Farrin Reid
19:50:40  * Nodejitsu-Githubpart
19:51:12  * c4miloquit (Read error: Connection reset by peer)
19:51:26  * c4milojoined
19:52:05  * YoYjoined
19:53:36  * njh__joined
19:53:37  * vekexasiapart
19:55:33  * ferloresquit (Remote host closed the connection)
19:58:59  * kevindentequit (Remote host closed the connection)
20:00:23  * st_lukequit (Remote host closed the connection)
20:01:34  * thl0quit (Ping timeout: 265 seconds)
20:08:42  * joshonthewebquit (Quit: Computer has gone to sleep.)
20:09:39  * sreeixquit (Quit: sreeix)
20:11:56  * thepumpkinjoined
20:15:19  * kenperkinsjoined
20:17:30  * YoYquit (Ping timeout: 272 seconds)
20:17:34  * cpjolicoeurquit (Quit: ...later...)
20:19:37  * YoYjoined
20:19:43  * sorensoquit (Quit: Computer has gone to sleep.)
20:21:43  * ebrightquit
20:23:08  * ebpanicjoined
20:23:43  * thurmda1joined
20:24:16  * groovecoderquit (Ping timeout: 252 seconds)
20:25:41  * bradleymeckquit (Quit: bradleymeck)
20:30:02  * thurmda1quit (Quit: Leaving.)
20:30:30  * YoYquit (Ping timeout: 252 seconds)
20:31:34  * YoYjoined
20:39:12  * YoYquit (Ping timeout: 276 seconds)
20:39:22  * admcquit (Quit: Leaving.)
20:41:04  * YoYjoined
20:41:17  * st_lukejoined
20:47:35  * eldiosjoined
20:50:19  * hpe1joined
20:50:36  * Sly[Tablet]quit (Quit: Bye)
20:51:48  * ArxPoeticaquit (Quit: Leaving.)
20:52:10  * ArxPoeticajoined
20:52:46  * cronopioquit (Quit: Bye)
20:54:14  * cronopiojoined
20:54:17  * jipiboilyjoined
20:56:17  * ArxPoeticaquit (Ping timeout: 240 seconds)
21:04:21  * wesbosquit (Quit: Linkinus - http://linkinus.com)
21:04:21  * thl0joined
21:04:21  * cronopioquit (Quit: leaving)
21:04:21  * kenperkinsquit (Quit: Computer has gone to sleep.)
21:04:21  * cronopiojoined
21:06:16  * YoYquit (Ping timeout: 272 seconds)
21:06:31  * joshonthewebjoined
21:06:33  * YoYjoined
21:07:27  * ebpanicpart ("["Textual IRC Client: www.textualapp.com"]")
21:07:44  * coderarityquit (Ping timeout: 246 seconds)