TraceMachina / TraceMachina/nativelink
Lost inputs no longer available remotely
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
Randomy, in my Bazel build, I will often see a slew of errors like:
Running Cargo build script crc32fast failed: Lost inputs no longer available remotely: external/rules_rs++crate+crates__crc32fast-1.5.0/crc32fast_build_script_ (47e96e44aa3acea97bd6ed4654277a29753a44863b525c23b540cf616ea75789/474144).
It's not clear to me what's causing this. The cache is warm, so I don't believe this is due to eviction, though it could be due to a race. It's possible the server or workers are not configured optimally; perhaps a consistency check is being missed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Bazel build and collecting the surrounding logs for the “Lost inputs no longer available remotely” error from the crc32fast Cargo build script. Trace the remote cache or execution path that reports the missing digest, then determine whether eviction, a race, or a consistency issue is responsible. Done means identifying a reproducible cause and a focused fix or regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100