Incompatible with git 2.36.0

[tjcutajar]

Bug

upgrading to git 2.36.0 causes garden to error.

Current Behavior

commands raise
Path /Users/myUser/.garden/bin/static/kubernetes/system is not in a git repository root. Garden must be run from within a git repo. Please run 'git init' if you're starting a new project and repository, or move the project to an existing repository, and try again.

Your environment

• OS: MacOS 12.3.1

garden version 0.12.39

[Orzelius]

what command are you running and are you running it within a git repository?

[tjcutajar]

running either deploy or delete from within a git repo. Downgrading git to 2.35.3 resolves it.

[twelvemo]

Hello @tjcutajar , thanks for flagging the issue. I am having a hard time reproducing it. I just upgraded to git 2.36.0 and ran garden deploy without any issues. I am also on MacOS. Can you give me any additional infos to reproduce?

[tjcutajar]

@twelvemo maybe try deleting your .garden directory

[alexkuretz]

We are getting this on Windows as well while trying to set up a new system. My coworker getting the error is using git 2.36.0 and my setup with git 2.35.1 does not show the error. We are running within our git repository.

Failed resolving provider kubernetes. Here is the output:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Path C:\Users\username\.garden\bin\static\kubernetes\system is not in a git repository root. Garden must be run from within a git repo. Please run git init if you're starting a new project and repository, or move the project to an existing repository, and try again.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Failed resolving one or more providers:

• kubernetes

[alexkuretz]

Another coworker encountered this today and found that by going into the .garden\bin\static\kubernetes\system directory and doing a 'git status' he was able to set a permission that allowed garden to work. I believe it's related to the "Stricter repository ownership checks" change in git 2.36:
https://github.blog/2022-04-18-highlights-from-git-2-36/

[edvald]

Thanks for the investigation @alexkuretz! I figure it's a simple fix, we'll get on it.

[ITHedgeHog]

I got around this by running the command git config --add safe.directory C:\git\oemplatform which is the project root for me, this got me running.

[vvagaytsev]

The fix is available in the edge release.