Closed kpgarrod closed 9 years ago
I'm assuming myData
is populated with your data - {}
pushed to a location in Firebase causes the key to be removed.
Assuming that, it doesn't look like the task is being claimed. You can add:
var winston = require('winston');
winston.level = 'debug';
Before you initialize the queue to get better debug logging. (you need to npm install winston)
What version of Node are you running? Some 0.11
versions are based on a V8 build with a broken sha implementation, which causes issues in the underlying Firebase client.
Besides that, you could also add:
var Firebase = require('firebase');
Firebase.enableLogging(true);
Again before initializing the queue, which will turn on the underlying Firebase debug logs
@drtriumph: thanks for the response. Yes, myData
has valid content, I have corrected the comment above to indicate that. I am using node.js v0.12.0.
My bad. It seems my code was not resolving a promise correctly in some circumstances.
I'm glad you found the cause, thank you for the follow-up
I am trying out firebase-queue and mostly enjoying the experience so far :).
I am experiencing one issue though. When I chain tasks, say:
When I start with
task_a
,task_a
andtask_b
run as I expect. When I start withtask_b
,task_b
runs as expected, buttask_c
does not.The task is left in this state:
If I restart the server, the task runs to completion as I expect.
Any suggestions please?