opened
AnthonyMDev
username_0
When the `execute` method is called, but the block was not called, because the rate limit had not been reached, the execution time was still being recorded. This would cause the block to never be called if the `execute` method was continually called too quickly. The execution time should only be recorded on a successful execution.
Fixed bug where limit was being reset when the block was not executed
issue
created
AnthonyMDev
username_0
I just realized that this is also fixed by #13, I think the syntax for fixing this bug is slightly cleaner in this PR. Also, #16 depends on this PR, so if you plan on pulling #16, you can actually just close this and #13.
comment
created
soffes
username_1
Thanks so much! Reworked a bit to make sure accessing the dictionary happens in the queue to avoid threading race conditions.
comment