calling complete! on already completed task messes up stats about durable-queue HOT 2 OPEN

Definitely not intentional, complete! should be idempotent.

from durable-queue.

I guess this is still an issue? I'm using the newest version of durable-queue, but I see the same issue:

  (Stats about from-tables-to-topics-queue:  {message {:num-slabs 1, :num-active-slabs 1, :enqueued 113245, :retried 0, :completed 113246, :in-progress -1}})

Also, I have 20 threads reading from this queue, and they then do an HTTP call, which is slow, so I am not surprised to see "20" as "in-process". But I am surprised to see a gap of 29 between enqueued and completed. I'm running this on an EC2 instance, and I know AWS has a reputation for poor I/O performance. Should I assume that the call to complete! is slow enough to explain the unexpected extra 9 between enqueued and completed?

Stats about the from-topics-to-persistence-queue:  {message {:num-slabs 1, :num-active-slabs 1, :enqueued 683, :retried 0, :completed 654, :in-progress 20}})

from durable-queue.