RateLimiterQueue doesn't process requests evenly when execEvenly option enabled

Most likely, there is a bug with returned result from a limiter. When any limiter is created with execEvenly and request is delayed, it is delayed with setTimeout, but msBeforeNext is not updated after timeout. RateLimiterQueue relies on msBeforeNext to make decision on how a request should be processed/queued.

Further investigation required.

Any updates on this?

@arslnb I think, nobody looked into it.