-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too much warning "cannot get cache context when getting data" #23160
Comments
I think this has been fixed in #23054 |
Well, I think it still triggered warns with Gitea latest version "1.20.0+dev-34-gb9a9b8e46 built with GNU Make 4.4, go1.20.1 : bindata" |
In #23054,
It seems that cache will read from database directly when server starts. So is it possible that this context data is just not existed in the database? |
Agree, maybe so. |
The warning is not because of the record is not exist in database but cannot get the context cache key. I think #23186 will fix this. |
Use context parameter in `services/repository`. And use `cache.WithCacheContext(ctx)` to generate push action history feeds. Fix #23160
Thanks, I think it has been fixed! |
In what version should this have been fixed? I'm still getting them with 1.19.0:
|
Oh, 1.20.0, supposedly. Let's wait a bit more then. |
Description
A large number of cache warnings appear after pushing a large number of tags (about 2,000)
Gitea Version
1.20.0+dev (90a7bba)
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
Git Version
2.39.0.198
Operating System
archlinux
How are you running Gitea?
a command-line
Database
MySQL
The text was updated successfully, but these errors were encountered: