[00:00] CrabDude: shesek: fair amount of experience mucking around in V8's D8 protocol and debugger, etc... [00:00] enki: AvianFlu: well, yeah, it might either run out of memory or unstuck after a really long time ;) [00:00] enki: but i'd say it's still broken buffering behavior [00:00] OneOfOne: enki: you try with 0.5.9? [00:00] shesek: CrabDude, well, hmm, I'm not sure what's simpler than typing console.log() in the console and not seeing anything [00:00] AvianFlu: if you don't have 0.5.9 installed, enki, I can test it in a second [00:00] enki: nope, this is 0.4.12 [00:00] enki: don't have 0.5 [00:01] shesek: CrabDude, maybe its worth mentioning I'm on 0.5.8? any chance it doesn't work there? [00:01] AvianFlu: doesn't happen in 0.5.9 for m [00:01] AvianFlu: me [00:01] CrabDude: shesek: is console.log only failing when inspector is on? what about when --debug is on, but inspector is not? [00:01] AvianFlu: but I'm 95% sure stdout is blocking in 0.5.9, so that would make a ton of sense [00:01] CrabDude: shesek: negative, that's what I'm running [00:02] AvianFlu: oh wait! it's hanging after outputting 1 on 0.5.9 [00:02] AvianFlu: how lulzy [00:02] lightcap has joined the channel [00:02] enki: stdio is hard, let's go shopping [00:02] AvianFlu: lulz [00:03] shesek: CrabDude, shesek@shesek:/tmp$ echo 'console.log(123456);' > test.js || shesek@shesek:/tmp$ node --debug test.js || debugger listening on port 5858123456 [00:04] Brandon_R: I have a question [00:05] CrabDude: shesek: well, first, you won't be able to debug that b/c it'll finish running before you have a chance to hit it in inspector [00:05] Brandon_R: Why do we write bindings in C++ and not C if node.js is written in c [00:05] shesek: yeah, I know, just wanted to check if console.log() works at all [00:05] CrabDude: shesek: 2nd, if executing a file with ONLY console.log('XXX') in it doesn't log "XXX", you have bigger problems than inspector [00:05] CrabDude: ah, ic [00:06] shesek: but... with debug-brk and continuing from node-inspector it does show up [00:06] shesek: most be a problem somehow related to my code [00:06] OneOfOne: Brandon_R: who told you it's written in C? [00:06] CrabDude: try hitting something like: var i=0; setInterval(function(){debugger; console.log(++i);},1000); [00:06] CrabDude: see if that logs [00:06] CrabDude: see if it breaks when you open in inspector [00:06] OneOfOne: Brandon_R: v8 is written in C++, nodejs is written in C++ as well, take a look at https://github.com/joyent/node/tree/master/src [00:07] Brandon_R: i thought cc was c extention and cpp was c++'s? [00:07] sechrist: does node have any kind of object merge in the stdlib? [00:07] OneOfOne: Brandon_R: no, .cc/.cpp = c++, .c = c [00:07] CrabDude: sechrist: underscore.extend? [00:07] Brandon_R: cool [00:07] Brandon_R: learn something new everyday [00:08] CrabDude: sechrist: util.inherits [00:08] sechrist: does it only work with instances of a function or does that matter? [00:09] OneOfOne: Brandon_R: when in doubt, open the source file and look, can easily tell the difference between c/ c++ [00:09] Brandon_R: will do [00:09] shesek: CrabDude, I tried something simpler - `console.log(123456);debugger;` in test.js, than `node --debug-brk test.js`, than opening up node-inspector and hitting play so it'll stop on the `debugger` statement. The 123456 does show up in the terminal, but not in node-inspector [00:10] CrabDude: util.inherits(A, B) === A.prototype = B.__proto__ === A = Object.create(B.__proto__); (i think that's right) [00:10] shesek: which is also weird, because console.log() didn't show up in the terminal either in my actual code [00:11] enmand has joined the channel [00:13] shipit has joined the channel [00:13] CrabDude: shesek: with your simple example with "--debug-brk" it didn't show in terminal? [00:13] CrabDude: either way all are working for me with the log showing in the terminal … :/ [00:13] CrabDude: :-/ [00:14] shesek: no, it does show up in the terminal, but in the node-inspector's console [00:14] CrabDude: shesek: which? [00:14] JakeyChan has joined the channel [00:14] dynacker has joined the channel [00:15] shesek: which what? [00:15] CrabDude: "no, it does show up in the terminal, but in the node-inspector's console" [00:16] CrabDude: you mean "does not show"? [00:17] shesek: ah, sorry, meant "no, it does show up in the terminal, but //not// in the node-inspector's console" [00:17] jacobolus has joined the channel [00:17] CrabDude: ahh, ya, same for me [00:17] CrabDude: shows only in the terminal [00:17] replore has joined the channel [00:17] replore_ has joined the channel [00:17] CrabDude: don't remember that being the case before [00:17] jtrudeau has joined the channel [00:17] CrabDude: maybe newer node? [00:18] Brandon_R: anyone here plays with electronics? [00:18] Brandon_R: like motherboards [00:18] shesek: maybe... I dunno. but in my "real" code it doesn't show up in the terminal either, I wonder why [00:18] Brandon_R: i noticed there was node.js screencasts for arduinos [00:21] gxdssoft has joined the channel [00:21] CrabDude: shesek: odd… even if --debug isn't set and/or inspector isn't on and/or --debug-brk isn't set? [00:22] CrabDude: cuz it sounds like we're trying to rule out inspector [00:22] gavin_huang has joined the channel [00:22] CIA-48: node: 03Arnout Kazemier 07 * re3d2ae0 10/ src/node.js : sys has been moved to util - http://git.io/NBhinA [00:23] jarek has joined the channel [00:23] jarek has joined the channel [00:23] shesek: Hmm... lets see [00:24] neoesque has joined the channel [00:24] zmbmartin has left the channel [00:24] ilikeit has joined the channel [00:24] tylerstalder has joined the channel [00:25] lukstr: CrabDude: is there much to do in the area? [00:25] shesek: Running `coffee file.coffee` and `coffee --nodejs --debug file.coffee` both display console.log in the terminal [00:26] CrabDude: lukstr: yes [00:26] shesek: How can I resume script execution when I use debug-brk without node-inspector? [00:26] CrabDude: lukstr: are you in the area? [00:26] lukstr: CrabDude: if I don't have a car and am not close to caltrain? [00:26] CIA-48: node: 03Ilya Dmitrichenko 07 * r39987cb 10/ doc/api/fs.markdown : docs: improved fs.Stats section in API documentation - http://git.io/Z0JovA [00:26] lukstr: CrabDude: considering a job in the area [00:26] CrabDude: shesek: so it's only if you run with -debug-brk? [00:26] CrabDude: lukstr: ah, yes, there's much to do [00:27] sechrist: nodeduinos? [00:27] CrabDude: not so much in the direct vicinity of cupertino [00:27] sechrist: nodrduinos [00:27] Brandon_R: lol [00:27] shesek: CrabDude, Yes, when I run with debug-brk and resume from node-inspector I don't get any console.log() output in the terminal [00:27] lukstr: CrabDude: yeah I'd be right near cupertino city hall [00:27] shesek: How can I test it with debug-brk without using node-inspector? [00:27] jldbasa has joined the channel [00:27] lukstr: CrabDude: so probably worth shipping my car down? [00:28] CrabDude: shesek: odd. i'm not getting that (when resuming from inspector). try http://nodejs.org/docs/v0.5.9/api/all.html#debugger [00:28] sechrist: lukstr: you moving here? [00:28] CrabDude: never used it before [00:28] CrabDude: lukstr: yes and no [00:28] CrabDude: cupertino's a touch far from the caltrain [00:28] dimroc has joined the channel [00:28] sechrist: yeah [00:28] CrabDude: but there're buses etc.. [00:28] sechrist: last one is mountain view [00:28] CrabDude: sechrist: last one? [00:29] CrabDude: caltrain goes all the way to san jose [00:29] sechrist: oh right i'm mistaking myself [00:29] CrabDude: lukstr: but yes, there's tons to do [00:29] TRUPPP: i got an error message that the module qs is missing. i cant find it on github... =( somebody has a link for me? thanks [00:29] CrabDude: I lived in denver, dallas, souther california before this [00:29] CrabDude: and i'm very happy with the amount of things to do [00:30] CrabDude: TRUPPP: npm install qs? [00:30] sechrist: dallas [00:30] sechrist: hmm [00:30] sechrist: I lived in houston and I like it a lot more here [00:30] sechrist: it snows in dallas, :\ [00:30] TRUPPP: CrabDude i habe windows :( [00:30] shykes_ has joined the channel [00:30] TRUPPP: *have [00:30] CrabDude: sechrist: I'm sure anywhere's better than houston [00:30] SubStack: the bay area is fun on account of all the javascripters [00:31] sechrist: yarly [00:31] willwhite has joined the channel [00:31] sechrist: we have cool meetups in cramped boardrooms with beer [00:31] SubStack: it's true [00:31] CrabDude: TRUPPP: you can still grab the tgz from the npm repo: http://registry.npmjs.org/qs/-/qs-0.3.1.tgz [00:31] chilts: I'm in Wellington (New Zealand) which I think is similar to the SF, but I wish there were more JavaScripters here [00:32] CIA-48: node: 03Ryan Dahl 07 * r3a34972 10/ (lib/http.js test/simple/test-http-conn-reset.js): Fix test-http-conn-reset.js on OSX - http://git.io/LpcGdQ [00:32] zmbmartin has joined the channel [00:32] CrabDude: TRUPPP: in general try going to http://registry.npmjs.org/XXXXX/ to get the package metadata and go from there....? [00:32] meso has joined the channel [00:32] SubStack: chilts: have you met dominictarr? [00:33] CrabDude: sechrist: it snows only 4 hours away from here! =D [00:33] CrabDude: snowboarding =) [00:33] chilts: SubStack: no, is he in Wellington or NZ? [00:33] SubStack: where I used to live would have snow on the ground for 6 or 7 months [00:33] chilts: it'd be good to chat to him if he is :) [00:33] sechrist: SubStack: alaska isn't a real place [00:33] shesek: CrabDude, I do see console.log output in the terminal with node's debugger [00:33] lukstr: CrabDude: moving [00:34] lukstr: CrabDude: not remotely close haha [00:34] CrabDude: shesek: then I'd file a bug with inspector [00:34] chilts: looks like he's in Melbourne [00:34] chilts: (from his GitHub profile) [00:34] SubStack: yeah [00:34] CrabDude: shesek: honestly though, it'd be hard to say [00:34] sechrist: SubStack: where you were, did you have the really long days and nights part of the year? [00:34] SubStack: chilts: he's in australia righ now being a hobo [00:34] chilts: heh [00:34] CrabDude: since inspector jsut consumes the D8 protocol that node's V8 puts out [00:34] SubStack: he stayed in my empty room in oakland for a month [00:34] CrabDude: so it might not even be an error in node, but possibly even V8 [00:35] CrabDude: shesek: hopefully it's just inspector though. I'd still file an issue and he'll at least know where to look. [00:35] CrabDude: shesek: I'm out, but good luck [00:35] chilts: cool, his redis-raw library looks pretty cool :) [00:35] lukstr: CrabDude: I've only lived in and around Toronto [00:36] shesek: SubStack, oh, hey. Thanks for all the stuff you're releasing, I find many of them quite useful :-) [00:36] sechrist: I made mrcolor my wallpaper [00:36] SubStack: haha [00:37] SubStack: shesek: oh goodness and just wait until this goes live: http://browserling.com:9088/ [00:37] lukstr: SubStack: also that (mrcolor) is quite nifty [00:37] shesek: and your logos are quite neat, too :P [00:37] SubStack: shesek: plus we have a continuous deployment stack in the works that will plug into testling really easily >:D [00:39] mandric has joined the channel [00:40] shesek: oh, wow, it looks awesome [00:41] AvianFlu has joined the channel [00:41] shesek: any chance you'll make it possible to run your stuff on a private server at some point? What I'm working on is quite confidential, I can't run them on a server that can be accessed by 3rd parties [00:42] davidbanham has joined the channel [00:44] sechrist: encrypted proxies! [00:46] Circlefusion has joined the channel [00:47] devildue has joined the channel [00:47] illumina has joined the channel [00:48] iammerrick has joined the channel [00:48] Dreamer3 has joined the channel [00:49] rmzg has joined the channel [00:50] shanebo: SubStack, what do you use for deployment? [00:50] shanebo: is there a capistrano equivalent in node.js [00:51] sechrist: You can use capistrano with node [00:51] shanebo: sechrist, without having cap and gemfiles in my node project? [00:51] sechrist: http://railsbros.de/2011/02/18/deploying_a_node_js_server_with_capistrano_and_cluster.html [00:51] sechrist: found that by googling, I haven't done it myself [00:52] sechrist: I use a combination of bash scripts with github [00:52] sechrist: lol [00:52] sechrist: if I wasn't using it github it would be post-receive hooks [00:54] SubStack: shanebo: we already have ssh tunnels in browserling, just need to modify them a little for testling [00:54] jtrudeau has joined the channel [00:54] metellus has joined the channel [00:55] tjholowaychuk: bash scripts ftw [00:55] SubStack: shanebo: we don't really use anything to manage deploys and it sucks [00:55] sechrist: dsh -M -c -g "someclusterhere" "curl https://mydeploymentwebserver | sudo sh" [00:55] sechrist: boom [00:55] SubStack: tried to get started with chef at one point but that also sucked [00:55] sechrist: chef 10 is good [00:55] sechrist: they finally added environments [00:56] sechrist: but literally all I used it for was idempotent config files for existing projects [00:57] sechrist: and I'm trying to move my configs into redis [00:57] Brandon_R: hi [00:57] sechrist: for newer ones [00:57] SubStack: chef doesn't work well for our stack because our services span multiple servers [00:57] SubStack: and people can be connected to the servers when we push out an update [00:58] SubStack: and we don't want to kill those connections [00:58] SubStack: so I'm writing stagecoach using bouncy to make it so that you can do zero-downtime deploys through some routing-table trickery [00:59] tjholowaychuk: just going to redirect traffic? [00:59] slickplaid: that sounds fun [01:00] tjholowaychuk: bouncy looks pretty nice, that's all i wanted out of http-proxy [01:00] chilts: yeah, I like the idea and will use it on my next project :) [01:00] AvianFlu has joined the channel [01:00] sechrist: SubStack: yep, the software I was using check on had to have a "drain" implemented, once triggered, no new connections would be allowed and when existing ones closed the server restarted [01:00] sechrist: with the upgrade [01:01] errordeveloper: hm .. I don't quite get thing - V8 has it's own implementation of websockets [01:01] errordeveloper: can that be used in node ? [01:01] illumina: node-browserify and socket.io don't seem to play nice together. in particular, it looks like browserify doesn't have a wrapper for 'crypto'. anyone gotten this to work? google seems lost too. [01:02] errordeveloper: illumina: hm .. have you tried skock.js intead of socket.io .. ? [01:02] clu3 has joined the channel [01:05] SubStack: tjholowaychuk: yes stagecoach will redirect new incomings to the instance you spin up once the tests pass [01:05] catb0t has joined the channel [01:05] illumina: errordeveloper: no. haven't come across that. ill look into it... [01:05] SubStack: and just garbage collect the old instance once all the connections drop off [01:05] tjholowaychuk: cool [01:05] tjholowaychuk: we do similar with hudson [01:06] aaronblohowiak has joined the channel [01:07] WarheadsSE: any meaning to every single test returning "-- CRASHED --" on testing with ARM ? [01:07] errordeveloper: illumina: yeah, I have have seen a presentation by the author of sock.js, and he said something about some fundamental concepts that it has .. though I can remember what exactly ;( [01:08] errordeveloper: WarheadsSE: hm .. did you build it yourself? [01:09] jldbasa has joined the channel [01:09] WarheadsSE: one of our automated builders did for ArchLinux ARM [01:09] WarheadsSE: we saw that in the build log [01:09] errordeveloper: WarheadsSE: well, get your debugger ready! [01:10] harthur has joined the channel [01:10] k1ttty has joined the channel [01:10] WarheadsSE: meh, wont hurt to try it [01:10] WarheadsSE: I built 4.11 locally a while back [01:10] WarheadsSE: this one is via the automated build system [01:11] piscisaureus_ has joined the channel [01:11] reid has joined the channel [01:11] silntbob has joined the channel [01:12] gxdssoft has joined the channel [01:13] springmeyer has joined the channel [01:14] errordeveloper: WarheadsSE: good luck, keep us posted :) [01:14] WarheadsSE: will do [01:14] WarheadsSE: finishing up an pacman -syu atm [01:14] errordeveloper: WarheadsSE: I didn't get to use node on arm yet, but I'm certainly going to very soon! [01:14] WarheadsSE: then ill pull the package and see what happens [01:15] WarheadsSE: We'll im doing this on armv5 softfloat kernels [01:15] WarheadsSE: Pogoplugs & Go Flex Nets [01:16] WarheadsSE: If this build works, we'll push it on the armv7 hardfloat [01:16] smus has joined the channel [01:17] meso has joined the channel [01:17] infynyxx has joined the channel [01:18] silntbob: has anyone read http://teddziuba.com/2011/10/node-js-is-cancer.html [01:18] metellus has joined the channel [01:18] ctide: no [01:18] marcello3d has joined the channel [01:19] sechrist: it's a hilarious joke post [01:19] mikeric has joined the channel [01:20] chilts: heh, no, no-one saw that before, we didn't see a thing (well at least that's how much attention it deserves) :) [01:21] CarterL has joined the channel [01:21] paulwe has joined the channel [01:21] avalanche123|h has joined the channel [01:23] digman543_ has joined the channel [01:23] infynyxx has joined the channel [01:24] dgathright_ has joined the channel [01:26] illumina: what do you guys recommend for sharing code between the browser and node? I was trying browserify… but it looks like requireJS may be more appropriate. [01:26] devildue: Eh Ess Eh Ess Eh Ess Eh Ess fight the romulans! [01:28] sechrist: illumina: in what way? [01:28] sechrist: ACTION uses browserify [01:28] Aikar: hmm [01:29] davidbanham has joined the channel [01:29] illumina: well, i don't really like the mashing up of files (makes it harder to debug). And it seems it doesn't fully support node packages (like socket.io) [01:29] jakehow has joined the channel [01:30] avalanche123|h has joined the channel [01:30] sechrist: http://funroll-loops.info/ [01:30] sechrist: classic [01:30] illumina: i'm a bit miffed at the current state of affairs for building multi-file browser side javascript projects. coming from other environments, it's amazing that there isn't a simple way to express dependencies [01:30] lightcap has joined the channel [01:30] illumina: or I'm totally missing something [01:31] tjholowaychuk: i have some thoughts on how to do that "correctly" [01:31] tjholowaychuk: but nothing complete yet :p [01:31] sechrist: what you want a package.json for each page and loading only the package the page needs? [01:31] SubStack: socket.io doesn't work in browserify because it's too clever and already has its own non-browser mode shimming that confuses browserify [01:31] illumina: no - in particular I'm doing some game development. so I actually have only one HTML page that's a canvas [01:31] SubStack: if you just write your code the node way then it browserifies fine [01:32] illumina: but my code (javascript) is complex. I want to break it up into multiple files so multiple people can work together.. express dependencies as objects, etc. (you know the drill) [01:32] SubStack: just throw your dependencies into a package.json [01:32] SubStack: let npm figure that out [01:32] illumina: SubStack: browserify seems to work great, except with socket. which is sort of the point of what I'm doing [01:33] isaacs: SubStack++ [01:33] illumina: what do you recommend then if it's too clever? [01:33] Circlefusion has joined the channel [01:33] SubStack: I don't recommend anything. [01:34] illumina: hmm. so no socket, eh? [01:34] balaa has joined the channel [01:34] SubStack: you could just use browserify for the non-socket.io stuff [01:34] dmwuw has joined the channel [01:34] davidban_ has joined the channel [01:35] illumina: so then I need a different dependency solution for the non-socket stuff [01:35] SubStack: just throw in a