Repository navigation
limiter: pass request context to LimitCounter I/O - #65
Open
team-humaki wants to merge 1 commit into
Open
team-humaki wants to merge 1 commit into
team-humaki wants to merge 1 commit into
Conversation
Add LimitCounterContext so network backends (Redis) can receive the request context for tracing. The limiter uses context.WithoutCancel so a client disconnect cannot skip the increment. Fixes go-chi#62
Benchmark Results |
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
1 participant
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.
Fixes #62.
Add
LimitCounterContextnext toLimitCounter. When a backend implements it,OnLimit/StatusContextpasscontext.WithoutCancel(r.Context())into increment/get so trace values propagate but a canceled request cannot skip the count.Existing
LimitCounterimplementations keep working via type assertion. The in-memory counter implements both.