On Tue, Jan 1, 2013 at 3:45 PM, wrote:
> I have the following code:
>
>> try {
>> require('./index.js');
>> }
>> catch(e) {
>> console.log('--');
>> console.log(e.stack);
>> }
>
>
> When I run the code, the following gets logged to the console:
>
>> C:\[path]\inde
On Thu, Jan 3, 2013 at 4:21 PM, am_p1 wrote:
> Thanks for the assist and the suggestion of paid support but I finally
> figured it out.
>
> Had two issues, both my bad:
> 1 - javascript scope of some of my variables was wrong, especially in async
> node.js world ("use strict" helped me since I'm s
On Thu, Jan 3, 2013 at 11:57 PM, am_p1 wrote:
> ok, so apparently eio is gone and libuv is what i'm actually using (not
> knowing the history of node makes for a confusing day)
>
> no wonder eio or eio-simple didn't work :-)
>
> so I couldn't find any min/max controls on threads anywhere so i assu
On Fri, Jan 4, 2013 at 6:12 AM, Aaron Wang wrote:
> I raised this problem on stackoverflow, didn't get proper answers yet, any
> thoughts?
It's good newsgroup etiquette to post the actual question (or
questions) instead of linking to a website; it lets people reply to
individual questions inline.
On Fri, Jan 4, 2013 at 5:41 PM, am_p1 wrote:
> It's working great but odbc to db2 queues and backs up some. I assume
> because when using ps -eLf I can see that there are still only 4 threads per
> node and the number doesn't change.
>
> Is the thread count suppose to change dynamically with libuv
On Fri, Jan 4, 2013 at 9:23 PM, Trevor Norris wrote:
> This is for all the committers out there.
>
> While working on my latest Buffers PR, noticed there are
> undocumented/unenforced ways things can go wrong. Say, for example, a user
> wants to extend Buffer with their own set of methods/properti
On Sat, Jan 5, 2013 at 5:49 PM, Mike Pilsbury wrote:
> I'm having some problems with secure connections in my implementation
> (tedious) of TDS. Under some conditions I don't get any response from the
> SQL Server instance to a TDS login packet sent to it.
>
> If I use RC4-MD5 everything works fin
On Tue, Jan 8, 2013 at 5:29 AM, Benjamin Farrell wrote:
> Hey everyone - I'm trying to bind Node.js to the OpenNI project
> (http://www.openni.org/). I'm coming at this having not really used much
> C++, let alone the Node build system.
>
> Anyway - I have been able to create a custom AddOn for N
On Tue, Jan 8, 2013 at 3:22 PM, Benjamin Farrell wrote:
> Awesome, I appreciate it! Onto the OpenNI forums! If anybody knows
> otherwise I'd love to hear it so I'm not banging my head against the wall
> needlessly. And honestly this is great news - I'm glad it wasn't what I was
> afraid of - th
On Wed, Jan 9, 2013 at 8:01 AM, David Jacobs wrote:
> Hey guys,
>
> I would love to convince my new company to build our platform using Nodejs
> as our server-side language. Node is a possibility for our small team, but a
> few questions will have to be answered before I can convince everyone that
t;
>
> 2012.01.09, Version 0.8.17 (Stable)
>
> * npm: Upgrade to v1.2.0
> - peerDependencies (Domenic Denicola)
> - node-gyp v0.8.2 (Nathan Rajlich)
> - Faster installs from github user/project shorthands (Nathan Zadoks)
>
> * typed arrays: fix 32 bit size/index overf
On Mon, Jan 14, 2013 at 10:56 PM, kapouer wrote:
> Of course nodejs is going to be updated in debian, it's only a matter of
> time.
> It is not small work to do, so you can help... or just wait, but don't hold
> your breath.
> Instead of working i just spend two hours on that matter tonight. Will
On Tue, Jan 15, 2013 at 7:08 AM, zhonghua wu wrote:
> HI,ALL
>
> I want to use CImg library to deal images in node.js,so i write an node
> addon to do it. The compile is success, i run node-gyp build commond, that's
> ok.
>
> But when i run the node program,the follow error occurs:
>
> [root@local
On Wed, Jan 16, 2013 at 2:52 PM, Michael wrote:
> I profiled my application a bit and found out, that a lot of time is spent
> in ___psynch_rw_unlock. I attached my processed v8.log. Any ideas what
> causes this?
>
> I am using v0.8.17 (Mac OS X Installer) on a OS X 10.8.2.
Something is calling p
On Wed, Jan 16, 2013 at 11:25 AM, Cheng Shao wrote:
> I'm trying out nodejs as a TCP server. i want to read unsigned 64bit integer
> from Buffer. find not similar function. why not to be added?
JS numbers are 64 bits doubles. That means you can't represent 64 bit
integers with them because they'
On Wed, Jan 16, 2013 at 11:30 AM, Andris Reinman
wrote:
> For some reason process.stdout.writable is false in v0.9.6 while other
> writable streams are not. Is it intentional because of the overhaul of the
> Stream system or is it a bug?
>
> In v.0.8.16:
> console.log(process.stdout.writable) -> t
On Wed, Jan 16, 2013 at 3:49 PM, Ben Noordhuis wrote:
> On Wed, Jan 16, 2013 at 11:30 AM, Andris Reinman
> wrote:
>> For some reason process.stdout.writable is false in v0.9.6 while other
>> writable streams are not. Is it intentional because of the overhaul of the
>>
On Wed, Jan 16, 2013 at 7:51 PM, mjosephd wrote:
> Hi All,
>
> In node.js the server crashes whenever an exception is thrown, I also read
> up that it IS possible to catch uncaught exceptions but the best practice is
> to do any necessary precautions such as logging details and then restarting
> t
On Wed, Jan 16, 2013 at 11:24 PM, preetam pattanashetty
wrote:
>
> Hi,
>
> Firstly, what we have is a Windows service (Christened: Aggregator ) written
> in .Net that processes data in real time and is listening to clients (which
> are flash based) on a port.. and when a tcp connection is made i
On Thu, Jan 17, 2013 at 10:01 AM, Michael Wittig
wrote:
> As far as I can see (I searched for pthread_rwlock_unlock in node_modules/)
> I can't find a module using pthread stuff.
They might be using libuv wrappers. Maybe grep for just 'rwlock', 'mutex', etc.
> I also do no use the crypto module
On Thu, Jan 17, 2013 at 7:19 PM, Chris Scribner wrote:
> I was doing some profiling to look into performance issues and got the
> following output.
>
> [Shared libraries]:
>ticks total nonlib name
> 222878 60.6%0.0% /usr/lib/system/libsystem_kernel.dylib
> 102818 27.9%0.0
On Thu, Jan 17, 2013 at 8:09 PM, Rel Guzman Apaza wrote:
> Hi, Is node.js going to participate in GSOC 2013 ?
There are no plans to the best of my knowledge. Why do you ask?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guid
On Thu, Jan 17, 2013 at 8:37 PM, Chris Scribner wrote:
> Thanks for the information so far. I'll try it out and see what sticks.
>
> A little more information...
>
> I was running a 1 master + 3 worker cluster (using node's clustering) when
> the profile was taken. Do you know how the profile comb
On Thu, Jan 17, 2013 at 11:07 PM, Ben Noordhuis wrote:
> On Thu, Jan 17, 2013 at 8:37 PM, Chris Scribner wrote:
>> Thanks for the information so far. I'll try it out and see what sticks.
>>
>> A little more information...
>>
>> I was running a 1 master + 3 w
On Sat, Jan 19, 2013 at 10:58 AM, 冼建民 wrote:
> www:/home/kenneth/node-v0.8.18# make
> make -C out BUILDTYPE=Release V=1
> make[1]: Entering directory `/home/kenneth/node-v0.8.18/out'
> flock /home/kenneth/node-v0.8.18/out/Release/linker.lock g++ -pthread
> -rdynamic -m64 -o /home/kenneth/node-v
On Sat, Jan 19, 2013 at 7:54 PM, thewilli wrote:
> Hi!
>
> The node documentation of the cluster module says about incoming server
> connections:
>
>> When multiple processes are all accept()ing on the same underlying
>> resource, the operating system load-balances across them very efficiently.
>>
On Mon, Jan 21, 2013 at 4:21 PM, Michael wrote:
> Hi,
>
> System: node 0.8.17 on CentOS 6.3
>
> I get the following log:
> node: ../deps/uv/src/uv-common.h:101: uv__req_unregister: Assertion
> `uv__has_active_reqs(loop)' failed.
> and my process gets a SIGABRT.
>
> The problem occurs at random. I
On Tue, Jan 22, 2013 at 10:46 AM, An dreas wrote:
> Currently I need to set SO_RCVBUF way higher on dgram-sockets I use combined
> with multicast...
Why is that?
If you're experiencing packet loss, you will want to verify that the
issue is really on your side. If packets get lost in transit or
On Tue, Jan 22, 2013 at 12:43 PM, Michael wrote:
> I did it 3 times, always the same result:
>
> Starting program: /usr/local/bin/node index.js
> [Thread debugging using libthread_db enabled]
> [New Thread 0x77fef700 (LWP 31807)]
> WARNING: ev_io is deprecated, use uv_poll_t
> WARNING: ev_time
On Tue, Jan 22, 2013 at 1:12 PM, An dreas wrote:
>
>
> On Tuesday, January 22, 2013 12:26:18 PM UTC+1, Ben Noordhuis wrote:
>>
>> On Tue, Jan 22, 2013 at 10:46 AM, An dreas
>> wrote:
>> > Currently I need to set SO_RCVBUF way higher on dgram-sockets I u
On Thu, Jan 24, 2013 at 7:36 PM, Isaac Schlueter wrote:
> * build: fix build with dtrace support on FreeBSD (Fedor Indutny)
The non-dtrace FreeBSD build is _also_ fixed in this this release. :-)
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Maili
On Fri, Jan 25, 2013 at 3:39 PM, Andrei Sedoi wrote:
> Hi Ben. Thanks for this. I am trying to compile node.js v0.8.18 with your
> changes applied (I created a patch for v0.8.18:
> https://gist.github.com/4634756) and getting an error:
> ../deps/openssl/openssl/e_os2.h:56:33: fatal error: openssl/
On Mon, Jan 28, 2013 at 9:33 AM, Zoid wrote:
> Hi all,
>
> I have 2 related questions:
>
> 1. Is there a way to put both 32-bit and 64-bit .node files under
> node_modules so correct version is chosen based on which node is running. I
> need both 32- and 64-bit node on the same system and would li
On Mon, Jan 28, 2013 at 12:10 PM, Zoid wrote:
> Open node REPL, enter:
>
> require('child_process').spawn('jo')
>
> 0.8.x displays the result value and in REPL
>
> 0.9.x displays result value, then displays a stacktrace and exits REPL
>
> Here is the trace:
>
> events.js:69
> throw argumen
On Mon, Jan 28, 2013 at 11:15 PM, Zoid wrote:
>
> On Monday, January 28, 2013 1:31:23 PM UTC+2, Ben Noordhuis wrote:
>>
>> On Mon, Jan 28, 2013 at 9:33 AM, Zoid wrote:
>>
>> > 2. Is there a way to help module maintainers to include precompiled
>> >
On Thu, Jan 31, 2013 at 1:59 AM, Michael Jackson wrote:
> It would be really nice to be able to exit a process gracefully on
> SIGINT/SIGTERM. Right now both signals are hardwired to exit with a status
> of 1 (see the SignalExit function in node.cc) without emitting the "exit"
> event on the proce
On Thu, Jan 31, 2013 at 11:49 AM, Masiar Babazadeh wrote:
> Hello everybody,
>
> I'm having a strange issue in the last couple of days: the return value of
> os.cpus() contains some values in the "time" object that are negative for
> some of the processes. I thought about a conversion error / over
On Thu, Jan 31, 2013 at 7:51 PM, smf wrote:
> Hi,
>
> Does anyone know what Node returns ECONNREFUSED insetad of ESERVFAIL for DNS
> queries that return SERVFAIL?
>
> [root@mail1-ec2 ~]# dig servfail.test.snert.net
>
> ; <<>> DiG 9.7.3-P3-RedHat-9.7.3-2.11.amzn1 <<>> servfail.test.snert.net
> ;; g
On Fri, Feb 1, 2013 at 12:39 AM, Dan Milon wrote:
>
> I was wondering if it is possible to use a core dump from a node
> process running on linux as a post mortem debugging mechanism.
>
> Would smartos' MDB understand a core dump coming from a linux machine?
>
> Thanks,
> danmilon.
The people at
On Thu, Jan 31, 2013 at 10:38 PM, Steve Freegard
wrote:
> Hi Ben,
>
>
> On Thursday, 31 January 2013 19:10:21 UTC, Ben Noordhuis wrote:
>>
>>
>> Not sure, it seems to work for me:
>>
>> $ out/Release/node tmp/dns-econn.js
>> { [Error: queryA
On Fri, Feb 1, 2013 at 9:42 AM, darcy wrote:
> Yes, I mean write+callback can be sync in some cases.
> If the callback should be promised to be async, we can use
> process.nextTick(cb.bind(this)) in Socket._write().
> But I think in userland it's not important whether write callback is sync or
> a
On Fri, Feb 1, 2013 at 4:38 PM, Dan Milon wrote:
> Thanks, I'll give it a try.
>
> Now, about getting an actual core dump, docs [1] say process.abort
> will generate one.
>
> $ node -e 'process.abort()'
> Aborted (core dumped)
>
> $ ls -a
> ./ ../
>
> Should I file this as a bug?
>
> [1] http://n
On Fri, Feb 1, 2013 at 5:27 PM, Dan Milon wrote:
> $ ulimit -c unlimited
>
> $ node -e 'process.abort()'
> Aborted (core dumped)
>
> $ ls -a
> ./ ../
>
> Any idea?
>
> BTW, could you point me to the actual code of process.abort in the source?
>
> danmilon.
Check what the kernel.core_pattern sysc
On Fri, Feb 1, 2013 at 4:01 PM, Steve Freegard wrote:
> On Friday, 1 February 2013 11:43:49 UTC, Ben Noordhuis wrote:
>>
>>
>> Right, I can reproduce it now.
>>
>> It seems to be a c-ares quirk (the DNS resolver library we use). If a
>> server replies wit
On Sat, Feb 2, 2013 at 7:26 AM, Jack Waugh wrote:
> It would be wonderful if the VM module (virtual machine) would let one catch
> the errors from trying to compile a Javascript source string, instead of
> having them go to stdout.
Maybe I'm misunderstanding you but it already works like that:
On Sat, Feb 2, 2013 at 6:05 PM, Zoid wrote:
> Hi
>
> I found that with 0.9.7 on Windows streams created by fs.createWriteStream()
> don't save syscalls: you get as many systalls as write() calls. It leads to
> mediocre file write performance.
>
> Here is demonstration code: http://hpaste.org/81687
On Sun, Feb 3, 2013 at 6:31 PM, xyz wrote:
> I like to know the best stress and load testing tool for node.js
> applications.
> Thanks,
You don't say what you want to stress-test but assuming it's HTTP,
look at ab, siege or jmeter.
I don't know of a single great tool for raw TCP or UDP traffic.
On Mon, Feb 4, 2013 at 8:01 PM, Andrew Bradley wrote:
> What character encodings does NodeJS support for source code .js files?
>
> In other words, if I intend to run "node foo.js" what character encodings am
> I allowed to use when saving "foo.js" from my text editor?
>
> I am aware that UTF-8 ap
On Tue, Feb 5, 2013 at 8:17 AM, Adam Stallard wrote:
> I would like a way to detect when there is no outstanding I/O. An event
> would suffice. A synchronous check would also be nice, but not as
> important.
>
> The only way I have figured out how to do this is to spawn a child process
> which c
On Wed, Feb 6, 2013 at 2:52 PM, TJ wrote:
> I needed the facility to build to an out-of-tree location rather than the
> hard-code "out/" directory in the source tree.
>
> So far it works with all the test scenarios I've needed it for so I thought
> I'd put it out for wider testing and feedback.
On Wed, Feb 6, 2013 at 4:04 PM, TJ wrote:
> On 06/02/13 14:55, Ben Noordhuis wrote:
>> On Wed, Feb 6, 2013 at 2:52 PM, TJ wrote:
>>> I needed the facility to build to an out-of-tree location rather than the
>>> hard-code "out/" directory in the source tree.
On Wed, Feb 6, 2013 at 10:44 PM, wrote:
> Hi,
>
> I just downloaded the binary distribution v0.8.19 for 64bit linux. While I
> can untar the file and execute the executable, I am unclear how I should
> install onto my computer. I understand that I can untar it into /usr/local
> but that might not
On Thu, Feb 7, 2013 at 5:54 PM, Grzegorz Junka wrote:
> Hi, I'm trying to install node.js on Solaris 10. The binary distribution
> that can be downloaded from node.js website is compiled on Solaris 11 and
> doesn't work on Solaris 10 (libsocket.so.1: version 'SUNW_1.7' not found).
>
> I tried to c
On Thu, Feb 7, 2013 at 10:02 PM, Sven Knuth wrote:
> at least I found the reason for the abuse.
>
> node.js starts many tests and one test
> (test/simple/test-dgram-send-error.js) is sending 1000-Request to random IPs
> to test the error handling, because the IPs should be unreachable, because
> i
On Thu, Feb 7, 2013 at 10:03 PM, Kevin Baker wrote:
> Hello all,
>
> I am working on Node.JS's OpenEmbedded support for a project here, test
> platform is Yocto "danny"/armv7a-vfp-neon-poky-linux-gnueabi/OMAP3730.
>
> So far I have updated the recipe to v0.8.15 and it builds, compiles, and
> runs
On Thu, Feb 7, 2013 at 6:02 AM, V'Raj Kanwade wrote:
> Ok. Let me rephrase the question:
>
> I am inside connectionHandler of net.createServer. Now when I determine the
> data from client is HTTP request, I want to convert it to HTTPRequest object
> so that I can leverage the HTTP headers, status
On Sun, Feb 10, 2013 at 2:28 PM, Paul wrote:
> Thanks for the reply! I was using Local::Cast(args[0]) instead of
> ->ToObject() so I switched that out to match your code below. In my module
> I take the Local from args[], assign it to a baton, pass the baton
> to my work function and then refere
On Tue, Feb 12, 2013 at 5:45 PM, Brent Baker wrote:
> I am seeing 2 failures running the "test" make target with a clean clone of
> the git repo and I am wondering if this is a local config issue I have or
> are these known issues?
>
> platform: OS X 10.8
>
> % ./configure
> % make -j20
> % make t
On Tue, Feb 12, 2013 at 4:24 PM, wrote:
> Hi,
>
> When I click on link for .msi file for Windows, it says 404 Not Found
>
> I am referring to this link
>
> http://nodejs.org/dist/v0.8.19/node-v0.8.19-x86.msi
>
> Please Please Please help me.
> I want to learn NodeJS & I just can't install it on W
On Wed, Feb 13, 2013 at 1:16 PM, TJ wrote:
> When calling .close() on a server that is listening on a socket rather than a
> TCP port
> the socket is not unlinked from the file-system - it remains in place. As a
> result
> subsequent attempts to use the same socket will fail with EADDRINUSE.
>
>
Banned.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsu
On Wed, Feb 13, 2013 at 2:11 PM, TJ wrote:
> On 13/02/13 12:47, Ben Noordhuis wrote:
>>> diff --git a/test/common.js b/test/common.js
>>> index 7b4c0bc..4cbdea6 100644
>>> --- a/test/common.js
>>> +++ b/test/common.js
>>> @@ -59,6 +59,10 @@ if (pro
On Wed, Feb 13, 2013 at 2:20 PM, Brent Baker wrote:
> I am new to this project and I am wondering if there is a continuous build
> running that I can look at in order to compare failures that I am seeing
> locally.
We don't have any CI set up at the moment but that's coming (again) in
the next mo
On Wed, Feb 13, 2013 at 3:01 PM, Brent Baker wrote:
>> The other two fail because they're timing sensitive. Debug builds are
>> a lot slower than release builds and that exacerbates it.
>
>
> What is the long term plan to deal with testcases that are not stable?
Wait for people to upgrade to new
On Wed, Feb 13, 2013 at 3:36 PM, TJ wrote:
> On 13/02/13 14:18, TJ wrote:
>> On 13/02/13 13:20, Ben Noordhuis wrote:
>>> Strange, I'm not able to reproduce that. (Unless I invoke the tests
>>> manually, of course.)
>>
>> Nice! That means I've fo
On Sat, Feb 16, 2013 at 12:00 PM, Jorge Chamorro
wrote:
> On 16/02/2013, at 11:26, Trevor Norris wrote:
>
>> Sending a callback to nextTick is almost the functional equivalent of
>> running it at the end of your script. They are intentionally run before the
>> following event loop. Try sending a
On Mon, Feb 18, 2013 at 10:41 AM, wrote:
> hi all
>I am building node-v0.8.20 from source in RedHatEnterpriseAS 4
>
> $ ./configure
> { 'target_defaults': { 'cflags': [],
>'default_configuration': 'Release',
>'defines': [],
>
On Tue, Feb 19, 2013 at 12:47 PM, Gustavo Machado wrote:
> Hi,
>
> We are getting EPIPE errors. Reproducing the error is a matter of uploading
> multiple files at the same time while keep on using the site, and eventually
> it will throw.
>
> Here is the stack trace:
>
> "stack":[
>
On Wed, Feb 20, 2013 at 1:07 PM, Gustavo Machado wrote:
> Hi Ben,
>
>>
>> EPIPE means you're writing to a pipe or socket when the other end has
>> terminated the connection.
>>
>> It's a run-time error; there is nothing you can do but close your end as
>> well.
>
>
> Since it's throwing, looks lik
On Wed, Feb 20, 2013 at 7:55 PM, am_p1 wrote:
> And does it use IPC or socket? or do I care?
>
> Thanks!!
It's a UNIX socketpair on Unices, a pipe on Windows.
The maximum length is 1 GB (after JSON.stringify-ing the message object.)
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
On Thu, Feb 21, 2013 at 3:54 PM, Burak Gürbüz wrote:
> When i try to run the chat system which i wrote, socket.js works on http but
> doesn't work on https.
With all due respect but please read
http://www.catb.org/esr/faqs/smart-questions.html first.
--
--
Job Board: http://jobs.nodejs.org/
Po
On Thu, Feb 21, 2013 at 6:17 PM, Gustavo Machado wrote:
> Hi,
>
> In turned out to be the process.stdout. Apart from reducing the console.logs
> to a minimum, we are planning to use epipebomb to avoid the process to crash
> under heavy load. Is there any way to re-open the connection to the
> c
On Fri, Feb 22, 2013 at 12:13 AM, wrote:
> Hi,
>
> I am trying to compile mentioned node version on Solaris SPARC 10 but got
> the error. I have installed python 2.7.3.
>
> When I ran configure, I got below error -
>
> bash-3.00# ./configure
> Traceback (most recent call last):
> File "./config
On Fri, Feb 22, 2013 at 5:26 PM, funny_falcon wrote:
> While eio has a call to fallocate, it is not exposed to js level. Why?
libeio is gone in node.js master.
Re: fallocate(): what would you use it for and why?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/
On Sat, Feb 23, 2013 at 10:36 AM, funny_falcon wrote:
> Fallocate is prooved to be useful when you are dealing with huge
> amount of ondisk data.
> Especially when you need to separately grow hundreds of thousand
> files, and then be sure it doesn't lead to huge fragmentation.
Sorry if I was uncl
On Sun, Feb 24, 2013 at 11:00 PM, Marcel Laverdet wrote:
> others. Really this is something that might just be better off in fs-ext
> (which I'm already using for flock) if you can't emulate it in Windows.
To be clear, it's not just Windows. fallocate() is a _Linux-ism_.
The nearest thing on ot
On Tue, Feb 26, 2013 at 7:45 AM, wrote:
> It seems I am getting a warning over a time gap detected in the processing
> loop. I can't find this error message anywhere in the source code, nor does
> anything show in searching for the term. Any one else ever see this message
> and/or have any idea
On Wed, Feb 27, 2013 at 11:44 PM, Tim Dickinson wrote:
> I have a build of node version 0.6.12 but my main install of node is 0.8.20
>
> This is my output
>
> [bob@bob-workstation test]$ /tests/tmp/node/0.6.12/bin/npm install daemon
> npm http GET https://registry.npmjs.org/daemon
> npm http 304 h
On Wed, Feb 27, 2013 at 11:59 PM, Tim Dickinson wrote:
> How would i override PATH so i dont have to set the version for each node
> install that i have.
> So I could have node 0.6.12 or 0.8.12 or 0.9.12 I dont really want to set
> PATH for each version im running. I might have more then one insta
On Thu, Feb 28, 2013 at 11:00 AM, Michael wrote:
> Hi,
>
> i make a lot of http calls to my backend. I use a custom
> var myagent = new http.Agent();
> myagent.maxSockets = 50;
> for my requests. If i make 51 requests at a time, the last request will see
> an error:
> Error: socket hang up
> at cr
On Thu, Feb 28, 2013 at 8:54 AM, Dennis Sänger wrote:
> Hi Guys,
>
> is there any chance to compile node.js in at least version 0.8 on a ubuntu
> 8.04 system?
> I didn't find any ppa's or guides how or even if this is possible.
>
> I tried to use nvm to install node 0.8.21 on an ubuntu 8.04 machin
On Fri, Mar 1, 2013 at 3:03 PM, Bert Belder wrote:
>
> On Friday, March 1, 2013 6:26:05 AM UTC+1, Tomasz Janczuk wrote:
>>
>> Can uv_async_init() and uv_default_loop() be called from any thread?
>
>
> uv_default_loop() is threadsafe.
Not on Unices.
I don't think there's much point it making it t
On Sat, Mar 2, 2013 at 12:01 AM, carlos8f wrote:
> Anyone have experience with using jailkit to deploy a node app?
>
> I have set up a minimal jail environment and used jk_cp to copy in the node
> binary (and auto-detected .so files):'
>
> ubuntu@ip-10-158-7-212:~/intl$ sudo jk_cp -v /opt/jail /us
On Sat, Mar 2, 2013 at 1:26 AM, carlos8f wrote:
> ok, here it is
>
> https://gist.github.com/carlos8f/5068936
Consider this fixed as of https://github.com/joyent/node/commit/7707acd :-)
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-Li
On Sat, Mar 2, 2013 at 7:55 AM, Sebi wrote:
> Okay, nothing that I think. Okay, then take a look at the change logs and
> see, that the early versions were released almost daily.
For those of you longing for the v0.1 days, we'll be releasing nightly
builds soon.
--
--
Job Board: http://jobs.no
On Mon, Mar 4, 2013 at 5:17 PM, Bodo Kaiser wrote:
> Hello,
>
> I am working on another WebSocket implementation and currently I experience
> that a socket closes after two minutes.
>
> Is there something I could set to avoid this behavior or do I have to use
> some sort of "heartbeat" frames?
>
>
On Tue, Mar 5, 2013 at 9:45 PM, Eugene Girshov wrote:
> Does Node really support half-closed HTTP connections? lib/http.js sets
> 'httpAllowHalfOpen' property in the http.Server, however it is not
> documented.
> A basic scenario works (test/simple/test-http-server.js) but this is the
> only test
On Tue, Mar 5, 2013 at 7:18 PM, Aziz Khoury wrote:
> I am having an Unknown Encoding error when a WriteStream.write()
> The stream creating seams fine, the default 'ut8' is in there, even if I
> specify the encoding, same error occurs..
>
> I have written the question on SO with details,
>
> http:
On Wed, Mar 6, 2013 at 5:54 PM, Bert Belder wrote:
>
>
> On Wednesday, March 6, 2013 2:32:11 PM UTC+1, Brian Hunt wrote:
>>
>> It would seem that there are two issues at work:
>> 1. getaddrinfo is returning IPv4 addresses even though the name
>> `myhost.local` is tied only to an IPv6 address in /
On Thu, Mar 7, 2013 at 8:33 AM, Anup Vasudeva
wrote:
> Can node.js be installed on an embedded server. I have a project requirement
> where I have an embedded device with a Baracudda server inside it.
> Is there any scope to run node.js on that server? Please assist.
> Thanks for reading.
Have yo
On Tue, Mar 12, 2013 at 3:09 PM, senthil kumar wrote:
> export NODE_PATH=ODE_PATH:lib && ./node_modules/it/bin/it -r dotmatrix
> /bin/sh: ./node_modules/it/bin/it: not found
> make: *** [test] Error 127
>
> Please help me on this.
>
> Thanks
You could start by telling what module that is...
See
On Wed, Mar 13, 2013 at 6:03 PM, AJ ONeal wrote:
> Perhaps the very best part of node v0.10.0 is that all of the core modules
> are finally fully ES5 compliant!!!
>
> Although, you can't use es5-compliant mode with a shebang
> (because you can't pass the --use_strict argument),
> so I made a shim
On Thu, Mar 14, 2013 at 2:16 PM, Matt wrote:
> Discussion here: https://github.com/joyent/node/issues/5005
>
> If you've ever done something like:
>
> fs.unlink(file); // don't care if it works or not
>
> This won't work in v0.10.0 any more. If you want to ignore errors you need
> to pass in a
On Thu, Mar 14, 2013 at 3:58 PM, Matt wrote:
> I still think the documentation should be updated to reflect that callbacks
> are no longer optional. They are only optional if the call succeeds, which
> you can't really know ahead of time.
https://github.com/joyent/node/commit/fa05e8a :-/
--
--
On Thu, Mar 14, 2013 at 4:10 PM, Chris Scribner wrote:
> StreamWrap: Aborting due to unwrap failure at ../src/stream_wrap.cc:125
>
> I'm seeing this error after upgrading to node v0.10. I haven't debugged into
> it yet, but does anyone have any details about that error?
>
> Thanks,
>
> Chris
It's
On Fri, Mar 15, 2013 at 3:27 PM, Benjamin Farrell wrote:
> Hey everyone,
> This group's help got me up and running with my first Node.js AddOn a couple
> months back, I'm pretty excited that all this stuff is working. But now
> that I have something stable, I realize that my C++ code is a little
On Fri, Mar 15, 2013 at 10:05 PM, Greg Martin wrote:
> In all Unices I've used the behavior for unlink is to mark a file for
> deletion when no file descriptors reference it. However, in using a UNIX
> socket with nodejs I have found that calling unlink after the socket is
> created causes it to b
On Tue, Mar 19, 2013 at 5:12 PM, Nabeel S. wrote:
> The make install did not install them. There's no mention of them being
> moved anywhere. node-gyp does not install them in any system directory, and
> the node-gyp configure and install do not find them either (though, a `find
> /` shows them in
On Tue, Mar 19, 2013 at 8:54 PM, Matt wrote:
> I created a simple script to test cluster's performance sending messages to
> workers.
>
> My problem is it slows down the send() rate significantly as I add workers,
> starting at 1 worker being the fastest. I would expect the send() rate to be
> com
On Wed, Mar 20, 2013 at 2:26 PM, Matt wrote:
> On Wed, Mar 20, 2013 at 8:34 AM, Ben Noordhuis wrote:
>>
>> What numbers are you seeing? large_number / number_of_workers is what
>> you should expect to see: a fairly constant total throughput with
>> per-worker throug
1 - 100 of 1151 matches
Mail list logo
