mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #1823] Cache restore-keys not matched in creation reverse order #886
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#886
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 @vladum on GitHub (May 25, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1823
Bug report info
Command used with act
Describe issue
First, thanks a lot for adding cache support! CC @wolfogre
Now, on the bug...
GitHub Actions cache docs says the following:
I don't think this happens in
act.This behavior is important when implementing the cache update trick documented here. In summary, we want to restore the latest cache entry and write to a new one.
Side note: In the repro I posted,
github.run_idis replaced by seconds since the epoch becauserun_idwould be always 1 inact. This is not important for this bug, but it would be nice to get a uniquerun_id- maybe there's a way and I don't know it.In the workflow I posted, the expectation is that
filewill keep getting dates appended to it every time the workflow is triggered. This happens on GitHub, but not onact.Anyway, I think the fix is trivial: change
findCachetoSortBy("CreatedAt").Reverse()instead of the currentSortBy("Key").Happy to contribute if someone more familiar with the code confirms this is the right approach.
Thanks!
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@github-actions[bot] commented on GitHub (Nov 22, 2023):
Issue is stale and will be closed in 14 days unless there is new activity