starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #2399] ::error::error while setting context status: Not Found #1104

New issue

Closed

opened 2026-03-01 21:48:55 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 21:48:55 +03:00

Owner

Originally created by @brianjmurrell on GitHub (Jul 16, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2399

Bug report info

act version:            0.2.64
GOOS:                   linux
GOARCH:                 amd64
NumCPU:                 12
Docker host:            unix:///run/user/1001/podman/podman.sock
Sockets found:
        /var/run/docker.sock
        $XDG_RUNTIME_DIR/podman/podman.sock
Config files:           
        /home/brian/.config/act/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
        /home/brian/.actrc:
                -s GITHUB_TOKEN=ghp_[redacted]
                --container-daemon-socket=unix:///run/user/1001/podman/podman.sock
Build info:
        Go version:            go1.22.4
        Module path:           github.com/nektos/act
        Main version:          (devel)
        Main path:             github.com/nektos/act
        Main checksum:         
        Build settings:
                -buildmode:           pie
                -compiler:            gc
                -trimpath:            true
                DefaultGODEBUG:       httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
                CGO_ENABLED:          1
                GOARCH:               amd64
                GOOS:                 linux
                GOAMD64:              v1
Docker Engine:
        Engine version:        5.1.1
        Engine runtime:        crun
        Cgroup version:        2
        Cgroup driver:         systemd
        Storage driver:        overlay
        Registry URI:          
        OS:                    fedora
        OS type:               linux
        OS version:            40
        OS arch:               amd64
        OS kernel:             6.9.6-200.fc40.x86_64
        OS CPU:                12
        OS memory:             63943 MB
        Security options:
                name=seccomp,profile=default
                name=rootless
                name=selinux

Command used with act

act --artifact-server-path=/var/tmp/artifacts --use-new-action-cache=false --pull=false -P self-hosted=-self-hosted -P light=-self-hosted -j …

Describe issue

My workflow has the following step:

      - name: Update commit status
        uses: ouzi-dev/commit-status-updater@v2
        with:
          # yamllint disable-line rule:line-length
          name: 'build/Build on ${{ env.DISTRO_NAME }} ${{ env.COMMIT_STATUS_DISTRO_VERSION && env.COMMIT_STATUS_DISTRO_VERSION || env.DISTRO_VERSION }}'
          status: "${{ job.status }}"

which causes the following error:

 ⭐ Run Main Update commit status
   ❗  ::error::error while setting context status: Not Found
   ❌  Failure - Main Update commit status
 exit status 1

While it does not seem at all unreasonable that such a step should not actually update any commit status, can this kind of failure be handled more gracefully than bombing the workflow run?

Link to GitHub repository

No response

Workflow content

- name: Update commit status
        uses: ouzi-dev/commit-status-updater@v2
        with:
          # yamllint disable-line rule:line-length
          name: 'build/Build on ${{ env.DISTRO_NAME }} ${{ env.COMMIT_STATUS_DISTRO_VERSION && env.COMMIT_STATUS_DISTRO_VERSION || env.DISTRO_VERSION }}'
          status: "${{ job.status }}"

Relevant log output

⭐ Run Main Update commit status
   ❗  ::error::error while setting context status: Not Found
   ❌  Failure - Main Update commit status
 exit status 1

Additional information

No response

Originally created by @brianjmurrell on GitHub (Jul 16, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2399 ### Bug report info ```plain text act version: 0.2.64 GOOS: linux GOARCH: amd64 NumCPU: 12 Docker host: unix:///run/user/1001/podman/podman.sock Sockets found: /var/run/docker.sock $XDG_RUNTIME_DIR/podman/podman.sock Config files: /home/brian/.config/act/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 /home/brian/.actrc: -s GITHUB_TOKEN=ghp_[redacted] --container-daemon-socket=unix:///run/user/1001/podman/podman.sock Build info: Go version: go1.22.4 Module path: github.com/nektos/act Main version: (devel) Main path: github.com/nektos/act Main checksum: Build settings: -buildmode: pie -compiler: gc -trimpath: true DefaultGODEBUG: httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1 CGO_ENABLED: 1 GOARCH: amd64 GOOS: linux GOAMD64: v1 Docker Engine: Engine version: 5.1.1 Engine runtime: crun Cgroup version: 2 Cgroup driver: systemd Storage driver: overlay Registry URI: OS: fedora OS type: linux OS version: 40 OS arch: amd64 OS kernel: 6.9.6-200.fc40.x86_64 OS CPU: 12 OS memory: 63943 MB Security options: name=seccomp,profile=default name=rootless name=selinux ``` ### Command used with act ```sh act --artifact-server-path=/var/tmp/artifacts --use-new-action-cache=false --pull=false -P self-hosted=-self-hosted -P light=-self-hosted -j … ``` ### Describe issue My workflow has the following step: ```yaml - name: Update commit status uses: ouzi-dev/commit-status-updater@v2 with: # yamllint disable-line rule:line-length name: 'build/Build on ${{ env.DISTRO_NAME }} ${{ env.COMMIT_STATUS_DISTRO_VERSION && env.COMMIT_STATUS_DISTRO_VERSION || env.DISTRO_VERSION }}' status: "${{ job.status }}" ``` which causes the following error: ``` ⭐ Run Main Update commit status ❗ ::error::error while setting context status: Not Found ❌ Failure - Main Update commit status exit status 1 ``` While it does not seem at all unreasonable that such a step should not actually update any commit status, can this kind of failure be handled more gracefully than bombing the workflow run? ### Link to GitHub repository _No response_ ### Workflow content ```yml - name: Update commit status uses: ouzi-dev/commit-status-updater@v2 with: # yamllint disable-line rule:line-length name: 'build/Build on ${{ env.DISTRO_NAME }} ${{ env.COMMIT_STATUS_DISTRO_VERSION && env.COMMIT_STATUS_DISTRO_VERSION || env.DISTRO_VERSION }}' status: "${{ job.status }}" ``` ### Relevant log output ```sh ⭐ Run Main Update commit status ❗ ::error::error while setting context status: Not Found ❌ Failure - Main Update commit status exit status 1 ``` ### Additional information _No response_

kerem

2026-03-01 21:48:55 +03:00

closed this issue
added the
stale

kind/bug
labels

kerem commented

2026-03-01 21:48:56 +03:00

Author

Owner

@brianjmurrell commented on GitHub (Jul 16, 2024):

Maybe something like this step needs to be conditional (i.e. if:) on actually running in a real GHA runner? ~~Is there an accepted expression (i.e. something stable that is not subject to change in the future) that can be set in an if: clause for such a case?~~ Skipping Steps

@brianjmurrell commented on GitHub (Jul 16, 2024): Maybe something like this step needs to be conditional (i.e. `if:`) on actually running in a real GHA runner? ~~Is there an accepted expression (i.e. something stable that is not subject to change in the future) that can be set in an `if:` clause for such a case?~~ [Skipping Steps](https://nektosact.com/usage/index.html?highlight=skipping#skipping-steps)

kerem commented

2026-03-01 21:48:56 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 13, 2025):

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

@github-actions[bot] commented on GitHub (Jan 13, 2025): Issue is stale and will be closed in 14 days unless there is new activity

kerem referenced this issue

2026-03-01 21:52:39 +03:00

[PR #1104] [MERGED] feat: add option to specify git remote name #1778

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1104

No description provided.

Rows
Columns