fatal: 'origin' is not a commit and a branch 'v0.14.1' cannot be created from it

[Voxar]

I got the asdf 0.16 notice a few days ago on our failing GHA builds. I Added the with: asdf_branch: v0.14.1 as 0.14.1 seemed to be the version used on our latest successful build, and that worked.

But since yesterday we are instead met with this message. Any ideas to what could possibly have changed?

Run asdf-vm/actions/install@v3
  with:
    asdf_branch: v0.14.1
    skip_install: false
  env:
    EXPO_BUILD_RELEASE: true
Updating asdf in ASDF_DIR "/Users/runner/.asdf" on branch "v0.14.1"
/opt/homebrew/bin/git remote set-branches origin v0.14.1
/opt/homebrew/bin/git fetch --depth 1 origin v0.14.1
From https://github.com/asdf-vm/asdf
 * tag               v0.14.1    -> FETCH_HEAD
/opt/homebrew/bin/git checkout -B v0.14.1 origin
fatal: 'origin' is not a commit and a branch 'v0.14.1' cannot be created from it
Error: Action failed with error Error: The process '/opt/homebrew/bin/git' failed with exit code 128

The build step

      - name: Install asdf & tools
        uses: asdf-vm/actions/install@v3
        with:
          asdf_branch: v0.14.1

Same result when I try asdf_branch: v0.15.0

[Voxar]

Here's the log from the successful build 2 days ago

Run asdf-vm/actions/install@v3
  with:
    asdf_branch: v0.14.1
    skip_install: false
  env:
    EXPO_BUILD_RELEASE: true
Cloning asdf into ASDF_DIR "/Users/runner/.asdf" on branch "v0.14.1"
/opt/homebrew/bin/git clone --depth 1 --branch v0.14.1 --single-branch https://github.com/asdf-vm/asdf.git /Users/runner/.asdf
Cloning into '/Users/runner/.asdf'...
/Users/runner/.asdf/bin/asdf plugin-list
No plugins installed
Installing nodejs plugin...
/Users/runner/.asdf/bin/asdf plugin-add nodejs
initializing plugin repository...Cloning into '/Users/runner/.asdf/repository'...
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

[Voxar]

How can the git commands be so different?

Working:

/opt/homebrew/bin/git clone --depth 1 --branch v0.14.1 --single-branch https://github.com/asdf-vm/asdf.git /Users/runner/.asdf`

Failing:

/opt/homebrew/bin/git remote set-branches origin v0.14.1
/opt/homebrew/bin/git fetch --depth 1 origin v0.14.1

[Voxar]

Ah. I am cacheing the .asdf directory and the failing builds are trying to do an update instead of an install.

The update step is broken:

actions/src/setup/index.ts

Lines 26 to 32 in 1bf052e

	if (fs.existsSync(asdfDir)) {
	core.info(`Updating asdf in ASDF_DIR "${asdfDir}" on branch "${branch}"`);
	const options = {cwd: asdfDir};
	await exec.exec('git', ['remote', 'set-branches', 'origin', branch], options);
	await exec.exec('git', ['fetch', '--depth', '1', 'origin', branch], options);
	await exec.exec('git', ['checkout', '-B', branch, 'origin'], options);
	} else {

[Voxar]

It might be a new minor git version that broke it

Working build with .asdf cache hit

  /opt/homebrew/bin/git version
  git version 2.47.1

Broken build with .asdf cache hit

  /opt/homebrew/bin/git version
  git version 2.48.1

[Voxar]

And this is why we want to cache the .asdf directory

Cache miss

Cache hit

[se-chris-thach]

+1 seeing the same issue.

[Voxar]

PR: #591

[jthegedus]

To use the change from #591 immediately you can reference the specific SHA from master:

steps:
  # Reference a specific commit (most strict, for the supply-chain paranoid)
  - uses: asdf-vm/actions/install@179e9530fcd91100e4621bf7e563e7daa8398c52

The final v4 release requires additional maintenance in other areas before release. I am working on this today.

Thanks for your collective patience.

closed in #591