Closed dreadjr closed 8 years ago
Looking into this - likely a Firebase client bug
Makes sense. I'll see if I can narrow it down to a query from the client.
On Tuesday, August 18, 2015, Chris Raynor notifications@github.com wrote:
Looking into this - likely a Firebase client bug
— Reply to this email directly or view it on GitHub https://github.com/firebase/firebase-queue/issues/31#issuecomment-132366994 .
@dreadjr we tracked the issue down to a quirk in the way we raise events for indexed data in the firebase client and the way firebase-queue responds to events. I think we have enough info now to work on a fix.
Sweet. Thanks.
On Tuesday, August 18, 2015, jdimond notifications@github.com wrote:
@dreadjr https://github.com/dreadjr we tracked the issue down to a quirk in the way we raise events for indexed data in the firebase client and the way firebase-queue responds to events. I think we have enough info now to work on a fix.
— Reply to this email directly or view it on GitHub https://github.com/firebase/firebase-queue/issues/31#issuecomment-132378492 .
Any progress on this issue?
@dreadjr this should have been fixed with version 2.3.0 of the client library. Closing, please reopen if you think this is still broken.
I am having an issue when i have IndexOn: ["_state"] and tasks are being left unprocessed until the process is restarted.
I created a simple reproducible repo with the code and package versions. Maybe i am doing something stupid, please let me know if you can reproduce or what is wrong.