Worker<->Scheduler communication should throw a warning if versions are mismatched

Open
#1,253 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
distributed-systems

Research direction

Start by locating the Worker-to-Scheduler connection and metadata handling entry points in NativeLink. Trace how each side identifies its NativeLink version, then define completion as both sides exchanging and comparing versions and emitting a warning when they differ; no specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

enhancement good first issue

If a worker is connecting to the scheduler it both sides should express what version of nativelink they have in the metadata and validate that they match and if they don't throw a warning.

This will make it easier to see if any errors being thrown are related to an API change.

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

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.

More from TraceMachina/nativelink

All issues in TraceMachina/nativelink

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.