[sergo] Sergo Report: Mass-Landed-Fix Reconcile - 2026-10-04 #65500
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Sergo - Serena Go Expert. A newer discussion is available at Discussion #65754. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
Registry stable at 76 analyzers (no new linter since R85 / fprintferrorunchecked). The gh api reconcile matched memory exact expectations (14 open sergo issues), but reading the CODE behind each one instead of trusting the open label revealed something unusual: 13 of the 14 opens are already fixed in the codebase. This is the largest landed-fix-rate reconcile in sergo run history. Only timenowsub remains genuinely broken and has been refiled.
Tool and Registry Status
Strategy: 50/50 Cached Reuse + New Exploration
Cached component: reconciled all 14 open sergo issues against current code rather than only against GitHub state, since prior runs established that issues are rarely closed even when fixed (phantom_reconcile pattern).
New-explore component: swept three candidate veins for undiscovered bugs - AssignStmt-only nodeFilter shapes, sameExpr-style equality helpers, and nolint-wiring parity across all 76 linters. All three came back clean; these veins are now exhausted per standing memory notes.
Findings
New issue filed - timenowsub (pkg/linters/timenowsub/timenowsub.go lines 50 and 103) still has zero UnwrapParenExpr calls before two bare type assertions, so a parenthesized time.Now() receiver or qualifier escapes detection. This is CI-enforced (native and wasm) with no test coverage for either shape. 3rd occurrence of this exact lineage (sg77a3, then timenowsub misses parenthesized time.Now() call: (time.Now()).Sub(t) escapes this CI-enforced linter #63344, now refiled).
13 issues confirmed fixed in code since R85, all still open on GitHub:
Generated Tasks
Recommendation for Maintainers
This workflow has no close-issue capability in its safe-output tools, so the 13 landed issues above remain open despite being fixed. Please bulk-close them when convenient. Separately, an issue titled sergo test probe 2 was created by mistake this run while diagnosing a tooling gotcha - please close that one too, it has no real content.
Metrics
Historical Context
Total runs: 86. Total findings across all runs: 533. Running average success score: 8.74.
Next Run Focus (R87)
Verify the timenowsub refile lands. Re-tally open issues once the 13 landed fixes are bulk-closed - the open count should drop sharply. Since most standing bug veins (paren_unwrap_gap, branch_state_merge, presnapshot_position_blind, idiom_reflag_no_allowlist, block_scope_state_reset, ident_only_equality_gap) just closed out in this one sweep, R87 is a good point to pick an entirely fresh exploration target rather than continuing to probe exhausted veins. If the registry grows to a 77th analyzer, audit it fresh with the standing day-one checks.
References:
All reactions