Skip to content

test(review): lock in estimateReviewEffort multi-file band-5 case (#2151) - #3758

Closed
luciferlive112116 wants to merge 3 commits into
JSONbored:mainfrom
luciferlive112116:test/review-effort-estimator-2151
Closed

test(review): lock in estimateReviewEffort multi-file band-5 case (#2151)#3758
luciferlive112116 wants to merge 3 commits into
JSONbored:mainfrom
luciferlive112116:test/review-effort-estimator-2151

Conversation

@luciferlive112116

Copy link
Copy Markdown
Contributor

Closes #2151

Summary

Validation

  • npm run typecheck
  • npx vitest run test/unit/review-effort.test.ts

UI Evidence

N/A — test-only.

@superagent-security

Copy link
Copy Markdown
Contributor

Superagent didn't find any vulnerabilities or security issues in this PR.

@loopover-orb loopover-orb Bot added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jul 6, 2026
@loopover-orb

loopover-orb Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Caution

🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥

🛑 Gittensory review result - reject/close recommended

Review updated: 2026-07-06 07:56:53 UTC

3 files · 1 AI reviewer · 1 blocker · readiness 100/100 · CI pending · blocked

🛑 Suggested Action - Reject/Close

  • AI reviewers agree on a likely critical defect: scripts/check-miner-package.mjs:9 and its test are an undisclosed, unrelated change bundled into a PR whose description and title only claim a review-effort test addition for feat(review): deterministic review-effort/complexity estimator (1-5 band + minutes) #2151 — this is scope-creep with no linked issue justifying the miner-package regex change. — Resolve the flagged defect, or override if the AI reviewers are mistaken, then re-run the gate.

Review summary
This PR is described purely as adding a band-5 boundary test to estimateReviewEffort for issue #2151, and that part is correct: 5 files × 100 added lines = 500, plus 5×3 file overhead = 515, which does map to band 5 with minutes = round(515/2) = 258. However, the diff also silently ships an unrelated functional change to scripts/check-miner-package.mjs (widening the allowed lib/ path regex to permit nested subdirectories) plus its accompanying test, neither of which is mentioned in the PR description or tied to #2151 or any other linked issue.

Blockers

Nits — 4 non-blocking
  • scripts/check-miner-package.mjs:9 — the new `(?:[a-z0-9-]+\/)*` pattern is exercised only against trusted, locally-generated npm-pack output (not attacker-controlled input), so the flagged 'ReDoS' risk is largely theoretical, but consider a comment noting why nested lib/ paths are now allowed since the intent isn't obvious from the diff alone.
  • test/unit/review-effort.test.ts:52 — the inline arithmetic comment is a nice touch; consider adding a similarly explicit comment for why 5 files was chosen over fewer/more to hit band 5, for future maintainers tuning the band thresholds.
  • Split the check-miner-package.mjs regex change and its test into a separate PR linked to its own issue (or amend this PR's description to explain why it's included and link the relevant issue), per the repo's convention that every PR must close or clearly link an eligible issue.
  • If the nested-lib-subdirectory support is intentional and needed now, briefly document the motivating case (e.g., a calibration/ subfolder) in the PR description so reviewers aren't left inferring intent from the regex diff alone.

Why this is blocked

Signal Result Evidence
Code review ❌ 1 blocker 1 reviewer
Linked issue ✅ Linked #2151
Related work ✅ No active overlap found No same-issue or scoped active PR overlap found.
Change scope ✅ 20/20 Low review scope from cached public metadata (1 linked issue).
Validation posture ✅ 25/25 PR body includes validation/test evidence.
Contributor workload ✅ 10/10 Author activity: 191 registered-repo PR(s), 102 merged, 18 issue(s).
Contributor context ✅ Confirmed Gittensor contributor luciferlive112116; Gittensor profile; 191 PR(s), 18 issue(s).
Gate result ❌ Blocking Repo-configured hard blocker found.
Review context
  • Author: luciferlive112116
  • Role context: outside_contributor
  • Public audience mode: oss maintainer
  • Lane context: Repository registration is not available in the local Gittensory cache.
  • Public profile languages: JavaScript, MDX, Python, Rust, TypeScript
  • Official Gittensor activity: 191 PR(s), 18 issue(s).
  • PR-specific overlap: none found.
Contributor next steps
  • Keep the PR focused and include validation evidence before maintainer review.
Signal definitions
  • Related work = same linked issue, overlapping active PRs, or title/path similarity.
  • Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
  • Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
  • Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
  • Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed


💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

  • Re-run Gittensory review

@codecov

codecov Bot commented Jul 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@53279f9). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3758   +/-   ##
=======================================
  Coverage        ?   93.29%           
=======================================
  Files           ?      317           
  Lines           ?    32368           
  Branches        ?    11872           
=======================================
  Hits            ?    30199           
  Misses          ?     1537           
  Partials        ?      632           
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@loopover-orb

loopover-orb Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Gittensory is closing this pull request on the maintainer's behalf (AI reviewers agree on a likely critical defect: scripts/check-miner-package.mjs:9 and its test are an undisclosed, unrelated change bundled into a PR whose description and title only claim a review-effort test addition for #2151 — this is scope-creep with no linked issue justifying the miner-package regex change.). This is an automated maintenance action — to pursue this change, please open a new pull request with the issues resolved. Closed PRs may be analyzed later to improve review accuracy, but they are not automatically reopened or re-reviewed.

@loopover-orb loopover-orb Bot closed this Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(review): deterministic review-effort/complexity estimator (1-5 band + minutes)

1 participant