fix: Reset all counter in metadata with purge for RequestQueue#1686
Merged
vdusek merged 1 commit intoapify:masterfrom Jan 26, 2026
Merged
fix: Reset all counter in metadata with purge for RequestQueue#1686vdusek merged 1 commit intoapify:masterfrom
purge for RequestQueue#1686vdusek merged 1 commit intoapify:masterfrom
Conversation
Collaborator
Author
|
@vdusek The current behavior of |
Pijukatel
approved these changes
Jan 26, 2026
Collaborator
|
Yeah, I initially thought |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
purgeforRequestQueue. This will be more consistent with JS. Also, saving thetotal_request_countandhandled_request_countcounters causes confusion among users, especially when this happens with thedefaultqueue.Issues