Skip to content
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

Commit count num in cache data will not be refreshed #23060

Closed
yp05327 opened this issue Feb 22, 2023 · 2 comments
Closed

Commit count num in cache data will not be refreshed #23060

yp05327 opened this issue Feb 22, 2023 · 2 comments
Labels

Comments

@yp05327
Copy link
Contributor

yp05327 commented Feb 22, 2023

Description

Relate to #22621 (comment)
It seems that commit count num in cache data will not be refreshed in the latest version.
But in try.gitea.io it works well. (Why? It seems that there are no changes related to this in recent)
Can anyone reproduce this too?

I added:

cache.Remove(repo.GetCommitsCountCacheKey(opts.NewBranch, true))

then the count nun will refresh after apping a partch.

Related functions maybe as following:
image

Gitea Version

latest

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

build

Database

None

@lunny
Copy link
Member

lunny commented Feb 22, 2023

try.gitea.io will always follow the latest version automatically.

@yp05327
Copy link
Contributor Author

yp05327 commented Feb 22, 2023

I tested this issue on another pc again and it worked well. So I close this issue.

@yp05327 yp05327 closed this as completed Feb 22, 2023
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants