Public report — dolt, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
1492findings with an exact file:lineof 1518 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
47/113dimensions across the health lenses271 LoC · 2 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
dolthub/dolt is sound in substance but carries real gaps (61%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (93%) — the structure is clean and changes stay contained. Security (78%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Maturity (57%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Domain Modelling (59%) is the next concern — the domain model leaks and drifts, so business rules are harder to trust and change.
Leadership focus, highest impact first: Record significant decisions one document per decision (Architecture documentation); 1 No ADRs found finding(s) in ADR Quality (ADR Quality); Move business rules onto the aggregates/entities they govern… (Rich vs anemic model).
For scale: Hobby (~271 production lines); rebuilding it from scratch would take roughly ~1.2 person-years (~1–3 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (93%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.5) — CQRS, domain model, high decision density × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 22.3–133.8 engineer-days every year, paid as drag on the ~138,664 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–2 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 6–14% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 34,191 line(s) changed over a 90-day window ⇒ ~138,664/year · D1/D2/D4 code quality: averaging 5.4/10 ⇒ a 6–14% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 2 months.
Root cause: an un-encapsulated domain · Medium · Root cause
12 findings across public setters, anemic types and primitive ids share one root cause — the domain layer doesn't protect its own invariants. Fixing the encapsulation pattern resolves them together, rather than chasing each finding.
→ Address encapsulation as one pattern (private setters + behaviour + strongly-typed ids), not 100 separate findings.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Architecture — module dependency matrix
199 modules, 1212 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 63% · Adequate · gated by D2, R1
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
16
High / Critical
A05:2021 — Security Misconfiguration
3
High / Critical
A02:2021 — Cryptographic Failures
2
High / Critical
A04:2021 — Insecure Design
2
Medium
Roadmap
First, establish a central repository for architecture decisions by creating dated, context-rich documents that capture the rationale and consequences of key design choices. Next, address the absence of any existing architecture decision records to ensure future changes are properly documented. Then, shift business rules from anemic services to the entities they govern, ensuring invariants are enforced at the source. Finally, make entity state changes through controlled methods rather than public setters, and update the root README to include a high-level overview of the architecture.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Make entity setters private/init-only; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 45 of 47 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 47 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1492 of 1518 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
The LLM boundary
LLM-set scores this run (4): D19, D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
342 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was doltWorkflowManager.updateExistingWorkflow at 193. A further 8 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being val.compare at 33 — they are counted neither in the figure above nor in this dimension's score.
+ 337 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 doltWorkflowManager.updateExistingWorkflow (cyclomatic 193) finding(s) in Cyclomatic Complexity — start with workflow_manager.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Database.getTableInsensitiveWithRoot (cyclomatic 191) finding(s) in Cyclomatic Complexity — start with database.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 sqlserver.ConfigureServices (cyclomatic 89) finding(s) in Cyclomatic Complexity — start with server.go. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 697 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 main.main (cognitive 16) finding(s) in Cognitive Complexity — start with main.go (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 doltWorkflowManager.updateExistingWorkflow (cognitive 944) finding(s) in Cognitive Complexity — start with workflow_manager.go. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Database.getTableInsensitiveWithRoot (cognitive 303) finding(s) in Cognitive Complexity — start with database.go. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 57 FileTooLong finding(s) in God Classes — start with dolt_queries.go, dolt_queries_diff.go, dolt_queries_merge.go. — One of this dimension's main actionable groups (57 warning-level).
Resolve the 29 TooManyMethods finding(s) in God Classes — start with database.go (2), command_line_config.go (2), controller.go (2). — One of this dimension's main actionable groups (29 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 27 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling6.9 / 10Adequate✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.7 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
102 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is go/libraries/doltcore/sqle/enginetest/dolt_queries_legacy.go.
Off-boarding risk: anonymized user #1 · ×8
Further sole-owners (lower concentration)
What to do
Resolve the 8 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (8 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Dolt's documentation is clear and comprehensive: a strong README with a video intro, What's it for?, and a full CLI section; proto/README covers Protobuf message/service definitions and the update target; docker/README explains Dolt as Git for Data!, its hosted services (DoltHub/DoltLab), and Docker usage; integration-test docs cover ORM compatibility tests, BATS testing, data-dump loading, and GitHub Actions workflows. The README files are well-structured with a visible outline and consistent branding. The documentation is strong for its focus on testing and storage backends: the SQL server tests README gives a clear debugging guide with environment-variable timeouts, remote-debugging setup, and an outline of every listed test; corrupt-dbs contains well-organized examples (bad_commit, bad_journal_crc) that are each named in the document's outline. The Noms Block Store README is thorough — it explains both local and AWS configurations, the content-addressed DAG model, concurrency semantics, and a benchmark comparing NBS to LevelDB with concrete numbers for an MP4 video import on an MBP i5. However, there is no architecture or design doc (the only non-README document in this set is the go/utils/remotesrv README), so the reader cannot tell whether the Noms storage layer is backed by a single AWS S3 bucket versus multiple DynamoDB tables as originally planned and how that affects availability and cost.
What to do
Improve Documentation Quality — currently 7.6/10. — Dolt's documentation is clear and comprehensive: a strong README with a video intro, What's it for?, and a full CLI section; proto/README covers Protobuf message/service definitions and the update target; docker/README explains Dolt as Git for Data!, its hosted services (DoltHub/DoltLab), and Docker usage; integration-test docs cover ORM compatibility tests, BATS testing, data-dump loading, and GitHub Actions workflows. The README files are well-structured with a visible outline and consistent branding. The documentation is strong for its focus on testing and storage backends: the SQL server tests README gives a clear debugging guide with environment-variable timeouts, remote-debugging setup, and an outline of every listed test; corrupt-dbs contains well-organized examples (bad_commit, bad_journal_crc) that are each named in the document's outline. The Noms Block Store README is thorough — it explains both local and AWS configurations, the content-addressed DAG model, concurrency semantics, and a benchmark comparing NBS to LevelDB with concrete numbers for an MP4 video import on an MBP i5. However, there is no architecture or design doc (the only non-README document in this set is the go/utils/remotesrv README), so the reader cannot tell whether the Noms storage layer is backed by a single AWS S3 bucket versus multiple DynamoDB tables as originally planned and how that affects availability and cost.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: slack-webhook-urlsamples/go/coffee/main.go:123detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 1 Secret finding(s) in Secrets (history) — start with main.go. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
High IaC: DS-0002docker/Dockerfiledetected by trivy finding
Medium IaC: CKV_DOCKER_9 · ×2docker/Dockerfile:6detected by trivy finding
✓ On the Gold path — maintain.
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.
Medium: watchdog-personal-data-in-log · ×2go/cmd/dolt/commands/credcmds/check.go:177detected by semgrep finding
What to do
Resolve the 2 Medium finding(s) in Data Compliance (PII/GDPR) — start with check.go, login.go. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
31 of 786 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is go/performance/import_benchmarker/testdef.go.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret passed as a command-line argument finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×4.github/actions/ses-email-action/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted]go/go.moddetected by osv-scanner finding
Medium CVE: GO-2026-5158 · ×5go/go.moddetected by osv-scanner finding
Medium vulnerability: GO-2026-5841 · ×2go/go.moddetected by osv-scanner finding
What to do
Resolve the 4 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2), go.mod (2). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with go.mod. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with go.mod (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.6 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Workflow` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow.go:23
`WorkflowDoltTestStep` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_dolt_test_step.go:22
`WorkflowDoltTestStepGroup` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_dolt_test_step_groups.go:22
`WorkflowDoltTestStepTest` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_dolt_test_step_tests.go:22
`WorkflowEvent` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_event.go:34
`WorkflowEventTrigger` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_event_trigger.go:38
`WorkflowEventTriggerBranch` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_event_trigger_branch.go:19
`WorkflowJob` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_job.go:23
`WorkflowSavedQueryStep` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_saved_query_step.go:32
`WorkflowSavedQueryExpectedRowColumnResult` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_saved_query_step_expected_row_column_result.go:38
`WorkflowStep` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — workflow_step.go:34
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state (private/init-only setters) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
`StatsController` exposes publicly writable state (Debug, Stats). — controller.go:68
What to do
Make entity setters private/init-only; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 12 of 17 project(s) that lack one — worth up to 1.4 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add gosec / govulncheck (or golangci-lint) (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: gosec / govulncheck (or golangci-lint) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Do you agree with this assessment?
R1 · Type Safety2.2 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
5 typed · 18 plain JS — the untyped files are integration-tests/mysql-client-tests/node/concurrency.js, integration-tests/mysql-client-tests/node/database.js, integration-tests/mysql-client-tests/node/helpers.js, integration-tests/mysql-client-tests/node/index.js, integration-tests/mysql-client-tests/node/knex.js, integration-tests/mysql-client-tests/node/mariadb-connector.js (+12 more).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
integration-tests/mysql-client-tests/node/workbenchTests/databases.js:7 · integration-tests/mysql-client-tests/node/workbenchTests/table.js:153 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — databases.js:7
integration-tests/mysql-client-tests/node/workbenchTests/matchers.js:137 · integration-tests/mysql-client-tests/node/workbenchTests/matchers.js:154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — matchers.js:137
integration-tests/mysql-client-tests/node/workbenchTests/matchers.js:109 · integration-tests/mysql-client-tests/node/workbenchTests/matchers.js:127 · integration-tests/mysql-client-tests/node/workbenchTests/matchers.js:144 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — matchers.js:109
integration-tests/mysql-client-tests/node/workbenchTests/index.js:48 · integration-tests/mysql-client-tests/node/workbenchTests/index.js:66 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — index.js:48
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.3 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~105451 lines of test source are present (.go) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .ex, .exs, .go, .java, .py, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.cs, .ex, .exs, .go, .java, .py, .ts) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is mostly .ex, .exs, .go, .java, .py, .ts, which this pass does not read, so cohesion was not assessed for this repository. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
D9 Test Distribution — Tests outside the analyzed solution
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 2 CQRS handler(s); 2 event-sourced shape(s) (event folds / event-recording aggregates)
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this check looks for (2 Go aggregate(s) recording domain events (own events-slice append / raise-record))
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`go test -coverprofile=coverage.out ./...`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — no production JavaScript/TypeScript files to cover (23 test file(s) present) — nothing to measure
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Issue — 10 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×4
High CVE: [GHSA redacted] .github/actions/ses-email-action/package-lock.json— fast-xml-builder 1.1.5: [GHSA redacted] — fast-xml-builder is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fast-xml-builder to 1.1.7 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against fast-xml-builder 1.1.5, and their fixed versions do not agree — anything below 1.1.7 still leaves at least one of them open. Take this package to 1.1.7 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against fast-xml-builder 1.1.5: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] go/go.mod— github.com/apache/thrift 0.13.1-0.20201008052519-daf620915714: [GHSA redacted] — github.com/apache/thrift is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go -C go get github.com/apache/thrift@v0.23.0`, which updates the require line go/go.mod already holds for it).
High CVE: [GHSA redacted] go/go.mod— golang.org/x/image 0.38.0: [GHSA redacted] — golang.org/x/image is not a DIRECT requirement of this module: go.mod records it as `// indirect`, pulled in transitively, so raise it in place (run `go -C go get golang.org/x/image@v0.41.0`, which updates the require line go/go.mod already holds for it). This one row stands for the 7 advisories this scan raises against golang.org/x/image 0.38.0: [GHSA redacted], GO-2026-4961, GO-2026-4962, GO-2026-5031, GO-2026-5061, GO-2026-5062, GO-2026-5066.
High CVE: [GHSA redacted] .github/actions/ses-email-action/package-lock.json— undici 6.24.0: [GHSA redacted] — undici is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin undici to 6.27.0 with an `overrides` entry). This is 1 of 7 advisories with a published fix this scan raises against undici 6.24.0, and their fixed versions do not agree — anything below 6.28.0 still leaves at least one of them open. Take this package to 6.28.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 7 advisories this scan raises against undici 6.24.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: System.Net.Http 4.3.0 — System.Net.Http 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High CVE: System.Text.RegularExpressions 4.3.0 — System.Text.RegularExpressions 4.3.0 (transitive) has a High advisory. https://github.com/advisories/[GHSA redacted]
High IaC: DS-0002 docker/Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN useradd -r -M app` — or whatever this base image's account tooling is, `adduser` and `useradd` are not both present everywhere`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] go/go.mod— google.golang.org/grpc 1.79.3: [GHSA redacted] — upgrade to 1.82.1
FileTooLong: enginetest/dolt_queries.go go/libraries/doltcore/sqle/enginetest/dolt_queries.go:0— FileTooLong — 5287 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_diff.go go/libraries/doltcore/sqle/enginetest/dolt_queries_diff.go:0— FileTooLong — 4271 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_merge.go go/libraries/doltcore/sqle/enginetest/dolt_queries_merge.go:0— FileTooLong — 3710 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sqle/tables.go go/libraries/doltcore/sqle/tables.go:0— FileTooLong — 2070 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_transaction_queries.go go/libraries/doltcore/sqle/enginetest/dolt_transaction_queries.go:0— FileTooLong — 1963 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sqle/database.go go/libraries/doltcore/sqle/database.go:0— FileTooLong — 1907 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_schema_merge.go go/libraries/doltcore/sqle/enginetest/dolt_queries_schema_merge.go:0— FileTooLong — 1880 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: nbs/store.go go/store/nbs/store.go:0— FileTooLong — 1695 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: merge/merge_prolly_rows.go go/libraries/doltcore/merge/merge_prolly_rows.go:0— FileTooLong — 1506 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dolt_ci/workflow_manager.go go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:0— FileTooLong — 1496 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: doltdb/doltdb.go go/libraries/doltcore/doltdb/doltdb.go:0— FileTooLong — 1391 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_rebase.go go/libraries/doltcore/sqle/enginetest/dolt_queries_rebase.go:0— FileTooLong — 1248 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/diff.go go/cmd/dolt/commands/diff.go:0— FileTooLong — 1196 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: dsess/session.go go/libraries/doltcore/sqle/dsess/session.go:0— FileTooLong — 1179 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sqle/database_provider.go go/libraries/doltcore/sqle/database_provider.go:0— FileTooLong — 1153 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_legacy.go go/libraries/doltcore/sqle/enginetest/dolt_queries_legacy.go:0— FileTooLong — 1072 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: blobstore/git_blobstore.go go/store/blobstore/git_blobstore.go:0— FileTooLong — 1054 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: index/dolt_index.go go/libraries/doltcore/sqle/index/dolt_index.go:0— FileTooLong — 930 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: enginetest/dolt_queries_schema_override.go go/libraries/doltcore/sqle/enginetest/dolt_queries_schema_override.go:0— FileTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: SchemaOverrideTests (24-1570). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: cluster/controller.go go/libraries/doltcore/sqle/cluster/controller.go:0— FileTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: sqlserver/server.go go/cmd/dolt/commands/sqlserver/server.go:0— FileTooLong — 824 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: ConfigureServices (125-991). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: doltdb/root_val.go go/libraries/doltcore/doltdb/root_val.go:0— FileTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: merge/merge_schema.go go/libraries/doltcore/merge/merge_schema.go:0— FileTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/sql.go go/cmd/dolt/commands/sql.go:0— FileTooLong — 796 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: remotestorage/chunk_store.go go/libraries/doltcore/remotestorage/chunk_store.go:0— FileTooLong — 778 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/cherry-pick.go:227— go/cmd/dolt/commands/cherry-pick.go:227-238 | go/cmd/dolt/commands/cherry-pick.go:305-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/ci/export.go:85— go/cmd/dolt/commands/ci/export.go:85-96 | go/cmd/dolt/commands/ci/remove.go:78-89 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/fetch.go:105— go/cmd/dolt/commands/fetch.go:105-116 | go/cmd/dolt/commands/pull.go:269-280 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/fetch.go:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/merge.go:424— go/cmd/dolt/commands/merge.go:424-435 | go/cmd/dolt/commands/merge.go:456-467 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/merge.go:424` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/schcmds/import.go:486— go/cmd/dolt/commands/schcmds/import.go:486-497 | go/cmd/dolt/commands/schcmds/import.go:528-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/schcmds/import.go:486` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/cmd/dolt/commands/utils.go:833— go/cmd/dolt/commands/utils.go:833-844 | go/cmd/dolt/commands/utils.go:851-862 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/utils.go:833` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/branch_control/expr_parser_node.go:155— go/libraries/doltcore/branch_control/expr_parser_node.go:155-166 | go/libraries/doltcore/branch_control/expr_parser_node.go:255-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/branch_control/expr_parser_node.go:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12 lines × 2) go/libraries/doltcore/cherry_pick/cherry_pick.go:298— go/libraries/doltcore/cherry_pick/cherry_pick.go:298-311 | go/libraries/doltcore/revert/revert.go:210-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/revert/revert.go:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/doltdb/root_val.go:638— go/libraries/doltcore/doltdb/root_val.go:638-649 | go/libraries/doltcore/doltdb/root_val.go:681-692 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/doltdb/root_val.go:638` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1092— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1092-1103 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1193-1205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1092` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1287— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1287-1298 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1312-1323 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1287` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/merge/merge_schema.go:331— go/libraries/doltcore/merge/merge_schema.go:331-342 | go/libraries/doltcore/merge/merge_schema.go:344-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_schema.go:331` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/merge/merge_schema.go:957— go/libraries/doltcore/merge/merge_schema.go:957-968 | go/libraries/doltcore/merge/merge_schema.go:972-983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_schema.go:957` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) go/libraries/doltcore/merge/merge_schema.go:1247— go/libraries/doltcore/merge/merge_schema.go:1247-1258 | go/libraries/doltcore/merge/merge_schema.go:1269-1280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_schema.go:1247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/schema/collation_comparator.go:41— go/libraries/doltcore/schema/collation_comparator.go:41-52 | go/store/val/tuple_compare.go:58-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/schema/collation_comparator.go:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/schema/schema_impl.go:542— go/libraries/doltcore/schema/schema_impl.go:542-554 | go/libraries/doltcore/schema/schema_impl.go:602-613 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/schema/schema_impl.go:542` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/cluster/branch_control_replica.go:125— go/libraries/doltcore/sqle/cluster/branch_control_replica.go:125-136 | go/libraries/doltcore/sqle/cluster/mysqldb_persister.go:144-155 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/cluster/branch_control_replica.go:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/database.go:2086— go/libraries/doltcore/sqle/database.go:2086-2097 | go/libraries/doltcore/sqle/database.go:2149-2160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dfunctions/merge_base.go:100— go/libraries/doltcore/sqle/dfunctions/merge_base.go:100-111 | go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:485-498 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:379— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:379-390 | go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:397-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:379` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_test_run.go:230— go/libraries/doltcore/sqle/dtablefunctions/dolt_test_run.go:230-241 | go/libraries/doltcore/sqle/dtablefunctions/dolt_test_run.go:267-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_test_run.go:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtables/branch_control_table.go:187— go/libraries/doltcore/sqle/dtables/branch_control_table.go:187-198 | go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:176-190 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/branch_control_table.go:187` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:180— go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:180-191 | go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:273-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtables/diff_iter.go:93— go/libraries/doltcore/sqle/dtables/diff_iter.go:93-104 | go/libraries/doltcore/sqle/dtables/diff_iter.go:108-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/diff_iter.go:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) go/libraries/doltcore/sqle/dtables/diff_table.go:900— go/libraries/doltcore/sqle/dtables/diff_table.go:900-911 | go/libraries/doltcore/sqle/dtables/diff_table.go:914-926 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/diff_table.go:900` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) go/cmd/dolt/commands/branch.go:449— go/cmd/dolt/commands/branch.go:449-459 | go/cmd/dolt/commands/rm.go:113-123 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/diff/table_deltas.go:152— go/libraries/doltcore/diff/table_deltas.go:152-162 | go/libraries/doltcore/diff/table_deltas.go:196-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/diff/table_deltas.go:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/doltdb/ignore.go:100— go/libraries/doltcore/doltdb/ignore.go:100-110 | go/libraries/doltcore/sqle/database.go:1165-1175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) go/libraries/doltcore/doltdb/ignore.go:151— go/libraries/doltcore/doltdb/ignore.go:151-161 | go/libraries/doltcore/doltdb/ignore.go:180-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/doltdb/ignore.go:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1677— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1677-1687 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1733-1745 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/env/actions/remotes.go:221— go/libraries/doltcore/env/actions/remotes.go:221-232 | go/libraries/doltcore/env/actions/remotes.go:405-415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) go/libraries/doltcore/merge/merge_prolly_rows.go:1232— go/libraries/doltcore/merge/merge_prolly_rows.go:1232-1242 | go/libraries/doltcore/merge/merge_prolly_rows.go:1263-1273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_prolly_rows.go:1232` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/merge/merge_prolly_rows.go:2052— go/libraries/doltcore/merge/merge_prolly_rows.go:2052-2062 | go/libraries/doltcore/merge/merge_prolly_rows.go:2077-2087 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_prolly_rows.go:2052` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/merge/violations_fk.go:315— go/libraries/doltcore/merge/violations_fk.go:315-325 | go/libraries/doltcore/merge/violations_fk.go:351-362 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/violations_fk.go:315` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/remotesrv/grpc.go:283— go/libraries/doltcore/remotesrv/grpc.go:283-293 | go/libraries/doltcore/remotesrv/grpc.go:399-415 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/remotesrv/grpc.go:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) go/libraries/doltcore/schema/index_coll.go:225— go/libraries/doltcore/schema/index_coll.go:225-235 | go/libraries/doltcore/schema/index_coll.go:254-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/schema/index_coll.go:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dfunctions/has_ancestor.go:66— go/libraries/doltcore/sqle/dfunctions/has_ancestor.go:66-76 | go/libraries/doltcore/sqle/dfunctions/has_ancestor.go:82-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dfunctions/has_ancestor.go:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:274— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:274-284 | go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_summary.go:266-276 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_summary.go:275— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_summary.go:275-285 | go/libraries/doltcore/sqle/dtablefunctions/dolt_patch.go:133-143 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_summary.go:275` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_log.go:498— go/libraries/doltcore/sqle/dtablefunctions/dolt_log.go:498-508 | go/libraries/doltcore/sqle/dtablefunctions/dolt_log.go:517-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_log.go:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/branch_control_table.go:309— go/libraries/doltcore/sqle/dtables/branch_control_table.go:309-319 | go/libraries/doltcore/sqle/dtables/branch_namespace_control.go:270-283 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/branch_control_table.go:309` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/column_diff_table.go:148— go/libraries/doltcore/sqle/dtables/column_diff_table.go:148-158 | go/libraries/doltcore/sqle/dtables/unscoped_diff_table.go:174-184 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/column_diff_table.go:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/column_diff_table.go:336— go/libraries/doltcore/sqle/dtables/column_diff_table.go:336-346 | go/libraries/doltcore/sqle/dtables/unscoped_diff_table.go:362-372 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/column_diff_table.go:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/log_table.go:487— go/libraries/doltcore/sqle/dtables/log_table.go:487-497 | go/libraries/doltcore/sqle/dtables/log_table.go:499-509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/log_table.go:487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/workspace_table.go:526— go/libraries/doltcore/sqle/dtables/workspace_table.go:526-536 | go/libraries/doltcore/sqle/dtables/workspace_table.go:546-556 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/workspace_table.go:526` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/dtables/workspace_table.go:782— go/libraries/doltcore/sqle/dtables/workspace_table.go:782-792 | go/libraries/doltcore/sqle/dtables/workspace_table.go:793-803 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/index/index_reader.go:540— go/libraries/doltcore/sqle/index/index_reader.go:540-550 | go/libraries/doltcore/sqle/index/index_reader.go:664-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/index/index_reader.go:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/index/index_reader.go:607— go/libraries/doltcore/sqle/index/index_reader.go:607-617 | go/libraries/doltcore/sqle/index/secondary_iter.go:364-377 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) go/libraries/doltcore/sqle/indexed_dolt_table.go:188— go/libraries/doltcore/sqle/indexed_dolt_table.go:188-198 | go/libraries/doltcore/sqle/tables.go:1335-1345 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/indexed_dolt_table.go:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) go/libraries/doltcore/table/untyped/sqlexport/batch_sqlwriter.go:63— go/libraries/doltcore/table/untyped/sqlexport/batch_sqlwriter.go:63-74 | go/libraries/doltcore/table/untyped/sqlexport/sqlwriter.go:51-61 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) go/cmd/dolt/commands/ci/run.go:101— go/cmd/dolt/commands/ci/run.go:101-108 | go/cmd/dolt/commands/ci/view.go:103-110 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) go/cmd/dolt/commands/diff_output.go:150— go/cmd/dolt/commands/diff_output.go:150-157 | go/cmd/dolt/commands/diff_output.go:602-609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) go/cmd/dolt/commands/diff_output.go:242— go/cmd/dolt/commands/diff_output.go:242-249 | go/cmd/dolt/commands/diff_output.go:389-397 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/diff_output.go:242` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/cmd/dolt/commands/fetch.go:138— go/cmd/dolt/commands/fetch.go:138-145 | go/cmd/dolt/commands/pull.go:331-338 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) go/cmd/dolt/commands/rebase.go:128— go/cmd/dolt/commands/rebase.go:128-136 | go/cmd/dolt/commands/rebase.go:175-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/rebase.go:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/doltdb/commit.go:207— go/libraries/doltcore/doltdb/commit.go:207-214 | go/libraries/doltcore/doltdb/commit.go:231-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/doltdb/commit.go:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:642— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:642-649 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:655-662 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/merge/fulltext_table.go:161— go/libraries/doltcore/merge/fulltext_table.go:161-168 | go/libraries/doltcore/merge/fulltext_table.go:172-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/fulltext_table.go:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/merge/merge_schema.go:790— go/libraries/doltcore/merge/merge_schema.go:790-799 | go/libraries/doltcore/merge/merge_schema.go:906-913 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/merge/merge_schema.go:790` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/remotesrv/grpc.go:223— go/libraries/doltcore/remotesrv/grpc.go:223-230 | go/libraries/doltcore/remotesrv/grpc.go:331-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) go/libraries/doltcore/remotesrv/grpc.go:324— go/libraries/doltcore/remotesrv/grpc.go:324-331 | go/libraries/doltcore/remotesrv/grpc.go:448-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/remotesrv/grpc.go:324` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/remotesrv/grpc.go:549— go/libraries/doltcore/remotesrv/grpc.go:549-556 | go/libraries/doltcore/remotesrv/grpc.go:612-619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:663— go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:663-670 | go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:727-734 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:663` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:1018— go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:1018-1025 | go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:1053-1060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/binlogreplication/binlog_type_serialization.go:1018` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/dprocedures/dolt_rebase.go:671— go/libraries/doltcore/sqle/dprocedures/dolt_rebase.go:671-678 | go/libraries/doltcore/sqle/dprocedures/dolt_rebase.go:1041-1048 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dprocedures/dolt_rebase.go:671` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:94— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:94-101 | go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:151-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:94` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts.go:194— go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts.go:194-201 | go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts_summary.go:162-169 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts.go:194` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/dtables/conflicts_tables_prolly.go:804— go/libraries/doltcore/sqle/dtables/conflicts_tables_prolly.go:804-811 | go/libraries/doltcore/sqle/dtables/conflicts_tables_prolly.go:821-828 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/index/dolt_index.go:286— go/libraries/doltcore/sqle/index/dolt_index.go:286-293 | go/libraries/doltcore/sqle/index/dolt_index.go:474-481 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/index/dolt_index.go:286` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/indexed_dolt_table.go:51— go/libraries/doltcore/sqle/indexed_dolt_table.go:51-58 | go/libraries/doltcore/sqle/indexed_dolt_table.go:133-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/indexed_dolt_table.go:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/indexed_dolt_table.go:72— go/libraries/doltcore/sqle/indexed_dolt_table.go:72-80 | go/libraries/doltcore/sqle/indexed_dolt_table.go:90-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/indexed_dolt_table.go:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/kvexec/builder.go:369— go/libraries/doltcore/sqle/kvexec/builder.go:369-376 | go/libraries/doltcore/sqle/kvexec/builder.go:379-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/kvexec/builder.go:369` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) go/libraries/doltcore/sqle/statspro/controller.go:477— go/libraries/doltcore/sqle/statspro/controller.go:477-484 | go/libraries/doltcore/sqle/statspro/controller.go:492-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/statspro/controller.go:477` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (8 lines × 2) go/store/blobstore/oci.go:317— go/store/blobstore/oci.go:317-324 | go/store/blobstore/oci.go:353-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/blobstore/oci.go:317` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) go/store/datas/pull/clone.go:169— go/store/datas/pull/clone.go:169-176 | go/store/datas/pull/clone.go:223-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) go/cmd/dolt/cli/documentation_helper.go:253— go/cmd/dolt/cli/documentation_helper.go:253-262 | go/cmd/dolt/cli/documentation_helper.go:297-306 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/cmd/dolt/commands/cherry-pick.go:206— go/cmd/dolt/commands/cherry-pick.go:206-215 | go/cmd/dolt/commands/cherry-pick.go:287-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/cherry-pick.go:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/cmd/dolt/commands/ci/run.go:80— go/cmd/dolt/commands/ci/run.go:80-89 | go/cmd/dolt/commands/ci/view.go:83-92 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/ci/run.go:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/cmd/dolt/commands/revert.go:113— go/cmd/dolt/commands/revert.go:113-122 | go/cmd/dolt/commands/revert.go:127-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/revert.go:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) go/cmd/dolt/commands/schcmds/import.go:469— go/cmd/dolt/commands/schcmds/import.go:469-478 | go/cmd/dolt/commands/schcmds/import.go:509-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/schcmds/import.go:469` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) go/libraries/doltcore/cherry_pick/cherry_pick.go:283— go/libraries/doltcore/cherry_pick/cherry_pick.go:283-294 | go/libraries/doltcore/revert/revert.go:198-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/libraries/doltcore/remotesrv/sealer.go:83— go/libraries/doltcore/remotesrv/sealer.go:83-92 | go/libraries/doltcore/remotesrv/sealer.go:147-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/dsess/transactions.go:468— go/libraries/doltcore/sqle/dsess/transactions.go:468-477 | go/libraries/doltcore/sqle/dsess/transactions.go:493-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dsess/transactions.go:468` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:108— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:108-117 | go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:140-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/enginetest/validation.go:201— go/libraries/doltcore/sqle/enginetest/validation.go:201-210 | go/libraries/doltcore/sqle/enginetest/validation.go:299-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/enginetest/validation.go:201` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/index/prolly_index_iter.go:314— go/libraries/doltcore/sqle/index/prolly_index_iter.go:314-323 | go/libraries/doltcore/sqle/index/prolly_row_iter.go:224-233 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/index/prolly_index_iter.go:314` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/schema_table.go:276— go/libraries/doltcore/sqle/schema_table.go:276-285 | go/libraries/doltcore/sqle/schema_table.go:415-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/tables.go:224— go/libraries/doltcore/sqle/tables.go:224-233 | go/libraries/doltcore/sqle/tables.go:267-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/tables.go:411— go/libraries/doltcore/sqle/tables.go:411-420 | go/libraries/doltcore/sqle/tables.go:1190-1199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/tables.go:2838— go/libraries/doltcore/sqle/tables.go:2838-2847 | go/libraries/doltcore/sqle/tables.go:2872-2881 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/tables.go:2838` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/writer/prolly_index_writer.go:165— go/libraries/doltcore/sqle/writer/prolly_index_writer.go:165-174 | go/libraries/doltcore/sqle/writer/prolly_index_writer.go:221-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/writer/prolly_index_writer.go:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/libraries/doltcore/sqle/writer/prolly_index_writer.go:317— go/libraries/doltcore/sqle/writer/prolly_index_writer.go:317-326 | go/libraries/doltcore/sqle/writer/prolly_index_writer_keyless.go:213-222 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) go/performance/import_benchmarker/cmd/main.go:67— go/performance/import_benchmarker/cmd/main.go:67-76 | go/performance/sysbench/cmd/main.go:77-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) go/performance/import_benchmarker/testdef.go:116— go/performance/import_benchmarker/testdef.go:116-125 | go/performance/sysbench/testdef.go:177-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/performance/import_benchmarker/testdef.go:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/store/datas/stashlist.go:74— go/store/datas/stashlist.go:74-83 | go/store/datas/stashlist.go:129-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/datas/stashlist.go:74` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) go/store/nbs/archive_reader.go:698— go/store/nbs/archive_reader.go:698-708 | go/store/nbs/archive_reader.go:802-811 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) go/store/nbs/aws_table_persister.go:148— go/store/nbs/aws_table_persister.go:148-159 | go/store/nbs/bs_persister.go:49-58 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) go/store/nbs/journal_chunk_source.go:298— go/store/nbs/journal_chunk_source.go:298-307 | go/store/nbs/journal_chunk_source.go:317-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) go/store/nbs/table_reader.go:815— go/store/nbs/table_reader.go:815-824 | go/store/nbs/table_reader.go:882-891 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/nbs/table_reader.go:815` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) go/store/prolly/tree/map.go:93— go/store/prolly/tree/map.go:93-102 | go/store/prolly/tree/map.go:115-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/prolly/tree/map.go:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TooManyMethods: DoltDB go/libraries/doltcore/doltdb/doltdb.go:126— TooManyMethods — 120 methods, declared across 2 files: doltdb/doltdb.go (119), doltdb/commit.go (1). That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: doltWorkflowManager go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:64— TooManyMethods — 112 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Database go/libraries/doltcore/sqle/database.go:76— TooManyMethods — 96 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DoltSession go/libraries/doltcore/sqle/dsess/session.go:48— TooManyMethods — 77 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: commandLineServerConfig go/cmd/dolt/commands/sqlserver/command_line_config.go:33— TooManyMethods — 74 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: commandLineServerConfig go/cmd/dolt/commands/sqlserver/command_line_config.go:33— TooManyMethods — 74 methods. Most of these members implement servercfg.ServerConfig (52 of 74 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: NomsBlockStore go/store/nbs/store.go:96— TooManyMethods — 71 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DoltEnv go/libraries/doltcore/env/environment.go:82— TooManyMethods — 61 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StatsController go/libraries/doltcore/sqle/statspro/controller.go:68— TooManyMethods — 61 methods, declared across 4 files: statspro/controller.go (28), statspro/listener.go (12), statspro/worker.go (12), statspro/stats_kv.go (9). That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: YAMLConfig go/libraries/doltcore/servercfg/yaml_config.go:152— TooManyMethods — 59 methods. Most of these members implement servercfg.ServerConfig (52 of 59 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: TupleBuilder go/store/val/tuple_builder.go:66— TooManyMethods — 55 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TupleDesc go/store/val/tuple_descriptor.go:47— TooManyMethods — 54 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DoltDatabaseProvider go/libraries/doltcore/sqle/database_provider.go:55— TooManyMethods — 50 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TempTable go/libraries/doltcore/sqle/temp_table.go:38— TooManyMethods — 44 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GenerationalNBS go/store/nbs/generational_chunk_store.go:40— TooManyMethods — 44 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DoltChunkStore go/libraries/doltcore/remotestorage/chunk_store.go:120— TooManyMethods — 42 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: database go/libraries/doltcore/sqle/clusterdb/database.go:36— TooManyMethods — 42 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DoltTable go/libraries/doltcore/sqle/tables.go:88— TooManyMethods — 42 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Controller go/libraries/doltcore/sqle/cluster/controller.go:101— TooManyMethods — 41 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GitBlobstore go/store/blobstore/git_blobstore.go:274— TooManyMethods — 40 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: doltIndex go/libraries/doltcore/sqle/index/dolt_index.go:598— TooManyMethods — 38 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: rootValue go/libraries/doltcore/doltdb/root_val.go:136— TooManyMethods — 37 methods. Most of these members implement doltdb.RootValue (32 of 37 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: Table go/libraries/doltcore/doltdb/table.go:67— TooManyMethods — 37 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AlterableDoltTable go/libraries/doltcore/sqle/tables.go:1492— TooManyMethods — 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: database go/store/datas/database_common.go:37— TooManyMethods — 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (9 lines × 2) go/cmd/dolt/commands/ci/destroy.go:78— go/cmd/dolt/commands/ci/destroy.go:78-87 | go/cmd/dolt/commands/ci/import.go:141-149 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) go/cmd/dolt/commands/ci/init.go:73— go/cmd/dolt/commands/ci/init.go:73-81 | go/cmd/dolt/commands/ci/ls.go:77-85 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/ci/init.go:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/cmd/dolt/commands/debug.go:196— go/cmd/dolt/commands/debug.go:196-204 | go/cmd/dolt/commands/sql.go:274-282 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) go/cmd/dolt/commands/dump.go:698— go/cmd/dolt/commands/dump.go:698-706 | go/cmd/dolt/commands/tblcmds/export.go:120-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/cmd/dolt/commands/dump.go:698` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/cmd/dolt/commands/sql.go:1159— go/cmd/dolt/commands/sql.go:1159-1167 | go/cmd/dolt/commands/sql.go:1173-1181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) go/libraries/doltcore/cherry_pick/cherry_pick.go:270— go/libraries/doltcore/cherry_pick/cherry_pick.go:270-278 | go/libraries/doltcore/revert/revert.go:184-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/cherry_pick/cherry_pick.go:270` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/libraries/doltcore/dbfactory/az.go:77— go/libraries/doltcore/dbfactory/az.go:77-85 | go/libraries/doltcore/dbfactory/gs.go:84-92 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) go/libraries/doltcore/schema/index.go:207— go/libraries/doltcore/schema/index.go:207-215 | go/libraries/doltcore/schema/index.go:230-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/cluster/branch_control_replica.go:60— go/libraries/doltcore/sqle/cluster/branch_control_replica.go:60-68 | go/libraries/doltcore/sqle/cluster/mysqldb_persister.go:69-78 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/cluster/branch_control_replica.go:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/database.go:767— go/libraries/doltcore/sqle/database.go:767-775 | go/libraries/doltcore/sqle/database.go:779-787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/database.go:767` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/database_provider.go:1976— go/libraries/doltcore/sqle/database_provider.go:1976-1984 | go/libraries/doltcore/sqle/database_provider.go:2020-2028 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/database_provider.go:1976` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts_summary.go:154— go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts_summary.go:154-162 | go/libraries/doltcore/sqle/dtablefunctions/dolt_query_diff.go:155-163 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_preview_merge_conflicts_summary.go:154` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/dtables/column_diff_table.go:126— go/libraries/doltcore/sqle/dtables/column_diff_table.go:126-134 | go/libraries/doltcore/sqle/dtables/unscoped_diff_table.go:141-149 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/column_diff_table.go:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/dtables/column_diff_table.go:186— go/libraries/doltcore/sqle/dtables/column_diff_table.go:186-194 | go/libraries/doltcore/sqle/dtables/unscoped_diff_table.go:198-206 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/dtables/commit_ancestors_table.go:126— go/libraries/doltcore/sqle/dtables/commit_ancestors_table.go:126-134 | go/libraries/doltcore/sqle/dtables/commits_table.go:129-137 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/commit_ancestors_table.go:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/dtables/diff_iter.go:287— go/libraries/doltcore/sqle/dtables/diff_iter.go:287-295 | go/libraries/doltcore/sqle/dtables/workspace_table.go:1000-1008 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtables/diff_iter.go:287` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/index/secondary_iter.go:261— go/libraries/doltcore/sqle/index/secondary_iter.go:261-269 | go/libraries/doltcore/sqle/index/secondary_iter.go:320-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/index/secondary_iter.go:261` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) go/libraries/doltcore/sqle/kvexec/builder.go:395— go/libraries/doltcore/sqle/kvexec/builder.go:395-404 | go/libraries/doltcore/sqle/kvexec/builder.go:449-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) go/performance/utils/benchmark_runner/doltgres.go:141— go/performance/utils/benchmark_runner/doltgres.go:141-149 | go/performance/utils/benchmark_runner/postgres.go:134-142 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/performance/utils/benchmark_runner/doltgres.go:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/store/blobstore/gcs.go:177— go/store/blobstore/gcs.go:177-185 | go/store/blobstore/inmem.go:130-138 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/blobstore/gcs.go:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/store/nbs/file_manifest.go:177— go/store/nbs/file_manifest.go:177-185 | go/store/nbs/file_manifest.go:201-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/nbs/file_manifest.go:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (9 lines × 2) go/store/nbs/no_conjoin_bs_persister.go:59— go/store/nbs/no_conjoin_bs_persister.go:59-67 | go/store/nbs/single_blob_bs_persister.go:53-61 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/nbs/no_conjoin_bs_persister.go:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) go/store/nbs/table_reader.go:238— go/store/nbs/table_reader.go:238-246 | go/store/nbs/table_reader.go:578-586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/nbs/table_reader.go:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) go/store/prolly/artifact_map.go:405— go/store/prolly/artifact_map.go:405-414 | go/store/prolly/artifact_map.go:484-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) go/store/prolly/message/merge_artifacts.go:122— go/store/prolly/message/merge_artifacts.go:122-130 | go/store/prolly/message/prolly_map.go:120-128 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/store/prolly/message/merge_artifacts.go:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/branch_control/expr_parser.go:132— go/libraries/doltcore/branch_control/expr_parser.go:132-144 | go/libraries/doltcore/branch_control/expr_parser_node.go:443-455 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/branch_control/expr_parser.go:132` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/cherry_pick/cherry_pick.go:575— go/libraries/doltcore/cherry_pick/cherry_pick.go:575-587 | go/libraries/doltcore/revert/revert.go:583-595 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/cherry_pick/cherry_pick.go:575` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/doltdb/commit.go:169— go/libraries/doltcore/doltdb/commit.go:169-181 | go/libraries/doltcore/doltdb/doltdb.go:908-920 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) go/libraries/doltcore/doltdb/stash.go:62— go/libraries/doltcore/doltdb/stash.go:62-75 | go/libraries/doltcore/doltdb/tag.go:38-50 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1167— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1167-1179 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1269-1281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1480— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1480-1492 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1528-1541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1480` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1501— go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1501-1513 | go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1565-1577 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/env/actions/dolt_ci/workflow_manager.go:1501` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/cluster/branch_control_replica.go:253— go/libraries/doltcore/sqle/cluster/branch_control_replica.go:253-265 | go/libraries/doltcore/sqle/cluster/mysqldb_persister.go:286-298 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/cluster/branch_control_replica.go:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/database.go:2068— go/libraries/doltcore/sqle/database.go:2068-2080 | go/libraries/doltcore/sqle/database.go:2125-2137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/database.go:2068` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/database.go:2528— go/libraries/doltcore/sqle/database.go:2528-2540 | go/libraries/doltcore/sqle/database.go:2593-2606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/dsess/session.go:1981— go/libraries/doltcore/sqle/dsess/session.go:1981-1993 | go/libraries/doltcore/sqle/dsess/session.go:1995-2007 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dsess/session.go:1981` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:835— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff.go:835-848 | go/libraries/doltcore/sqle/schema_override.go:78-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:172— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:172-184 | go/libraries/doltcore/sqle/dtablefunctions/dolt_patch.go:315-327 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:172` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:348— go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:348-360 | go/libraries/doltcore/sqle/dtablefunctions/dolt_schema_diff.go:370-382 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `go/libraries/doltcore/sqle/dtablefunctions/dolt_diff_stat.go:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.