TraceMachina / TraceMachina/nativelink

Many "Failed to delete key from cache on callback" messages

Open
#2,009 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.6k
Forks
244
Avg merge
1d 16h
Merged PRs (30d)
54

Description

I see a large number of these, but my caches are big and not so heavily used, so they seem a bit out of place.

025-10-26T17:13:38.579944Z  INFO nativelink_store::existence_cache_store: Failed to delete key from cache on callback, store_key: Digest(DigestInfo("f54f8dd70fc6b2f99bac1a5ef868f454fd9619c837e2b1077f61cb100d56b5ac-197"))
at nativelink-store/src/existence_cache_store.rs:81
in nativelink_store::filesystem_store::filesystem_store_emplace_file
in nativelink_service::bytestream_server::inner_write with digest: DigestInfo("f31a04270c78a5c0313f140affb15804aa803500f8f8a53acda9af254b16ae38-87654143"), stream: WriteRequestStreamWrapper { resource_info: ResourceInfo { instance_name: ">
in nativelink_service::bytestream_server::bytestream_write
in nativelink_service::bytestream_server::write with request: Streaming
in nativelink_util::task::http_executor
in nativelink::services::http_connection with remote_addr: 192.168.191.220:64842, socket_addr: 0.0.0.0:50051

Contributor guide

Open the contributing guide

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.

Research direction

Start at nativelink-store/src/existence_cache_store.rs:81 and trace the callback from filesystem_store_emplace_file through the bytestream write path shown in the report. Determine why cache-key deletion fails and verify the fix against the reported logging behavior and cache usage scenario.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.