TraceMachina / TraceMachina/nativelink

Revisit how `recently_completed_actions` are handled in the scheduler.

Open
#192 0 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

Spawned from: https://reviewable.io/reviews/allada/turbo-cache/177#-N_UvdbR6if15-0rySV9

I think there's other alternatives that need to be thought about in more detail as outlined here:
https://reviewable.io/reviews/allada/turbo-cache/177#-N_UZDcjCStLmxJZG5Cn

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 by reading the scheduler handling for recently_completed_actions and the two linked Reviewable discussion sections. Compare the alternatives described there and determine which behavior should replace the current approach. Done means the scheduler behavior and its intended design are agreed and the issue's open alternatives are resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.