[eslint-refiner] ESLint Refiner daily report -- 2026-09-10

[github-actions[bot]]

Overview

Daily ESLint Refiner pass over eslint-factory (62 registered rules, up from 61 yesterday — require-fs-chmod-try-catch shipped since the last run). Filed 2 issues, both grounded in live code in actions/setup/js/**.

Key finding: issues can expire unfixed

Two prior findings — #57868 (shared try/catch suggestion builder skips VariableDeclaration call sites) and #57869 (no-json-stringify-equality misses indirect template-literal comparisons) — were auto-closed on 2026-09-09 by the tracking bot's TTL (state_reason: not_planned), not because they were fixed or rejected. Re-checking the current source confirmed both defects are still present and still grounded in live code, so both were re-filed as explicitly-labeled recurrences rather than silently dropped.

Issues filed

• eslint-factory: shared try/catch suggestion builder still skips VariableDeclaration call sites — recurrence of expired eslint-factory: shared try/catch suggestion builder silently skips VariableDeclaration call sites #57868. SAFE_WRAPPABLE_STATEMENT_TYPES in try-catch-rule-utils.ts still only covers ExpressionStatement/ReturnStatement, so the dominant real-world shape (const x = fs.someSync(y);, const parsed = JSON.parse(raw);) gets a diagnostic but no autofix, across 14 rules that share this util (one more than at original filing — require-fs-chmod-try-catch inherits it too).
• no-json-stringify-equality: still misses indirect template-literal comparisons — recurrence of expired no-json-stringify-equality: misses indirect template-literal comparisons (live gap: trace_graders.cjs gradeLoops) #57869. trace_graders.cjs:357-366 (gradeLoops) still compares two template-literal-embedded JSON.stringify(...) results (key === prevKey) unnoticed, since the rule only matches direct JSON.stringify(a) === JSON.stringify(b) call expressions.

Rules reviewed this run with no defect found

• require-fs-chmod-try-catch (new, 62nd rule) — inherits the two family-wide known gaps above (and the already-tracked eslint-factory: isIdentifierBoundToFsModule in try-catch-rule-utils.ts does not check for reassignment #59377 reassignment blind spot) but has no chmod-specific defect of its own; all 18 live chmodSync/fchmodSync call sites in the corpus are already inside try blocks.
• require-return-after-core-setfailed — extremely mature and well-tested (JSDoc-annotated DI parameters, switch fall-through, braceless control bodies, cross-block/loop continuation are all already covered); no gap found.
• no-math-minmax-array-spread — zero live Math.min(...)/Math.max(...) spread call sites exist anywhere in actions/setup/js/**, so no grounded finding was possible (a theoretical bare-destructured-call gap exists but isn't worth filing without a live occurrence).

Next actions

• Rebuild coverage on the ~46 of 62 rules never reviewed by this memory, prioritizing rules with hasSuggestions: true and heavy live corpus usage.
• Before treating a past run's "already has an open issue" note as settled, re-check it's still open — the auto-expire TTL can close a tracking issue unfixed.
• Do not re-derive the fs-resolver reassignment gap (eslint-factory: isIdentifierBoundToFsModule in try-catch-rule-utils.ts does not check for reassignment #59377 / eslint-factory: isChildProcessObjectBinding (try-catch-rule-utils.ts) doesn't check for reassignment, unlike sibling resolvers #57624) — already comprehensively filed and still open.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• api.anthropic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 🤖 ESLint Refiner · claude · agent · 307.1 AIC · ⌖ 8.12 AIC · ⊞ 5.8K · ◷

• expires on Sep 10, 2026, 9:32 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by ESLint Refiner.

A newer discussion is available at Discussion #60198.