[GH-ISSUE #2243] Getting "Caching for 'false' is not supported" error when using 3rd party action #1056

Closed
opened 2026-03-01 21:48:34 +03:00 by kerem · 3 comments
Owner

Originally created by @higaski on GitHub (Mar 7, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2243

Bug report info

act version:            0.2.60
GOOS:                   linux
GOARCH:                 amd64
NumCPU:                 16
Docker host:            DOCKER_HOST environment variable is not set
Sockets found:
        /var/run/docker.sock
Config files:           
        /home/vinci/.actrc:
                -P ubuntu-latest=catthehacker/ubuntu:full-latest
                -P ubuntu-22.04=catthehacker/ubuntu:full-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:full-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:full-18.04
Build info:
        Go version:            go1.22.0
        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,panicnil=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
                CGO_ENABLED:          1
                GOARCH:               amd64
                GOOS:                 linux
                GOAMD64:              v1
Docker Engine:
        Engine version:        25.0.3
        Engine runtime:        runc
        Cgroup version:        2
        Cgroup driver:         systemd
        Storage driver:        overlay2
        Registry URI:          https://index.docker.io/v1/
        OS:                    Garuda Linux
        OS type:               linux
        OS version:            
        OS arch:               x86_64
        OS kernel:             6.7.8-zen1-1-zen
        OS CPU:                16
        OS memory:             31241 MB
        Security options:
                name=seccomp,profile=builtin
                name=cgroupns

Command used with act

act

Describe issue

I have a workflow which uses the install-qt-action action which I'd like to run locally. Sadly this GitHub action seems to setup some Python stuff which act complains about.

No response

Workflow content

name: build

on:
  push:
    branches: [master]

jobs:
  x86_64-linux-gnu-gcc:
    runs-on: ubuntu-22.04
    steps:
      - uses: actions/checkout@v4.1.1
        with:
          fetch-depth: 0
      - uses: jurplel/install-qt-action@v3
        with:
          version: '6.6.2'
      - run: cmake -Bbuild
        env:
          CC:   gcc-13
          CXX:  g++-13
      - run: cmake --build build --parallel --target all

Relevant log output

[build/x86_64-linux-gnu-gcc] ⭐ Run Main jurplel/install-qt-action@v3
[build/x86_64-linux-gnu-gcc]   🐳  docker cp src=/home/vinci/.cache/act/jurplel-install-qt-action@v3/ dst=/var/run/act/actions/jurplel-install-qt-action@v3/
[build/x86_64-linux-gnu-gcc]   🐳  docker exec cmd=[chown -R 1001:127 /var/run/act/actions/jurplel-install-qt-action@v3/] user=0 workdir=
[build/x86_64-linux-gnu-gcc] ⭐ Run Main Setup Python
[build/x86_64-linux-gnu-gcc]   🐳  docker cp src=/home/vinci/.cache/act/actions-setup-python@v5/ dst=/var/run/act/actions/actions-setup-python@v5/
[build/x86_64-linux-gnu-gcc]   🐳  docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-python@v5/] user=0 workdir=
[build/x86_64-linux-gnu-gcc]   🐳  docker exec cmd=[node /var/run/act/actions/actions-setup-python@v5/dist/setup/index.js] user= workdir=
[build/x86_64-linux-gnu-gcc]   💬  ::debug::Python is expected to be installed into /opt/hostedtoolcache
[build/x86_64-linux-gnu-gcc]   ❓  ::group::Installed versions
[build/x86_64-linux-gnu-gcc]   💬  ::debug::Semantic version spec of 3.6.x - 3.11.x is 3.6.x - 3.11.x
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? false
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.10.13
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.11.7
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.12.1
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.7.17
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.8.18
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::isExplicit: 3.9.18
[build/x86_64-linux-gnu-gcc]   💬  ::debug::explicit? true
[build/x86_64-linux-gnu-gcc]   💬  ::debug::evaluating 6 versions
[build/x86_64-linux-gnu-gcc]   💬  ::debug::matched: 3.11.7
[build/x86_64-linux-gnu-gcc]   💬  ::debug::checking cache: /opt/hostedtoolcache/Python/3.11.7/x64
[build/x86_64-linux-gnu-gcc]   💬  ::debug::Found tool in cache Python 3.11.7 x64
| Successfully set up CPython (3.11.7)
[build/x86_64-linux-gnu-gcc]   ❓  ::endgroup::
[build/x86_64-linux-gnu-gcc]   ❗  ::error::Caching for 'false' is not supported
[build/x86_64-linux-gnu-gcc]   ❌  Failure - Main Setup Python

Additional information

I don't have a lot of experience with GitHub actions yet, please forgive me if this isn't a really a bug. Might it be due to act not supporting caching?

Originally created by @higaski on GitHub (Mar 7, 2024). Original GitHub issue: https://github.com/nektos/act/issues/2243 ### Bug report info ```plain text act version: 0.2.60 GOOS: linux GOARCH: amd64 NumCPU: 16 Docker host: DOCKER_HOST environment variable is not set Sockets found: /var/run/docker.sock Config files: /home/vinci/.actrc: -P ubuntu-latest=catthehacker/ubuntu:full-latest -P ubuntu-22.04=catthehacker/ubuntu:full-22.04 -P ubuntu-20.04=catthehacker/ubuntu:full-20.04 -P ubuntu-18.04=catthehacker/ubuntu:full-18.04 Build info: Go version: go1.22.0 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,panicnil=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1 CGO_ENABLED: 1 GOARCH: amd64 GOOS: linux GOAMD64: v1 Docker Engine: Engine version: 25.0.3 Engine runtime: runc Cgroup version: 2 Cgroup driver: systemd Storage driver: overlay2 Registry URI: https://index.docker.io/v1/ OS: Garuda Linux OS type: linux OS version: OS arch: x86_64 OS kernel: 6.7.8-zen1-1-zen OS CPU: 16 OS memory: 31241 MB Security options: name=seccomp,profile=builtin name=cgroupns ``` ### Command used with act ```sh act ``` ### Describe issue I have a workflow which uses the [install-qt-action](https://github.com/jurplel/install-qt-action) action which I'd like to run locally. Sadly this GitHub action seems to setup some Python stuff which act complains about. ### Link to GitHub repository _No response_ ### Workflow content ```yml name: build on: push: branches: [master] jobs: x86_64-linux-gnu-gcc: runs-on: ubuntu-22.04 steps: - uses: actions/checkout@v4.1.1 with: fetch-depth: 0 - uses: jurplel/install-qt-action@v3 with: version: '6.6.2' - run: cmake -Bbuild env: CC: gcc-13 CXX: g++-13 - run: cmake --build build --parallel --target all ``` ### Relevant log output ```sh [build/x86_64-linux-gnu-gcc] ⭐ Run Main jurplel/install-qt-action@v3 [build/x86_64-linux-gnu-gcc] 🐳 docker cp src=/home/vinci/.cache/act/jurplel-install-qt-action@v3/ dst=/var/run/act/actions/jurplel-install-qt-action@v3/ [build/x86_64-linux-gnu-gcc] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/jurplel-install-qt-action@v3/] user=0 workdir= [build/x86_64-linux-gnu-gcc] ⭐ Run Main Setup Python [build/x86_64-linux-gnu-gcc] 🐳 docker cp src=/home/vinci/.cache/act/actions-setup-python@v5/ dst=/var/run/act/actions/actions-setup-python@v5/ [build/x86_64-linux-gnu-gcc] 🐳 docker exec cmd=[chown -R 1001:127 /var/run/act/actions/actions-setup-python@v5/] user=0 workdir= [build/x86_64-linux-gnu-gcc] 🐳 docker exec cmd=[node /var/run/act/actions/actions-setup-python@v5/dist/setup/index.js] user= workdir= [build/x86_64-linux-gnu-gcc] 💬 ::debug::Python is expected to be installed into /opt/hostedtoolcache [build/x86_64-linux-gnu-gcc] ❓ ::group::Installed versions [build/x86_64-linux-gnu-gcc] 💬 ::debug::Semantic version spec of 3.6.x - 3.11.x is 3.6.x - 3.11.x [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? false [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.10.13 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.11.7 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.12.1 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.7.17 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.8.18 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::isExplicit: 3.9.18 [build/x86_64-linux-gnu-gcc] 💬 ::debug::explicit? true [build/x86_64-linux-gnu-gcc] 💬 ::debug::evaluating 6 versions [build/x86_64-linux-gnu-gcc] 💬 ::debug::matched: 3.11.7 [build/x86_64-linux-gnu-gcc] 💬 ::debug::checking cache: /opt/hostedtoolcache/Python/3.11.7/x64 [build/x86_64-linux-gnu-gcc] 💬 ::debug::Found tool in cache Python 3.11.7 x64 | Successfully set up CPython (3.11.7) [build/x86_64-linux-gnu-gcc] ❓ ::endgroup:: [build/x86_64-linux-gnu-gcc] ❗ ::error::Caching for 'false' is not supported [build/x86_64-linux-gnu-gcc] ❌ Failure - Main Setup Python ``` ### Additional information I don't have a lot of experience with GitHub actions yet, please forgive me if this isn't a really a bug. Might it be due to act not supporting caching?
kerem 2026-03-01 21:48:34 +03:00
  • closed this issue
  • added the
    kind/bug
    label
Author
Owner

@QuentiumYT commented on GitHub (Apr 29, 2024):

Same issue here

[Build Stacer Application/Build App]   💬  ::debug::Found tool in cache Python 3.11.9 x64
| Successfully set up CPython (3.11.9)
[Build Stacer Application/Build App]   ❓  ::endgroup::
[Build Stacer Application/Build App]   ❗  ::error::Caching for 'false' is not supported
[Build Stacer Application/Build App]   ❌  Failure - Main Setup Python
[Build Stacer Application/Build App]   ⚙  ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib
[Build Stacer Application/Build App]   ⚙  ::set-output:: python-version=3.11.9
[Build Stacer Application/Build App]   ⚙  ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python
[Build Stacer Application/Build App]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin
[Build Stacer Application/Build App] exitcode '1': failure
[Build Stacer Application/Build App]   ❌  Failure - Main Install Qt
[Build Stacer Application/Build App]   ⚙  ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib
[Build Stacer Application/Build App]   ⚙  ::set-output:: python-version=3.11.9
[Build Stacer Application/Build App]   ⚙  ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python
[Build Stacer Application/Build App]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App]   ⚙  ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin
[Build Stacer Application/Build App] exitcode '1': failure```
<!-- gh-comment-id:2082570416 --> @QuentiumYT commented on GitHub (Apr 29, 2024): Same issue here ```bash [Build Stacer Application/Build App] 💬 ::debug::Found tool in cache Python 3.11.9 x64 | Successfully set up CPython (3.11.9) [Build Stacer Application/Build App] ❓ ::endgroup:: [Build Stacer Application/Build App] ❗ ::error::Caching for 'false' is not supported [Build Stacer Application/Build App] ❌ Failure - Main Setup Python [Build Stacer Application/Build App] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig [Build Stacer Application/Build App] ⚙ ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib [Build Stacer Application/Build App] ⚙ ::set-output:: python-version=3.11.9 [Build Stacer Application/Build App] ⚙ ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python [Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin [Build Stacer Application/Build App] exitcode '1': failure [Build Stacer Application/Build App] ❌ Failure - Main Install Qt [Build Stacer Application/Build App] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig [Build Stacer Application/Build App] ⚙ ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib [Build Stacer Application/Build App] ⚙ ::set-output:: python-version=3.11.9 [Build Stacer Application/Build App] ⚙ ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python [Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64 [Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin [Build Stacer Application/Build App] exitcode '1': failure```
Author
Owner

@peret2000 commented on GitHub (May 21, 2024):

It is failing, whatever value you set for 'cache' when using jurplel/install-qt-action@v3
The error is:
::error::Caching for 'false'/'true' is not supported

So, I do not see the way to use this action with act

This is the interesting code:

      - name: Install Qt Android
        uses: jurplel/install-qt-action@v3
        with:
          version: '5.15.0'
          host: 'linux'
          target: 'android'
          arch: 'android'
          modules: 'qtcharts  qtnetworkauth'
          dir: '${{ github.workspace }}/output/android/'
          # cache: 'true'
          # cache-key-prefix: 'install-qt-action-android'                    

Uncomment last two lines to test with 'true'

<!-- gh-comment-id:2123185734 --> @peret2000 commented on GitHub (May 21, 2024): It is failing, whatever value you set for 'cache' when using jurplel/install-qt-action@v3 The error is: ❗ ::error::Caching for 'false'/'true' is not supported So, I do not see the way to use this action with act This is the interesting code: ``` - name: Install Qt Android uses: jurplel/install-qt-action@v3 with: version: '5.15.0' host: 'linux' target: 'android' arch: 'android' modules: 'qtcharts qtnetworkauth' dir: '${{ github.workspace }}/output/android/' # cache: 'true' # cache-key-prefix: 'install-qt-action-android' ``` Uncomment last two lines to test with 'true'
Author
Owner

@ChristopherHX commented on GitHub (Jun 3, 2024):

My veto against not deriving the inputs context from env variables shaped like INPUT_NAME was too weak, now we have the problem (It is also my fault as a reviewer here).

We have an ugly action input pollution, in this example is the default value has not been taken out of action.yml due to beeing shadowed by an composite action.

If you have time and push this problem forward to a solution, we need your time to test this change carefully: https://github.com/nektos/act/pull/2348

You can always download act as an artifacts from the test Github Actions Workflow triggered by the PR or build locally.

I for my part need to create testdata to cover the odd bits of the code in act, better coverage can prevent bad design decisions to be merged due to broken tests.

<!-- gh-comment-id:2146227098 --> @ChristopherHX commented on GitHub (Jun 3, 2024): My veto against not deriving the inputs context from env variables shaped like `INPUT_NAME` was too weak, now we have the problem (It is also my fault as a reviewer here). We have an ugly action input pollution, in this example is the default value has not been taken out of action.yml due to beeing shadowed by an composite action. If you have time and push this problem forward to a solution, we need your time to test this change carefully: https://github.com/nektos/act/pull/2348 You can always download act as an artifacts from the test Github Actions Workflow triggered by the PR or build locally. I for my part need to create testdata to cover the odd bits of the code in act, better coverage can prevent bad design decisions to be merged due to broken tests.
Sign in to join this conversation.
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#1056
No description provided.