I was expecting that I could call drained() at any point and it would wait until the fastq was empty.
From the implementation:
it looks like this isn't true if the fastq is already empty when you call it.
I think other people may expect it to work the way I did, so I am filing a bug in case.
I was expecting that I could call
drained()at any point and it would wait until the fastq was empty.From the implementation:
fastq/queue.js
Line 268 in 9435e99
I think other people may expect it to work the way I did, so I am filing a bug in case.