g10k: g10k cache sometimes gets corrupted
From time to time I find that the g10k cache becomes corrupted and I am forced to delete it. This is a big problem in production and ultimately may mean I can’t use g10k in production. A recent example was a failure like this:
executeCommand(): git command failed: git --git-dir /tmp/g10k/git@git.example.com-PUP_puppet-fstab.git remote update --prune exit status 128
Output: fatal: Not a git repository: '/tmp/g10k/git@git.example.com-PUP_puppet-fstab.git'
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 26 (9 by maintainers)
Commits related to this issue
- add -maxextractworker parameter/config setting using remeh/sizedwaitgroup #79 #77 #76 — committed to xorpaul/g10k by xorpaul 7 years ago
- add -retrygitcommands cli parameter or retry_git_commands g10k config setting for corrupted Git caches #76 — committed to xorpaul/g10k by xorpaul 7 years ago
Alright then.