perf(pr-pipeline): lane audit listing reserve, count-call reuse and busiest-first order
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, node.js
- Domain
- devtools
Research direction
Start with .github/scripts/maintenance-audit-lane-runs/collect.mjs and its tests in .github/scripts/maintenance-audit-lane-runs/*.test.mjs; trace the reserve calculation, count request, and slice D ordering. Run node --test .github/scripts/maintenance-audit-lane-runs/*.test.mjs first. Done means the 4A/0D/4C case completes, count-call runs are reused, and busiest workflows are read first.
Written by the indexing model from the issue text.
Description
Refs: #9297
Summary
Review suggestions from Automation Lanes on #9323 (lane audit full 24 h window), deferred so the reviewed head could merge. All three are in .github/scripts/maintenance-audit-lane-runs/collect.mjs.
Fix
DETAIL_RESERVE(about lines 23-27) assumes 2 D units. With 4 A, 0 D and 4 C units a run needs 184 calls, not 170, so it stops early and reports the window as incomplete. Set the reserve from the real unit mix (184 for that case) or correct the comment.- The per_page=1 count call (about line 105) is followed by page 1 of the same range (about line 124). Use per_page=100 for the count call and keep its runs; that saves about 27 calls a run.
- Reading the smallest workflows first (about line 131) means a short budget leaves the busiest ones partly read. Rank slice D by the counted totals.
Verification
node --test .github/scripts/maintenance-audit-lane-runs/*.test.mjspasses, with tests for a 4A/0D/4C mix completing, the count call's runs reused, and busiest-first order.
Related
#9323, #9297
🤖 Generated with Claude Code
- Dominant language
- Shell
- Stars
- 22
- Forks
- 2
- Avg merge
- 6h 58m
- Merged PRs (30d)
- 951
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from melodic-software/claude-code-plugins
-
pipeline-canary priority: low status: ready work-class: mechanical
Difficulty 1/5 Under an hour Newbie friendliness 88/100
melodic-software/claude-code-plugins#9263 · 1 comment ·
Maintainers usually reply within 1 day
-
good first issue priority: low
Difficulty 1/5 Under an hour Newbie friendliness 90/100
melodic-software/claude-code-plugins#9251 · 1 comment ·
Maintainers usually reply within 1 day
-
area: security needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
melodic-software/claude-code-plugins#9211 · 1 comment ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
melodic-software/claude-code-plugins#9202 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
melodic-software/claude-code-plugins#9179 · 1 comment ·
Maintainers usually reply within 1 day
All issues in melodic-software/claude-code-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MISP/misp-docker#478 ·
Maintainers usually reply within 1 day
-
roadmap-100
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#18073 · 1 comment ·
Maintainers usually reply within 1 day
-
Uptime "Test Monitor" always fails with an empty HTTP 400 (uptime-checker API endpoint not configured)Possibly taken @ayoubjemai claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/self-hosted#4582 ·
Maintainers usually reply within 1 day