Skip to content

If a repository return no commitstatus, then still cache it but not query it from database (#30700) #30734

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

Conversation

lunny
Copy link
Member

@lunny lunny commented Apr 27, 2024

Backport #30700

The previous repository default branch commit status cache will only store if the commit status has value. So the repository which have no any commit status will always be fetched from database.

This PR will store the empty state of commit status of a repository into cache because the cache will be updated once there is a commit status stored.

…uery it from database (go-gitea#30700)

The previous repository default branch commit status cache will only
store if the commit status has value. So the repository which have no
any commit status will always be fetched from database.

This PR will store the empty state of commit status of a repository into
cache because the cache will be updated once there is a commit status
stored.
@lunny lunny added the performance/speed performance issues with slow downs label Apr 27, 2024
@lunny lunny added this to the 1.21.12 milestone Apr 27, 2024
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 27, 2024
@github-actions github-actions bot added the modifies/go Pull requests that update Go code label Apr 27, 2024
@wxiaoguang
Copy link
Contributor

Why backport a non-bugfix PR to 1.21?

@lunny lunny closed this Apr 27, 2024
@GiteaBot GiteaBot removed this from the 1.21.12 milestone Apr 27, 2024
@lunny lunny deleted the lunny/store_nostate_commitstatus_cache_2 branch April 27, 2024 17:04
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Jul 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. modifies/go Pull requests that update Go code performance/speed performance issues with slow downs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants