Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Rust caching is less effective

Open
  • Is something wrong?
#32 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, github-actions, rust
Domain
build-system, ci-cd, mobile

Research direction

Start by reviewing the GitHub Actions configuration for the rust-cache action and the Android cross-compilation targets. Compare the host clippy cache behavior with the Android target builds, then determine whether nested targets need separate cache configuration. Done means Android targets reuse their caches reliably instead of rebuilding on each run.

Written by the indexing model from the issue text.

Description

Previously, the rust-cache action was working well for some of the Android targets, but lately they're all being rebuilt. The host target clippy run appears to be the only thing benefiting from caching. It's unclear how well the action supports cross-compilation targets. Perhaps we need to specify each nested target directly separately?

Dominant language
Java
Stars
1
Forks
1
Avg merge
10h 4m
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from divviup/divviup-android

All issues in divviup/divviup-android

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.