mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #2243] Getting "Caching for 'false' is not supported" error when using 3rd party action #1056
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#1056
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @higaski on GitHub (Mar 7, 2024).
Original GitHub issue: https://github.com/nektos/act/issues/2243
Bug report info
Command used with 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.
Link to GitHub repository
No response
Workflow content
Relevant log output
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?
@QuentiumYT commented on GitHub (Apr 29, 2024):
Same issue here
@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:
Uncomment last two lines to test with 'true'
@ChristopherHX commented on GitHub (Jun 3, 2024):
My veto against not deriving the inputs context from env variables shaped like
INPUT_NAMEwas 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.