infinite error loop

[pagameba]

I'm experiencing an infinite stack dump when using long-stack-traces in my code, I've boiled it down to the shortest path that reproduces the problem. Without long-stack-traces, the code works fine. I'm going to try to attach a zip with a stripped down test case.

The workflow involves using node-seq to serialize some async calls on server startup. I'm setting up a database connection to a postgres database using node-postgres. As part of the server startup, I also load some SQL and create tables in the database if they do not already exist. This is the point at which the error happens - if the table doesn't exist then with long-stack-traces it goes into some kind of infinite loop - without long-stack-traces, it creates the table (no error) and happily continues.

Pre-requisites for running the test case are

• postgres
• npm install pg
• npm install seq
• modify config.json in the testcase to supply your postgres credentials for localhost (and perhaps create a test database)

[pagameba]

ok, there is no way (that I can see) to attach files to issues so I put them into https://gist.github.com/798996. The code assumes that test.sql is in a folder called sql next to test.js.

[tlrobinson]

I'm unable to reproduce this. I've installed postgres, pg, and seq, creates a new database and user, run test.js, and got the following output on the first and second run:

$ node test.js 
connected to database
checking for test with sql SELECT relname FROM pg_class  WHERE relname = 'test';
loading sql for table
Table created, moving on
null
okay, we are done here.
^C
$ node test.js 
connected to database
checking for test with sql SELECT relname FROM pg_class  WHERE relname = 'test';
okay, we are done here.

Are you running 0.1.1 or 0.1.0?

[pagameba]

0.1.1 installed via npm, node 0.3.4