You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In such a scenario I would expect to get "Hello World" logged immediately (or perhaps after 1 second) but instead all 10 of the cancelled tasks remain in the queue and are ejected one by one, causing "Hello World" to print after 10 seconds.
The text was updated successfully, but these errors were encountered:
My team also just ran into a situation where we batch up a bunch of stuff into the queue and then sometimes cancel a large portion. The fact that these are still counted towards the intervalCap is having a pretty big impact on the throughput/speed.
The documentation for the
signal
option of theadd()
method is misleading:However, when a providing an abort signal, the associated items are not removed from the queue. This is problematic when combined with an
intervalCap
:In such a scenario I would expect to get "Hello World" logged immediately (or perhaps after 1 second) but instead all 10 of the cancelled tasks remain in the queue and are ejected one by one, causing "Hello World" to print after 10 seconds.
The text was updated successfully, but these errors were encountered: