gin-contrib / gin-contrib/cache
Appending cache values
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 456
- Forks
- 100
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
is this issue or feature? I dont understand why check cache again and append the value if there are some value?
First time we check the cache when initializing CachePage middleware and this is the second one. There is a problem with concurrently similar requests.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the CachePage middleware initialization and the later cache check described in the issue. Reproduce concurrent similar requests and determine the intended behavior when a cache value already exists; the issue is ready only once the duplicate-check and append behavior are clearly specified and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100