Some actions tag can act erroneous sometimes

[Porkepix]

Bug report info

$ act --bug-report
act version:            0.2.41
GOOS:                   linux
GOARCH:                 amd64
NumCPU:                 16
Docker host:            DOCKER_HOST environment variable is unset/empty.
Sockets found:
        /var/run/docker.sock
Config files:
        /home/clement/.actrc:
                -P ubuntu-latest=catthehacker/ubuntu:act-latest
                -P ubuntu-22.04=catthehacker/ubuntu:act-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:act-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:act-18.04
        .actrc:
                -P ubuntu-latest=catthehacker/ubuntu:act-latest
                -P ubuntu-22.04=catthehacker/ubuntu:act-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:act-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:act-18.04
Build info:
        Go version:            go1.19.5
        Module path:           github.com/nektos/act
        Main version:          (devel)
        Main path:             github.com/nektos/act
        Main checksum:
        Build settings:
                -compiler:            gc
                -trimpath:            true
                CGO_ENABLED:          1
                GOARCH:               amd64
                GOOS:                 linux
                GOAMD64:              v1
                vcs:                  git
                vcs.revision:         6f08ded8cd7a488cc0e99471829e0c6bdcaee2d6
                vcs.time:             2023-02-01T15:56:26Z
                vcs.modified:         true
Docker Engine:
        Engine version:        20.10.23
        Engine runtime:        runc
        Cgroup version:        2
        Cgroup driver:         systemd
        Storage driver:        overlay2
        Registry URI:          https://index.docker.io/v1/
        OS:                    Arch Linux
        OS type:               linux
        OS version:
        OS arch:               x86_64
        OS kernel:             6.1.7-arch1-1
        OS CPU:                16
        OS memory:             31802 MB
        Security options:
                name=seccomp,profile=default
                name=cgroupns

Command used with act

act

Describe issue

One of the action I used have an issue with the tag we're supposed to use. the issue only happens with act and can't be reproduced on GitHub Actions.

Link to GitHub repository

No response

Workflow content

- name: Run install
  uses: borales/actions-yarn@v4
  with:
    cmd: install # will run `yarn install` command

Relevant log output

[Tests/unit_tests]   ☁  git clone 'https://github.com/borales/actions-yarn' # ref=v4
[Tests/unit_tests] Unable to resolve v4: unsupported object type
[Tests/unit_tests] Unable to resolve v4: unsupported object type
[Tests/unit_tests] unsupported object type
[Tests/unit_tests]   ☁  git clone 'https://github.com/borales/actions-yarn' # ref=v4
[Tests/unit_tests] Unable to resolve v4: unsupported object type
[Tests/unit_tests] Unable to resolve v4: unsupported object type

Additional information

This tag points to the exact same commit hash as the v4.2.0 tag, and replacing v4 by v4.2.0 fixes the issue and make it work, however that means the workflows/actions won't benefit from next major releases of the action.

Only act get such issue while running, this can't be reproduced directly on GitHub.

Also, a little bit out of topic but while debugging/reproducing the issue, I noticed that the actions I wrote myself weren't updated while present in ~/.cache/act, using @main ref. As I'm still working alone on those actions, I use some force push to keep the history clean for this bootstrap, can this cause a hard time updating the actions for act? Shouldn't it be able to deal with it? (Here the only solution is to remove them from ~/.cache/act).

[remcovg89]

I'm experiencing this same issue, did you manage to solve this or find a workaround?

[github-actions]

Issue is stale and will be closed in 14 days unless there is new activity

[Porkepix]

Issue probably's still around, though I'm not currently using act.

[eurek]

Same issue

[victorpopkov]

Most likely, the issue is due to the use of Git nested tags, which currently don't seem to be supported by https://github.com/go-git/go-git which this project uses as a dependency. See go-git/go-git#361.

For example:

$ git tag -s v4 v4.2.0

Will result in the creation of the nested tag v4 which references the tag v4.2.0.

Git should even give a hint regarding that

hint: You have created a nested tag. The object referred to by your new tag is
hint: already a tag. If you meant to tag the object that it points to, use:
hint: 
hint:     git tag -f v4 v4.2.0^{}
hint: Disable this message with "git config advice.nestedTag false"

Respectively, as of now, it's better to reference the object the v4.2.0 tag points to instead:

$ git tag -s v4 v4.2.0^{}

For those who want to see if this is what is causing the issue on their side, you may try changing your tags in act cache first: ~/.cache/act/. Then run act with --action-offline-mode flag to avoid fetching and pulling. For example:

$ cd ~/.cache/act/<your action reference>/
$ git tag -fs v4 v4.2.0^{}
$ cd /path/to/your/project/
$ act --action-offline-mode ...

[github-actions]

Issue is stale and will be closed in 14 days unless there is new activity

[Porkepix]

I don't have environment to test this anymore, unfortunately. Without fix it's likely the issue is still around, but I can't tell currently.

[github-actions]

Issue is stale and will be closed in 14 days unless there is new activity

[Porkepix]

I did some tests and found that v4 tag is still affected while new v5 works without any issue.

So there's still something weird around v4 tag that might also affect other actions, I guess that means this issue should stay open?