When Queue is not empty, cannot call commit() in a query callback to queue COMMIT. That is, COMMIT is executed immediately, without waiting for the Queue to clear completely. This is because the original query callback causes the Queue to re-execute, causing the COMMIT query to be executed, as well.
When Queue is not empty, cannot call commit() in a query callback to queue COMMIT. That is, COMMIT is executed immediately, without waiting for the Queue to clear completely. This is because the original query callback causes the Queue to re-execute, causing the COMMIT query to be executed, as well.
This should be fixed in 0.3.2