The performance README points to a measure script at the wrong path

Open Beginner friendly

#1,446 opened on Sep 24, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 92/100

Issue type: Documentation
Clarity: Clearly specified
Activity status: Active
Tech stack: shell
Domain: documentation

Research direction

Start with docs/benchmarks/performance/README.md:10 and the example at docs/benchmarks/performance/measure-cli.sh:7. From the repository root, run both documented --help commands and confirm they print the script usage; done means both examples resolve the existing script path and the documentation check passes.

Written by the indexing model from the issue text.

Description

area:build bug good first issue sev:papercut

Found on santos/dev2 at 008363c98 (#1410). On dev@debffabf6 too.

What happened

The documented command names docs/benchmarks/measure-cli.sh, which does not exist. The executable is docs/benchmarks/performance/measure-cli.sh. The same stale path is on dev.

Replication

Deterministic (no model). From a clean checkout, run the README's path with --help. The shell reports that the file does not exist. Run docs/benchmarks/performance/measure-cli.sh --help; it prints usage.

Where

docs/benchmarks/performance/README.md:10 contains the stale command. The script's own example at docs/benchmarks/performance/measure-cli.sh:7 also uses the stale path, at 008363c98.

The fix

Use the existing performance/measure-cli.sh path in both examples.

Acceptance

e2e: both documented --help commands execute from the repository root and print the script's usage.
Unit: a documentation check resolves every local script path in these examples.
The change entry's invalidates names the former path.

Dominant language: Go
Stars: 115
Forks: 14
Avg merge: 9h 38m
Merged PRs (30d): 730

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

OOMs triggered by `GoLink` actions taking up to 10 times Bazel's default Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

bazel-contrib/rules_go#4726 · 1 comment · Opened Sep 25, 2026
[GEP-38] Create plutono panels to display the volume usage and utilization metrics similar to what we have for CPU and Memory Open

area/auto-scaling area/monitoring area/ops-productivity kind/enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

gardener/gardener#15814 · Opened Sep 25, 2026
update: nil context panics while restarting the daemon after a successful update Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

kenn-io/msgvault#940 · Opened Sep 25, 2026
docs(readme): use make setup for first-time local setup Open

Type/Improvement

Difficulty 1/5 1-3 hours Newbie friendliness 90/100

OpenNSW/nsw-srilanka#522 · Opened Sep 25, 2026
`docker context export` writes a truncated tar archive Open

Difficulty 2/5 1-3 hours Newbie friendliness 92/100

docker/cli#7332 · Opened Sep 25, 2026

More Go issues