11
31
Fork
You've already forked silverfish
19

CI Cache fallback #133

Open
opened 2025年10月20日 21:24:41 +02:00 by jalil · 0 comments
Contributor
Copy link

When I was working on #132 I noticed the cache was cleared because the Cargo.lock was updated (added a dependency on thiserror to silverfish-command). In theory the build cache should've been used, but it wasn't because of the lockfile update (see https://codeberg.org/conjured/silverfish/actions/runs/313/jobs/0).

Maybe https://github.com/Swatinem/rust-cache works out of the box and we can just use it? Otherwise we could set restore-keys, but that may make the cache grow to infinity and beyond.

When I was working on #132 I noticed the cache was cleared because the `Cargo.lock` was updated (added a dependency on `thiserror` to `silverfish-command`). In theory the build cache should've been used, but it wasn't because of the lockfile update (see https://codeberg.org/conjured/silverfish/actions/runs/313/jobs/0). Maybe https://github.com/Swatinem/rust-cache works out of the box and we can just use it? Otherwise we could set `restore-keys`, but that may make the cache grow to infinity and beyond.
Sign in to join this conversation.
No Branch/Tag specified
main
zkat/products
150_musl_build
zkat/scaffolder
v0.0.1
Labels
Clear labels
Compat
Breaking
 Breaking change that won't be backward compatible
Flag/Good First Issue
Good issue for first-time contributors
Kind/Accessibility
Accessibility issue, bug or otherwise
Kind/Appearance
Design, styling, and other aesthetic and visual items
Kind/Bug
Something is not working
Kind/Compliance
Legal, policy, or some other kind of compliance
Kind/DevOps
CI/CD, releases, etc
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Performance
Gotta go fast
Kind/Security
This is security issue
Kind/Technical Improvement
Underlying technical improvement that is not necessarily user-impacting or visible.
Kind/Testing
Issue or pull request related to testing
Kind/UX
Related to user experience/product
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Size
L
 Significant change
Size
M
 Medium-size change
Size
S
 Small change
Size
XL
 Very large change that might take months to complete and impact many components
Size
XS
 Trivially small change
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
Status
Needs Design
 Requires design/review from Alchemists (product/UX)
Status
Needs Discussion
 A discussion needs to happen before implementation
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
Assignees
Clear assignees
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
conjured/silverfish#133
Reference in a new issue
conjured/silverfish
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?