Re: [nodejs] Re: Segmentation fault - how to diagnose?

2012-11-08 Thread Graeme Foster
Thanks chaps; consider that can of worms well and truly opened :) I didn't come across segvhandler when I was searching for info - looks very handy! Cheers, G. On Thursday, November 8, 2012 4:39:52 PM UTC, Ben Noordhuis wrote: On Thu, Nov 8, 2012 at 5:18 PM, Paul Serby

[nodejs] Segmentation fault - how to diagnose?

2012-11-07 Thread Graeme Foster
Hi all I'm using node 0.8.14 and I've got a test suite that results in a segmentation fault on both OSX and whatever Travis is building on. I thought I'd be clever and use gdb to get a stack trace but here's what I got: (gdb) set args ./node_modules/mocha/bin/mocha (gdb) run Starting

[nodejs] Re: Segmentation fault - how to diagnose?

2012-11-07 Thread Graeme Foster
Oops, I forgot about browserify... Run this and then the tests will pass (up to the seg fault): mkdir public node_modules/browserify/bin/cmd.js --entry client/src/lib/main.js -o public/client.js Cheers, G. On Wednesday, November 7, 2012 9:45:01 PM UTC, Paul Serby wrote: Sorry I've just seen

[nodejs] https://new.npmjs.org/ test coverage

2012-07-10 Thread Graeme Foster
In order to soak up its nodey design philosophy I've been looking at the repo for https://new.npmjs.org/, but I can't find any tests! I've only dabbled with toy websites myself (at least with node), but when I've played around I've started with an end-to-end test to kick off the TDD process

Re: [nodejs] npm outdated

2012-06-15 Thread Graeme Foster
That :) Thanks, and looking forward to it. On Friday, June 15, 2012, Ryan Schmidt wrote: https://github.com/isaacs/npm/issues/1428 -- -- Graeme Foster -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You

[nodejs] Re: npm outdated

2012-06-15 Thread Graeme Foster
Excellent; police -l will do for the time being. I was going to build something similar myself now that the necessary bits of npm are split into modules, but this will do! Many thanks. G. On Friday, June 15, 2012 1:18:11 PM UTC+1, Mike Pilsbury wrote: https://github.com/pksunkara/npm-police

[nodejs] npm outdated

2012-06-14 Thread Graeme Foster
Hi all I just noticed that when I ran npm outdated it said everything was hunky-dory but in fact some of my packages were out of date. The packages * were* up-to-date with respect to the versions specified in my package.json dependencies, but I understood that I could use npm outdated to tell

Re: [nodejs] npm outdated

2012-06-14 Thread Graeme Foster
That checks the globally-installed packages, and I would imagine behaves in the same way. G. On Thursday, June 14, 2012 6:06:55 PM UTC+1, Yuri Teixeira wrote: Did you try with -g option? Eg: npm -g outdated -- Job Board: http://jobs.nodejs.org/ Posting guidelines:

Re: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server

2012-06-12 Thread Graeme Foster
Could you change now into soon? It's very early days and Windows only for the moment! G. -- Graeme Foster On 12 June 2012 00:36, Chad Retz chad.r...@gmail.com wrote: Fantastic. I guess I can retire https://github.com/cretz/node-tds now as I haven't had much time to work on it anyways

Re: [nodejs] Re: Microsoft Driver for Node.JS for SQL Server

2012-06-09 Thread Graeme Foster
That's excellent news and will definitely make SQL Server more attractive to some. I was a bit worried when I saw it's based on the native Windows driver :) -- Graeme Foster On 9 June 2012 16:15, Jonathan Guerin jgue...@microsoft.com wrote: Linux support is on our roadmap. :) This is just

Re: [nodejs] unix: fix loop starvation under high network load (what was this?)

2012-06-07 Thread Graeme Foster
Sounds like socket pooling is getting in your way (caught me out too), see the second tip here: http://engineering.linkedin.com/nodejs/blazing-fast-nodejs-10-performance-tips-linkedin-mobile G. -- Graeme Foster On 7 June 2012 14:36, Brad Carleton b...@techpines.com wrote: I have had issues