Gitea: Git Healthcheck/GC failures (gc.log) #38
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#38
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are a number of repositories that have gotten to have a 'gc.log' file; most with the following contents:
The implication seems to be that the garbage-collection isnt functioning properly (it should, internally, also be doing a git prune, according to documentation on the subject).
The current setup does not have the garbage-collection enabled (its off by default), and having triggered it manually a little while before, it's clear that some repositories have a git-repo that's 'complex' enough to have a default timeout of 60 seconds being way too short for that. Even the git.timout
GC
of 360 seconds seems to be too short for some repositories.Proposal for now is to add/modify the app.ini with the following:
as well as change the GIT GC timeout
Philipp Oeser referenced this issue2023-02-17 11:49:26 +01:00
Git Healthcheck/GC failures (gc.log)to Gitea: Git Healthcheck/GC failures (gc.log)