Run any Skill in Manus with one click

$pwd:

nativelink-lre-debug

Name: Nativelink Lre Debug
Author: TraceMachina

// Use when debugging NativeLink local remote execution, remote cache/executor self-tests, BEP event ingestion, worker scheduling, CAS misses, or Bazel remote execution behavior.

Run Skill in Manus

$ git log --oneline --stat

stars:1,535

forks:217

updated:April 30, 2026 at 14:40

SKILL.md

readonly

name	nativelink-lre-debug
description	Use when debugging NativeLink local remote execution, remote cache/executor self-tests, BEP event ingestion, worker scheduling, CAS misses, or Bazel remote execution behavior.

NativeLink Local Remote Execution Debugging

Use this skill when NativeLink is acting as a remote cache, remote executor, local remote execution server, or BEP target and something is missing, slow, or failing.

Identify The Mode

Start by recording the exact Bazel command and which NativeLink mode is involved:

Remote cache self-test: --config=self_test, usually grpc://127.0.0.1:50051.
Remote executor self-test: --config=self_execute, usually grpc://127.0.0.1:50052.
Local remote execution overlays under local-remote-execution/.
BEP ingestion or dashboard testing, which needs Build Event Protocol upload flags.

For rich action-level BEP data, include:

--build_event_publish_all_actions

This matters for helping users find build failures and slow actions faster.

First Checks

Confirm the NativeLink server process is running.
Confirm the expected ports aren't occupied by stale processes.
Capture NativeLink logs and the exact Bazel stdout/stderr.
Check whether the failure is CAS/AC storage, scheduler matching, worker execution, protocol, or client config.

Don't kill user services unless the user explicitly asks. Inspect ports and processes first.

Subsystem Map

CAS/AC or cache misses: start in nativelink-store/.
Worker execution failure: start in nativelink-worker/.
Queueing, platform properties, or worker compatibility: start in nativelink-scheduler/.
REAPI, bytestream, action cache, or BEP API behavior: start in nativelink-service/.
Client templates and flags: start in templates/ and local-remote-execution/.

Useful Verification Commands

Inspect labels before running if unsure.

bazel build //:nativelink
bazel test //nativelink-store/...
bazel test //nativelink-scheduler/...
bazel test //nativelink-worker/...
bazel test //nativelink-service/...

For full confidence:

bazel test //...

Debug Output To Preserve

When reporting a failure, include:

NativeLink server config path and relevant ports.
Bazel remote cache/executor URL.
Whether --build_event_publish_all_actions was set.
First server-side error and first client-side error.
The failing target label and action mnemonic, if available.

related-skills.json

same repository

migrate-to-bazelmod.md

from "TraceMachina/nativelink"

Migrate a Bazel project from WORKSPACE to Bzlmod (MODULE.bazel). Use when a project has a WORKSPACE / WORKSPACE.bazel file but no MODULE.bazel, when the user asks to "migrate to bzlmod", "adopt MODULE.bazel", "drop WORKSPACE", "move to Bazel modules", or upgrade to Bazel 8/9 compatibility. Covers the hybrid WORKSPACE.bzlmod gradual migration, dependency translation (http_archive→bazel_dep, repo rules→use_repo_rule / module extensions, bind→alias), toolchain registration, override directives, the toolchainization pattern for rule-set authors, dual WORKSPACE/Bzlmod API design for library modules, minimum-version strategy with single_version_override, fixing Label(@computed_repo_name) patterns, and writing parameterized backwards-compatibility smoke tests.

2026-05-091.5k

nativelink-bazel-verification.md

from "TraceMachina/nativelink"

Use when verifying NativeLink changes with Bazel, selecting focused test targets, debugging rustfmt/clippy aspect failures, or preparing a confidence report for Rust/Bazel changes.

2026-04-301.5k

nativelink-config-protocol.md

from "TraceMachina/nativelink"

Use when changing NativeLink JSON5 configuration, deployment examples, protobuf/service protocol surfaces, or compatibility-sensitive config behavior.

2026-04-301.5k

nativelink-dependency-update.md

from "TraceMachina/nativelink"

Use when updating NativeLink Cargo dependencies, Bazel module dependencies, rules_rust pins, lock files, toolchains, or generated dependency metadata.

2026-04-301.5k

nativelink-rust-change.md

from "TraceMachina/nativelink"

Use when implementing or reviewing Rust changes in NativeLink crates, especially storage, scheduler, worker, service, config, and shared utility behavior.

2026-04-301.5k

package.json

"author": "TraceMachina"

"repository": "TraceMachina/nativelink"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	nativelink-lre-debug
description	Use when debugging NativeLink local remote execution, remote cache/executor self-tests, BEP event ingestion, worker scheduling, CAS misses, or Bazel remote execution behavior.

NativeLink Local Remote Execution Debugging

Use this skill when NativeLink is acting as a remote cache, remote executor, local remote execution server, or BEP target and something is missing, slow, or failing.

Identify The Mode

Start by recording the exact Bazel command and which NativeLink mode is involved:

Remote cache self-test: --config=self_test, usually grpc://127.0.0.1:50051.
Remote executor self-test: --config=self_execute, usually grpc://127.0.0.1:50052.
Local remote execution overlays under local-remote-execution/.
BEP ingestion or dashboard testing, which needs Build Event Protocol upload flags.

For rich action-level BEP data, include:

--build_event_publish_all_actions

This matters for helping users find build failures and slow actions faster.

First Checks

Confirm the NativeLink server process is running.
Confirm the expected ports aren't occupied by stale processes.
Capture NativeLink logs and the exact Bazel stdout/stderr.
Check whether the failure is CAS/AC storage, scheduler matching, worker execution, protocol, or client config.

Don't kill user services unless the user explicitly asks. Inspect ports and processes first.

Subsystem Map

CAS/AC or cache misses: start in nativelink-store/.
Worker execution failure: start in nativelink-worker/.
Queueing, platform properties, or worker compatibility: start in nativelink-scheduler/.
REAPI, bytestream, action cache, or BEP API behavior: start in nativelink-service/.
Client templates and flags: start in templates/ and local-remote-execution/.

Useful Verification Commands

Inspect labels before running if unsure.

bazel build //:nativelink
bazel test //nativelink-store/...
bazel test //nativelink-scheduler/...
bazel test //nativelink-worker/...
bazel test //nativelink-service/...

For full confidence:

bazel test //...

Debug Output To Preserve

When reporting a failure, include:

NativeLink server config path and relevant ports.
Bazel remote cache/executor URL.
Whether --build_event_publish_all_actions was set.
First server-side error and first client-side error.
The failing target label and action mnemonic, if available.

nativelink-lre-debug

NativeLink Local Remote Execution Debugging

Identify The Mode

First Checks

Subsystem Map

Useful Verification Commands

Debug Output To Preserve

More from this repository

NativeLink Local Remote Execution Debugging

Identify The Mode

First Checks

Subsystem Map

Useful Verification Commands

Debug Output To Preserve

More from this repository