dronus

Clearly a synchronisation issue, subsequent runs of the same code in a fresh node showing different outcomes, sometimes capturing the err, sometimes not.

simple example that produces different, buggy outputs on repeated runs: test.sqlite dump: ``` CREATE TABLE users (id INTEGER PRIMARY KEY ON CONFLICT REPLACE, email TEXT UNIQUE ON CONFLICT ABORT); INSERT...

As my sqlite3 was quite old, I managed to install 3.8.3.1. The error message changed, the erratic behaviour persists. OS is Ubuntu 12.04 x64.

I don't think the problem should be intercepted by error handlers, as it is not caused by sqlite3 errors itself, nor the content or errors of the database. It triggers...

a small thought: If we talk about the query callback err, we do not talk about an error in sense of some code problem, but about a condition that can...

This is a hard one! Actually, your new test works fine for me. However, the following self-contained code does not: ``` var dblite = require('dblite' ); var db=dblite('/tmp/test.sqlite'); db .query('DROP...

The problem was introduced by commit 939ec0c57e930b8ce1ab745230a527b1e413cea5 . Prior version is working as expected!

What may going on: stderr and stdout of the sqlite process are not synchronized by any mechanism. If sqlite purges both pipes without much delay inbetween, it is upon kernel...

"The word compromise is the key, what you don't consider an error is an error to me.", well it also is named error by dblite and send to 'stderr' by...

Maybe you could merge the two output streams while invoking the sqlite3 process. They are then less prone to go out of sync, and arrive at one node.js callback just...