[GH-ISSUE #311 ] Unable to resolve v1: reference not found #217

Author

Owner

@jean-francois-labbe commented on GitHub (Jul 23, 2020):

I have the same issue

@jean-francois-labbe commented on GitHub (Jul 23, 2020): I have the same issue

kerem commented

Author

Owner

@thelfensdrfer commented on GitHub (Jul 27, 2020):

This usually means that the version, in your case v1, does not exist. You can try e.g. uses: ruby/setup-ruby@v1.40.0.

@thelfensdrfer commented on GitHub (Jul 27, 2020): This usually means that the version, in your case `v1`, does not exist. You can try e.g. `uses: ruby/setup-ruby@v1.40.0`.

kerem commented

Author

Owner

@PsypherPunk commented on GitHub (Jul 30, 2020):

I'm seeing something similar using actions-rs/toolchain@v1. If pushed to Github, the Action works as intended; running act locally, I see Unable to resolve v1: reference not found.

If I change this to actions-rs/toolchain@v1.0.6 then act works as expected.

As far as I can see, both v1.0.6 and v1 are valid references: https://github.com/actions-rs/toolchain/tags

@PsypherPunk commented on GitHub (Jul 30, 2020): I'm seeing something similar using `actions-rs/toolchain@v1`. If pushed to Github, the Action works as intended; running `act` locally, I see `Unable to resolve v1: reference not found`. If I change this to `actions-rs/toolchain@v1.0.6` then `act` works as expected. As far as I can see, both `v1.0.6` and `v1` are valid references: https://github.com/actions-rs/toolchain/tags

kerem commented

Author

Owner

@plauche commented on GitHub (Jul 30, 2020):

I'm seeing a similar issue but when using @HEAD as the ref which should generally be valid in a git repo. Works fine when deployed to GH actions.

@plauche commented on GitHub (Jul 30, 2020): I'm seeing a similar issue but when using `@HEAD` as the ref which should generally be valid in a git repo. Works fine when deployed to GH actions.

kerem commented

Author

Owner

@drewcoo commented on GitHub (Jul 31, 2020):

I'm seeing this failure in Act but not on GitHub, too.
I'm using cypress-io/github-action.
Using @v2 works on GitHub.
The repo does not have a v2 tag, so that fails with reference not found.
It had a v2.2.2 tag, which Act can find, but then it fails with this:

[web redesign functional test/tryit-2] Exec command '[node \actions\cypress-io-github-action@v2.2.2\dist\index.js]'
| internal/modules/cjs/loader.js:628
| throw err;
| ^
|
| Error: Cannot find module '/github/workspace/\actions\cypress-io-github-action@v2.2.2\dist\index.js'
| at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15)
| at Function.Module._load (internal/modules/cjs/loader.js:527:27)
| at Function.Module.runMain (internal/modules/cjs/loader.js:839:10)
| at internal/main/run_main_module.js:17:11 {
| code: 'MODULE_NOT_FOUND',
| requireStack: []
| }

(marking the output above as code mangled it badly, so I bolded instead)

@drewcoo commented on GitHub (Jul 31, 2020): I'm seeing this failure in Act but not on GitHub, too. I'm using cypress-io/github-action. Using @v2 works on GitHub. The repo does not have a v2 tag, so that fails with reference not found. It had a v2.2.2 tag, which Act can find, but then it fails with this: **[web redesign functional test/tryit-2] Exec command '[node \actions\cypress-io-github-action@v2.2.2\dist\index.js]' | internal/modules/cjs/loader.js:628 | throw err; | ^ | | Error: Cannot find module '/github/workspace/\actions\cypress-io-github-action@v2.2.2\dist\index.js' | at Function.Module._resolveFilename (internal/modules/cjs/loader.js:625:15) | at Function.Module._load (internal/modules/cjs/loader.js:527:27) | at Function.Module.runMain (internal/modules/cjs/loader.js:839:10) | at internal/main/run_main_module.js:17:11 { | code: 'MODULE_NOT_FOUND', | requireStack: [] | }** (marking the output above as code mangled it badly, so I bolded instead)

kerem commented

Author

Owner

@joerodrig commented on GitHub (Jul 31, 2020):

I was having this issue as well on Act. I got around it by forking the repo and creating a new tag off of the head of the latest release(v1.40.0) and creating a new tag that was just v1, which was recognized. See this release tag. My guess is that this parser code is looking for a base version tag(ie. v1), which it's not finding because the base v1 tag here is v1.0.0

I'm not 100% sure if this worked as a full workaround though, because I'm getting a new issue when attempting to install my specified ruby version now:

[Rails Unit Tests/build]   ❓  ::group::Extracting Ruby
| [command]/bin/tar -xz -C /github/home/.rubies -f /tmp/e24aa2b2-f52a-435c-9cde-66bd2b89b387
| Took   0.25 seconds
[Rails Unit Tests/build]   ❓  ::endgroup::
[Rails Unit Tests/build]   ⚙  ::set-env:: PATH=/github/home/.rubies/ruby-2.6.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[Rails Unit Tests/build]   ❓  ::group::Installing Bundler
| Using Bundler 2 from Gemfile.lock BUNDLED WITH 2.1.4
| [command]/github/home/.rubies/ruby-2.6.6/bin/gem install bundler -v ~> 2 --no-document
| Took   0.00 seconds
[Rails Unit Tests/build]   ❓  ::endgroup::
[Rails Unit Tests/build]   ❗  ::error::There was an error when attempting to execute the process '/github/home/.rubies/ruby-2.6.6/bin/gem'. This may indicate the process failed to start. Error: spawn /github/home/.rubies/ruby-2.6.6/bin/gem ENOENT
[Rails Unit Tests/build]   ❌  Failure - joerodrig/setup-ruby@v1

@joerodrig commented on GitHub (Jul 31, 2020): I was having this issue as well on Act. I got around it by forking the repo and creating a new tag off of the head of the latest release(v1.40.0) and creating a new tag that was just `v1`, which was recognized. See [this release tag](https://github.com/joerodrig/setup-ruby/releases/tag/v1). My guess is that this parser code is looking for a base version tag(ie. v1), which it's not finding because the base v1 tag here is `v1.0.0` I'm not 100% sure if this worked as a full workaround though, because I'm getting a new issue when attempting to install my specified ruby version now: ``` [Rails Unit Tests/build] ❓ ::group::Extracting Ruby | [command]/bin/tar -xz -C /github/home/.rubies -f /tmp/e24aa2b2-f52a-435c-9cde-66bd2b89b387 | Took 0.25 seconds [Rails Unit Tests/build] ❓ ::endgroup:: [Rails Unit Tests/build] ⚙ ::set-env:: PATH=/github/home/.rubies/ruby-2.6.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [Rails Unit Tests/build] ❓ ::group::Installing Bundler | Using Bundler 2 from Gemfile.lock BUNDLED WITH 2.1.4 | [command]/github/home/.rubies/ruby-2.6.6/bin/gem install bundler -v ~> 2 --no-document | Took 0.00 seconds [Rails Unit Tests/build] ❓ ::endgroup:: [Rails Unit Tests/build] ❗ ::error::There was an error when attempting to execute the process '/github/home/.rubies/ruby-2.6.6/bin/gem'. This may indicate the process failed to start. Error: spawn /github/home/.rubies/ruby-2.6.6/bin/gem ENOENT [Rails Unit Tests/build] ❌ Failure - joerodrig/setup-ruby@v1 ```

kerem commented

Author

Owner

@mossad-zika commented on GitHub (Aug 20, 2020):

cmon, fix it please

@mossad-zika commented on GitHub (Aug 20, 2020): cmon, fix it please

kerem commented

Author

Owner

@pezholio commented on GitHub (Sep 10, 2020):

@joerodrig Yep, I'm having exactly the same problem. It worked the first couple of times specifying the full tag, but now I'm getting that same error

@pezholio commented on GitHub (Sep 10, 2020): @joerodrig Yep, I'm having exactly the same problem. It worked the first couple of times specifying the full tag, but now I'm getting that same error

kerem commented

Author

Owner

@marartner commented on GitHub (Sep 15, 2020):

same issue with symfonycorp/security-checker-action@v2 - working fine on github itself, definitely exists. but locally:

[symfony-security-check/symfony]   ☁  git clone 'https://github.com/symfonycorp/security-checker-action' # ref=v2
[symfony-security-check/symfony] Unable to resolve v2: reference not found

doing symfonycorp/security-checker-action@038cecb1ee1bf871d1ef43e873f813d900a1125c (038... being the exact commit that tag is on) works. but that ofc shouldn't be a long term solution...

@marartner commented on GitHub (Sep 15, 2020): same issue with `symfonycorp/security-checker-action@v2` - working fine on github itself, definitely exists. but locally: ```sh [symfony-security-check/symfony] ☁ git clone 'https://github.com/symfonycorp/security-checker-action' # ref=v2 [symfony-security-check/symfony] Unable to resolve v2: reference not found ``` doing `symfonycorp/security-checker-action@038cecb1ee1bf871d1ef43e873f813d900a1125c` (038... being the exact commit that tag is on) works. but that ofc shouldn't be a long term solution...

kerem commented

Author

Owner

@askoriy commented on GitHub (Oct 5, 2020):

The issue occurs if v1, v2 refs are branches, not tags. But yes, it's very annoying and needs to be fixed.

The same is https://github.com/nektos/act/issues/234

@cplee could you look into? Thanks so much

@askoriy commented on GitHub (Oct 5, 2020): The issue occurs if v1, v2 refs are branches, not tags. But yes, it's very annoying and needs to be fixed. The same is https://github.com/nektos/act/issues/234 @cplee could you look into? Thanks so much

kerem commented

Author

Owner

@bndynet commented on GitHub (Nov 11, 2020):

I'm seeing something similar using actions-rs/toolchain@v1. If pushed to Github, the Action works as intended; running act locally, I see Unable to resolve v1: reference not found.

If I change this to actions-rs/toolchain@v1.0.6 then act works as expected.

As far as I can see, both v1.0.6 and v1 are valid references: https://github.com/actions-rs/toolchain/tags

I used the exact version and resolved.

@bndynet commented on GitHub (Nov 11, 2020): > I'm seeing something similar using `actions-rs/toolchain@v1`. If pushed to Github, the Action works as intended; running `act` locally, I see `Unable to resolve v1: reference not found`. > > If I change this to `actions-rs/toolchain@v1.0.6` then `act` works as expected. > > As far as I can see, both `v1.0.6` and `v1` are valid references: https://github.com/actions-rs/toolchain/tags I used the exact version and resolved.

kerem commented

Author

Owner

@akoshulian-exos commented on GitHub (Nov 12, 2020):

I'm seeing something similar using actions-rs/toolchain@v1. If pushed to Github, the Action works as intended; running act locally, I see Unable to resolve v1: reference not found.
If I change this to actions-rs/toolchain@v1.0.6 then act works as expected.
As far as I can see, both v1.0.6 and v1 are valid references: https://github.com/actions-rs/toolchain/tags

I used the exact version and resolved.

It works the first time after changing to the full version. On the second time, I get the same error.

@akoshulian-exos commented on GitHub (Nov 12, 2020): > > I'm seeing something similar using `actions-rs/toolchain@v1`. If pushed to Github, the Action works as intended; running `act` locally, I see `Unable to resolve v1: reference not found`. > > If I change this to `actions-rs/toolchain@v1.0.6` then `act` works as expected. > > As far as I can see, both `v1.0.6` and `v1` are valid references: https://github.com/actions-rs/toolchain/tags > > I used the exact version and resolved. It works the first time after changing to the full version. On the second time, I get the same error.

kerem commented

Author

Owner

@rna commented on GitHub (Jan 3, 2021):

Is anyone found a fix for ruby setup: Error: reference not found

    - name: Set up Ruby
      uses: ruby/setup-ruby@v1

@rna commented on GitHub (Jan 3, 2021): Is anyone found a fix for ruby setup: `Error: reference not found` ``` - name: Set up Ruby uses: ruby/setup-ruby@v1 ```

kerem commented

Author

Owner

@tonyaajjackson commented on GitHub (Jan 3, 2021):

Seeing the same issue with the setup-python action:

[Tests/build-3] ⭐  Run Set up Python ${{ matrix.python-version }}
[Tests/build-3]   ☁  git clone 'https://github.com/actions/setup-python' # ref=v1
[Tests/build-3] Unable to resolve v1: reference not found

Running git clone 'https://github.com/actions/setup-python' # ref=v1 locally is successful.

Github actions yaml file can be found here:
https://github.com/plamere/spotipy/blob/master/.github/workflows/pythonapp.yml

@tonyaajjackson commented on GitHub (Jan 3, 2021): Seeing the same issue with the `setup-python` action: ``` [Tests/build-3] ⭐ Run Set up Python ${{ matrix.python-version }} [Tests/build-3] ☁ git clone 'https://github.com/actions/setup-python' # ref=v1 [Tests/build-3] Unable to resolve v1: reference not found ``` Running `git clone 'https://github.com/actions/setup-python' # ref=v1` locally is successful. Github actions yaml file can be found here: https://github.com/plamere/spotipy/blob/master/.github/workflows/pythonapp.yml

kerem commented

Author

Owner

@ps-brandmonitor commented on GitHub (Jan 12, 2021):

Is anyone found a fix for ruby setup: Error: reference not found
    - name: Set up Ruby
      uses: ruby/setup-ruby@v1

I did:

uses: ruby/setup-ruby@v1.62.0

That seemed to do the trick!

@ps-brandmonitor commented on GitHub (Jan 12, 2021): > Is anyone found a fix for ruby setup: `Error: reference not found` > > ``` > - name: Set up Ruby > uses: ruby/setup-ruby@v1 > ``` I did: uses: ruby/setup-ruby@v1.62.0 That seemed to do the trick!

kerem commented

Author

Owner

@rna commented on GitHub (Jan 13, 2021):

Now, I'm getting this new error after changing as per your suggestion. @ps-rruiz

[Rails Tests/RSpec] ⭐  Run actions/checkout@v2
[Rails Tests/RSpec]   ✅  Success - actions/checkout@v2
[Rails Tests/RSpec] ⭐  Run ruby/setup-ruby@v1.62.0
[Rails Tests/RSpec]   ☁  git clone 'https://github.com/ruby/setup-ruby' # ref=v1.62.0
[Rails Tests/RSpec]   🐳  docker cp src=/home/ramesh/.cache/act/ruby-setup-ruby@v1.62.0 dst=/actions/
[Rails Tests/RSpec]   ❗  ::error::The environment variable ImageOS must be set
[Rails Tests/RSpec]   ❌  Failure - ruby/setup-ruby@v1.62.0
Error: exit with `FAILURE`: 1

@rna commented on GitHub (Jan 13, 2021): Now, I'm getting this new error after changing as per your suggestion. @ps-rruiz ``` [Rails Tests/RSpec] ⭐ Run actions/checkout@v2 [Rails Tests/RSpec] ✅ Success - actions/checkout@v2 [Rails Tests/RSpec] ⭐ Run ruby/setup-ruby@v1.62.0 [Rails Tests/RSpec] ☁ git clone 'https://github.com/ruby/setup-ruby' # ref=v1.62.0 [Rails Tests/RSpec] 🐳 docker cp src=/home/ramesh/.cache/act/ruby-setup-ruby@v1.62.0 dst=/actions/ [Rails Tests/RSpec] ❗ ::error::The environment variable ImageOS must be set [Rails Tests/RSpec] ❌ Failure - ruby/setup-ruby@v1.62.0 Error: exit with `FAILURE`: 1 ```

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jan 13, 2021):

@rna specify OS version in env file e.g.: ImageOS=ubuntu18 and use it via --env-file flag

@catthehacker commented on GitHub (Jan 13, 2021): @rna specify OS version in `env` file e.g.: `ImageOS=ubuntu18` and use it via `--env-file` flag

kerem commented

Author

Owner

@lufia commented on GitHub (Jan 15, 2021):

I added commits on #471 and #433 and they were merged (but they aren't released yet), so I'm expecting this issue will be fixed.

@lufia commented on GitHub (Jan 15, 2021): I added commits on #471 and #433 and they were merged (but they aren't released yet), so I'm expecting this issue will be fixed.

kerem commented

Author

Owner

@theowenyoung commented on GitHub (Jan 23, 2021):

@cplee may I know when to release next version? This fix really helps.

@theowenyoung commented on GitHub (Jan 23, 2021): @cplee may I know when to release next version? This fix really helps.

kerem commented

Author

Owner

@cplee commented on GitHub (Jan 23, 2021):

@theowenyoung - just released v0.2.19

@cplee commented on GitHub (Jan 23, 2021): @theowenyoung - just released `v0.2.19`

kerem commented

Author

Owner

@yuuuxt commented on GitHub (Jan 23, 2021):

It's working in Windows 10 using cmd and powershell, but not working with cmder. using the just released version 0.2.19.

@yuuuxt commented on GitHub (Jan 23, 2021): It's working in Windows 10 using `cmd` and `powershell`, but not working with `cmder`. using the just released version 0.2.19.

kerem commented

Author

Owner

@lufia commented on GitHub (Jan 23, 2021):

What cmder is? Could I get the workflow file to reproduce the error?

@lufia commented on GitHub (Jan 23, 2021): What `cmder` is? Could I get the workflow file to reproduce the error?

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jan 23, 2021):

What cmder is? Could I get the workflow file to reproduce the error?

https://cmder.net/

Cmder is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

@catthehacker commented on GitHub (Jan 23, 2021): > What `cmder` is? Could I get the workflow file to reproduce the error? https://cmder.net/ > Cmder is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

kerem commented

Author

Owner

@yuuuxt commented on GitHub (Jan 24, 2021):

What cmder is? Could I get the workflow file to reproduce the error?

Hi @lufia ,

First of all thanks for your work! You can reproduce with the following steps:

download a portable version of cmder (link), put it somewhere and open it;
clone the demo (sample repo) provided;
run act.

I just tried and reproduced.

@yuuuxt commented on GitHub (Jan 24, 2021): > > > What `cmder` is? Could I get the workflow file to reproduce the error? Hi @lufia , First of all thanks for your work! You can reproduce with the following steps: - download a portable version of `cmder` ([link](https://github.com/cmderdev/cmder/releases/download/v1.3.17/cmder.7z)), put it somewhere and open it; - clone the demo (sample repo) provided; - run `act`. I just tried and reproduced.

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jan 24, 2021):

Works fine for me

@catthehacker commented on GitHub (Jan 24, 2021): Works fine for me ![image](https://user-images.githubusercontent.com/31106839/105628729-f10bd580-5e3e-11eb-9740-73baa38e41f6.png)

kerem commented

Author

Owner

@yuuuxt commented on GitHub (Jan 24, 2021):

Then I have no idea what went wrong..

Anyway I can use act with something other than cmder :)

@yuuuxt commented on GitHub (Jan 24, 2021): Then I have no idea what went wrong.. Anyway I can use `act` with something other than `cmder` :)

kerem commented

Author

Owner

@mjuarez commented on GitHub (Jan 27, 2021):

I came across this issue after having act interrupted mid-way through a job and leaving the act's cache in a bad state. I ran rm -rf ~/.cache/act and was able to continue working

@mjuarez commented on GitHub (Jan 27, 2021): I came across this issue after having act interrupted mid-way through a job and leaving the act's cache in a bad state. I ran `rm -rf ~/.cache/act` and was able to continue working

kerem commented