influxdata/influxdb

Executive summary

influxdata/influxdb is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because the project keeps no record of its design decisions. It scores 66 out of 100, which the At risk rating leaves unchanged.

Maturity, at 54, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 10 points. Adding test instructions to the README is another step, worth about 4 points. Raising Maturity to 70 would lift the score to about 73.

Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eleven passwords or keys are open to anyone who can read the repository, and sixteen parts of the code are no longer understood by anyone working on it. Pinning each tool to an exact version, replacing each exposed password or key and having someone learn the forgotten files would close these risks. The three unsafe settings in infrastructure or container files need changing to safe values. The two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The eight sets of files in separate parts that keep changing together need that dependency made explicit.

The product code is 333,684 lines, about €430,000 to rebuild.

Code Health 79 Strong Architecture 96 ★ Exemplary Maturity 54 Adequate, capped by Architecture documentation Production Readiness 69 Adequate Security and Compliance 74 Adequate, capped by Secrets (history), Static Analysis (SAST) and Supply-chain Provenance & Signing Domain Modelling 100 ★ Exemplary Event Sourcing 100 ★ Exemplary Performance 91 ★ Exemplary

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Maturity 54 · counts for 45%Production Readiness 69 · counts for 25%Security and Compliance 74 · counts for 14%Code Health 79 · counts for 8%Performance 91 · counts for 4%Architecture 96 · counts for 2%Domain Modelling 100 · counts for 1%Event Sourcing 100 · counts for 1%

If Maturity rose from 54 to 70, the lowest score rated Strong, the score would rise from 66 to about 73.

Code composition: what the lines of code are

Product code 93%Tests 7%

New since the last survey: 21 findings

These 21 critical or serious findings weren't in the previous survey, on 11 October 2026.

Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Secrets (history) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Knowledge Freshness · Orphaned knowledge influxdb3_catalog/src/log/versions/v4.rs
Knowledge Freshness · Orphaned knowledge influxdb3_processing_engine/src/scheduler/tests.rs
Knowledge Freshness · Orphaned knowledge influxdb3_processing_engine/src/scheduler.rs
Knowledge Freshness · Orphaned knowledge influxdb3_catalog/src/log/versions/v3.rs
Knowledge Freshness · Orphaned knowledge influxdb3_processing_engine/src/worker/local.rs
Supply-chain Provenance & Signing · REDACTED
Documentation (README) · README may be stale

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 9 findings

These 9 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one.

Churn × Complexity Hotspots · Hotspot: influxdb3_server/src/http.rs influxdb3_server/src/http.rs
Churn × Complexity Hotspots · Hotspot: influxdb3/src/commands/serve.rs influxdb3/src/commands/serve.rs
Churn × Complexity Hotspots · Hotspot: influxdb3_authz/src/authorizer.rs influxdb3_authz/src/authorizer.rs
Churn × Complexity Hotspots · Hotspot: influxdb3/src/commands/create.rs influxdb3/src/commands/create.rs
Churn × Complexity Hotspots · Hotspot: influxdb3_write/src/write_buffer/queryable_buffer.rs influxdb3_write/src/write_buffer/queryable_buffer.rs
Churn × Complexity Hotspots · Hotspot: influxdb3_processing_engine/src/lib.rs influxdb3_processing_engine/src/lib.rs
Churn × Complexity Hotspots · Hotspot: influxdb3_write/src/write_buffer/validator.rs influxdb3_write/src/write_buffer/validator.rs
Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0315 REDACTED
Supply-chain Provenance & Signing REDACTED

Rebuild cost: about €430,000 · Estimate

Cost to rebuild	€140,000 to €720,000, for 2,373 to 7,527 hours of work, about 2.9 person-years for 1 to 6 engineers
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.9 at a score of 66. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Large: 333,684 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Resolve the 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 10 points · Low effort · ADR Quality

Record your significant design decisions.

Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Raises the score by about 8 points · Medium effort · Architecture documentation

Explain in the README how to run the tests.

Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.

Raises the score by about 4 points · Medium effort · Documentation (README)

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €430,000 to build again, about 2.9 person-years of work. Its weakest lens is Maturity, at 54 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

Based on: the rebuild estimate · the Maturity grade · how much each lens counts

What to do: Start with the Maturity actions in Top priorities.

If you do one thing first · First action

Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 10 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

715 modules, with 2309 dependencies between them. 4 loops run through 215 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 675 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 arrow_util.dictionary	2 authz.permission	3 influxdb2_client.models.ast.identifier	5 iox_query.physical_optimizer.sort.merge_partitions	6 metric	7 data_types.partition	8 influxdb3_authz	9 influxdb3_catalog.catalog.versions.v3.events	10 influxdb_influxql_parser.visit	11 influxdb_influxql_parser.visit_mut	12 iox_time	13 influxdb3_catalog.catalog	14 influxdb_influxql_parser.expression.arithmetic	15 influxdb3_catalog.log.versions.v1	16 influxdb3_catalog.snapshot.versions.v1	17 influxdb_influxql_parser.select	18 schema	19 influxdb3_catalog.log.versions.v2	20 influxdb3_catalog.log.versions.v3	21 influxdb3_catalog.log.versions.v4	22 influxdb3_catalog.catalog.versions.v2	23 influxdb3_id	24 influxdb3_wal	25 influxdb3_catalog.catalog.versions.v3.schema.node	26 influxdb3_catalog.catalog.versions.v3.schema.trigger	27 influxdb3.commands.serve	28 influxdb3_catalog.catalog.versions.v1	29 influxdb3_catalog.catalog.versions.v3.schema.cache	30 influxdb2_client.models.ast.duration	32 data_types	33 data_types.columns	34 influxdb3_catalog.format.record	35 arrow_util.test_util	38 iox_query.exec.context
1 arrow_util.dictionary
2 authz.permission
3 influxdb2_client.models.ast.identifier
4 iox_http.write.params
5 iox_query.physical_optimizer.sort.merge_partitions
6 metric
7 data_types.partition																														3	3		3
8 influxdb3_authz		1	1																			2					4						9
9 influxdb3_catalog.catalog.versions.v3.events	1			1
10 influxdb_influxql_parser.visit													4			9
11 influxdb_influxql_parser.visit_mut													4			9
12 iox_time				1																									3	1			3
13 influxdb3_catalog.catalog							1				1											1
14 influxdb_influxql_parser.expression.arithmetic			1						4	4																							8
15 influxdb3_catalog.log.versions.v1		1										1										14		6	8	1	8	12	2	7	4
16 influxdb3_catalog.snapshot.versions.v1												1					2					4		4	2	1	2	2		3	4	3
17 influxdb_influxql_parser.select		3	1						9	9			6																				9
18 schema															1																2		2
19 influxdb3_catalog.log.versions.v2		1										1		25			1					17		6	9	2	1	13	2	7	4		3
20 influxdb3_catalog.log.versions.v3		2										1		11			1	2				19		7	8	2	3	10	5	7	4		3
21 influxdb3_catalog.log.versions.v4		2										1		9			2	2	6		8	21		5	4	2	3	8	6	7	4		4
22 influxdb3_catalog.catalog.versions.v2			7		2		4	3			3	12		8	1		7	1	2	7		9		3	4	2	30	7	5	7	7		3
23 influxdb3_id																					1									1	1		17
24 influxdb3_wal											2					1						1							3	1	1		2
25 influxdb3_catalog.catalog.versions.v3.schema.node			1																				1			1	2						1
26 influxdb3_catalog.catalog.versions.v3.schema.trigger		1	1																			3		1			2						2
27 influxdb3.commands.serve					1																		1		1		1		2
28 influxdb3_catalog.catalog.versions.v1			4				1				2	6		8	2		3	1	2	1		3		2	4	1		4	4	4	2		2
29 influxdb3_catalog.catalog.versions.v3.schema.cache		1	2																			2		2			4		3	2
30 influxdb2_client.models.ast.duration																												3
31 client_util.connection	1																												1
32 data_types		2				8					1		2																1		5		10
33 data_types.columns		2															2													1			1
34 influxdb3_catalog.format.record																															1
35 arrow_util.test_util																																3
36 influxdb3_catalog.catalog.versions.v3.catalog		1			1		3	2			2	4									3	5	1	3	2	1	7	5	7	2			3
37 influxdb3_catalog.format.registry								1																			2					1	1
38 iox_query.exec.context	1																															1	5
39 iox_query.query_log					3						2																		3	2			3	1
40 iox_query_influxql.plan.planner				2									6			6	2																	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 79% · Strong ·

The Good

D3 · Rust God Classes 9.1 D4 · Rust Code Duplication 9.5 D17 · Rust Explicit Debt 9.9 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

D1 · Rust Cyclomatic Complexity 6.7 D2 · Rust Cognitive Complexity 6.4 X4 · Repo Structured logging 5.3

At a glance — Architecture · 96% · Exemplary ·

The Good

D6 · Rust Cohesion (LCOM4) 9.9 D26 · Rust Project Cohesion 9.5 D35 · Rust Change Coupling 9.9 AX10 · Repo Code composition 9.6 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX8 · Repo Test isolation 10.0 AX9 · Repo CQS / query purity 10.0

The Bad

D5 · Rust Coupling 6.9

At a glance — Maturity · 54% · Adequate · gated by M2 ·

The Good

D15 · Rust Churn × Complexity Hotspots 10.0 D16 · Rust Bus Factor 10.0 D19 · Rust Documentation Quality 10.0 D34 · Rust Knowledge Freshness 7.9 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 5.3 M4 · Repo Documentation accuracy 6.0

The Ugly

D20 · Rust ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 69% · Adequate ·

The Good

D9 · Rust Test Distribution 10.0 D12 · Rust Dependency Hygiene 8.9 D13 · Rust REDACTED Scanning 10.0 D14 · Rust License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 10.0

The Bad

P3 · Repo Security & performance tooling 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0

At a glance — Security · 74% · Adequate · gated by D28, D29, D36 ·

The Good

D37 · Rust Vulnerability-disclosure Policy 10.0 D43 · Rust Malicious Dependencies 10.0 D44 · Rust Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D30 · Rust Dependency Vulnerabilities 6.0

The Ugly

D28 · Rust Secrets (history) 0.0 D29 · Rust Static Analysis (SAST) 0.5 D31 · Rust IaC & Container Security 4.0 D36 · Rust Supply-chain Provenance & Signing 2.5

At a glance — Domain Modelling · 100% · Exemplary ·

The Good

DM1 · Repo Aggregate boundaries 10.0 DM2 · Repo Strongly-typed ids 10.0 DM4 · Repo Rich vs anemic domain model 10.0 DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good

ES1 · Repo Fold determinism 10.0 ES2 · Repo Immutable events 10.0

At a glance — Performance · 91% · Exemplary ·

The Good

PF1 · Repo Benchmark discipline 8.5 PF3 · Repo Async & latency hygiene 10.0

Security & Compliance — OWASP Top-10 mapping

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
A03:2025 — Software Supply Chain Failures	24	High / Critical
A05:2025 — Injection	18	High / Critical
A07:2025 — Authentication Failures	12	High / Critical
A02:2025 — Security Misconfiguration	10	High / Critical

Roadmap

First, establish architectural governance by creating a dedicated ADR folder to document significant design decisions and their consequences. Next, ensure documentation accuracy by fixing broken links in the README and adding a clear section on how to run the test suite. Finally, improve code health by removing orphaned knowledge artifacts, starting with the identified files in the test and version modules.

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.	+10.0 pts	Low	ADR Quality
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+8.0 pts	Medium	Architecture documentation
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.	+4.0 pts	Medium	Documentation (README)
Reconcile the README with reality: core/catalog_cache/README.md links to `../docs/catalog_service.md`, but `core/docs/catalog_service.md` does not exist; core/iox_query/README.md links to `../docs/query_processing.md`, but `core/docs/query_processing.md` does not exist.	+3.2 pts	Medium	Documentation accuracy
Resolve the 16 Orphaned knowledge finding(s) in Knowledge Freshness — start with tests.rs (7), v3.rs (2), v1.rs.	+3.0 pts	Medium	Knowledge Freshness
Improve Dependency Hygiene — currently 9.0/10.	+1.9 pts	Medium	Dependency Hygiene
Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED.	+0.8 pts	Low	Secrets (history)
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.	+1.6 pts	Medium	Deployment & Rollback

File quality

Per-file score 0–10 — a quality signature. Of 232 files carrying findings, judged against the Production bar: 2% slop · 54% mixed · 44% near-clean.

File	Score	Band	Worst signal
influxdb3/src/commands/serve.rs	1.0	Slop	Change Coupling: Boundary-crossing change coupling: serve.rs ↔ sender.rs
REDACTED	1.4	Slop	IaC & Container Security: Critical IaC: REDACTED
influxdb3_query_executor/src/lib.rs	1.7	Slop	Change Coupling: Boundary-crossing change coupling: lib.rs ↔ lib.rs
REDACTED	3.0	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
influxdb3/src/commands/create.rs	5.1	Mixed	Change Coupling: Boundary-crossing change coupling: create.rs ↔ manager.rs
REDACTED	5.1	Mixed	Secrets (history): High secret: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.6	Mixed	IaC & Container Security: Medium IaC: REDACTED
REDACTED	5.8	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	5.8	Mixed	Secrets (history): High secret: REDACTED
influxdb3_write/src/write_buffer/queryable_buffer.rs	5.9	Mixed	Cyclomatic Complexity: QueryableBuffer::buffer_wal_contents_and_persist_snapshotted_data (cyclomatic 17)
influxdb3_catalog/src/catalog.rs	5.9	Mixed	Code Duplication: Duplicated block (18 lines × 2)
core/iox_query/src/test.rs	5.9	Mixed	Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
core/iox_query_influxql/src/plan/planner.rs	6.0	Mixed	Explicit Debt: TodoComment
influxdb3_server/src/http.rs	6.0	Mixed	Explicit Debt: TodoComment
influxdb3_catalog/src/catalog/versions/v2.rs	6.0	Mixed	Explicit Debt: TodoComment
influxdb3_catalog/src/catalog/versions/v1.rs	6.0	Mixed	Explicit Debt: TodoComment
core/iox_query_influxql/src/window/integral.rs	6.0	Mixed	Explicit Debt: TodoComment

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 57

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 797

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 205

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 15

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

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. 71 of 71 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — 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 — 71 dimensions across the health lenses

D1D2D3D4D5D6D9D12D13D14D15D16D17D19D20D26D28D29D30D31D34D35D36D37D43D44AX10AX3AX4AX8AX9C2DM1DM2DM4DM5DM6ES1ES2M1M2M3M4P1P10P2P3P4P6PF1PF3S1X1X12X13X14X15X17X19X21X22X23X24X25X26X27X28X29X3X30X4

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, 995 of 1059 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17522-fbee-76c9-a085-d545c4ec0f76.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 489 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. REDACTED.dockerignore, REDACTED.dockerignore carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 2 of 4 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> #syntax=docker/dockerfile:1.2 2 | ARG RUST_VERSION=1.92 3 | FROM rust:${RUST_VERSION}-slim-bookworm as build -------------------- ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1.2: failed to do request: Head "https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.2": Forbidden; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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 — an in-process token-stream comparison over sliding windows, with type-aware normalization — so 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.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED 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.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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 on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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.
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.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain 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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.7 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Prevented

32 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was InfluxQLToLogicalPlan::function_to_df_expr at 51. A further 19 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 StatementParam::try_from at 42 — they are counted neither in the figure above nor in this dimension's score. 16 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: core/iox_query_params/src/params.rs (StatementParam::try_from at 42), core/predicate/src/rpc_predicate/rewrite.rs (predicate::rpc_predicate::rewrite::is_comparison at 42), influxdb3_catalog/src/snapshot/versions/v1.rs (DataType::from at 41), influxdb3_catalog/src/snapshot/versions/v2.rs (DataType::from at 41), influxdb3_catalog/src/snapshot/versions/v3.rs (DataType::from at 41), and 11 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

influxdb3::commands::serve::command (cyclomatic 32) · ×5influxdb3/src/commands/serve.rs:952

iox_query::statistics::partition_statistics::statistics_by_partition (cyclomatic 19) · ×4core/iox_query/src/statistics/partition_statistics/mod.rs:338

InfluxQLToLogicalPlan::function_to_df_expr (cyclomatic 51) · ×2core/iox_query_influxql/src/plan/planner.rs:2668

influxdb3_server::http::perform_routing (cyclomatic 47) · ×2influxdb3_server/src/http.rs:2742

iox_query_influxql::plan::planner_rewrite_expression::rewrite_binary_expr (cyclomatic 31) · ×2core/iox_query_influxql/src/plan/planner_rewrite_expression.rs:274

+ 17 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 32 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with InfluxQLToLogicalPlan::function_to_df_expr (cyclomatic 51), influxdb3_server::http::perform_routing (cyclomatic 47), Error::into_response (cyclomatic 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 32 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.

Do you agree with this assessment?

D2 · Cognitive Complexity6.4 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 100% · ceiling Prevented

114 method(s) exceeded the cognitive complexity threshold of 15; the worst was InnerCatalog::apply_delete_batch at 67.

iox_query::query_log::collect_ingester_metrics (cognitive 27) · ×12core/iox_query/src/query_log.rs:1374

InfluxQLToLogicalPlan::select_aggregate (cognitive 59) · ×8core/iox_query_influxql/src/plan/planner.rs:1471

influxdb3::commands::create::command (cognitive 48) · ×6influxdb3/src/commands/create.rs:330

InnerCatalog::apply_delete_batch (cognitive 67) · ×4influxdb3_catalog/src/catalog/versions/v2.rs:1914

influxdb3_server::http::record_batch_stream_to_body (cognitive 48) · ×4influxdb3_server/src/http.rs:2440

+ 68 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with InnerCatalog::apply_delete_batch (cognitive 67). — Refactoring it lifts Cognitive Complexity from 6.4 to about 6.5/10.
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 Classes9.1 / 10Stronggated by 87 serious findings✓ 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.

Maturity: Documented → Verified → Prevented · effective 9.1 / 10 · rule-coverage 100% · ceiling Prevented

87 god class(es) detected.

FileTooLong: versions/v2.rs · ×43influxdb3_catalog/src/catalog/versions/v2.rs

MethodTooLong: Error.into_response · ×14influxdb3_server/src/http.rs:728

FunctionTooLong: influxdb3::commands::serve::command · ×13influxdb3/src/commands/serve.rs:952

ClassTooLong: Catalog · ×10influxdb3_catalog/src/catalog/versions/v3/catalog.rs:400

TooManyMethods: Catalog · ×6influxdb3_catalog/src/catalog/versions/v3/catalog.rs:400

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 43 FileTooLong finding(s) in God Classes — start with lib.rs (9), v2.rs (2), update.rs (2). — One of this dimension's main actionable groups (43 warning-level).
Resolve the 14 MethodTooLong finding(s) in God Classes — start with table_index_cache.rs (2), query_log.rs (2), http.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 13 FunctionTooLong finding(s) in God Classes — start with http.rs (2), lib.rs (2), serve.rs. — One of this dimension's main actionable groups (13 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.

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 386 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Verified

366 duplicated block group(s) detected. A further 20 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 386 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (9 lines × 2) · ×33core/flightsql/src/planner.rs:444

Duplicated block (8 lines × 2) · ×28core/influxdb_influxql_parser/src/visit.rs:623

Duplicated block (7 lines × 2) · ×25core/influxdb_influxql_parser/src/visit_mut.rs:761

Duplicated block (10 lines × 2) · ×23core/influxdb_influxql_parser/src/common.rs:125

Duplicated block (11 lines × 2) · ×19core/metric_exporters/src/lib.rs:115

+ 100 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 33 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with lib.rs (8), v1.rs (7), v2.rs (5). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 28 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with v1.rs (6), v2.rs (4), planner.rs (3). — One of this dimension's main actionable groups (28 warning-level).
Resolve the 25 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with v2.rs (6), v1.rs (3), storage.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

87 production modules (Cargo), 0 dependency cycle(s), 10 unstable depended-on module(s). Read from the build's own module declarations; 21 module(s) off the main sequence, with abstractness counted on 82 of the 87 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: arrow_util · ×21

Unstable project dml

Unstable project influxdb3_commands

Unstable project influxdb3_query_executor

Unstable project influxdb3_server

+ 6 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 21 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 1 Unstable project dml finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project influxdb3_commands finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 3 serious findings✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

3 of 676 classes have LCOM4 above 3.

Low cohesion: Column (LCOM4 6) · ×3core/data_types/src/columns.rs:190

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with columns.rs, test.rs, lib.rs. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

4115 test methods: 3807 unit, 308 integration, 0 BDD, 0 e2e. The Rust suite contributes 4115 `#[test]` function(s) across 489 file(s) declaring at least one; its unit/integration split is Cargo's own — 39 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene~~8.9~~ 8.9 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 99% · ceiling Verified

21 outdated, 0 yanked direct Cargo dependencies. 128 of 129 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Outdated: clap · ×21

What to do

Improve Dependency Hygiene — currently 9.0/10. — 21 outdated, 0 yanked direct Cargo dependencies. 128 of 129 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 670 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 36 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor10.0 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No source file's living knowledge is concentrated in a single author. Counted over 716 of the 940 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 114 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

114 deducted task-comment markers across 333684 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×109influxdb3_write/src/lib.rs:188

XxxComment · ×2influxdb3_processing_engine/src/virtualenv.rs:20

HackComment · ×2core/object_store_mem_cache/src/store.rs:86

FixmeCommentcore/predicate/src/lib.rs:197

What to do

Resolve the 109 TodoComment finding(s) in Explicit Debt — start with lib.rs (18), tests.rs (8), v1.rs (6). — One of this dimension's main actionable groups (109 warning-level).
Resolve the 2 XxxComment finding(s) in Explicit Debt — start with virtualenv.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with store.rs, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 13 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D26 · Project Cohesion9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

2 of 88 build units (Cargo) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

11 finding(s): 0 critical, 11 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED

What to do

Resolve the 6 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 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.

Do you agree with this assessment?

D29 · Static Analysis (SAST)0.5 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.5 / 10 · rule-coverage 100% · ceiling Documented

18 finding(s): 0 critical, 18 high, 0 medium, 0 low. 1 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 12 file(s) — `core/backoff/src/lib.rs` (line 457, line 480), `core/iox_query/src/analyzer/handle_gapfill.rs` (line 157), `core/iox_query_influxql/src/plan/planner.rs` (line 315, line 512, line 1032), `core/iox_query_influxql/src/plan/rewriter.rs` (line 155, line 1066, line 1491, …), `core/object_store_mem_cache/src/cache_system/loader.rs` (line 370, line 403, line 495, …), … (+7 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

What to do

Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D30 · Dependency Vulnerabilities6.0 / 10Adequate✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

19 finding(s): 0 critical, 1 high, 18 medium, 0 low.

REDACTED

What to do

Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D31 · IaC & Container Security~~8.0~~ 4.0 / 10Weak✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 4.0 / 10 · rule-coverage 50% · ceiling Documented

10 finding(s): 1 critical, 2 high, 6 medium, 1 low.

REDACTED

What to do

Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED.ci (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED.ci. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED.ci (3). — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D34 · Knowledge Freshness7.9 / 10Adequategated by 16 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 100% · ceiling Documented

148 of 716 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is influxdb3_catalog/src/catalog/versions/v1.rs. Counted over 716 of the 940 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×16influxdb3_catalog/src/catalog/versions/v1.rs:1

Orphaned file · ×132influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:1

Further orphaned files (smaller)

What to do

Resolve the 16 Orphaned knowledge finding(s) in Knowledge Freshness — start with tests.rs (7), v3.rs (2), v1.rs. — One of this dimension's main actionable groups (16 issue-level).
Resolve the 132 Orphaned file finding(s) in Knowledge Freshness — start with tests.rs (34), mod.rs (4), enterprise.rs (3). — One of this dimension's main actionable groups (132 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling9.9 / 10Adequategated by 8 critical findings✓ Tool-verified

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. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: snapshot_tracker.rs↔mod.rs 80%; catalog.rs↔serialize.rs 78%; serve.rs↔sender.rs 75%

Boundary-crossing change coupling: snapshot_tracker.rs ↔ mod.rs · ×8influxdb3_wal/src/snapshot_tracker.rs:1

Change coupling: catalog.rs ↔ serialize.rs · ×2influxdb3_catalog/src/catalog.rs:1

What to do

Resolve the 8 Boundary-crossing change coupling finding(s) in Change Coupling — start with snapshot_tracker.rs (2), serve.rs (2), lib.rs (2). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with catalog.rs, queryable_buffer.rs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED 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.

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.6 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Do you agree with this assessment?

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether an aggregate references another aggregate by identity rather than embedding it by object reference.

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?

DM2 · Strongly-typed ids10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

Do you agree with this assessment?

DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.

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.

Do you agree with this assessment?

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

Do you agree with this assessment?

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

Do you agree with this assessment?

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

Do you agree with this assessment?

M1 · Documentation (README)5.3 / 10Adequate✓ Tool-verified

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.

504 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 85 of 93 project(s) that lack one — worth up to 1.8 pts.
Review the README against recent changes; refresh the parts that drifted.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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 numbered `NNNN-title` documents in any markup this check reads, 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.

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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.

Do you agree with this assessment?

M4 · Documentation accuracy6.0 / 10Adequate✓ Tool-verified

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.

core/catalog_cache/README.md links to `../docs/catalog_service.md`, but `core/docs/catalog_service.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — core/catalog_cache/README.md:2
core/iox_query/README.md links to `../docs/query_processing.md`, but `core/docs/query_processing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — core/iox_query/README.md:3

What to do

Reconcile the README with reality: core/catalog_cache/README.md links to `../docs/catalog_service.md`, but `core/docs/catalog_service.md` does not exist; core/iox_query/README.md links to `../docs/query_processing.md`, but `core/docs/query_processing.md` does not exist.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

Do you agree with this assessment?

P2 · Observability10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

Do you agree with this assessment?

P3 · Security & performance tooling6.0 / 10Adequate✓ Tool-verified

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.

What to do

Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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.

What to do

Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

PF1 · Benchmark discipline8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

Do you agree with this assessment?

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`.serve_connection(` (influxdb3_server/src/lib.rs:297)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (influxdb3_server/src/lib.rs:297).

What to do

Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Do you agree with this assessment?

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging5.3 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

`info!` at line 39 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/trace/src/lib.rs:39
`warn!` at line 905 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/service_grpc_flight/src/lib.rs:905
`warn!` at line 909 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/service_grpc_flight/src/lib.rs:909
`warn!` at line 666 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/schema/src/lib.rs:666
`warn!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_v1_query_api/src/handler.rs:158
`warn!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query_params/src/params.rs:520
`trace!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/statistics/aggregate_per_plan.rs:128
`trace!` at line 147 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/statistics/aggregate_per_plan.rs:147
`trace!` at line 210 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — core/iox_query/src/statistics/aggregate_per_plan.rs:210, core/iox_query/src/provider/progressive_eval.rs:210
`trace!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/provider/deduplicate.rs:190
`trace!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/provider/progressive_eval.rs:223
`trace!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/provider/progressive_eval.rs:331
`trace!` at line 373 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/provider/progressive_eval.rs:373
`trace!` at line 87 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:87
`trace!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:159
`trace!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:235
`trace!` at line 265 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:265
`trace!` at line 386 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/lexical_range.rs:386
`trace!` at line 113 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/physical_optimizer/sort/regroup_files.rs:113
`debug!` at line 607 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/exec/context.rs:607
`debug!` at line 427 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/exec/split.rs:427
`debug!` at line 450 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/iox_query/src/exec/split.rs:450
`error!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/batched_write.rs:158
`error!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/batched_write.rs:233
`error!` at line 256 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/batched_write.rs:256
`info!` at line 68 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/reloadable_token.rs:68
`info!` at line 82 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/reloadable_token.rs:82
`warn!` at line 86 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/influxdb_iox_client/src/client/reloadable_token.rs:86
`error!` at line 148 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — core/data_types/src/service_limits.rs:148

What to do

Interpolated log message defeats structured logging

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.

Lens	Score	Rating	Impact
Code Health	79%	Strong	Solid.
Architecture	96%	Exemplary	Solid.
Maturity	54%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	69%	Adequate	Acceptable, with room to improve.
Security	74%	Adequate — gated by D28, D29, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	100%	Exemplary	Strongest area.
Event Sourcing	100%	Exemplary	Solid.
Performance	91%	Exemplary	Solid.

Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 1 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

Not included — 52 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 — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> #syntax=docker/dockerfile:1.2 2 | ARG RUST_VERSION=1.92 3 | FROM rust:${RUST_VERSION}-slim-bookworm as build -------------------- ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1.2: failed to do request: Head "https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.2": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~25776 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (iox_query_influxql), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. 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 — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
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, and the automatic-re-run check to any GitHub-Actions workflow, 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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
X16 Unfloored truncation loop — 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
X18 Disposal-pattern 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 — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

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.

Critical — 57 finding(s)

D34 · Knowledge Freshness · Orphaned knowledge · ×16

Orphaned knowledge influxdb3_catalog/src/catalog/versions/v1.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge influxdb3_catalog/src/catalog/migrations/v3/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/serialize/versions/v1/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/log/versions/v4.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_processing_engine/src/scheduler/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_processing_engine/src/scheduler.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_authz/src/authorizer/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/log/versions/v3.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge influxdb3_processing_engine/src/worker/local.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/catalog/versions/v3/ops/node/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_authz/src/permissions.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/catalog/migrations/v3.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/format/records/node/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge influxdb3_catalog/src/catalog/versions/v2/enterprise/tests.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D35 · Change Coupling · Boundary-crossing change coupling · ×8

Boundary-crossing change coupling: snapshot_tracker.rs ↔ mod.rs influxdb3_wal/src/snapshot_tracker.rs:1 — `influxdb3_wal/src/snapshot_tracker.rs` (context influxdb3_wal) and `influxdb3_write/src/write_buffer/mod.rs` (context influxdb3_write) sit in DIFFERENT parts of the tree yet change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a67b50da` feat: add concurrency limit for WAL replay (#26483); `4eccc381` fix: reproducer for the empty snapshot file issue (#25835); `aa9213c4` feat: check mem and force snapshot (#25767) — run `git show` on any of them.
Boundary-crossing change coupling: serve.rs ↔ sender.rs influxdb3/src/commands/serve.rs:1 — `influxdb3/src/commands/serve.rs` (context influxdb3) and `influxdb3_telemetry/src/sender.rs` (context influxdb3_telemetry) sit in DIFFERENT parts of the tree yet change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4ab0d6e9` feat(port): port from ent to core (#26996); `1f076b69` feat: add trigger count to telemetry (#26426); `a3428261` feat: add `cluser_uuid`/`catalog_uuid` to telemetry (#26335) — run `git show` on any of them.
Boundary-crossing change coupling: lib.rs ↔ lib.rs influxdb3_query_executor/src/lib.rs:1 — `influxdb3_query_executor/src/lib.rs` (context influxdb3_query_executor) and `influxdb3_server/src/lib.rs` (context influxdb3_server) sit in DIFFERENT parts of the tree yet change together 65% of the time (60 of the 93 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 60 shared commits counted here, the most recent 3 are `6c275e8a` Revert "chore: use CompactedData to reduce PersistedFiles initializat…; `f7021ff6` feat: Add plugin file system table (#26875) (at that commit the file was still `influxdb3_server/src/query_executor/mod.rs`); `f9c8e0a9` fix(wal_replay): limit the number of wal files preloaded to num_cpus … (at that commit the file was still `influxdb3_server/src/query_executor/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: lib.rs ↔ mod.rs influxdb3_query_executor/src/lib.rs:1 — `influxdb3_query_executor/src/lib.rs` (context influxdb3_query_executor) and `influxdb3_write/src/write_buffer/mod.rs` (context influxdb3_write) sit in DIFFERENT parts of the tree yet change together 61% of the time (57 of the 93 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 57 shared commits counted here, the most recent 3 are `6c275e8a` Revert "chore: use CompactedData to reduce PersistedFiles initializat…; `95fda6c8` chore: clarify parquet file limit error message (#27019); `f9c8e0a9` fix(wal_replay): limit the number of wal files preloaded to num_cpus … (at that commit the file was still `influxdb3_server/src/query_executor/mod.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: serialize.rs ↔ http.rs influxdb3_catalog/src/serialize.rs:1 — `influxdb3_catalog/src/serialize.rs` (context influxdb3_catalog) and `influxdb3_server/src/http.rs` (context influxdb3_server) sit in DIFFERENT parts of the tree yet change together 59% of the time (16 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `d07d2f75` feat: Add retention period to cli commands (#26520); `d499c59b` chore: backport hard delete time in Catalog and deleter service from …; `c930d9ee` feat(processing_engine): error handling for triggers. (#26086) — run `git show` on any of them.
Boundary-crossing change coupling: create.rs ↔ manager.rs influxdb3/src/commands/create.rs:1 — `influxdb3/src/commands/create.rs` (context influxdb3) and `influxdb3_processing_engine/src/manager.rs` (context influxdb3_processing_engine) sit in DIFFERENT parts of the tree yet change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c930d9ee` feat(processing_engine): error handling for triggers. (#26086); `b0a24220` feat(processing_engine): Allow async plugin execution. (#25994); `9a542469` feat: Update trigger creation to validate plugin file present (#25918) — run `git show` on any of them.
Boundary-crossing change coupling: serve.rs ↔ snapshot_tracker.rs influxdb3/src/commands/serve.rs:1 — `influxdb3/src/commands/serve.rs` (context influxdb3) and `influxdb3_wal/src/snapshot_tracker.rs` (context influxdb3_wal) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a67b50da` feat: add concurrency limit for WAL replay (#26483); `b6cb6dd5` chore: back-port catalog debug log cleanup from enterprise (#26128); `aa9213c4` feat: check mem and force snapshot (#25767) — run `git show` on any of them.
Boundary-crossing change coupling: snapshot_tracker.rs ↔ queryable_buffer.rs influxdb3_wal/src/snapshot_tracker.rs:1 — `influxdb3_wal/src/snapshot_tracker.rs` (context influxdb3_wal) and `influxdb3_write/src/write_buffer/queryable_buffer.rs` (context influxdb3_write) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `4eccc381` fix: reproducer for the empty snapshot file issue (#25835); `aa9213c4` feat: check mem and force snapshot (#25767); `6e2e39cd` feat: snapshot when wal buffer is empty (#25765) — run `git show` on any of them.

D28 · Secrets (history) · High secret · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D30 · Dependency Vulnerabilities · High CVE · ×1

REDACTED

D31 · IaC & Container Security · Critical IaC · ×1

REDACTED

Serious — 797 finding(s)

D17 · Explicit Debt · TodoComment · ×109

TodoComment influxdb3_write/src/lib.rs:188 — // TODO: deprecate this alias — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_write/src/lib.rs:813 — // TODO: we may open this up more to other scalar types, e.g., other timestamp types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_write/src/write_buffer/persisted_files/tests.rs:76 — // TODO: Just tying in TODO within build_snapshot function below. Even though — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_write/src/write_buffer/persisted_files/tests.rs:222 — // TODO: Check why `add_parquet_file` method does not check if file is — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_wal/src/object_store.rs:536 — // TODO: Maybe need a separate issue to address any of those left — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_types/src/http.rs:117 — // TODO: this should eventually be made optional, so that if not provided, the columns used will — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_telemetry/src/store.rs:320 — // TODO: Maybe this should be float to hold less than 1 MB or — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_server/src/http.rs:1313 — // todo(pjb): We could also reject the request right now if the content-length is bigger than the max, but — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_server/src/http.rs:2696 — // TODO: Move logging to TraceLayer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_query_executor/src/lib.rs:285 — // TODO: see if this clone can be removed satisfying — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_query_executor/src/lib.rs:334 — // TODO: Enforce concurrency limit here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_py_api/src/logging.rs:304 — // todo(pjb): potential memory issue - unbounded log accumulation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_client/src/lib.rs:1333 — // TODO - for now the send method just returns the bytes from the response. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_client/src/tests.rs:131 — // TODO - could add content-type header but that may be too brittle — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/id.rs:1 — // TODO: move the catalog id code from id crate here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/object_store/versions/v1.rs:141 — // TODO: should we retry based on error type? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/object_store/versions/v2.rs:310 — // TODO: should we retry based on error type? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/object_store/versions/v3.rs:827 — // TODO(june): We should broadcast the snapshot load here, in a way that would allow the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/object_store/versions/v3/tests.rs:461 — // TODO(june): fast-forwarding should correctly remove hard-deleted records when it encounters a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/object_store/versions/v2/tests.rs:86 — // TODO: more test cases — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/log/versions/v4.rs:727 — // TODO: Update when InfluxFieldType supports Binary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:449 — // TODO: Update when InfluxFieldType supports Binary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/log/versions/v2/conversion.rs:107 — // todo: enterprise conversions should go in it's own module — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/catalog/versions/v1.rs:543 — // TODO(tjh): using default here will result in an empty config; some type state could — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment influxdb3_catalog/src/catalog/versions/v2.rs:1594 — // TODO(tjh): using default here will result in an empty config; some type state could — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
+ 84 more in this group — see findings.md.

D3 · God Classes · FileTooLong · ×43

FileTooLong: versions/v2.rs influxdb3_catalog/src/catalog/versions/v2.rs — FileTooLong — 3019 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 2519 over it, 6.04× the bar. 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: plan/planner.rs core/iox_query_influxql/src/plan/planner.rs — FileTooLong — 2750 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 2250 over it, 5.50× the bar. 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: v3/catalog.rs influxdb3_catalog/src/catalog/versions/v3/catalog.rs — FileTooLong — 2591 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: Catalog (10 blocks, 400-4067). The bar is 500 significant lines; this is 2091 over it, 5.18× the bar. 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: src/http.rs influxdb3_server/src/http.rs — FileTooLong — 2198 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1698 over it, 4.40× the bar. 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: versions/v1.rs influxdb3_catalog/src/catalog/versions/v1.rs — FileTooLong — 1641 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1141 over it, 3.28× the bar. 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: v2/update.rs influxdb3_catalog/src/catalog/versions/v2/update.rs — FileTooLong — 1446 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: Catalog (112-1440). The bar is 500 significant lines; this is 946 over it, 2.89× the bar. 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: src/lib.rs core/data_types/src/lib.rs — FileTooLong — 1297 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 797 over it, 2.59× the bar. 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/serve.rs influxdb3/src/commands/serve.rs — FileTooLong — 1253 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 753 over it, 2.51× the bar. 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: src/lib.rs influxdb3_client/src/lib.rs — FileTooLong — 1104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: Client (2 blocks, 128-1233). The bar is 500 significant lines; this is 604 over it, 2.21× the bar. 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: src/query_log.rs core/iox_query/src/query_log.rs — FileTooLong — 1052 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 552 over it, 2.10× the bar. 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: src/lib.rs core/service_grpc_flight/src/lib.rs — FileTooLong — 1017 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 517 over it, 2.03× the bar. 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: plan/rewriter.rs core/iox_query_influxql/src/plan/rewriter.rs — FileTooLong — 965 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 465 over it, 1.93× the bar. 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: src/lib.rs influxdb3_processing_engine/src/lib.rs — FileTooLong — 918 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 418 over it, 1.84× the bar. 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: versions/v4.rs influxdb3_catalog/src/log/versions/v4.rs — FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 390 over it, 1.78× the bar. 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: src/object_store.rs influxdb3_clap_blocks/src/object_store.rs — FileTooLong — 828 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 328 over it, 1.66× the bar. 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: write_buffer/table_buffer.rs influxdb3_write/src/write_buffer/table_buffer.rs — FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 276 over it, 1.55× the bar. 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: src/visit.rs core/influxdb_influxql_parser/src/visit.rs — FileTooLong — 775 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 275 over it, 1.55× the bar. 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: src/table_index_cache.rs influxdb3_write/src/table_index_cache.rs — FileTooLong — 758 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 80% of them inside a single declaration: TableIndexCache (2 blocks, 257-1349). The bar is 500 significant lines; this is 258 over it, 1.52× the bar. 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: v1/update.rs influxdb3_catalog/src/catalog/versions/v1/update.rs — FileTooLong — 748 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: Catalog (85-786). The bar is 500 significant lines; this is 248 over it, 1.50× the bar. 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: src/scheduler.rs influxdb3_processing_engine/src/scheduler.rs — FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. 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: v2/enterprise.rs influxdb3_catalog/src/catalog/versions/v2/enterprise.rs — FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 191 over it, 1.38× the bar. 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: src/object_store.rs influxdb3_wal/src/object_store.rs — FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: WalObjectStore (3 blocks, 37-697). The bar is 500 significant lines; this is 185 over it, 1.37× the bar. 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: src/visit_mut.rs core/influxdb_influxql_parser/src/visit_mut.rs — FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 179 over it, 1.36× the bar. 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: src/lib.rs core/influxdb_line_protocol/src/lib.rs — FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 37 free functions. The bar is 500 significant lines; this is 173 over it, 1.35× the bar. 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: last_cache/cache.rs influxdb3_cache/src/last_cache/cache.rs — FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 168 over it, 1.34× the bar. 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.
+ 18 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×33

Duplicated block (9 lines × 2) core/flightsql/src/planner.rs:444 — core/flightsql/src/planner.rs:444-452 | core/flightsql/src/planner.rs:500-508 — 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) core/influxdb_line_protocol/src/lib.rs:603 — core/influxdb_line_protocol/src/lib.rs:603-611 | core/influxdb_line_protocol/src/v3/mod.rs:166-174 — before extracting anything, compare `core/influxdb_line_protocol/src/lib.rs` and `core/influxdb_line_protocol/src/v3/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) core/iox_query/src/exec/sleep.rs:307 — core/iox_query/src/exec/sleep.rs:307-315 | core/iox_query/src/exec/sleep.rs:322-330 — 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) core/iox_query/src/logical_optimizer/influx_regex_to_datafusion_regex.rs:57 — core/iox_query/src/logical_optimizer/influx_regex_to_datafusion_regex.rs:57-65 | core/iox_query/src/logical_optimizer/regex_to_in_list.rs:82-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) core/iox_query_influxql/src/frontend/planner.rs:225 — core/iox_query_influxql/src/frontend/planner.rs:225-233 | influxdb3_query_executor/src/query_planner.rs:61-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.
Duplicated block (9 lines × 2) core/object_store_mem_cache/src/cache_system/s3_fifo_cache/mod.rs:79 — core/object_store_mem_cache/src/cache_system/s3_fifo_cache/mod.rs:79-87 | core/object_store_mem_cache/src/cache_system/s3_fifo_cache/mod.rs:131-139 — 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) influxdb3/src/lib.rs:206 — influxdb3/src/lib.rs:206-214 | influxdb3/src/lib.rs:288-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.
Duplicated block (9 lines × 2) influxdb3_cache/src/distinct_cache/table_function.rs:173 — influxdb3_cache/src/distinct_cache/table_function.rs:173-181 | influxdb3_cache/src/last_cache/table_function.rs:177-185 — `influxdb3_cache/src/distinct_cache/table_function.rs` and `influxdb3_cache/src/last_cache/table_function.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog.rs:320 — influxdb3_catalog/src/catalog.rs:320-328 | influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs:105-113 — before extracting anything, compare `influxdb3_catalog/src/catalog.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:614 — influxdb3_catalog/src/catalog/versions/v1.rs:614-622 | influxdb3_catalog/src/catalog/versions/v2.rs:1702-1710 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1984 — influxdb3_catalog/src/catalog/versions/v1.rs:1984-1992 | influxdb3_catalog/src/catalog/versions/v2.rs:4007-4015 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2305 — influxdb3_catalog/src/catalog/versions/v1.rs:2305-2313 | influxdb3_catalog/src/catalog/versions/v2.rs:4429-4437 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2407 — influxdb3_catalog/src/catalog/versions/v1.rs:2407-2415 | influxdb3_catalog/src/catalog/versions/v2.rs:4537-4545 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:310 — influxdb3_catalog/src/catalog/versions/v1/update.rs:310-318 | influxdb3_catalog/src/catalog/versions/v2/update.rs:474-482 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:1133 — influxdb3_catalog/src/catalog/versions/v2.rs:1133-1141 | influxdb3_catalog/src/catalog/versions/v2.rs:1157-1165 — 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) influxdb3_catalog/src/catalog/versions/v2.rs:3061 — influxdb3_catalog/src/catalog/versions/v2.rs:3061-3069 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:387-395 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:513 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:513-521 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1241-1249 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:539 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:539-547 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1266-1274 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) influxdb3_catalog/src/format/records/query_group.rs:71 — influxdb3_catalog/src/format/records/query_group.rs:71-79 | influxdb3_catalog/src/format/records/query_group.rs:127-135 — 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) influxdb3_shutdown/src/lib.rs:317 — influxdb3_shutdown/src/lib.rs:317-325 | influxdb3_shutdown/src/lib.rs:365-373 — 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) influxdb3_write/src/lib.rs:273 — influxdb3_write/src/lib.rs:273-281 | influxdb3_write/src/lib.rs:289-297 — 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) core/influxdb_line_protocol/src/lib.rs:318 — core/influxdb_line_protocol/src/lib.rs:318-326 | core/influxdb_line_protocol/src/v3/mod.rs:85-93 — before extracting anything, compare `core/influxdb_line_protocol/src/lib.rs` and `core/influxdb_line_protocol/src/v3/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) core/object_store_mock/src/lib.rs:554 — core/object_store_mock/src/lib.rs:554-562 | influxdb3_test_helpers/src/object_store/mock.rs:478-486 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) core/object_store_mock/src/lib.rs:568 — core/object_store_mock/src/lib.rs:568-576 | influxdb3_test_helpers/src/object_store/mock.rs:492-500 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) core/object_store_mock/src/lib.rs:622 — core/object_store_mock/src/lib.rs:622-630 | influxdb3_test_helpers/src/object_store/mock.rs:546-554 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 8 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×28

Duplicated block (8 lines × 2) core/influxdb_influxql_parser/src/visit.rs:623 — core/influxdb_influxql_parser/src/visit.rs:623-630 | core/influxdb_influxql_parser/src/visit_mut.rs:652-659 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) core/iox_query_influxql/src/plan/planner.rs:3581 — core/iox_query_influxql/src/plan/planner.rs:3581-3588 | core/iox_query_influxql/src/plan/planner.rs:3983-3990 — 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) core/iox_query_influxql/src/plan/planner.rs:3716 — core/iox_query_influxql/src/plan/planner.rs:3716-3723 | core/iox_query_influxql/src/plan/planner.rs:3809-3816 — 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) core/metric/src/duration.rs:149 — core/metric/src/duration.rs:149-156 | core/metric/src/histogram.rs:18-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) influxdb3/src/commands/serve.rs:1096 — influxdb3/src/commands/serve.rs:1096-1103 | influxdb3/src/commands/serve.rs:1125-1132 — 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) influxdb3_cache/src/distinct_cache/provider.rs:302 — influxdb3_cache/src/distinct_cache/provider.rs:302-309 | influxdb3_cache/src/last_cache/provider.rs:389-396 — `influxdb3_cache/src/distinct_cache/provider.rs` and `influxdb3_cache/src/last_cache/provider.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) influxdb3_cache/src/parquet_cache/mod.rs:472 — influxdb3_cache/src/parquet_cache/mod.rs:472-479 | influxdb3_cache/src/parquet_cache/mod.rs:486-493 — 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) influxdb3_catalog/src/catalog/versions/v1.rs:2069 — influxdb3_catalog/src/catalog/versions/v1.rs:2069-2076 | influxdb3_catalog/src/catalog/versions/v2.rs:4100-4107 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:268 — influxdb3_catalog/src/catalog/versions/v1/update.rs:268-275 | influxdb3_catalog/src/catalog/versions/v2/update.rs:423-430 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:401 — influxdb3_catalog/src/catalog/versions/v1/update.rs:401-408 | influxdb3_catalog/src/catalog/versions/v2/update.rs:578-585 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) influxdb3_catalog/src/log/versions/v2.rs:368 — influxdb3_catalog/src/log/versions/v2.rs:368-375 | influxdb3_catalog/src/log/versions/v3.rs:483-490 — before extracting anything, compare `influxdb3_catalog/src/log/versions/v2.rs` and `influxdb3_catalog/src/log/versions/v3.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_processing_engine/src/plugins.rs:316 — influxdb3_processing_engine/src/plugins.rs:316-323 | influxdb3_processing_engine/src/plugins.rs:386-393 — 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) influxdb3_processing_engine/src/worker/local.rs:454 — influxdb3_processing_engine/src/worker/local.rs:454-461 | influxdb3_processing_engine/src/worker/local.rs:493-500 — 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) influxdb3_server/src/lib.rs:426 — influxdb3_server/src/lib.rs:426-433 | influxdb3_server/src/lib.rs: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.
Duplicated block (8 lines × 2) influxdb3_system_tables_common/src/databases.rs:88 — influxdb3_system_tables_common/src/databases.rs:88-95 | influxdb3_system_tables_common/src/tables.rs:117-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) core/iox_query_influxql/src/frontend/planner.rs:89 — core/iox_query_influxql/src/frontend/planner.rs:89-96 | influxdb3_query_executor/src/query_planner.rs:87-94 — 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 (8 lines × 2) core/object_store_mem_cache/src/store.rs:331 — core/object_store_mem_cache/src/store.rs:331-338 | influxdb3_cache/src/parquet_cache/mod.rs:773-780 — 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 (8 lines × 2) core/object_store_mock/src/lib.rs:352 — core/object_store_mock/src/lib.rs:352-359 | influxdb3_test_helpers/src/object_store/mock.rs:290-297 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2384 — influxdb3_catalog/src/catalog/versions/v1.rs:2384-2391 | influxdb3_catalog/src/catalog/versions/v2.rs:4514-4521 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2393 — influxdb3_catalog/src/catalog/versions/v1.rs:2393-2400 | influxdb3_catalog/src/catalog/versions/v2.rs:4523-4530 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2436 — influxdb3_catalog/src/catalog/versions/v1.rs:2436-2443 | influxdb3_catalog/src/catalog/versions/v2.rs:4566-4573 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2445 — influxdb3_catalog/src/catalog/versions/v1.rs:2445-2452 | influxdb3_catalog/src/catalog/versions/v2.rs:4575-4582 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2535 — influxdb3_catalog/src/catalog/versions/v1.rs:2535-2542 | influxdb3_catalog/src/catalog/versions/v2.rs:4665-4672 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:1200 — influxdb3_catalog/src/catalog/versions/v2.rs:1200-1207 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1223-1230 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2402 — influxdb3_catalog/src/catalog/versions/v2.rs:2402-2409 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:182-189 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
+ 3 more in this group — see findings.md.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×25

Duplicated block (7 lines × 2) core/influxdb_influxql_parser/src/visit_mut.rs:761 — core/influxdb_influxql_parser/src/visit_mut.rs:761-767 | core/influxdb_influxql_parser/src/visit_mut.rs:1026-1032 — 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 (7 lines × 2) core/iox_query/src/sorts/run_optimized_merge/cache.rs:118 — core/iox_query/src/sorts/run_optimized_merge/cache.rs:118-124 | core/iox_query/src/sorts/run_optimized_merge/cache.rs:138-144 — 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 (7 lines × 2) core/iox_query/src/statistics/partition_statistics/project_schema.rs:80 — core/iox_query/src/statistics/partition_statistics/project_schema.rs:80-86 | core/iox_query/src/statistics/partition_statistics/project_schema.rs:165-171 — 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 (7 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2043 — influxdb3_catalog/src/catalog/versions/v1.rs:2043-2049 | influxdb3_catalog/src/catalog/versions/v2.rs:4068-4074 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2421 — influxdb3_catalog/src/catalog/versions/v2.rs:2421-2427 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:201-207 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2/update.rs:1286 — influxdb3_catalog/src/catalog/versions/v2/update.rs:1286-1296 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2109-2115 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2/update.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_server/src/http.rs:907 — influxdb3_server/src/http.rs:907-913 | influxdb3_server/src/http.rs:919-925 — 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 (7 lines × 2) core/iox_query_influxql/src/window/cumulative_sum.rs:51 — core/iox_query_influxql/src/window/cumulative_sum.rs:51-57 | core/query_functions/src/difference.rs:64-70 — 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 (7 lines × 2) core/iox_v1_query_api/src/response/buffered.rs:44 — core/iox_v1_query_api/src/response/buffered.rs:44-50 | core/iox_v1_query_api/src/response/chunked.rs:44-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog.rs:241 — influxdb3_catalog/src/catalog.rs:241-247 | influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs:30-36 — before extracting anything, compare `influxdb3_catalog/src/catalog.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:555 — influxdb3_catalog/src/catalog/versions/v1.rs:555-561 | influxdb3_catalog/src/catalog/versions/v2.rs:1606-1612 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:563 — influxdb3_catalog/src/catalog/versions/v1.rs:563-569 | influxdb3_catalog/src/catalog/versions/v2.rs:1614-1620 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3789 — influxdb3_catalog/src/catalog/versions/v2.rs:3789-3795 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:60-66 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3798 — influxdb3_catalog/src/catalog/versions/v2.rs:3798-3804 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:72-78 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3807 — influxdb3_catalog/src/catalog/versions/v2.rs:3807-3813 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:81-87 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3816 — influxdb3_catalog/src/catalog/versions/v2.rs:3816-3822 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:90-96 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:4703 — influxdb3_catalog/src/catalog/versions/v2.rs:4703-4709 | influxdb3_catalog/src/catalog/versions/v3/deletes.rs:36-42 — 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 (7 lines × 2) influxdb3_catalog/src/catalog/versions/v2/legacy.rs:263 — influxdb3_catalog/src/catalog/versions/v2/legacy.rs:263-269 | influxdb3_catalog/src/catalog/versions/v3/legacy.rs:244-250 — 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 (7 lines × 2) influxdb3_catalog/src/catalog/versions/v3/schema/storage.rs:28 — influxdb3_catalog/src/catalog/versions/v3/schema/storage.rs:28-34 | influxdb3_catalog/src/log/versions/v4.rs:90-96 — 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 (7 lines × 2) core/data_types/src/snapshot/namespace.rs:276 — core/data_types/src/snapshot/namespace.rs:276-282 | core/data_types/src/snapshot/root.rs:169-175 — before extracting anything, compare `core/data_types/src/snapshot/namespace.rs` and `core/data_types/src/snapshot/root.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) influxdb3_catalog/src/catalog/versions/v3/schema/storage.rs:78 — influxdb3_catalog/src/catalog/versions/v3/schema/storage.rs:78-84 | influxdb3_catalog/src/format/records/generation.rs:76-82 — 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 (7 lines × 2) influxdb3_catalog/src/format/records/types.rs:132 — influxdb3_catalog/src/format/records/types.rs:132-138 | influxdb3_catalog/src/log/versions/v4.rs:596-602 — 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 (7 lines × 2) influxdb3_catalog/src/log/versions/v4.rs:580 — influxdb3_catalog/src/log/versions/v4.rs:580-586 | influxdb3_catalog/src/snapshot/versions/v4.rs:188-194 — 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 (7 lines × 2) influxdb3_system_tables_common/src/distinct_caches.rs:83 — influxdb3_system_tables_common/src/distinct_caches.rs:83-89 | influxdb3_system_tables_common/src/last_caches.rs:104-110 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) core/influxdb_line_protocol/src/lib.rs:767 — core/influxdb_line_protocol/src/lib.rs:767-773 | core/influxdb_line_protocol/src/lib.rs:780-786 — 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.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×23

Duplicated block (10 lines × 2) core/influxdb_influxql_parser/src/common.rs:125 — core/influxdb_influxql_parser/src/common.rs:125-134 | core/influxdb_influxql_parser/src/expression/arithmetic.rs:507-516 — 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) core/iox_query_influxql/src/plan/planner.rs:1322 — core/iox_query_influxql/src/plan/planner.rs:1322-1331 | core/iox_query_influxql/src/plan/planner.rs:1339-1348 — 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) core/iox_query_influxql/src/plan/planner.rs:2035 — core/iox_query_influxql/src/plan/planner.rs:2035-2044 | core/iox_query_influxql/src/plan/planner.rs:2217-2226 — 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) core/iox_v1_query_api/src/response/buffered.rs:57 — core/iox_v1_query_api/src/response/buffered.rs:57-66 | core/iox_v1_query_api/src/response/chunked.rs:56-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:194 — influxdb3_catalog/src/catalog/versions/v1.rs:194-203 | influxdb3_catalog/src/catalog/versions/v2.rs:698-707 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:430 — influxdb3_catalog/src/catalog/versions/v1/update.rs:430-439 | influxdb3_catalog/src/catalog/versions/v2/update.rs:607-616 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2934 — influxdb3_catalog/src/catalog/versions/v2.rs:2934-2943 | influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:273-282 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/column.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v3/ops/node.rs:155 — influxdb3_catalog/src/catalog/versions/v3/ops/node.rs:155-164 | influxdb3_catalog/src/catalog/versions/v3/ops/node.rs:212-221 — 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) influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:254 — influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:254-263 | influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:360-369 — 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) influxdb3_catalog/src/log/versions/v2.rs:340 — influxdb3_catalog/src/log/versions/v2.rs:340-349 | influxdb3_catalog/src/log/versions/v3.rs:455-464 — before extracting anything, compare `influxdb3_catalog/src/log/versions/v2.rs` and `influxdb3_catalog/src/log/versions/v3.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/log/versions/v2.rs:354 — influxdb3_catalog/src/log/versions/v2.rs:354-363 | influxdb3_catalog/src/log/versions/v3.rs:469-478 — before extracting anything, compare `influxdb3_catalog/src/log/versions/v2.rs` and `influxdb3_catalog/src/log/versions/v3.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_server/src/lib.rs:273 — influxdb3_server/src/lib.rs:273-282 | influxdb3_server/src/lib.rs:440-450 — 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) influxdb3_write/src/table_index_cache.rs:572 — influxdb3_write/src/table_index_cache.rs:572-581 | influxdb3_write/src/table_index_cache.rs:999-1008 — 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) core/catalog_cache/src/local/limit.rs:82 — core/catalog_cache/src/local/limit.rs:82-91 | core/object_store_mem_cache/src/cache_system/hook/notify/mod.rs:23-32 — 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) core/iox_query_influxql/src/show_databases.rs:31 — core/iox_query_influxql/src/show_databases.rs:31-40 | core/iox_query_influxql/src/show_retention_policies.rs:24-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1957 — influxdb3_catalog/src/catalog/versions/v1.rs:1957-1966 | influxdb3_catalog/src/catalog/versions/v2.rs:3979-3988 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2473 — influxdb3_catalog/src/catalog/versions/v1.rs:2473-2482 | influxdb3_catalog/src/catalog/versions/v2.rs:4603-4612 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2524 — influxdb3_catalog/src/catalog/versions/v1.rs:2524-2533 | influxdb3_catalog/src/catalog/versions/v2.rs:4654-4663 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) influxdb3_catalog/src/catalog/versions/v2/update.rs:2112 — influxdb3_catalog/src/catalog/versions/v2/update.rs:2112-2121 | influxdb3_catalog/src/repository.rs:275-284 — 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) influxdb3_catalog/src/catalog/versions/v3/schema/node.rs:347 — influxdb3_catalog/src/catalog/versions/v3/schema/node.rs:347-356 | influxdb3_catalog/src/format/records/node.rs:412-421 — 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) influxdb3_write/src/table_index_cache.rs:1217 — influxdb3_write/src/table_index_cache.rs:1217-1226 | influxdb3_write/src/table_index_cache.rs:1316-1327 — 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) core/iox_query_influxql/src/aggregate/mode.rs:83 — core/iox_query_influxql/src/aggregate/mode.rs:83-93 | core/iox_query_influxql/src/aggregate/percentile.rs:66-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) influxdb3_query_executor/src/lib.rs:304 — influxdb3_query_executor/src/lib.rs:304-314 | influxdb3_query_executor/src/lib.rs:361-370 — 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.

D5 · Coupling · Off the main sequence · ×21

Off the main sequence: arrow_util — arrow_util: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: backoff — backoff: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: cli_types — cli_types: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: error_reporting — error_reporting: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: jemalloc_stats — jemalloc_stats: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: logfmt — logfmt: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: object_store_mock — object_store_mock: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: object_store_size_hinting — object_store_size_hinting: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: tower_trailer — tower_trailer: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: influxdb3_id — influxdb3_id: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
Off the main sequence: iox_query_params — iox_query_params: abstractness 0.00, instability 0.08, distance 0.92 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: schema — schema: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 23 project(s), so it's rigid to change.
Off the main sequence: metric — metric: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: influxdb-line-protocol — influxdb-line-protocol: abstractness 0.08, instability 0.10, distance 0.82 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: influxdb_influxql_parser — influxdb_influxql_parser: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: linear_buffer — linear_buffer: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: trace — trace: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: data_types — data_types: abstractness 0.03, instability 0.20, distance 0.77 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: query_functions — query_functions: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: influxdb3_shutdown — influxdb3_shutdown: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: iox_time — iox_time: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 23 project(s), so it's rigid to change.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×19

Duplicated block (11 lines × 2) core/metric_exporters/src/lib.rs:115 — core/metric_exporters/src/lib.rs:115-125 | core/metric_exporters/src/lib.rs:142-152 — 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) core/object_store_mock/src/lib.rs:76 — core/object_store_mock/src/lib.rs:76-86 | influxdb3_test_helpers/src/object_store/mock.rs:65-75 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2081 — influxdb3_catalog/src/catalog/versions/v1.rs:2081-2091 | influxdb3_catalog/src/catalog/versions/v2.rs:4113-4123 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:208 — influxdb3_catalog/src/catalog/versions/v1/update.rs:208-218 | influxdb3_catalog/src/catalog/versions/v2/update.rs:335-345 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:729 — influxdb3_catalog/src/catalog/versions/v1/update.rs:729-739 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1099-1109 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:461 — influxdb3_catalog/src/catalog/versions/v2.rs:461-471 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:166-176 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2428 — influxdb3_catalog/src/catalog/versions/v2.rs:2428-2438 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:208-218 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:595 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:595-605 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1664-1674 — 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) influxdb3_catalog/src/object_store/versions/v1.rs:152 — influxdb3_catalog/src/object_store/versions/v1.rs:152-162 | influxdb3_catalog/src/object_store/versions/v2.rs:321-331 — before extracting anything, compare `influxdb3_catalog/src/object_store/versions/v1.rs` and `influxdb3_catalog/src/object_store/versions/v2.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_server/src/http.rs:1997 — influxdb3_server/src/http.rs:1997-2007 | influxdb3_server/src/http.rs:2027-2037 — 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) influxdb3_system_tables_common/src/distinct_caches.rs:68 — influxdb3_system_tables_common/src/distinct_caches.rs:68-78 | influxdb3_system_tables_common/src/last_caches.rs:78-88 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) influxdb3_write/src/paths.rs:243 — influxdb3_write/src/paths.rs:243-253 | influxdb3_write/src/paths.rs:356-366 — 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) core/iox_query/src/provider/progressive_eval.rs:172 — core/iox_query/src/provider/progressive_eval.rs:172-182 | core/iox_query/src/provider/reorder_partitions.rs:129-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) core/iox_query_influxql/src/window/cumulative_sum.rs:18 — core/iox_query_influxql/src/window/cumulative_sum.rs:18-28 | core/query_functions/src/difference.rs:38-48 — 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) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:77 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:77-87 | influxdb3_catalog/src/catalog/versions/v3/usage.rs:134-144 — 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) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:89 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:89-99 | influxdb3_catalog/src/catalog/versions/v3/usage.rs:146-156 — 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) core/iox_query_influxql/src/plan/planner.rs:1371 — core/iox_query_influxql/src/plan/planner.rs:1371-1384 | core/iox_query_influxql/src/plan/planner.rs:1422-1432 — 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) core/iox_query_influxql/src/show_retention_policies.rs:172 — core/iox_query_influxql/src/show_retention_policies.rs:172-183 | core/iox_query_influxql/src/show_retention_policies.rs:187-197 — 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) core/influxdb_influxql_parser/src/string.rs:71 — core/influxdb_influxql_parser/src/string.rs:71-81 | core/influxdb_influxql_parser/src/string.rs:90-100 — 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.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×19

Duplicated block (6 lines × 2) core/iox_query/src/query_log.rs:1157 — core/iox_query/src/query_log.rs:1157-1162 | core/iox_query/src/query_log.rs:1212-1217 — 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 (6 lines × 2) core/iox_query_influxql/src/show_databases.rs:90 — core/iox_query_influxql/src/show_databases.rs:90-95 | influxdb3_internal_api/src/query_executor.rs:129-134 — 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 (6 lines × 2) core/service_grpc_flight/src/lib.rs:1190 — core/service_grpc_flight/src/lib.rs:1190-1195 | core/service_grpc_flight/src/lib.rs:1259-1264 — 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 (6 lines × 2) influxdb3_cache/src/distinct_cache/cache.rs:519 — influxdb3_cache/src/distinct_cache/cache.rs:519-524 | influxdb3_cache/src/last_cache/cache.rs:503-508 — 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 (6 lines × 2) influxdb3_cache/src/last_cache/cache.rs:1079 — influxdb3_cache/src/last_cache/cache.rs:1079-1084 | influxdb3_cache/src/last_cache/cache.rs:1096-1101 — 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 (6 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:423 — influxdb3_catalog/src/catalog/versions/v1/update.rs:423-428 | influxdb3_catalog/src/catalog/versions/v2/update.rs:600-605 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:481 — influxdb3_catalog/src/catalog/versions/v1/update.rs:481-486 | influxdb3_catalog/src/catalog/versions/v2/update.rs:658-663 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:566 — influxdb3_catalog/src/catalog/versions/v1/update.rs:566-571 | influxdb3_catalog/src/catalog/versions/v2/update.rs:904-909 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:687 — influxdb3_catalog/src/catalog/versions/v1/update.rs:687-692 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1057-1062 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) influxdb3_catalog/src/catalog/versions/v3/ops/database.rs:164 — influxdb3_catalog/src/catalog/versions/v3/ops/database.rs:164-169 | influxdb3_catalog/src/catalog/versions/v3/ops/table.rs:100-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) influxdb3_catalog/src/format/records/cache.rs:56 — influxdb3_catalog/src/format/records/cache.rs:56-61 | influxdb3_catalog/src/format/records/cache.rs:109-114 — 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 (6 lines × 2) influxdb3_clap_blocks/src/object_store.rs:249 — influxdb3_clap_blocks/src/object_store.rs:249-254 | influxdb3_clap_blocks/src/object_store.rs:283-288 — 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 (6 lines × 2) influxdb3_clap_blocks/src/object_store.rs:255 — influxdb3_clap_blocks/src/object_store.rs:255-260 | influxdb3_clap_blocks/src/object_store.rs:289-294 — 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 (6 lines × 2) influxdb3_shutdown/src/lib.rs:76 — influxdb3_shutdown/src/lib.rs:76-81 | influxdb3_shutdown/src/lib.rs:91-96 — 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 (6 lines × 2) influxdb3_cache/src/distinct_cache/cache.rs:544 — influxdb3_cache/src/distinct_cache/cache.rs:544-549 | influxdb3_cache/src/last_cache/cache.rs:520-525 — 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 (6 lines × 2) core/data_types/src/snapshot/namespace.rs:174 — core/data_types/src/snapshot/namespace.rs:174-179 | core/data_types/src/snapshot/root.rs:99-104 — before extracting anything, compare `core/data_types/src/snapshot/namespace.rs` and `core/data_types/src/snapshot/root.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) core/iox_query_influxql/src/plan/planner/select.rs:278 — core/iox_query_influxql/src/plan/planner/select.rs:278-283 | core/iox_query_influxql/src/plan/planner/select.rs:367-372 — 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 (6 lines × 2) influxdb3_write/src/paths.rs:406 — influxdb3_write/src/paths.rs:406-411 | influxdb3_write/src/paths.rs:514-519 — 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 (6 lines × 2) influxdb3_catalog/src/log/versions/v3.rs:91 — influxdb3_catalog/src/log/versions/v3.rs:91-96 | influxdb3_catalog/src/log/versions/v4.rs:171-176 — before extracting anything, compare `influxdb3_catalog/src/log/versions/v3.rs` and `influxdb3_catalog/src/log/versions/v4.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×15

Duplicated block (13 lines × 2) core/influxdb_influxql_parser/src/expression/conditional.rs:281 — core/influxdb_influxql_parser/src/expression/conditional.rs:281-293 | core/influxdb_influxql_parser/src/lib.rs:73-85 — 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 (13 lines × 2) influxdb3/src/commands/create/token.rs:61 — influxdb3/src/commands/create/token.rs:61-73 | influxdb3/src/commands/create/token.rs:135-147 — 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 (13 lines × 2) influxdb3/src/commands/show.rs:159 — influxdb3/src/commands/show.rs:159-171 | influxdb3/src/commands/show.rs:181-193 — 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 (13 lines × 2) influxdb3_cache/src/distinct_cache/table_function.rs:361 — influxdb3_cache/src/distinct_cache/table_function.rs:361-373 | influxdb3_cache/src/last_cache/table_function.rs:412-424 — `influxdb3_cache/src/distinct_cache/table_function.rs` and `influxdb3_cache/src/last_cache/table_function.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:623 — influxdb3_catalog/src/catalog/versions/v1.rs:623-635 | influxdb3_catalog/src/catalog/versions/v2.rs:1713-1725 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2418 — influxdb3_catalog/src/catalog/versions/v1.rs:2418-2430 | influxdb3_catalog/src/catalog/versions/v2.rs:4548-4560 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2459 — influxdb3_catalog/src/catalog/versions/v1.rs:2459-2471 | influxdb3_catalog/src/catalog/versions/v2.rs:4589-4601 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:224 — influxdb3_catalog/src/catalog/versions/v1/update.rs:224-236 | influxdb3_catalog/src/catalog/versions/v2/update.rs:351-363 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:661 — influxdb3_catalog/src/catalog/versions/v1/update.rs:661-673 | influxdb3_catalog/src/catalog/versions/v2/update.rs:999-1011 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) influxdb3_write/src/lib.rs:254 — influxdb3_write/src/lib.rs:254-266 | influxdb3_write/src/lib.rs:595-607 — 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 (13 lines × 2) core/object_store_mock/src/lib.rs:377 — core/object_store_mock/src/lib.rs:377-389 | influxdb3_test_helpers/src/object_store/mock.rs:315-327 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:846 — influxdb3_catalog/src/catalog/versions/v1.rs:846-858 | influxdb3_catalog/src/catalog/versions/v2.rs:2035-2047 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2246 — influxdb3_catalog/src/catalog/versions/v1.rs:2246-2258 | influxdb3_catalog/src/catalog/versions/v2.rs:4370-4382 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:441 — influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:441-453 | influxdb3_catalog/src/log/versions/v4.rs:719-731 — 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 (13 lines × 2) .circleci/packages/sandbox_verify.py:637 — .circleci/packages/sandbox_verify.py:637-649 | .circleci/packages/sandbox_verify.py:658-670 — 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.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×15

Duplicated block (12 lines × 2) core/data_types/src/snapshot/namespace.rs:96 — core/data_types/src/snapshot/namespace.rs:96-107 | core/data_types/src/snapshot/root.rs:67-78 — before extracting anything, compare `core/data_types/src/snapshot/namespace.rs` and `core/data_types/src/snapshot/root.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/influxdb_influxql_parser/src/expression/conditional.rs:266 — core/influxdb_influxql_parser/src/expression/conditional.rs:266-277 | core/influxdb_influxql_parser/src/select.rs:554-565 — 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 (12 lines × 2) core/influxdb_line_protocol/src/lib.rs:682 — core/influxdb_line_protocol/src/lib.rs:682-693 | core/influxdb_line_protocol/src/v3/mod.rs:177-188 — before extracting anything, compare `core/influxdb_line_protocol/src/lib.rs` and `core/influxdb_line_protocol/src/v3/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) core/iox_query/src/query_log.rs:610 — core/iox_query/src/query_log.rs:610-621 | core/iox_query/src/query_log.rs:646-657 — 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 (12 lines × 2) core/iox_query_influxql/src/plan/planner.rs:3703 — core/iox_query_influxql/src/plan/planner.rs:3703-3714 | core/iox_query_influxql/src/plan/planner.rs:4053-4064 — 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 (12 lines × 2) core/object_store_mem_cache/src/cache_system/s3_fifo_cache/s3_fifo.rs:879 — core/object_store_mem_cache/src/cache_system/s3_fifo_cache/s3_fifo.rs:879-890 | core/object_store_mem_cache/src/cache_system/s3_fifo_cache/s3_fifo.rs:947-958 — 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 (12 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:464 — influxdb3_catalog/src/catalog/versions/v1.rs:464-475 | influxdb3_catalog/src/catalog/versions/v2.rs:1512-1523 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2233 — influxdb3_catalog/src/catalog/versions/v1.rs:2233-2244 | influxdb3_catalog/src/catalog/versions/v2.rs:4357-4368 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) influxdb3_catalog/src/catalog/versions/v2/legacy.rs:33 — influxdb3_catalog/src/catalog/versions/v2/legacy.rs:33-44 | influxdb3_catalog/src/catalog/versions/v3/legacy.rs:25-36 — 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 (12 lines × 2) influxdb3_catalog/src/enterprise/format/records/token.rs:51 — influxdb3_catalog/src/enterprise/format/records/token.rs:51-62 | influxdb3_catalog/src/format/records/token.rs:40-51 — 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 (12 lines × 2) influxdb3_server/src/http.rs:2478 — influxdb3_server/src/http.rs:2478-2489 | influxdb3_server/src/http.rs:2546-2557 — 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 (12 lines × 2) core/data_types/src/lib.rs:590 — core/data_types/src/lib.rs:590-601 | core/generated_types/src/lib.rs:392-403 — 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 (12 lines × 2) core/generated_types/src/google.rs:139 — core/generated_types/src/google.rs:139-150 | core/ingester_query_grpc/src/lib.rs:59-70 — 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 (12 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3165 — influxdb3_catalog/src/catalog/versions/v2.rs:3165-3176 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:98-109 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) influxdb3_cache/src/distinct_cache/provider.rs:340 — influxdb3_cache/src/distinct_cache/provider.rs:340-351 | influxdb3_cache/src/last_cache/provider.rs:427-438 — `influxdb3_cache/src/distinct_cache/provider.rs` and `influxdb3_cache/src/last_cache/provider.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D3 · God Classes · MethodTooLong · ×14

MethodTooLong: Error.into_response influxdb3_server/src/http.rs:728 — MethodTooLong — into_response runs 274 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryableBuffer.buffer_wal_contents_and_persist_snapshotted_data influxdb3_write/src/write_buffer/queryable_buffer.rs:225 — MethodTooLong — buffer_wal_contents_and_persist_snapshotted_data runs 170 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: V1HttpHandler.execute_query core/iox_v1_query_api/src/handler.rs:204 — MethodTooLong — execute_query runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DateBinWallclockUDF.invoke_with_args core/query_functions/src/date_bin_wallclock.rs:190 — MethodTooLong — invoke_with_args runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TokioInstrumentDispatcher.report core/tokio_metrics_bridge/src/bridge.rs:99 — MethodTooLong — report runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TableIndexCache.split_persisted_snapshots_to_table_index_snapshots influxdb3_write/src/table_index_cache.rs:334 — MethodTooLong — split_persisted_snapshots_to_table_index_snapshots runs 122 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FlightSQLCommand.fmt core/flightsql/src/cmd.rs:217 — MethodTooLong — fmt runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MutableTableChunk.append_row influxdb3_write/src/write_buffer/table_buffer.rs:592 — MethodTooLong — append_row runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: QueryLogEntry.emit_log core/iox_query/src/query_log.rs:539 — MethodTooLong — emit_log runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Metrics.new core/iox_query/src/query_log.rs:1542 — MethodTooLong — new runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FlightSQLPlanner.do_get_logical_plan core/flightsql/src/planner.rs:106 — MethodTooLong — do_get_logical_plan runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CreateDistinctCacheOp.prepare influxdb3_catalog/src/catalog/versions/v3/ops/cache.rs:82 — MethodTooLong — prepare runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TableIndexCache.update_all_from_object_store influxdb3_write/src/table_index_cache.rs:1169 — MethodTooLong — update_all_from_object_store runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CoreTableIndex.update_from_object_store influxdb3_write/src/table_index.rs:354 — MethodTooLong — update_from_object_store runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×14

Duplicated block (14 lines × 2) core/influxdb_influxql_parser/src/show_measurements.rs:109 — core/influxdb_influxql_parser/src/show_measurements.rs:109-122 | core/influxdb_influxql_parser/src/show_tag_values.rs:63-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) core/influxdb_influxql_parser/src/visit_mut.rs:983 — core/influxdb_influxql_parser/src/visit_mut.rs:983-996 | core/influxdb_influxql_parser/src/visit_mut.rs:1045-1058 — 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 (14 lines × 2) core/influxdb_line_protocol/src/lib.rs:581 — core/influxdb_line_protocol/src/lib.rs:581-594 | core/influxdb_line_protocol/src/v3/mod.rs:144-157 — before extracting anything, compare `core/influxdb_line_protocol/src/lib.rs` and `core/influxdb_line_protocol/src/v3/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) core/iox_query_influxql/src/plan/rewriter.rs:1482 — core/iox_query_influxql/src/plan/rewriter.rs:1482-1495 | core/iox_query_influxql/src/plan/rewriter.rs:1502-1515 — 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 (14 lines × 2) core/object_store_mock/src/lib.rs:690 — core/object_store_mock/src/lib.rs:690-703 | influxdb3_test_helpers/src/object_store/mock.rs:637-650 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:577 — influxdb3_catalog/src/catalog/versions/v1.rs:577-590 | influxdb3_catalog/src/catalog/versions/v2.rs:1653-1666 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:129 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:129-142 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:708-721 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:248 — influxdb3_catalog/src/catalog/versions/v1/update.rs:248-261 | influxdb3_catalog/src/catalog/versions/v2/update.rs:402-415 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:1256 — influxdb3_catalog/src/catalog/versions/v2.rs:1256-1269 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:3913-3926 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3477 — influxdb3_catalog/src/catalog/versions/v2.rs:3477-3490 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:312-325 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:4716 — influxdb3_catalog/src/catalog/versions/v2.rs:4716-4729 | influxdb3_catalog/src/catalog/versions/v3/deletes.rs:49-62 — 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 (14 lines × 2) influxdb3_client/src/lib.rs:628 — influxdb3_client/src/lib.rs:628-641 | influxdb3_client/src/lib.rs:662-675 — 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 (14 lines × 2) influxdb3_client/src/lib.rs:1159 — influxdb3_client/src/lib.rs:1159-1172 | influxdb3_client/src/lib.rs:1206-1219 — 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 (14 lines × 2) core/influxdb_influxql_parser/src/expression/conditional.rs:297 — core/influxdb_influxql_parser/src/expression/conditional.rs:297-310 | core/influxdb_influxql_parser/src/select.rs:585-598 — 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.

D3 · God Classes · FunctionTooLong · ×13

FunctionTooLong: influxdb3::commands::serve::command influxdb3/src/commands/serve.rs:952 — FunctionTooLong — influxdb3::commands::serve::command runs 462 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 362 over it, 4.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3::commands::create::command influxdb3/src/commands/create.rs:330 — FunctionTooLong — influxdb3::commands::create::command runs 211 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3_server::http::perform_routing influxdb3_server/src/http.rs:2742 — FunctionTooLong — influxdb3_server::http::perform_routing runs 137 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3_server::http::record_batch_stream_to_body influxdb3_server/src/http.rs:2440 — FunctionTooLong — influxdb3_server::http::record_batch_stream_to_body runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iox_query_influxql::plan::planner_rewrite_expression::rewrite_binary_expr core/iox_query_influxql/src/plan/planner_rewrite_expression.rs:274 — FunctionTooLong — iox_query_influxql::plan::planner_rewrite_expression::rewrite_binary_expr runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3_server::serve influxdb3_server/src/lib.rs:366 — FunctionTooLong — influxdb3_server::serve runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iox_query::physical_optimizer::projection_pushdown::optimize_plan core/iox_query/src/physical_optimizer/projection_pushdown.rs:53 — FunctionTooLong — iox_query::physical_optimizer::projection_pushdown::optimize_plan runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3::maybe_print_help influxdb3/src/lib.rs:630 — FunctionTooLong — influxdb3::maybe_print_help runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: iox_query::provider::physical::chunks_to_physical_nodes core/iox_query/src/provider/physical.rs:150 — FunctionTooLong — iox_query::provider::physical::chunks_to_physical_nodes runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line influxdb3_write/src/write_buffer/validator.rs:188 — FunctionTooLong — influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb3::commands::update::command influxdb3/src/commands/update.rs:93 — FunctionTooLong — influxdb3::commands::update::command runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: mutable_batch_pb::decode::write_table_batch core/mutable_batch_pb/src/decode.rs:80 — FunctionTooLong — mutable_batch_pb::decode::write_table_batch runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: influxdb_influxql_parser::time_range::split_cond core/influxdb_influxql_parser/src/time_range.rs:178 — FunctionTooLong — influxdb_influxql_parser::time_range::split_cond runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D2 · Cognitive Complexity · iox_query · ×12

iox_query::query_log::collect_ingester_metrics (cognitive 27) core/iox_query/src/query_log.rs:1374 — iox_query::query_log::collect_ingester_metrics has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query::exec::series_limit::plan_series_limit (cognitive 22) core/iox_query/src/exec/series_limit/mod.rs:49 — iox_query::exec::series_limit::plan_series_limit has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query::exec::query_tracing::send_metrics_to_tracing (cognitive 21) core/iox_query/src/exec/query_tracing.rs:112 — iox_query::exec::query_tracing::send_metrics_to_tracing has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (6 pts), boolean chains 3, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query::physical_optimizer::sort::extract_ranges::extract_ranges_from_plan (cognitive 21) core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:83 — iox_query::physical_optimizer::sort::extract_ranges::extract_ranges_from_plan has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query::provider::physical::chunks_to_physical_nodes (cognitive 20) core/iox_query/src/provider/physical.rs:150 — iox_query::provider::physical::chunks_to_physical_nodes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 3 (8 pts), loops 2 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
iox_query::chunk_statistics::create_chunk_statistics (cognitive 19) core/iox_query/src/chunk_statistics.rs:120 — iox_query::chunk_statistics::create_chunk_statistics has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 4 (8 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
iox_query::statistics::partition_statistics::statistics_by_partition (cognitive 19) core/iox_query/src/statistics/partition_statistics/mod.rs:338 — iox_query::statistics::partition_statistics::statistics_by_partition has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
iox_query::physical_optimizer::projection_pushdown::optimize_plan (cognitive 18) core/iox_query/src/physical_optimizer/projection_pushdown.rs:53 — iox_query::physical_optimizer::projection_pushdown::optimize_plan has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
iox_query::exec::sleep::array_to_duration (cognitive 17) core/iox_query/src/exec/sleep.rs:277 — iox_query::exec::sleep::array_to_duration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
iox_query::logical_optimizer::regex_to_in_list::enumerate_hir (cognitive 17) core/iox_query/src/logical_optimizer/regex_to_in_list.rs:382 — iox_query::logical_optimizer::regex_to_in_list::enumerate_hir has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 4 (8 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
iox_query::exec::query_tracing::get_timestamps (cognitive 16) core/iox_query/src/exec/query_tracing.rs:294 — iox_query::exec::query_tracing::get_timestamps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query::statistics::partition_statistics::project_schema::proj_exec_stats (cognitive 16) core/iox_query/src/statistics/partition_statistics/project_schema.rs:232 — iox_query::statistics::partition_statistics::project_schema::proj_exec_stats has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×11

Members sharing a duplicated core (4 members, 50+ identical tokens) core/influxdb_influxql_parser/src/show_field_keys.rs:35 — core/influxdb_influxql_parser/src/show_field_keys.rs:35-55 | core/influxdb_influxql_parser/src/show_measurements.rs:98-122 | core/influxdb_influxql_parser/src/show_tag_keys.rs:40-64 | core/influxdb_influxql_parser/src/show_tag_values.rs:50-76 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/iox_query_influxql/src/plan/planner.rs:3574 — core/iox_query_influxql/src/plan/planner.rs:3574-3747 | core/iox_query_influxql/src/plan/planner.rs:3752-3837 | core/iox_query_influxql/src/plan/planner.rs:3842-3969 | core/iox_query_influxql/src/plan/planner.rs:3974-4085 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/iox_query_influxql/src/show_databases.rs:82 — core/iox_query_influxql/src/show_databases.rs:82-97 | core/iox_query_influxql/src/show_retention_policies.rs:157-225 | influxdb3_internal_api/src/query_executor.rs:121-140 | influxdb3_internal_api/src/query_executor.rs:186-211 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v1.rs:355 — influxdb3_catalog/src/catalog/versions/v1.rs:355-401 | influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:32-124 | influxdb3_catalog/src/catalog/versions/v2.rs:1030-1076 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:380-472 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v1.rs:706 — influxdb3_catalog/src/catalog/versions/v1.rs:706-773 | influxdb3_catalog/src/catalog/versions/v1.rs:775-844 | influxdb3_catalog/src/catalog/versions/v2.rs:1843-1912 | influxdb3_catalog/src/catalog/versions/v2.rs:1914-2033 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v1.rs:1279 — influxdb3_catalog/src/catalog/versions/v1.rs:1279-1300 | influxdb3_catalog/src/catalog/versions/v1.rs:1307-1328 | influxdb3_catalog/src/catalog/versions/v2.rs:2745-2766 | influxdb3_catalog/src/catalog/versions/v2.rs:2773-2794 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v1/update.rs:480 — influxdb3_catalog/src/catalog/versions/v1/update.rs:480-554 | influxdb3_catalog/src/catalog/versions/v1/update.rs:565-673 | influxdb3_catalog/src/catalog/versions/v2/update.rs:657-734 | influxdb3_catalog/src/catalog/versions/v2/update.rs:903-1011 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v2.rs:1132 — influxdb3_catalog/src/catalog/versions/v2.rs:1132-1149 | influxdb3_catalog/src/catalog/versions/v2.rs:1156-1173 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1604-1621 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1625-1642 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v2.rs:2446 — influxdb3_catalog/src/catalog/versions/v2.rs:2446-2464 | influxdb3_catalog/src/catalog/versions/v2.rs:2473-2492 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:232-250 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:257-276 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:333 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:333-349 | influxdb3_catalog/src/log/versions/v2.rs:856-872 | influxdb3_catalog/src/log/versions/v3.rs:988-1004 | influxdb3_catalog/src/log/versions/v4.rs:1346-1362 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/iox_query/src/test.rs:900 — core/iox_query/src/test.rs:900-950 | core/iox_query/src/test.rs:963-1012 | core/iox_query/src/test.rs:1026-1082 | core/iox_query/src/test.rs:1101-1160 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×11

Duplicated block (16 lines × 2) core/iox_query_influxql/src/plan/planner.rs:2870 — core/iox_query_influxql/src/plan/planner.rs:2870-2885 | core/iox_query_influxql/src/plan/planner.rs:2925-2940 — 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 (16 lines × 2) core/iox_query_influxql/src/plan/planner.rs:3193 — core/iox_query_influxql/src/plan/planner.rs:3193-3208 | core/iox_query_influxql/src/plan/planner.rs:3272-3287 — 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 (16 lines × 2) influxdb3/src/lib.rs:683 — influxdb3/src/lib.rs:683-698 | influxdb3/src/lib.rs:735-750 — 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 (16 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:275 — influxdb3_catalog/src/catalog/versions/v1.rs:275-290 | influxdb3_catalog/src/catalog/versions/v2.rs:950-965 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:758 — influxdb3_catalog/src/catalog/versions/v1.rs:758-773 | influxdb3_catalog/src/catalog/versions/v2.rs:1897-1912 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:1134 — influxdb3_catalog/src/catalog/versions/v2.rs:1134-1149 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1606-1621 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:1158 — influxdb3_catalog/src/catalog/versions/v2.rs:1158-1173 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1627-1642 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3248 — influxdb3_catalog/src/catalog/versions/v2.rs:3248-3263 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:178-193 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:277 — influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:277-292 | influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:301-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.
Duplicated block (16 lines × 2) influxdb3_server/src/http.rs:1965 — influxdb3_server/src/http.rs:1965-1980 | influxdb3_server/src/http.rs:2043-2058 — 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 (16 lines × 2) core/iox_query/src/test.rs:833 — core/iox_query/src/test.rs:833-848 | core/iox_query/src/test.rs:873-888 — 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.

D3 · God Classes · ClassTooLong · ×10

ClassTooLong: Catalog influxdb3_catalog/src/catalog/versions/v3/catalog.rs:400 — ClassTooLong — 2317 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 165 methods, 10 blocks, lines 400-4067. The bar is 400 significant lines; this is 1917 over it, 5.79× the bar. 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.
ClassTooLong: HttpApi influxdb3_server/src/http.rs:1040 — ClassTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 48 methods, 3 blocks, lines 1040-2245. The bar is 400 significant lines; this is 472 over it, 2.18× the bar. 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.
ClassTooLong: Client influxdb3_client/src/lib.rs:128 — ClassTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 47 methods, 2 blocks, lines 128-1233. The bar is 400 significant lines; this is 326 over it, 1.82× the bar. 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.
ClassTooLong: Catalog influxdb3_catalog/src/catalog/versions/v2.rs:268 — ClassTooLong — 678 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 117 methods, 6 blocks, lines 268-1497. The bar is 400 significant lines; this is 278 over it, 1.70× the bar. 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.
ClassTooLong: TableIndexCache influxdb3_write/src/table_index_cache.rs:257 — ClassTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 257-1349. The bar is 400 significant lines; this is 205 over it, 1.51× the bar. 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.
ClassTooLong: Persister influxdb3_write/src/persister.rs:128 — ClassTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 2 blocks, lines 128-1017. The bar is 400 significant lines; this is 107 over it, 1.27× the bar. 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.
ClassTooLong: ProcessingEngineManagerImpl influxdb3_processing_engine/src/lib.rs:114 — ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 3 blocks, lines 114-1274. The bar is 400 significant lines; this is 100 over it, 1.25× the bar. 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.
ClassTooLong: Writer core/mutable_batch/src/writer.rs:45 — ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 4 blocks, lines 45-977. The bar is 400 significant lines; this is 62 over it, 1.16× the bar. 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.
ClassTooLong: WalObjectStore influxdb3_wal/src/object_store.rs:37 — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 8 methods, 3 blocks, lines 37-697. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. 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.
ClassTooLong: WriteBufferImpl influxdb3_write/src/write_buffer/mod.rs:170 — ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 7 blocks, lines 170-872. The bar is 400 significant lines; this is 5 over it, 1.01× the bar. 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.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×10

Duplicated block (5 lines × 2) core/iox_query/src/exec/gapfill/algo.rs:415 — core/iox_query/src/exec/gapfill/algo.rs:415-420 | core/iox_query/src/exec/gapfill/algo.rs:769-773 — 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 (5 lines × 2) core/iox_query_influxql/src/show_databases.rs:93 — core/iox_query_influxql/src/show_databases.rs:93-97 | core/iox_query_influxql/src/show_retention_policies.rs:221-225 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) influxdb3_cache/src/distinct_cache/table_function.rs:126 — influxdb3_cache/src/distinct_cache/table_function.rs:126-130 | influxdb3_cache/src/last_cache/table_function.rs:125-129 — `influxdb3_cache/src/distinct_cache/table_function.rs` and `influxdb3_cache/src/last_cache/table_function.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2111 — influxdb3_catalog/src/catalog/versions/v1.rs:2111-2115 | influxdb3_catalog/src/catalog/versions/v2.rs:4145-4149 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) influxdb3_catalog/src/catalog/versions/v2/update.rs:743 — influxdb3_catalog/src/catalog/versions/v2/update.rs:743-747 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1020-1024 — 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 (5 lines × 2) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2173 — influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2173-2177 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2247-2251 — 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 (5 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:431 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:431-435 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:1003-1007 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3526 — influxdb3_catalog/src/catalog/versions/v2.rs:3526-3530 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:384-388 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:373 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:373-377 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:945-949 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) influxdb3_commands/src/test.rs:115 — influxdb3_commands/src/test.rs:115-119 | influxdb3_commands/src/test.rs:148-152 — 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.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×9

Duplicated block (18 lines × 2) influxdb3_catalog/src/catalog.rs:264 — influxdb3_catalog/src/catalog.rs:264-281 | influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs:56-73 — before extracting anything, compare `influxdb3_catalog/src/catalog.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/tokens.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:229 — influxdb3_catalog/src/catalog/versions/v1.rs:229-246 | influxdb3_catalog/src/catalog/versions/v2.rs:755-772 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:347 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:347-364 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:919-936 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:403 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:403-420 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:975-992 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18 lines × 2) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:515 — influxdb3_catalog/src/catalog/versions/v3/catalog.rs:515-532 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:938-955 — 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 (18 lines × 2) influxdb3_catalog/src/object_store/versions/v2.rs:157 — influxdb3_catalog/src/object_store/versions/v2.rs:157-174 | influxdb3_catalog/src/object_store/versions/v3.rs:459-476 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) influxdb3_py_api/src/system_py.rs:443 — influxdb3_py_api/src/system_py.rs:443-460 | influxdb3_py_api/src/system_py.rs:517-534 — 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 (18 lines × 2) influxdb3_server/src/lib.rs:453 — influxdb3_server/src/lib.rs:453-470 | influxdb3_server/src/lib.rs:509-526 — 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 (18 lines × 2) influxdb3_cache/src/distinct_cache/provider.rs:194 — influxdb3_cache/src/distinct_cache/provider.rs:194-211 | influxdb3_cache/src/last_cache/provider.rs:216-234 — `influxdb3_cache/src/distinct_cache/provider.rs` and `influxdb3_cache/src/last_cache/provider.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D2 · Cognitive Complexity · InfluxQLToLogicalPlan · ×8

InfluxQLToLogicalPlan::select_aggregate (cognitive 59) core/iox_query_influxql/src/plan/planner.rs:1471 — InfluxQLToLogicalPlan::select_aggregate has cognitive complexity 59 (threshold 15). Drivers by points: if/else 30 (41 pts), match/switch 4 (8 pts), loops 2 (6 pts), boolean chains 4 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfluxQLToLogicalPlan::function_to_df_expr (cognitive 54) core/iox_query_influxql/src/plan/planner.rs:2668 — InfluxQLToLogicalPlan::function_to_df_expr has cognitive complexity 54 (threshold 15). Drivers by points: if/else 25 (46 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 24). Of this number, 49 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfluxQLToLogicalPlan::show_tag_keys_to_plan (cognitive 29) core/iox_query_influxql/src/plan/planner.rs:3574 — InfluxQLToLogicalPlan::show_tag_keys_to_plan has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 4 (10 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfluxQLToLogicalPlan::varref_to_df_expr (cognitive 25) core/iox_query_influxql/src/plan/planner.rs:2530 — InfluxQLToLogicalPlan::varref_to_df_expr has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 6 (18 pts), if/else 3 (6 pts), boolean chains 1 (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
InfluxQLToLogicalPlan::expand_show_from_clause (cognitive 25) core/iox_query_influxql/src/plan/planner.rs:3470 — InfluxQLToLogicalPlan::expand_show_from_clause has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 2 (6 pts), match/switch 2 (4 pts) (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
InfluxQLToLogicalPlan::show_tag_values_to_plan (cognitive 25) core/iox_query_influxql/src/plan/planner.rs:3839 — InfluxQLToLogicalPlan::show_tag_values_to_plan has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 4 (13 pts), if/else 5 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
InfluxQLToLogicalPlan::union_from (cognitive 23) core/iox_query_influxql/src/plan/planner.rs:1018 — InfluxQLToLogicalPlan::union_from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (6 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfluxQLToLogicalPlan::show_measurements_to_plan (cognitive 16) core/iox_query_influxql/src/plan/planner.rs:3971 — InfluxQLToLogicalPlan::show_measurements_to_plan has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (6 pts), if/else 3 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D30 · Dependency Vulnerabilities · Medium CVE · ×8

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×8

Duplicated block (20 lines × 2) core/iox_query/src/frontend/reorg.rs:79 — core/iox_query/src/frontend/reorg.rs:79-98 | core/iox_query/src/frontend/reorg.rs:188-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.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:411 — influxdb3_catalog/src/catalog/versions/v1.rs:411-430 | influxdb3_catalog/src/catalog/versions/v2.rs:1287-1306 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1281 — influxdb3_catalog/src/catalog/versions/v1.rs:1281-1300 | influxdb3_catalog/src/catalog/versions/v2.rs:2747-2766 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1309 — influxdb3_catalog/src/catalog/versions/v1.rs:1309-1328 | influxdb3_catalog/src/catalog/versions/v2.rs:2775-2794 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:483 — influxdb3_catalog/src/catalog/versions/v2.rs:483-502 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:188-207 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2506 — influxdb3_catalog/src/catalog/versions/v2.rs:2506-2525 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:304-323 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2179 — influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2179-2198 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2253-2272 — 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 (20 lines × 2) influxdb3_catalog/src/serialize/versions/v1.rs:50 — influxdb3_catalog/src/serialize/versions/v1.rs:50-69 | influxdb3_catalog/src/serialize/versions/v2.rs:54-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×7

Duplicated block (17 lines × 2) core/iox_query/src/statistics/partition_statistics/project_schema.rs:128 — core/iox_query/src/statistics/partition_statistics/project_schema.rs:128-144 | core/iox_query/src/statistics/partition_statistics/project_schema.rs:205-221 — 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 (17 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1146 — influxdb3_catalog/src/catalog/versions/v1.rs:1146-1162 | influxdb3_catalog/src/catalog/versions/v2.rs:2566-2582 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2282 — influxdb3_catalog/src/catalog/versions/v1.rs:2282-2298 | influxdb3_catalog/src/catalog/versions/v2.rs:4406-4422 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2343 — influxdb3_catalog/src/catalog/versions/v1.rs:2343-2359 | influxdb3_catalog/src/catalog/versions/v2.rs:4473-4489 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2362 — influxdb3_catalog/src/catalog/versions/v1.rs:2362-2378 | influxdb3_catalog/src/catalog/versions/v2.rs:4492-4508 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:754 — influxdb3_catalog/src/catalog/versions/v1/update.rs:754-770 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1241-1257 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 2) .circleci/packages/sandbox_verify.py:345 — .circleci/packages/sandbox_verify.py:345-361 | .circleci/packages/sandbox_verify.py:365-381 — 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.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×7

Duplicated block (15 lines × 2) core/influxdb_line_protocol/src/lib.rs:1082 — core/influxdb_line_protocol/src/lib.rs:1082-1096 | core/influxdb_line_protocol/src/lib.rs:1110-1124 — 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 (15 lines × 2) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:51 — core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:51-65 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:75-89 — before extracting anything, compare `core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs` and `core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:491 — influxdb3_catalog/src/catalog/versions/v1.rs:491-505 | influxdb3_catalog/src/catalog/versions/v2.rs:1539-1553 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:2265 — influxdb3_catalog/src/catalog/versions/v1.rs:2265-2279 | influxdb3_catalog/src/catalog/versions/v2.rs:4389-4403 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:149 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:149-163 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:722-736 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:4737 — influxdb3_catalog/src/catalog/versions/v2.rs:4737-4751 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:287-301 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) .circleci/packages/sandbox_verify.py:865 — .circleci/packages/sandbox_verify.py:865-879 | .circleci/packages/sandbox_verify.py:883-897 — 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.

D2 · Cognitive Complexity · influxdb3 · ×6

influxdb3::commands::create::command (cognitive 48) influxdb3/src/commands/create.rs:330 — influxdb3::commands::create::command has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (30 pts), match/switch 7 (13 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3::commands::serve::command (cognitive 48) influxdb3/src/commands/serve.rs:952 — influxdb3::commands::serve::command has cognitive complexity 48 (threshold 15). Drivers by points: if/else 24 (33 pts), match/switch 6 (12 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3::commands::update::command (cognitive 37) influxdb3/src/commands/update.rs:93 — influxdb3::commands::update::command has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
influxdb3::non_serve_main (cognitive 23) influxdb3/src/lib.rs:516 — influxdb3::non_serve_main has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
influxdb3::startup (cognitive 21) influxdb3/src/lib.rs:172 — influxdb3::startup has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 3 (6 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
influxdb3::extract_user_params (cognitive 18) influxdb3/src/lib.rs:985 — influxdb3::extract_user_params has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D3 · God Classes · TooManyMethods · ×6

TooManyMethods: Catalog influxdb3_catalog/src/catalog/versions/v3/catalog.rs:400 — TooManyMethods — 165 methods. The bar is 30 methods; this is 135 over it, 5.50× the bar. 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: Catalog influxdb3_catalog/src/catalog/versions/v2.rs:268 — TooManyMethods — 117 methods, declared across 4 files: versions/v2.rs (63), v2/update.rs (36), v2/enterprise.rs (17), update/enterprise.rs (1). The bar is 30 methods; this is 87 over it, 3.90× the bar. 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: HttpApi influxdb3_server/src/http.rs:1040 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. 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: InfluxQLToLogicalPlan core/iox_query_influxql/src/plan/planner.rs:726 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. 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: Client influxdb3_client/src/lib.rs:128 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. 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: Catalog influxdb3_catalog/src/catalog/versions/v1.rs:69 — TooManyMethods — 38 methods, declared across 3 files: versions/v1.rs (20), v1/update.rs (17), v1/enterprise.rs (1). The bar is 30 methods; this is 8 over it, 1.27× the bar. 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.

D31 · IaC & Container Security · Medium IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D1 · Cyclomatic Complexity · influxdb3 · ×5

influxdb3::commands::serve::command (cyclomatic 32) influxdb3/src/commands/serve.rs:952 — influxdb3::commands::serve::command has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
influxdb3::commands::create::command (cyclomatic 29) influxdb3/src/commands/create.rs:330 — influxdb3::commands::create::command has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
influxdb3::non_serve_main (cyclomatic 24) influxdb3/src/lib.rs:516 — influxdb3::non_serve_main has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
influxdb3::maybe_print_help (cyclomatic 24) influxdb3/src/lib.rs:630 — influxdb3::maybe_print_help has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
influxdb3::commands::update::command (cyclomatic 18) influxdb3/src/commands/update.rs:93 — influxdb3::commands::update::command has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D30 · Dependency Vulnerabilities · Medium vulnerability · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×5

Duplicated block (19 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1030 — influxdb3_catalog/src/catalog/versions/v1.rs:1030-1048 | influxdb3_catalog/src/catalog/versions/v2.rs:2307-2325 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1401 — influxdb3_catalog/src/catalog/versions/v1.rs:1401-1419 | influxdb3_catalog/src/catalog/versions/v2.rs:2867-2885 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:103 — influxdb3_catalog/src/catalog/versions/v1/update.rs:103-121 | influxdb3_catalog/src/catalog/versions/v2/update.rs:133-151 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19 lines × 2) influxdb3_catalog/src/catalog/versions/v1/update.rs:452 — influxdb3_catalog/src/catalog/versions/v1/update.rs:452-470 | influxdb3_catalog/src/catalog/versions/v2/update.rs:629-647 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3296 — influxdb3_catalog/src/catalog/versions/v2.rs:3296-3314 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:211-229 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×5

Duplicated block (5 lines × 3) core/iox_query_influxql/src/plan/planner.rs:1208 — core/iox_query_influxql/src/plan/planner.rs:1208-1212 | core/iox_query_influxql/src/plan/planner.rs:1249-1254 | core/iox_query_influxql/src/plan/planner.rs:1274-1279 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) influxdb3_catalog/src/catalog/versions/v1/update.rs:213 — influxdb3_catalog/src/catalog/versions/v1/update.rs:213-218 | influxdb3_catalog/src/catalog/versions/v2/update.rs:340-345 | influxdb3_catalog/src/catalog/versions/v2/update.rs:368-372 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) influxdb3_catalog/src/catalog/versions/v2/update.rs:1118 — influxdb3_catalog/src/catalog/versions/v2/update.rs:1118-1122 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1150-1154 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1181-1185 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) influxdb3_client/src/lib.rs:1109 — influxdb3_client/src/lib.rs:1109-1113 | influxdb3_client/src/lib.rs:1158-1162 | influxdb3_client/src/lib.rs:1205-1209 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) influxdb3_catalog/src/format/records/user.rs:63 — influxdb3_catalog/src/format/records/user.rs:63-67 | influxdb3_catalog/src/format/records/user.rs:98-102 | influxdb3_catalog/src/format/records/user.rs:425-429 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D1 · Cyclomatic Complexity · iox_query · ×4

iox_query::statistics::partition_statistics::statistics_by_partition (cyclomatic 19) core/iox_query/src/statistics/partition_statistics/mod.rs:338 — iox_query::statistics::partition_statistics::statistics_by_partition has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
iox_query::logical_optimizer::regex_to_in_list::enumerate_hir (cyclomatic 17) core/iox_query/src/logical_optimizer/regex_to_in_list.rs:382 — iox_query::logical_optimizer::regex_to_in_list::enumerate_hir has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
iox_query::exec::sleep::array_to_duration (cyclomatic 16) core/iox_query/src/exec/sleep.rs:277 — iox_query::exec::sleep::array_to_duration has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
iox_query::physical_optimizer::projection_pushdown::optimize_plan (cyclomatic 16) core/iox_query/src/physical_optimizer/projection_pushdown.rs:53 — iox_query::physical_optimizer::projection_pushdown::optimize_plan has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · InnerCatalog · ×4

InnerCatalog::apply_delete_batch (cognitive 67) influxdb3_catalog/src/catalog/versions/v2.rs:1914 — InnerCatalog::apply_delete_batch has cognitive complexity 67 (threshold 15). Drivers by points: if/else 8 (43 pts), loops 4 (15 pts), match/switch 3 (8 pts), boolean chains 1 (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InnerCatalog::apply_delete_batch (cognitive 55) influxdb3_catalog/src/catalog/versions/v1.rs:775 — InnerCatalog::apply_delete_batch has cognitive complexity 55 (threshold 15). Drivers by points: if/else 7 (40 pts), loops 3 (11 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 42). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
InnerCatalog::apply_database_batch (cognitive 37) influxdb3_catalog/src/catalog/versions/v1.rs:706 — InnerCatalog::apply_database_batch has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
InnerCatalog::apply_database_batch (cognitive 37) influxdb3_catalog/src/catalog/versions/v2.rs:1843 — InnerCatalog::apply_database_batch has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · influxdb3_server · ×4

influxdb3_server::http::record_batch_stream_to_body (cognitive 48) influxdb3_server/src/http.rs:2440 — influxdb3_server::http::record_batch_stream_to_body has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (28 pts), match/switch 9 (18 pts), loops 1 (2 pts) (nesting depth added 25). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
influxdb3_server::serve (cognitive 35) influxdb3_server/src/lib.rs:366 — influxdb3_server::serve has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 3 (10 pts), loops 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3_server::serve_admin_token_recovery_endpoint (cognitive 32) influxdb3_server/src/lib.rs:223 — influxdb3_server::serve_admin_token_recovery_endpoint has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 3 (10 pts), loops 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3_server::http::validate_db_name (cognitive 16) influxdb3_server/src/http.rs:2366 — influxdb3_server::http::validate_db_name has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Catalog · ×4

Catalog::list_hard_deleted_dbs_tables (cognitive 21) influxdb3_catalog/src/catalog/versions/v2.rs:820 — Catalog::list_hard_deleted_dbs_tables has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Catalog::list_hard_deleted_dbs_tables (cognitive 21) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1719 — Catalog::list_hard_deleted_dbs_tables has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Catalog::background_update (cognitive 20) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:308 — Catalog::background_update has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Catalog::update_to_sequence_number (cognitive 17) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:3306 — Catalog::update_to_sequence_number has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D4 · Code Duplication · Duplicated block (23 lines × 2) · ×4

Duplicated block (23 lines × 2) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:73 — core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:73-95 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:98-120 — before extracting anything, compare `core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs` and `core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) core/object_store_mock/src/lib.rs:665 — core/object_store_mock/src/lib.rs:665-687 | influxdb3_test_helpers/src/object_store/mock.rs:612-634 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1427 — influxdb3_catalog/src/catalog/versions/v1.rs:1427-1449 | influxdb3_catalog/src/catalog/versions/v2.rs:2893-2915 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) influxdb3_write/src/paths.rs:191 — influxdb3_write/src/paths.rs:191-213 | influxdb3_write/src/paths.rs:298-320 — 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.

D4 · Code Duplication · Duplicated block (6 lines × 3) · ×4

Duplicated block (6 lines × 3) core/iox_query_influxql/src/plan/planner.rs:2021 — core/iox_query_influxql/src/plan/planner.rs:2021-2026 | core/iox_query_influxql/src/plan/planner.rs:2035-2040 | core/iox_query_influxql/src/plan/planner.rs:2217-2222 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:573 — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:573-581 | influxdb3_catalog/src/catalog/versions/v2/update.rs:1285-1293 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:2108-2113 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2/update.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) influxdb3_system_tables_common/src/databases.rs:87 — influxdb3_system_tables_common/src/databases.rs:87-92 | influxdb3_system_tables_common/src/distinct_caches.rs:123-128 | influxdb3_system_tables_common/src/tables.rs:116-121 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) influxdb3_catalog/src/catalog/versions/v1.rs:479 — influxdb3_catalog/src/catalog/versions/v1.rs:479-484 | influxdb3_catalog/src/catalog/versions/v2.rs:1527-1532 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:336-341 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 3) · ×4

Duplicated block (8 lines × 3) influxdb3_catalog/src/catalog/versions/v1.rs:1579 — influxdb3_catalog/src/catalog/versions/v1.rs:1579-1586 | influxdb3_catalog/src/catalog/versions/v2.rs:3271-3278 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:200-207 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) influxdb3_catalog/src/catalog/versions/v1/update.rs:50 — influxdb3_catalog/src/catalog/versions/v1/update.rs:50-57 | influxdb3_catalog/src/catalog/versions/v2/update.rs:69-76 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:157-164 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) influxdb3_catalog/src/catalog/versions/v1/update.rs:65 — influxdb3_catalog/src/catalog/versions/v1/update.rs:65-72 | influxdb3_catalog/src/catalog/versions/v2/update.rs:84-91 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:172-179 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:195 — influxdb3_catalog/src/snapshot/versions/v1.rs:195-202 | influxdb3_catalog/src/snapshot/versions/v2.rs:238-245 | influxdb3_catalog/src/snapshot/versions/v3.rs:262-269 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D2 · Cognitive Complexity · iox_query_influxql · ×3

iox_query_influxql::plan::rewriter::from_field_and_dimensions (cognitive 37) core/iox_query_influxql/src/plan/rewriter.rs:590 — iox_query_influxql::plan::rewriter::from_field_and_dimensions has cognitive complexity 37 (threshold 15). Drivers by points: if/else 5 (20 pts), match/switch 3 (10 pts), loops 3 (7 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query_influxql::plan::rewriter::fields_expand_wildcards (cognitive 26) core/iox_query_influxql/src/plan/rewriter.rs:697 — iox_query_influxql::plan::rewriter::fields_expand_wildcards has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 3 (7 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
iox_query_influxql::plan::planner::build_gap_fill_node (cognitive 17) core/iox_query_influxql/src/plan/planner.rs:4182 — iox_query_influxql::plan::planner::build_gap_fill_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · influxdb3_write · ×3

influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line (cognitive 31) influxdb3_write/src/write_buffer/validator.rs:188 — influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 5 (9 pts), loops 4 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3_write::deleter::background_catalog_update (cognitive 24) influxdb3_write/src/deleter.rs:225 — influxdb3_write::deleter::background_catalog_update has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3_write::write_buffer::table_buffer::builder_read (cognitive 19) influxdb3_write/src/write_buffer/table_buffer.rs:1058 — influxdb3_write::write_buffer::table_buffer::builder_read has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×3

REDACTED
REDACTED
REDACTED

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3

Members sharing a duplicated core (5 members, 50+ identical tokens) core/influxdb_influxql_parser/src/visit.rs:730 — core/influxdb_influxql_parser/src/visit.rs:730-795 | core/influxdb_influxql_parser/src/visit.rs:889-926 | core/influxdb_influxql_parser/src/visit.rs:1000-1037 | core/influxdb_influxql_parser/src/visit.rs:1041-1080 | core/influxdb_influxql_parser/src/visit.rs:1084-1115 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) core/influxdb_influxql_parser/src/visit_mut.rs:752 — core/influxdb_influxql_parser/src/visit_mut.rs:752-798 | core/influxdb_influxql_parser/src/visit_mut.rs:886-912 | core/influxdb_influxql_parser/src/visit_mut.rs:981-1007 | core/influxdb_influxql_parser/src/visit_mut.rs:1011-1039 | core/influxdb_influxql_parser/src/visit_mut.rs:1043-1065 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) influxdb3_system_tables_common/src/databases.rs:54 — influxdb3_system_tables_common/src/databases.rs:54-95 | influxdb3_system_tables_common/src/distinct_caches.rs:67-131 | influxdb3_system_tables_common/src/last_caches.rs:77-186 | influxdb3_system_tables_common/src/tables.rs:58-124 | influxdb3_system_tables_common/src/tokens.rs:117-201 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.

D4 · Code Duplication · Duplicated block (16 lines × 3) · ×3

Duplicated block (16 lines × 3) core/mutable_batch/src/writer.rs:455 — core/mutable_batch/src/writer.rs:455-470 | core/mutable_batch/src/writer.rs:564-579 | core/mutable_batch/src/writer.rs:635-652 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 3) influxdb3_commands/src/disable.rs:15 — influxdb3_commands/src/disable.rs:15-30 | influxdb3_commands/src/enable.rs:15-30 | influxdb3_commands/src/test.rs:29-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (16 lines × 3) influxdb3_system_tables_common/src/distinct_caches.rs:100 — influxdb3_system_tables_common/src/distinct_caches.rs:100-115 | influxdb3_system_tables_common/src/last_caches.rs:121-136 | influxdb3_system_tables_common/src/last_caches.rs:146-161 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3

Duplicated block (11 lines × 3) influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:330 — influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:330-340 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:385-395 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:438-448 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) influxdb3_server/src/http.rs:792 — influxdb3_server/src/http.rs:792-802 | influxdb3_server/src/http.rs:815-825 | influxdb3_server/src/http.rs:868-878 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) core/mutable_batch/src/writer.rs:275 — core/mutable_batch/src/writer.rs:275-285 | core/mutable_batch/src/writer.rs:332-342 | core/mutable_batch/src/writer.rs:389-399 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D6 · Cohesion (LCOM4) · Low cohesion · ×3

Low cohesion: Column (LCOM4 6) core/data_types/src/columns.rs:190 — Column's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TestDatabase (LCOM4 4) core/iox_query/src/test.rs:158 — TestDatabase's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MutableBatch (LCOM4 4) core/mutable_batch/src/lib.rs:58 — MutableBatch's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

D1 · Cyclomatic Complexity · InfluxQLToLogicalPlan · ×2

InfluxQLToLogicalPlan::function_to_df_expr (cyclomatic 51) core/iox_query_influxql/src/plan/planner.rs:2668 — InfluxQLToLogicalPlan::function_to_df_expr has cyclomatic complexity 51 (threshold 15). Of this number, 48 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InfluxQLToLogicalPlan::select_aggregate (cyclomatic 36) core/iox_query_influxql/src/plan/planner.rs:1471 — InfluxQLToLogicalPlan::select_aggregate has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · influxdb3_server · ×2

influxdb3_server::http::perform_routing (cyclomatic 47) influxdb3_server/src/http.rs:2742 — influxdb3_server::http::perform_routing has cyclomatic complexity 47 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
influxdb3_server::http::record_batch_stream_to_body (cyclomatic 27) influxdb3_server/src/http.rs:2440 — influxdb3_server::http::record_batch_stream_to_body has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · iox_query_influxql · ×2

iox_query_influxql::plan::planner_rewrite_expression::rewrite_binary_expr (cyclomatic 31) core/iox_query_influxql/src/plan/planner_rewrite_expression.rs:274 — iox_query_influxql::plan::planner_rewrite_expression::rewrite_binary_expr has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
iox_query_influxql::plan::rewriter::fields_expand_wildcards (cyclomatic 19) core/iox_query_influxql/src/plan/rewriter.rs:697 — iox_query_influxql::plan::rewriter::fields_expand_wildcards has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: FieldChecker::check_aggregate_function (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.

D17 · Explicit Debt · XxxComment · ×2

XxxComment influxdb3_processing_engine/src/virtualenv.rs:20 — // XXX: use build flag? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment influxdb3_processing_engine/src/virtualenv.rs:134 — // XXX: ideally we would reorganize the code so that we can — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D17 · Explicit Debt · HackComment · ×2

HackComment core/object_store_mem_cache/src/store.rs:86 — // HACK: `Bytes` is a view-based type and may reference and underlying larger buffer. Maybe that causes — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment core/catalog_cache/src/lib.rs:114 — // HACK: `Bytes` is a view-based type and may reference and underlying larger buffer. Maybe that causes — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.

D2 · Cognitive Complexity · influxdb3_system_tables_common · ×2

influxdb3_system_tables_common::last_caches::from_last_cache_definitions (cognitive 31) influxdb3_system_tables_common/src/last_caches.rs:73 — influxdb3_system_tables_common::last_caches::from_last_cache_definitions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 5 (13 pts), match/switch 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
influxdb3_system_tables_common::tokens::to_record_batch (cognitive 20) influxdb3_system_tables_common/src/tokens.rs:112 — influxdb3_system_tables_common::tokens::to_record_batch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TokenAuthenticatorAndAuthorizer · ×2

TokenAuthenticatorAndAuthorizer::authorize_action (cognitive 24) influxdb3_authz/src/authorizer.rs:70 — TokenAuthenticatorAndAuthorizer::authorize_action has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 4 (8 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TokenAuthenticatorAndAuthorizer::authorize (cognitive 20) influxdb3_authz/src/authorizer.rs:198 — TokenAuthenticatorAndAuthorizer::authorize has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (16 pts), if/else 1 (2 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · WalObjectStore · ×2

WalObjectStore::replay (cognitive 24) influxdb3_wal/src/object_store.rs:147 — WalObjectStore::replay has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 3 (10 pts), if/else 3 (9 pts), loops 3 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalObjectStore::flush_buffer (cognitive 18) influxdb3_wal/src/object_store.rs:311 — WalObjectStore::flush_buffer has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 2 (4 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · influxdb_line_protocol · ×2

influxdb_line_protocol::escape_or_fallback_inner (cognitive 21) core/influxdb_line_protocol/src/lib.rs:1005 — influxdb_line_protocol::escape_or_fallback_inner has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 3 (11 pts), if/else 4 (9 pts), loops 1 (nesting depth added 13). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
influxdb_line_protocol::parameterized_separated_list (cognitive 16) core/influxdb_line_protocol/src/lib.rs:1067 — influxdb_line_protocol::parameterized_separated_list has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · data_types · ×2

data_types::partition_template::parsed_implicit_defaults (cognitive 18) core/data_types/src/partition_template.rs:1314 — data_types::partition_template::parsed_implicit_defaults has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
data_types::partition_template::validate_new_time_format (cognitive 17) core/data_types/src/partition_template.rs:491 — data_types::partition_template::validate_new_time_format has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×2

REDACTED
REDACTED

D35 · Change Coupling · Change coupling · ×2

Change coupling: catalog.rs ↔ serialize.rs influxdb3_catalog/src/catalog.rs:1 — `influxdb3_catalog/src/catalog.rs` and `influxdb3_catalog/src/serialize.rs` change together 78% of the time (21 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 21 shared commits counted here, the most recent 3 are `d07d2f75` feat: Add retention period to cli commands (#26520); `d499c59b` chore: backport hard delete time in Catalog and deleter service from …; `147e2721` fix: use associated constant to ensure correct file ID is always used… — run `git show` on any of them.
Change coupling: queryable_buffer.rs ↔ validator.rs influxdb3_write/src/write_buffer/queryable_buffer.rs:1 — `influxdb3_write/src/write_buffer/queryable_buffer.rs` and `influxdb3_write/src/write_buffer/validator.rs` change together 55% of the time (16 of the 29 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `5d7cb88f` feat: track catalog retries as prometheus metric (#26251); `329ef2f1` feat: allow new tags in schema again (#26108); `d451ef0d` refactor: writer-id to node-id (#25905) — run `git show` on any of them.

D4 · Code Duplication · Duplicated block (40 lines × 2) · ×2

Duplicated block (40 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:665 — influxdb3_catalog/src/catalog/versions/v1.rs:665-704 | influxdb3_catalog/src/catalog/versions/v2.rs:1802-1841 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (40 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3202 — influxdb3_catalog/src/catalog/versions/v2.rs:3202-3241 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:135-174 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (31 lines × 2) · ×2

Duplicated block (31 lines × 2) core/object_store_mock/src/lib.rs:29 — core/object_store_mock/src/lib.rs:29-59 | influxdb3_test_helpers/src/object_store/mock.rs:24-54 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 2) influxdb3_catalog/src/object_store/versions/v1.rs:116 — influxdb3_catalog/src/object_store/versions/v1.rs:116-146 | influxdb3_catalog/src/object_store/versions/v2.rs:285-315 — before extracting anything, compare `influxdb3_catalog/src/object_store/versions/v1.rs` and `influxdb3_catalog/src/object_store/versions/v2.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2

Duplicated block (28 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:97 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:97-124 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:445-472 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (28 lines × 2) influxdb3_query_executor/src/lib.rs:322 — influxdb3_query_executor/src/lib.rs:322-349 | influxdb3_query_executor/src/lib.rs:374-401 — 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.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2

Duplicated block (26 lines × 2) core/object_store_mock/src/lib.rs:637 — core/object_store_mock/src/lib.rs:637-662 | influxdb3_test_helpers/src/object_store/mock.rs:584-609 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:376 — influxdb3_catalog/src/catalog/versions/v1.rs:376-401 | influxdb3_catalog/src/catalog/versions/v2.rs:1051-1076 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23–25 lines × 2) · ×2

Duplicated block (23–25 lines × 2) core/mutable_batch/src/writer.rs:564 — core/mutable_batch/src/writer.rs:564-586 | core/mutable_batch/src/writer.rs:635-659 — 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 (23–25 lines × 2) influxdb3_catalog/src/serialize/versions/v1.rs:74 — influxdb3_catalog/src/serialize/versions/v1.rs:74-96 | influxdb3_catalog/src/serialize/versions/v2.rs:127-151 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2

Duplicated block (24 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1339 — influxdb3_catalog/src/catalog/versions/v1.rs:1339-1362 | influxdb3_catalog/src/catalog/versions/v2.rs:2805-2828 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1370 — influxdb3_catalog/src/catalog/versions/v1.rs:1370-1393 | influxdb3_catalog/src/catalog/versions/v2.rs:2836-2859 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2

Duplicated block (22 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:318 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:318-339 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:890-911 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (22 lines × 2) influxdb3_catalog/src/catalog/versions/v3/schema/retention.rs:15 — influxdb3_catalog/src/catalog/versions/v3/schema/retention.rs:15-36 | influxdb3_catalog/src/log/versions/v4.rs:46-67 — 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.

D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×2

Duplicated block (19–20 lines × 2) core/service_grpc_flight/src/lib.rs:363 — core/service_grpc_flight/src/lib.rs:363-381 | core/service_grpc_flight/src/lib.rs:392-411 — 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 (19–20 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:788 — influxdb3_catalog/src/catalog/versions/v1.rs:788-806 | influxdb3_catalog/src/catalog/versions/v2.rs:1933-1952 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16 lines × 4) · ×2

Duplicated block (16 lines × 4) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:334 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:334-349 | influxdb3_catalog/src/log/versions/v2.rs:857-872 | influxdb3_catalog/src/log/versions/v3.rs:989-1004 | influxdb3_catalog/src/log/versions/v4.rs:1347-1362 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs` and `influxdb3_catalog/src/log/versions/v2.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 4) core/iox_query/src/test.rs:935 — core/iox_query/src/test.rs:935-950 | core/iox_query/src/test.rs:997-1012 | core/iox_query/src/test.rs:1067-1082 | core/iox_query/src/test.rs:1145-1160 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (15 lines × 4) · ×2

Duplicated block (15 lines × 4) core/iox_query_influxql/src/plan/planner.rs:2051 — core/iox_query_influxql/src/plan/planner.rs:2051-2065 | core/iox_query_influxql/src/plan/planner.rs:2070-2084 | core/iox_query_influxql/src/plan/planner.rs:2108-2122 | core/iox_query_influxql/src/plan/planner.rs:2173-2187 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 4) influxdb3_catalog/src/catalog/versions/v2.rs:2449 — influxdb3_catalog/src/catalog/versions/v2.rs:2449-2463 | influxdb3_catalog/src/catalog/versions/v2.rs:2476-2490 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:235-249 | influxdb3_catalog/src/catalog/versions/v3/schema/database.rs:260-274 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/database.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15 lines × 3) · ×2

Duplicated block (15 lines × 3) core/influxdb_influxql_parser/src/visit.rs:1002 — core/influxdb_influxql_parser/src/visit.rs:1002-1016 | core/influxdb_influxql_parser/src/visit.rs:1043-1057 | core/influxdb_influxql_parser/src/visit.rs:1086-1100 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 3) .circleci/packages/sandbox_verify.py:916 — .circleci/packages/sandbox_verify.py:916-930 | .circleci/packages/sandbox_verify.py:934-948 | .circleci/packages/sandbox_verify.py:952-966 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one 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.

D4 · Code Duplication · Duplicated block (13 lines × 4) · ×2

Duplicated block (13 lines × 4) influxdb3_catalog/src/catalog/versions/v1.rs:716 — influxdb3_catalog/src/catalog/versions/v1.rs:716-728 | influxdb3_catalog/src/catalog/versions/v1.rs:782-794 | influxdb3_catalog/src/catalog/versions/v2.rs:1853-1865 | influxdb3_catalog/src/catalog/versions/v2.rs:1927-1939 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) core/influxdb_influxql_parser/src/show_field_keys.rs:43 — core/influxdb_influxql_parser/src/show_field_keys.rs:43-55 | core/influxdb_influxql_parser/src/show_measurements.rs:110-122 | core/influxdb_influxql_parser/src/show_tag_keys.rs:52-64 | core/influxdb_influxql_parser/src/show_tag_values.rs:64-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2

Duplicated block (13 lines × 3) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:76 — core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:76-88 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:71-83 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:101-113 — before extracting anything, compare `core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs` and `core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:276 — influxdb3_catalog/src/snapshot/versions/v1.rs:276-288 | influxdb3_catalog/src/snapshot/versions/v2.rs:319-331 | influxdb3_catalog/src/snapshot/versions/v3.rs:343-355 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2

Duplicated block (12–13 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1997 — influxdb3_catalog/src/catalog/versions/v1.rs:1997-2008 | influxdb3_catalog/src/catalog/versions/v2.rs:4020-4032 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12–13 lines × 2) influxdb3_write/src/write_buffer/validator.rs:236 — influxdb3_write/src/write_buffer/validator.rs:236-247 | influxdb3_write/src/write_buffer/validator.rs:268-280 — 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.

D4 · Code Duplication · Duplicated block (12 lines × 4) · ×2

Duplicated block (12 lines × 4) core/influxdb_influxql_parser/src/visit_mut.rs:770 — core/influxdb_influxql_parser/src/visit_mut.rs:770-781 | core/influxdb_influxql_parser/src/visit_mut.rs:896-907 | core/influxdb_influxql_parser/src/visit_mut.rs:987-998 | core/influxdb_influxql_parser/src/visit_mut.rs:1049-1060 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) influxdb3_catalog/src/catalog/versions/v1.rs:1285 — influxdb3_catalog/src/catalog/versions/v1.rs:1285-1296 | influxdb3_catalog/src/catalog/versions/v1.rs:1313-1324 | influxdb3_catalog/src/catalog/versions/v2.rs:2751-2762 | influxdb3_catalog/src/catalog/versions/v2.rs:2779-2790 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2

Duplicated block (11–12 lines × 2) core/iox_query/src/physical_optimizer/projection_pushdown.rs:134 — core/iox_query/src/physical_optimizer/projection_pushdown.rs:134-145 | core/iox_query/src/physical_optimizer/projection_pushdown.rs:159-169 — 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–12 lines × 2) core/iox_query/src/query_log.rs:626 — core/iox_query/src/query_log.rs:626-636 | core/iox_query/src/query_log.rs:662-673 — 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.

D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×2

Duplicated block (10–11 lines × 2) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:34 — core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:34-44 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:58-67 — before extracting anything, compare `core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs` and `core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) influxdb3_internal_api/src/query_executor.rs:131 — influxdb3_internal_api/src/query_executor.rs:131-140 | influxdb3_internal_api/src/query_executor.rs:201-211 — 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.

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2

Duplicated block (9–10 lines × 2) influxdb3_cache/src/distinct_cache/table_function.rs:234 — influxdb3_cache/src/distinct_cache/table_function.rs:234-242 | influxdb3_cache/src/last_cache/table_function.rs:305-314 — `influxdb3_cache/src/distinct_cache/table_function.rs` and `influxdb3_cache/src/last_cache/table_function.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–10 lines × 2) influxdb3_catalog/src/catalog/versions/v3/ops/token.rs:44 — influxdb3_catalog/src/catalog/versions/v3/ops/token.rs:44-52 | influxdb3_catalog/src/catalog/versions/v3/ops/token.rs:201-210 — 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.

D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2

Duplicated block (8 lines × 4) core/parquet_file/src/metadata.rs:891 — core/parquet_file/src/metadata.rs:891-898 | core/parquet_file/src/metadata.rs:902-909 | core/parquet_file/src/metadata.rs:924-931 | core/parquet_file/src/metadata.rs:935-942 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 4) core/flightsql/src/cmd.rs:233 — core/flightsql/src/cmd.rs:233-249 | core/flightsql/src/cmd.rs:275-282 | core/flightsql/src/cmd.rs:288-295 | core/flightsql/src/cmd.rs:301-308 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7 lines × 3) · ×2

Duplicated block (7 lines × 3) core/iox_query_influxql/src/plan/planner.rs:3604 — core/iox_query_influxql/src/plan/planner.rs:3604-3610 | core/iox_query_influxql/src/plan/planner.rs:3874-3880 | core/iox_query_influxql/src/plan/planner.rs:4002-4008 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:215 — influxdb3_catalog/src/snapshot/versions/v1.rs:215-221 | influxdb3_catalog/src/snapshot/versions/v2.rs:258-264 | influxdb3_catalog/src/snapshot/versions/v3.rs:282-288 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D1 · Cyclomatic Complexity · Error · ×1

Error::into_response (cyclomatic 44) influxdb3_server/src/http.rs:728 — Error::into_response has cyclomatic complexity 44 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · influxdb_influxql_parser · ×1

influxdb_influxql_parser::time_range::split_cond (cyclomatic 34) core/influxdb_influxql_parser/src/time_range.rs:178 — influxdb_influxql_parser::time_range::split_cond has cyclomatic complexity 34 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · ValueSerializer · ×1

ValueSerializer::serialize (cyclomatic 28) core/iox_v1_query_api/src/value.rs:204 — ValueSerializer::serialize has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MutableTableChunk · ×1

MutableTableChunk::append_row (cyclomatic 28) influxdb3_write/src/write_buffer/table_buffer.rs:592 — MutableTableChunk::append_row has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · FieldChecker · ×1

FieldChecker::check_fields (cyclomatic 27) core/iox_query_influxql/src/plan/rewriter.rs:1023 — FieldChecker::check_fields has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CurrentCatalogUsage · ×1

CurrentCatalogUsage::handle_batch (cyclomatic 23) influxdb3_catalog/src/catalog/versions/v2.rs:150 — CurrentCatalogUsage::handle_batch has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · RewriteSelect · ×1

RewriteSelect::expand_projection (cyclomatic 22) core/iox_query_influxql/src/plan/rewriter.rs:223 — RewriteSelect::expand_projection has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · influxdb3_write · ×1

influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line (cyclomatic 22) influxdb3_write/src/write_buffer/validator.rs:188 — influxdb3_write::write_buffer::validator::validate_and_qualify_v1_line has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DateBinWallclockUDF · ×1

DateBinWallclockUDF::invoke_with_args (cyclomatic 20) core/query_functions/src/date_bin_wallclock.rs:190 — DateBinWallclockUDF::invoke_with_args has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · TokenAuthenticatorAndAuthorizer · ×1

TokenAuthenticatorAndAuthorizer::authorize_action (cyclomatic 20) influxdb3_authz/src/authorizer.rs:70 — TokenAuthenticatorAndAuthorizer::authorize_action has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · V1HttpHandler · ×1

V1HttpHandler::execute_query (cyclomatic 19) core/iox_v1_query_api/src/handler.rs:204 — V1HttpHandler::execute_query has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · InnerCatalog · ×1

InnerCatalog::apply_delete_batch (cyclomatic 18) influxdb3_catalog/src/catalog/versions/v2.rs:1914 — InnerCatalog::apply_delete_batch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · influxdb3_py_api · ×1

influxdb3_py_api::system_py::process_flask_response (cyclomatic 18) influxdb3_py_api/src/system_py.rs:614 — influxdb3_py_api::system_py::process_flask_response has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PersistedFiles · ×1

PersistedFiles::remove_files_for_deletion (cyclomatic 18) influxdb3_write/src/write_buffer/persisted_files.rs:205 — PersistedFiles::remove_files_for_deletion has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · mutable_batch_pb · ×1

mutable_batch_pb::decode::write_table_batch (cyclomatic 17) core/mutable_batch_pb/src/decode.rs:80 — mutable_batch_pb::decode::write_table_batch has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · QueryableBuffer · ×1

QueryableBuffer::buffer_wal_contents_and_persist_snapshotted_data (cyclomatic 17) influxdb3_write/src/write_buffer/queryable_buffer.rs:225 — QueryableBuffer::buffer_wal_contents_and_persist_snapshotted_data has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · Node · ×1

Node::evaluate_predicates (cyclomatic 16) influxdb3_cache/src/distinct_cache/cache.rs:362 — Node::evaluate_predicates has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D17 · Explicit Debt · FixmeComment · ×1

FixmeComment core/predicate/src/lib.rs:197 — // FIXME(lesam): This should properly be contains_all, but until — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

D2 · Cognitive Complexity · MutableTableChunk · ×1

MutableTableChunk::append_row (cognitive 58) influxdb3_write/src/write_buffer/table_buffer.rs:592 — MutableTableChunk::append_row has cognitive complexity 58 (threshold 15). Drivers by points: if/else 20 (44 pts), match/switch 3 (9 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CurrentCatalogUsage · ×1

CurrentCatalogUsage::handle_batch (cognitive 51) influxdb3_catalog/src/catalog/versions/v2.rs:150 — CurrentCatalogUsage::handle_batch has cognitive complexity 51 (threshold 15). Drivers by points: if/else 8 (32 pts), loops 4 (12 pts), match/switch 3 (7 pts) (nesting depth added 36). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · influxdb_influxql_parser · ×1

influxdb_influxql_parser::time_range::split_cond (cognitive 50) core/influxdb_influxql_parser/src/time_range.rs:178 — influxdb_influxql_parser::time_range::split_cond has cognitive complexity 50 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 8 (23 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · LastCacheProvider · ×1

LastCacheProvider::write_wal_contents_to_cache (cognitive 50) influxdb3_cache/src/last_cache/provider.rs:290 — LastCacheProvider::write_wal_contents_to_cache has cognitive complexity 50 (threshold 15). Drivers by points: loops 5 (26 pts), if/else 5 (22 pts), match/switch 1 (2 pts) (nesting depth added 39). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · Node · ×1

Node::evaluate_predicates (cognitive 47) influxdb3_cache/src/distinct_cache/cache.rs:362 — Node::evaluate_predicates has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (33 pts), loops 3 (13 pts), boolean chains 1 (nesting depth added 27). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · RewriteSelect · ×1

RewriteSelect::expand_projection (cognitive 42) core/iox_query_influxql/src/plan/rewriter.rs:223 — RewriteSelect::expand_projection has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 6 (12 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ValueSerializer · ×1

ValueSerializer::serialize (cognitive 39) core/iox_v1_query_api/src/value.rs:204 — ValueSerializer::serialize has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (29 pts), match/switch 3 (8 pts), boolean chains 2 (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · influxdb3_py_api · ×1

influxdb3_py_api::system_py::process_flask_response (cognitive 36) influxdb3_py_api/src/system_py.rs:614 — influxdb3_py_api::system_py::process_flask_response has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (32 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · FieldChecker · ×1

FieldChecker::check_fields (cognitive 35) core/iox_query_influxql/src/plan/rewriter.rs:1023 — FieldChecker::check_fields has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (26 pts), boolean chains 5, match/switch 2 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CatalogRequestFuture · ×1

CatalogRequestFuture::call (cognitive 34) core/catalog_cache/src/api/server.rs:142 — CatalogRequestFuture::call has cognitive complexity 34 (threshold 15). Drivers by points: match/switch 8 (23 pts), if/else 4 (11 pts) (nesting depth added 22). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · PersistedFiles · ×1

PersistedFiles::remove_files_for_deletion (cognitive 34) influxdb3_write/src/write_buffer/persisted_files.rs:205 — PersistedFiles::remove_files_for_deletion has cognitive complexity 34 (threshold 15). Drivers by points: loops 9 (21 pts), if/else 5 (9 pts), match/switch 2 (4 pts) (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · QueryableBuffer · ×1

QueryableBuffer::buffer_wal_contents_and_persist_snapshotted_data (cognitive 33) influxdb3_write/src/write_buffer/queryable_buffer.rs:225 — QueryableBuffer::buffer_wal_contents_and_persist_snapshotted_data has cognitive complexity 33 (threshold 15). Drivers by points: loops 9 (18 pts), if/else 3 (7 pts), match/switch 2 (7 pts), boolean chains 1 (nesting depth added 18). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · influxdb_iox_client · ×1

influxdb_iox_client::format::influxql::write_columnar (cognitive 31) core/influxdb_iox_client/src/format/influxql.rs:63 — influxdb_iox_client::format::influxql::write_columnar has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CatalogMetrics · ×1

CatalogMetrics::operation_observer (cognitive 30) influxdb3_catalog/src/catalog/versions/v2/metrics.rs:39 — CatalogMetrics::operation_observer has cognitive complexity 30 (threshold 15). Drivers by points: loops 8 (27 pts), match/switch 1 (3 pts) (nesting depth added 21). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · ProcessingEngineManagerImpl · ×1

ProcessingEngineManagerImpl::list_plugin_files (cognitive 30) influxdb3_processing_engine/src/lib.rs:967 — ProcessingEngineManagerImpl::list_plugin_files has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (20 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · TypeEvaluator · ×1

TypeEvaluator::eval_var_ref (cognitive 29) core/iox_query_influxql/src/plan/expr_type_evaluator.rs:110 — TypeEvaluator::eval_var_ref has cognitive complexity 29 (threshold 15). Drivers by points: if/else 3 (13 pts), match/switch 4 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · BufferedInput · ×1

BufferedInput::need_more (cognitive 28) core/iox_query/src/exec/gapfill/buffered_input.rs:99 — BufferedInput::need_more has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TrapezoidalRulePartitionEvaluator · ×1

TrapezoidalRulePartitionEvaluator::evaluate_all (cognitive 28) core/iox_query_influxql/src/window/integral.rs:112 — TrapezoidalRulePartitionEvaluator::evaluate_all has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 2, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WriteBufferImpl · ×1

WriteBufferImpl::new (cognitive 28) influxdb3_write/src/write_buffer/mod.rs:211 — WriteBufferImpl::new has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 5 (8 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DateBinWallclockUDF · ×1

DateBinWallclockUDF::invoke_with_args (cognitive 27) core/query_functions/src/date_bin_wallclock.rs:190 — DateBinWallclockUDF::invoke_with_args has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 10 (14 pts), if/else 8 (12 pts), boolean chains 1 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · DistinctCacheProvider · ×1

DistinctCacheProvider::write_wal_contents_to_cache (cognitive 27) influxdb3_cache/src/distinct_cache/provider.rs:255 — DistinctCacheProvider::write_wal_contents_to_cache has cognitive complexity 27 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 5 (12 pts) (nesting depth added 17). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · influxdb3_cache · ×1

influxdb3_cache::last_cache::table_function::convert_filter_exprs (cognitive 27) influxdb3_cache/src/last_cache/table_function.rs:119 — influxdb3_cache::last_cache::table_function::convert_filter_exprs has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 3 (10 pts), loops 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · influxdb3_processing_engine · ×1

influxdb3_processing_engine::background_catalog_update (cognitive 27) influxdb3_processing_engine/src/lib.rs:1285 — influxdb3_processing_engine::background_catalog_update has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (20 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · V1HttpHandler · ×1

V1HttpHandler::execute_query (cognitive 26) core/iox_v1_query_api/src/handler.rs:204 — V1HttpHandler::execute_query has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 8 (14 pts), if/else 8 (10 pts), boolean chains 2 (nesting depth added 8). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · PredicatePushdown · ×1

PredicatePushdown::optimize (cognitive 25) core/iox_query/src/physical_optimizer/predicate_pushdown.rs:27 — PredicatePushdown::optimize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (25 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · SeriesChunkMergeStream · ×1

SeriesChunkMergeStream::poll_next (cognitive 25) core/iox_v1_query_api/src/response/stream.rs:45 — SeriesChunkMergeStream::poll_next has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BufferedResponseStream · ×1

BufferedResponseStream::poll_next_unpin (cognitive 24) core/iox_v1_query_api/src/response/buffered.rs:52 — BufferedResponseStream::poll_next_unpin has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ChunkedResponseStream · ×1

ChunkedResponseStream::poll_next_unpin (cognitive 24) core/iox_v1_query_api/src/response/chunked.rs:52 — ChunkedResponseStream::poll_next_unpin has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Writer · ×1

Writer::write_batch_ranges (cognitive 24) core/mutable_batch/src/writer.rs:761 — Writer::write_batch_ranges has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (12 pts), match/switch 3 (11 pts), if/else 1 (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · sandbox_verify.test_ProtectProc_invisible (cognitive 24) · ×1

sandbox_verify.test_ProtectProc_invisible (cognitive 24) .circleci/packages/sandbox_verify.py:269 — sandbox_verify.test_ProtectProc_invisible has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 2 (4 pts), loops 2 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PriorityQueue · ×1

PriorityQueue::pop (cognitive 23) influxdb3_write/src/async_collections.rs:44 — PriorityQueue::pop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 1 (5 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DateBinGapExpander · ×1

DateBinGapExpander::get_bounds (cognitive 22) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:23 — DateBinGapExpander::get_bounds has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DateBinWallclockGapExpander · ×1

DateBinWallclockGapExpander::get_bounds (cognitive 22) core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:47 — DateBinWallclockGapExpander::get_bounds has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PersistedSnapshotCheckpoint · ×1

PersistedSnapshotCheckpoint::merge (cognitive 22) influxdb3_write/src/lib.rs:677 — PersistedSnapshotCheckpoint::merge has cognitive complexity 22 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 4 (10 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · Column · ×1

Column::num_rows (cognitive 21) core/table_batch/src/column.rs:14 — Column::num_rows has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (13 pts), loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 6). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · StatisticsVisitor · ×1

StatisticsVisitor::post_visit (cognitive 21) core/iox_query/src/statistics/aggregate_per_plan.rs:105 — StatisticsVisitor::post_visit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · schema · ×1

schema::parse_series_key_with_tracker (cognitive 21) core/schema/src/lib.rs:413 — schema::parse_series_key_with_tracker has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DistinctCacheExec · ×1

DistinctCacheExec::fmt_as (cognitive 21) influxdb3_cache/src/distinct_cache/table_function.rs:335 — DistinctCacheExec::fmt_as has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (6 pts), match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · LastCacheStore · ×1

LastCacheStore::push (cognitive 21) influxdb3_cache/src/last_cache/cache.rs:767 — LastCacheStore::push has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (9 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · flightsql · ×1

flightsql::planner::plan_get_tables (cognitive 20) core/flightsql/src/planner.rs:495 — flightsql::planner::plan_get_tables has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 4 (8 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SeriesLimitStream · ×1

SeriesLimitStream::process_batch (cognitive 20) core/iox_query/src/exec/series_limit/physical.rs:762 — SeriesLimitStream::process_batch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), loops 5 (7 pts), match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · mutable_batch_pb · ×1

mutable_batch_pb::decode::write_table_batch (cognitive 20) core/mutable_batch_pb/src/decode.rs:80 — mutable_batch_pb::decode::write_table_batch has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 4 (7 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ChunkFilter · ×1

ChunkFilter::new (cognitive 20) influxdb3_write/src/lib.rs:740 — ChunkFilter::new has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SelectStatement · ×1

SelectStatement::accept (cognitive 19) core/influxdb_influxql_parser/src/visit.rs:730 — SelectStatement::accept has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ExtractChunksVisitor · ×1

ExtractChunksVisitor::pre_visit (cognitive 19) core/iox_query/src/physical_optimizer/chunk_extraction.rs:104 — ExtractChunksVisitor::pre_visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WriteChunkStream · ×1

WriteChunkStream::poll_next (cognitive 19) influxdb3_commands/src/write.rs:311 — WriteChunkStream::poll_next has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Persister · ×1

Persister::load_snapshots (cognitive 19) influxdb3_write/src/persister.rs:228 — Persister::load_snapshots has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), match/switch 1 (2 pts) (nesting depth added 7). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · sandbox_verify.test_AmbientCapabilities (cognitive 19) · ×1

sandbox_verify.test_AmbientCapabilities (cognitive 19) .circleci/packages/sandbox_verify.py:589 — sandbox_verify.test_AmbientCapabilities has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 2, boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ListDecoder · ×1

ListDecoder::decode (cognitive 18) core/catalog_cache/src/api/list/v2.rs:100 — ListDecoder::decode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · QuorumCatalogCache · ×1

QuorumCatalogCache::get (cognitive 18) core/catalog_cache/src/api/quorum.rs:115 — QuorumCatalogCache::get has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · SchemaAdapterStream · ×1

SchemaAdapterStream::try_new (cognitive 18) core/iox_query/src/provider/adapter.rs:126 — SchemaAdapterStream::try_new has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CsvStream · ×1

CsvStream::poll_next (cognitive 18) core/iox_v1_query_api/src/response/csv.rs:62 — CsvStream::poll_next has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Selector · ×1

Selector::update_value_based (cognitive 17) core/query_functions/src/selectors/internal.rs:162 — Selector::update_value_based has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Args · ×1

Args::parse (cognitive 17) influxdb3_catalog_macros/src/lib.rs:73 — Args::parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · object_store_utils · ×1

object_store_utils::adaptive_get::get_adaptive_impl (cognitive 17) object_store_utils/src/adaptive_get.rs:83 — object_store_utils::adaptive_get::get_adaptive_impl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (3 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CatalogCache · ×1

CatalogCache::insert (cognitive 16) core/catalog_cache/src/local/mod.rs:87 — CatalogCache::insert has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.

D2 · Cognitive Complexity · Wrapper · ×1

Wrapper::try_from (cognitive 16) core/data_types/src/partition_template.rs:941 — Wrapper::try_from has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · mutable_batch_lp · ×1

mutable_batch_lp::write_line (cognitive 16) core/mutable_batch_lp/src/lib.rs:276 — mutable_batch_lp::write_line has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ExtendedLastCacheState · ×1

ExtendedLastCacheState::to_record_batch (cognitive 16) influxdb3_cache/src/last_cache/cache.rs:435 — ExtendedLastCacheState::to_record_batch has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (12 pts), if/else 2, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · influxdb3_catalog · ×1

influxdb3_catalog::catalog::migrations::v3::synthesize_table (cognitive 16) influxdb3_catalog/src/catalog/migrations/v3.rs:344 — influxdb3_catalog::catalog::migrations::v3::synthesize_table has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 4, boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D3 · God Classes · TooManyFields · ×1

TooManyFields: TelemetryPayload influxdb3_telemetry/src/sender.rs:49 — TooManyFields — 41 stored fields. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member family (4 members, 60 shared lines) · ×1

Near-duplicate member family (4 members, 60 shared lines) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:268 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:268-331 | influxdb3_catalog/src/log/versions/v2.rs:793-854 | influxdb3_catalog/src/log/versions/v3.rs:925-986 | influxdb3_catalog/src/log/versions/v4.rs:1283-1344 — These 4 members are variants of one another: a block of 60 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Near-duplicate member family (3 members, 44 shared lines) · ×1

Near-duplicate member family (3 members, 44 shared lines) influxdb3_catalog/src/snapshot/versions/v1.rs:241 — influxdb3_catalog/src/snapshot/versions/v1.rs:241-288 | influxdb3_catalog/src/snapshot/versions/v2.rs:284-331 | influxdb3_catalog/src/snapshot/versions/v3.rs:308-355 — These 3 members are variants of one another: a block of 44 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.

D4 · Code Duplication · Near-duplicate member pair (49 shared lines) · ×1

Near-duplicate member pair (49 shared lines) core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:27 — core/iox_query/src/exec/gapfill/date_bin_gap_expander.rs:27-95 | core/iox_query/src/exec/gapfill/date_bin_wallclock_gap_expander.rs:51-120 — These two members are variants of one another: 49 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×1

Edited copy of a member (52 corresponding lines) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:369 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:369-420 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:941-992 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1

Edited copy of a member (44 corresponding lines) influxdb3_catalog/src/catalog/versions/v2.rs:820 — influxdb3_catalog/src/catalog/versions/v2.rs:820-877 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1719-1770 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (7 members, 50+ identical tokens) influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:83 — influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:83-104 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:136-157 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:264-296 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:490-519 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:604-627 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:699-720 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:748-776 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.

D4 · Code Duplication · Duplicated block (99–100 lines × 2) · ×1

Duplicated block (99–100 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:169 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:169-268 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:742-840 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D4 · Code Duplication · Duplicated block (86–98 lines × 2) · ×1

Duplicated block (86–98 lines × 2) core/object_store_mock/src/lib.rs:207 — core/object_store_mock/src/lib.rs:207-292 | influxdb3_test_helpers/src/object_store/mock.rs:170-267 — before extracting anything, compare `core/object_store_mock/src/lib.rs` and `influxdb3_test_helpers/src/object_store/mock.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 251 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (55 lines × 2) · ×1

Duplicated block (55 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:3406 — influxdb3_catalog/src/catalog/versions/v2.rs:3406-3460 | influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:256-310 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/schema/table.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 169 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (51–52 lines × 2) · ×1

Duplicated block (51–52 lines × 2) influxdb3/src/commands/create.rs:35 — influxdb3/src/commands/create.rs:35-85 | influxdb3/src/commands/delete.rs:19-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (42–48 lines × 2) · ×1

Duplicated block (42–48 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:821 — influxdb3_catalog/src/catalog/versions/v2.rs:821-868 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1720-1761 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (43 lines × 4) · ×1

Duplicated block (43 lines × 4) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:289 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:289-331 | influxdb3_catalog/src/log/versions/v2.rs:812-854 | influxdb3_catalog/src/log/versions/v3.rs:944-986 | influxdb3_catalog/src/log/versions/v4.rs:1302-1344 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs` and `influxdb3_catalog/src/log/versions/v2.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1

Duplicated block (38 lines × 2) influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:277 — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:277-314 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:849-886 — `influxdb3_catalog/src/catalog/versions/v1/enterprise.rs` and `influxdb3_catalog/src/catalog/versions/v2/enterprise.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 270 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1

Duplicated block (34 lines × 2) influxdb3_catalog/src/object_store/versions/v1.rs:76 — influxdb3_catalog/src/object_store/versions/v1.rs:76-109 | influxdb3_catalog/src/object_store/versions/v2.rs:212-245 — before extracting anything, compare `influxdb3_catalog/src/object_store/versions/v1.rs` and `influxdb3_catalog/src/object_store/versions/v2.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1

Duplicated block (32 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:1164 — influxdb3_catalog/src/catalog/versions/v1.rs:1164-1195 | influxdb3_catalog/src/catalog/versions/v2.rs:2586-2617 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1

Duplicated block (27 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:323 — influxdb3_catalog/src/catalog/versions/v1.rs:323-349 | influxdb3_catalog/src/catalog/versions/v2.rs:998-1024 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1

Duplicated block (26–27 lines × 2) influxdb3_server/src/lib.rs:285 — influxdb3_server/src/lib.rs:285-310 | influxdb3_server/src/lib.rs:335-361 — 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.

D4 · Code Duplication · Duplicated block (26 lines × 4) · ×1

Duplicated block (26 lines × 4) core/iox_query_influxql/src/plan/planner.rs:2759 — core/iox_query_influxql/src/plan/planner.rs:2759-2784 | core/iox_query_influxql/src/plan/planner.rs:2787-2812 | core/iox_query_influxql/src/plan/planner.rs:2815-2840 | core/iox_query_influxql/src/plan/planner.rs:2843-2868 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (18–24 lines × 2) · ×1

Duplicated block (18–24 lines × 2) influxdb3_catalog/src/catalog/versions/v1.rs:737 — influxdb3_catalog/src/catalog/versions/v1.rs:737-754 | influxdb3_catalog/src/catalog/versions/v2.rs:1948-1971 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1

Duplicated block (23–24 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:597 — influxdb3_catalog/src/catalog/versions/v2.rs:597-619 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:1052-1075 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v2.rs` and `influxdb3_catalog/src/catalog/versions/v3/catalog.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 159 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1

Duplicated block (22–23 lines × 2) core/iox_query_influxql/src/plan/planner.rs:3657 — core/iox_query_influxql/src/plan/planner.rs:3657-3679 | core/iox_query_influxql/src/plan/planner.rs:4018-4039 — 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.

D4 · Code Duplication · Duplicated block (20–23 lines × 2) · ×1

Duplicated block (20–23 lines × 2) core/iox_query_influxql/src/window/integral.rs:276 — core/iox_query_influxql/src/window/integral.rs:276-298 | core/iox_query_influxql/src/window/integral.rs:354-373 — 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.

D4 · Code Duplication · Duplicated block (22 lines × 4) · ×1

Duplicated block (22 lines × 4) core/iox_query_influxql/src/plan/planner.rs:2998 — core/iox_query_influxql/src/plan/planner.rs:2998-3019 | core/iox_query_influxql/src/plan/planner.rs:3077-3098 | core/iox_query_influxql/src/plan/planner.rs:3103-3124 | core/iox_query_influxql/src/plan/planner.rs:3129-3150 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (18–22 lines × 3) · ×1

Duplicated block (18–22 lines × 3) influxdb3_catalog/src/catalog/versions/v1.rs:732 — influxdb3_catalog/src/catalog/versions/v1.rs:732-749 | influxdb3_catalog/src/catalog/versions/v2.rs:1869-1886 | influxdb3_catalog/src/catalog/versions/v2.rs:1943-1964 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15–22 lines × 2) · ×1

Duplicated block (15–22 lines × 2) core/iox_query/src/exec/gapfill/mod.rs:236 — core/iox_query/src/exec/gapfill/mod.rs:236-250 | core/iox_query/src/exec/series_limit/logical.rs:584-605 — 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.

D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1

Duplicated block (21–22 lines × 2) influxdb3/src/commands/create.rs:540 — influxdb3/src/commands/create.rs:540-560 | influxdb3/src/commands/update.rs:205-226 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (19–22 lines × 2) · ×1

Duplicated block (19–22 lines × 2) influxdb3_commands/src/debug/catalog/sequence.rs:77 — influxdb3_commands/src/debug/catalog/sequence.rs:77-95 | influxdb3_commands/src/debug/catalog/snapshot.rs:71-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1

Duplicated block (20 lines × 3) influxdb3_catalog/src/catalog/versions/v1.rs:873 — influxdb3_catalog/src/catalog/versions/v1.rs:873-892 | influxdb3_catalog/src/catalog/versions/v2.rs:2122-2141 | influxdb3_catalog/src/catalog/versions/v3/schema/storage.rs:51-70 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1

Duplicated block (18 lines × 4) core/iox_query_influxql/src/plan/planner.rs:3730 — core/iox_query_influxql/src/plan/planner.rs:3730-3747 | core/iox_query_influxql/src/plan/planner.rs:3820-3837 | core/iox_query_influxql/src/plan/planner.rs:3952-3969 | core/iox_query_influxql/src/plan/planner.rs:4068-4085 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (17–18 lines × 4) · ×1

Duplicated block (17–18 lines × 4) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:269 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:269-286 | influxdb3_catalog/src/log/versions/v2.rs:794-810 | influxdb3_catalog/src/log/versions/v3.rs:926-942 | influxdb3_catalog/src/log/versions/v4.rs:1284-1300 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs` and `influxdb3_catalog/src/log/versions/v2.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1

Duplicated block (18 lines × 3) core/service_grpc_flight/src/lib.rs:1111 — core/service_grpc_flight/src/lib.rs:1111-1128 | core/service_grpc_flight/src/lib.rs:1212-1229 | core/service_grpc_flight/src/lib.rs:1276-1293 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1

Duplicated block (17 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:257 — influxdb3_catalog/src/snapshot/versions/v1.rs:257-273 | influxdb3_catalog/src/snapshot/versions/v2.rs:300-316 | influxdb3_catalog/src/snapshot/versions/v3.rs:324-340 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×1

Duplicated block (16–17 lines × 2) influxdb3_server/src/http.rs:1530 — influxdb3_server/src/http.rs:1530-1546 | influxdb3_server/src/http.rs:1624-1639 — 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.

D4 · Code Duplication · Duplicated block (11–16 lines × 6) · ×1

Duplicated block (11–16 lines × 6) core/influxdb_influxql_parser/src/visit.rs:740 — core/influxdb_influxql_parser/src/visit.rs:740-750 | core/influxdb_influxql_parser/src/visit.rs:753-768 | core/influxdb_influxql_parser/src/visit.rs:902-917 | core/influxdb_influxql_parser/src/visit.rs:1007-1022 | core/influxdb_influxql_parser/src/visit.rs:1061-1071 | core/influxdb_influxql_parser/src/visit.rs:1091-1106 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1

Duplicated block (13–15 lines × 2) core/data_types/src/partition_template.rs:964 — core/data_types/src/partition_template.rs:964-978 | core/data_types/src/partition_template.rs:984-996 — 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.

D4 · Code Duplication · Duplicated block (14 lines × 6) · ×1

Duplicated block (14 lines × 6) core/iox_query_influxql/src/plan/planner.rs:2052 — core/iox_query_influxql/src/plan/planner.rs:2052-2065 | core/iox_query_influxql/src/plan/planner.rs:2071-2084 | core/iox_query_influxql/src/plan/planner.rs:2090-2103 | core/iox_query_influxql/src/plan/planner.rs:2109-2122 | core/iox_query_influxql/src/plan/planner.rs:2132-2145 | core/iox_query_influxql/src/plan/planner.rs:2155-2168 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1

Duplicated block (14 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:242 — influxdb3_catalog/src/snapshot/versions/v1.rs:242-255 | influxdb3_catalog/src/snapshot/versions/v2.rs:285-298 | influxdb3_catalog/src/snapshot/versions/v3.rs:309-322 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8–14 lines × 2) · ×1

Duplicated block (8–14 lines × 2) core/iox_query_influxql/src/plan/planner.rs:1180 — core/iox_query_influxql/src/plan/planner.rs:1180-1187 | core/iox_query_influxql/src/plan/planner.rs:1583-1596 — 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.

D4 · Code Duplication · Duplicated block (10–13 lines × 2) · ×1

Duplicated block (10–13 lines × 2) influxdb3_catalog/src/catalog/versions/v3/catalog.rs:855 — influxdb3_catalog/src/catalog/versions/v3/catalog.rs:855-864 | influxdb3_catalog/src/catalog/versions/v3/catalog.rs:897-909 — 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.

D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1

Duplicated block (12 lines × 3) influxdb3_catalog/src/snapshot/versions/v1.rs:226 — influxdb3_catalog/src/snapshot/versions/v1.rs:226-237 | influxdb3_catalog/src/snapshot/versions/v2.rs:269-280 | influxdb3_catalog/src/snapshot/versions/v3.rs:293-304 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×1

Duplicated block (10–12 lines × 3) influxdb3_server/src/http.rs:1154 — influxdb3_server/src/http.rs:1154-1163 | influxdb3_server/src/http.rs:1170-1181 | influxdb3_server/src/http.rs:1187-1196 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9–12 lines × 2) · ×1

Duplicated block (9–12 lines × 2) core/iox_query/src/provider/deduplicate.rs:358 — core/iox_query/src/provider/deduplicate.rs:358-369 | core/iox_query/src/provider/deduplicate.rs:386-394 — 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.

D4 · Code Duplication · Duplicated block (11 lines × 7) · ×1

Duplicated block (11 lines × 7) influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:84 — influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:84-94 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:137-147 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:265-275 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:491-501 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:605-615 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:700-710 | influxdb3_catalog/src/catalog/versions/v3/ops/user.rs:749-759 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (11 lines × 5) · ×1

Duplicated block (11 lines × 5) core/influxdb_influxql_parser/src/visit_mut.rs:773 — core/influxdb_influxql_parser/src/visit_mut.rs:773-783 | core/influxdb_influxql_parser/src/visit_mut.rs:899-909 | core/influxdb_influxql_parser/src/visit_mut.rs:990-1000 | core/influxdb_influxql_parser/src/visit_mut.rs:1026-1036 | core/influxdb_influxql_parser/src/visit_mut.rs:1052-1062 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1

Duplicated block (9–11 lines × 2) influxdb3_catalog/src/catalog/versions/v2.rs:2699 — influxdb3_catalog/src/catalog/versions/v2.rs:2699-2709 | influxdb3_catalog/src/format/records/database.rs:188-196 — 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.

D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1

Duplicated block (10 lines × 4) core/influxdb_influxql_parser/src/visit.rs:914 — core/influxdb_influxql_parser/src/visit.rs:914-923 | core/influxdb_influxql_parser/src/visit.rs:1025-1034 | core/influxdb_influxql_parser/src/visit.rs:1068-1077 | core/influxdb_influxql_parser/src/visit.rs:1103-1112 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1

Duplicated block (10 lines × 3) influxdb3_system_tables_common/src/distinct_caches.rs:72 — influxdb3_system_tables_common/src/distinct_caches.rs:72-81 | influxdb3_system_tables_common/src/last_caches.rs:82-91 | influxdb3_system_tables_common/src/last_caches.rs:94-103 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1

Duplicated block (9 lines × 3) core/iox_query_influxql/src/plan/rewriter.rs:1441 — core/iox_query_influxql/src/plan/rewriter.rs:1441-1449 | core/iox_query_influxql/src/plan/rewriter.rs:1481-1489 | core/iox_query_influxql/src/plan/rewriter.rs:1501-1509 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1

Duplicated block (7–8 lines × 2) influxdb3_system_tables_common/src/tokens.rs:180 — influxdb3_system_tables_common/src/tokens.rs:180-186 | influxdb3_system_tables_common/src/tokens.rs:193-200 — 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.

D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1

Duplicated block (7 lines × 4) influxdb3_catalog/src/catalog/versions/v1.rs:356 — influxdb3_catalog/src/catalog/versions/v1.rs:356-362 | influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:33-39 | influxdb3_catalog/src/catalog/versions/v2.rs:1031-1037 | influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:381-387 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v1.rs` and `influxdb3_catalog/src/catalog/versions/v2.rs` as WHOLE FILES: this scan already matched 61 separate duplicated blocks between them, totalling at least 878 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1

Duplicated block (6–7 lines × 2) core/iox_query_influxql/src/show_retention_policies.rs:218 — core/iox_query_influxql/src/show_retention_policies.rs:218-223 | influxdb3_internal_api/src/query_executor.rs:199-205 — 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.

D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1

Duplicated block (6 lines × 5) influxdb3_system_tables_common/src/distinct_caches.rs:123 — influxdb3_system_tables_common/src/distinct_caches.rs:123-128 | influxdb3_system_tables_common/src/last_caches.rs:177-182 | influxdb3_system_tables_common/src/tables.rs:116-121 | influxdb3_system_tables_common/src/tokens.rs:180-185 | influxdb3_system_tables_common/src/tokens.rs:193-198 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1

Duplicated block (6 lines × 4) influxdb3_cache/src/last_cache/cache.rs:1055 — influxdb3_cache/src/last_cache/cache.rs:1055-1060 | influxdb3_cache/src/last_cache/cache.rs:1063-1068 | influxdb3_cache/src/last_cache/cache.rs:1071-1076 | influxdb3_cache/src/last_cache/cache.rs:1087-1092 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1

Duplicated block (5 lines × 6) influxdb3_system_tables_common/src/databases.rs:86 — influxdb3_system_tables_common/src/databases.rs:86-90 | influxdb3_system_tables_common/src/distinct_caches.rs:121-125 | influxdb3_system_tables_common/src/last_caches.rs:173-177 | influxdb3_system_tables_common/src/tables.rs:111-115 | influxdb3_system_tables_common/src/tokens.rs:174-178 | influxdb3_system_tables_common/src/tokens.rs:188-192 — before extracting anything, compare `influxdb3_system_tables_common/src/distinct_caches.rs` and `influxdb3_system_tables_common/src/last_caches.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1

Duplicated block (5 lines × 4) influxdb3_catalog/src/catalog/versions/v1/update.rs:482 — influxdb3_catalog/src/catalog/versions/v1/update.rs:482-486 | influxdb3_catalog/src/catalog/versions/v1/update.rs:567-571 | influxdb3_catalog/src/catalog/versions/v2/update.rs:659-663 | influxdb3_catalog/src/catalog/versions/v2/update.rs:905-909 — `influxdb3_catalog/src/catalog/versions/v1/update.rs` and `influxdb3_catalog/src/catalog/versions/v2/update.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 20 separate duplicated blocks between them, totalling at least 203 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.

D4 · Code Duplication · Duplicated block (64 lines × 2) · ×1

Duplicated block (64 lines × 2) core/influxdb2_client/src/models/query.rs:46 — core/influxdb2_client/src/models/query.rs:46-160 | core/influxdb2_client/src/models/user.rs:26-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (30 lines × 3) · ×1

Duplicated block (30 lines × 3) influxdb3_catalog/src/log/versions/v2/enterprise.rs:15 — influxdb3_catalog/src/log/versions/v2/enterprise.rs:15-44 | influxdb3_catalog/src/log/versions/v3/enterprise.rs:15-44 | influxdb3_catalog/src/log/versions/v4/enterprise.rs:15-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 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 3 times.

D4 · Code Duplication · Duplicated block (10 lines × 5) · ×1

Duplicated block (10 lines × 5) influxdb3_catalog/src/catalog/versions/v3/schema/node.rs:264 — influxdb3_catalog/src/catalog/versions/v3/schema/node.rs:264-273 | influxdb3_catalog/src/error/enterprise.rs:11-20 | influxdb3_catalog/src/log/versions/v2.rs:246-255 | influxdb3_catalog/src/log/versions/v3.rs:327-336 | influxdb3_catalog/src/log/versions/v4.rs:466-475 — before extracting anything, compare `influxdb3_catalog/src/log/versions/v2.rs` and `influxdb3_catalog/src/log/versions/v3.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1

Duplicated block (9 lines × 4) influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:351 — influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:351-359 | influxdb3_catalog/src/log/versions/v2.rs:874-882 | influxdb3_catalog/src/log/versions/v3.rs:1006-1014 | influxdb3_catalog/src/log/versions/v4.rs:1364-1372 — before extracting anything, compare `influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs` and `influxdb3_catalog/src/log/versions/v2.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1

Duplicated block (10 lines × 6) influxdb3_catalog/src/snapshot/versions/v1.rs:298 — influxdb3_catalog/src/snapshot/versions/v1.rs:298-307 | influxdb3_catalog/src/snapshot/versions/v1.rs:311-320 | influxdb3_catalog/src/snapshot/versions/v2.rs:341-350 | influxdb3_catalog/src/snapshot/versions/v2.rs:354-363 | influxdb3_catalog/src/snapshot/versions/v3.rs:365-374 | influxdb3_catalog/src/snapshot/versions/v3.rs:378-387 — before extracting anything, compare `influxdb3_catalog/src/snapshot/versions/v1.rs` and `influxdb3_catalog/src/snapshot/versions/v2.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1

Duplicated block (7 lines × 5) core/flightsql/src/cmd.rs:234 — core/flightsql/src/cmd.rs:234-249 | core/flightsql/src/cmd.rs:261-271 | core/flightsql/src/cmd.rs:276-282 | core/flightsql/src/cmd.rs:289-295 | core/flightsql/src/cmd.rs:302-308 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D5 · Coupling · Unstable project dml · ×1

Unstable project dml — dml has instability 0.83 with 1 dependents.

D5 · Coupling · Unstable project influxdb3_commands · ×1

Unstable project influxdb3_commands — influxdb3_commands has instability 0.86 with 1 dependents.

D5 · Coupling · Unstable project influxdb3_query_executor · ×1

Unstable project influxdb3_query_executor — influxdb3_query_executor has instability 0.96 with 1 dependents.

D5 · Coupling · Unstable project influxdb3_server · ×1

Unstable project influxdb3_server — influxdb3_server has instability 0.94 with 2 dependents.

D5 · Coupling · Unstable project influxdb3_system_tables · ×1

Unstable project influxdb3_system_tables — influxdb3_system_tables has instability 0.86 with 2 dependents.

D5 · Coupling · Unstable project influxdb3_system_tables_common · ×1

Unstable project influxdb3_system_tables_common — influxdb3_system_tables_common has instability 0.83 with 1 dependents.

D5 · Coupling · Unstable project influxdb_iox_client · ×1

Unstable project influxdb_iox_client — influxdb_iox_client has instability 0.86 with 1 dependents.

D5 · Coupling · Unstable project iox_v1_query_api · ×1

Unstable project iox_v1_query_api — iox_v1_query_api has instability 0.91 with 1 dependents.

D5 · Coupling · Unstable project object_store_mem_cache · ×1

Unstable project object_store_mem_cache — object_store_mem_cache has instability 0.88 with 1 dependents.

D5 · Coupling · Unstable project service_grpc_flight · ×1

Unstable project service_grpc_flight — service_grpc_flight has instability 0.92 with 1 dependents.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 504 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

Minor — 184 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×132

Orphaned file influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/log/versions/v2/conversion.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_test_helpers/src/object_store/mock.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/table.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_types/src/http.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/cache.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/format/records/types.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/ops/cache.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/user.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/format/records/role.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_telemetry/src/store.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_startup/src/env_compat.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/column.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/events.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/format/records/user.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/ops/node.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/object_store/versions/v2.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/trigger.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_authz/src/permissions/tests.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/format/records/table.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_authz/src/authorizer.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/format/records/types/tests.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/catalog/versions/v3/schema/node.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_catalog/src/snapshot/versions/v4.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file influxdb3_py_api/src/logging.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 107 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×30

Interpolated log message defeats structured logging core/trace/src/lib.rs:39 — `info!` at line 39 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/service_grpc_flight/src/lib.rs:905 — `warn!` at line 905 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/service_grpc_flight/src/lib.rs:909 — `warn!` at line 909 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/schema/src/lib.rs:666 — `warn!` at line 666 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_v1_query_api/src/handler.rs:158 — `warn!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query_params/src/params.rs:520 — `warn!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/statistics/aggregate_per_plan.rs:128 — `trace!` at line 128 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/statistics/aggregate_per_plan.rs:147 — `trace!` at line 147 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/statistics/aggregate_per_plan.rs:210 — `trace!` at line 210 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/provider/deduplicate.rs:190 — `trace!` at line 190 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/provider/progressive_eval.rs:210 — `trace!` at line 210 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/provider/progressive_eval.rs:223 — `trace!` at line 223 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/provider/progressive_eval.rs:331 — `trace!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/provider/progressive_eval.rs:373 — `trace!` at line 373 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:87 — `trace!` at line 87 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:159 — `trace!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:235 — `trace!` at line 235 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/extract_ranges.rs:265 — `trace!` at line 265 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/lexical_range.rs:386 — `trace!` at line 386 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/physical_optimizer/sort/regroup_files.rs:113 — `trace!` at line 113 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/exec/context.rs:607 — `debug!` at line 607 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/exec/split.rs:427 — `debug!` at line 427 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/iox_query/src/exec/split.rs:450 — `debug!` at line 450 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/influxdb_iox_client/src/client/batched_write.rs:158 — `error!` at line 158 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging core/influxdb_iox_client/src/client/batched_write.rs:233 — `error!` at line 233 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
+ 5 more in this group — see findings.md.

X10 · Duplicated predicate · Duplicated predicate · ×7

Duplicated predicate influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:285 — `contains_all_resource_indicator && names.len() > 1` appears character-identically in 2 files — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs, influxdb3_catalog/src/catalog/versions/v2/enterprise.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate influxdb3_catalog/src/catalog/versions/v1.rs:1148 — `create_database.database_id != schema.id || create_database.database_name != schema.name` appears character-identically in 2 files — influxdb3_catalog/src/catalog/versions/v1.rs, influxdb3_catalog/src/catalog/versions/v2.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate influxdb3_catalog/src/log/versions/v2.rs:811 — `cron_schedule.is_empty() || Schedule::from_str(cron_schedule).is_err()` appears character-identically in 3 files — influxdb3_catalog/src/log/versions/v2.rs, influxdb3_catalog/src/log/versions/v3.rs, influxdb3_catalog/src/log/versions/v4.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate influxdb3_catalog/src/catalog/versions/v2/enterprise.rs:579 — `db.deleted || db.hard_delete_time.is_some()` appears character-identically in 3 files — influxdb3_catalog/src/catalog/versions/v2/enterprise.rs, influxdb3_catalog/src/catalog/versions/v2/update.rs, influxdb3_catalog/src/catalog/versions/v3/catalog.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate influxdb3_catalog/src/catalog/versions/v2.rs:3196 — `name && v >= next_auto_field_family_name` appears character-identically in 2 files — influxdb3_catalog/src/catalog/versions/v2.rs, influxdb3_catalog/src/catalog/versions/v3/schema/table.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/iox_query/src/physical_optimizer/sort/order_union_sorted_inputs.rs:2345 — `plan.as_any().downcast_ref::<UnionExec>() && union_exec.inputs().len() == 1` appears character-identically in 2 files — core/iox_query/src/physical_optimizer/sort/order_union_sorted_inputs.rs, core/iox_query/src/physical_optimizer/sort/order_union_sorted_inputs_for_constants.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate influxdb3_catalog/src/catalog/versions/v1/enterprise.rs:445 — `self.0.len() == 1 && self.0.contains(mode)` appears character-identically in 2 files — influxdb3_catalog/src/catalog/versions/v1/enterprise.rs, influxdb3_catalog/src/catalog/versions/v2/enterprise.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

M4 · Documentation accuracy · README/code drift · ×2

README/code drift core/catalog_cache/README.md:2 — core/catalog_cache/README.md links to `../docs/catalog_service.md`, but `core/docs/catalog_service.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift core/iox_query/README.md:3 — core/iox_query/README.md links to `../docs/query_processing.md`, but `core/docs/query_processing.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

X7 · Silent fallback defaults · Silent fallback default on Err · ×2

Silent fallback default on Err core/iox_query_influxql/src/plan/planner/select.rs:107 — `fields_to_exprs_no_nulls` turns every `Err` into `false` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err influxdb3/src/commands/serve/cli_params.rs:158 — `capture_cli_params` turns every `Err` into `"{}".to_string()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 2 of 88 project(s) overshoot their size bounds, lowering Project Cohesion to 9.5/10. The most over is `influxdb3_catalog` (66506 LoC, 479 module-visible types across 21 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D31 · IaC & Container Security · Low IaC · ×1

REDACTED

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 132 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: influxdb3_catalog/src/catalog/versions/v1/enterprise.rs, influxdb3_catalog/src/log/versions/v2/conversion.rs, influxdb3_test_helpers/src/object_store/mock.rs, influxdb3_catalog/src/catalog/versions/v3/schema/table.rs, influxdb3_catalog/src/catalog/versions/v3/schema/cache.rs, influxdb3_catalog/src/format/records/types.rs, influxdb3_catalog/src/catalog/versions/v3/ops/cache.rs, influxdb3_catalog/src/catalog/versions/v3/schema/user.rs (and 124 more) (148 orphaned of 716 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 716 of the 940 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, 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.

P6 · Release Hygiene · No changelog · ×1

No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `.serve_connection(` (influxdb3_server/src/lib.rs:297).

X9 · Subsumed condition operand · Subsumed condition operand · ×1

Subsumed condition operand influxdb3/tests/cli/mod.rs:1547 — `err.contains("File not found")` can never decide this `||` — every value satisfying `err.contains("File not found")` also satisfies `err.contains("not found")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.

Minor — 21 finding(s)

D12 · Dependency Hygiene · Outdated · ×21

Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: clap_builder — `clap_builder` is locked at 4.6.0 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.5.47"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap_builder` and commit the updated REDACTED.
Outdated: crc32fast — `crc32fast` is locked at 1.5.1 but 1.5.3 is the current stable release on crates.io, and it already satisfies the `"1.2.0"` requirement declared in influxdb3_catalog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crc32fast` and commit the updated REDACTED.
Outdated: croaring — `croaring` is locked at 2.7.0 but 2.8.0 is the current stable release on crates.io, and it already satisfies the `"2.6.0"` requirement declared in core/data_types/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p croaring` and commit the updated REDACTED.
Outdated: hyper — `hyper` is locked at 1.11.1 but 1.12.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in influxdb3_processing_engine/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hyper` and commit the updated REDACTED.
Outdated: hyper-util — `hyper-util` is locked at 0.1.20 but 0.1.21 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in influxdb3_server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hyper-util` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.14.1 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2.11.0"` requirement declared in influxdb3_authz/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: inventory — `inventory` is locked at 0.3.24 but 0.3.25 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in influxdb3_catalog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p inventory` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: ordered-float — `ordered-float` is locked at 5.5.0 but 5.5.1 is the current stable release on crates.io, and it already satisfies the `"5"` requirement declared in core/data_types/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ordered-float` and commit the updated REDACTED.
Outdated: proptest — `proptest` is locked at 1.11.0 but 1.12.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in core/influxdb_line_protocol/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p proptest` and commit the updated REDACTED.
Outdated: rustls — `rustls` is locked at 0.23.45 but 0.23.46 is the current stable release on crates.io, and it already satisfies the `"0.23"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustls` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.127"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: serde_with — `serde_with` is locked at 3.22.0 but 3.24.0 is the current stable release on crates.io, and it already satisfies the `"3.8.1"` requirement declared in influxdb3_catalog/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_with` and commit the updated REDACTED.
Outdated: siphasher — `siphasher` is locked at 1.0.3 but 1.0.4 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in influxdb3_write/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p siphasher` and commit the updated REDACTED.
Outdated: smallvec — `smallvec` is locked at 1.16.0 but 1.16.4 is the current stable release on crates.io, and it already satisfies the `"1.15.1"` requirement declared in core/influxdb2_client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p smallvec` and commit the updated REDACTED.
Outdated: sysinfo — `sysinfo` is locked at 0.39.5 but 0.39.6 is the current stable release on crates.io, and it already satisfies the `"0.39.5"` requirement declared in influxdb3_clap_blocks/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p sysinfo` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.1 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.52.2"` requirement declared in cli_types/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: tokio-util — `tokio-util` is locked at 0.7.19 but 0.7.20 is the current stable release on crates.io, and it already satisfies the `"0.7.13"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio-util` and commit the updated REDACTED.
Outdated: ureq — `ureq` is locked at 3.4.0 but 3.5.0 is the current stable release on crates.io, and it already satisfies the `"3.3.0"` requirement declared in core/iox_query_udf/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ureq` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.26.0 but 1.29.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in influxdb3/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2f444258fa464dd8844e09a6323a081d/history.json --exit-code 0 --source .	10	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2f444258fa464dd8844e09a6323a081d/tree.json --exit-code 0 --source .	1	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude .arrow --exclude .avro --exclude .csv --exclude .dat --exclude .db --exclude .feather --exclude .geojson --exclude .h5 --exclude .hdf5 --exclude .jsonl --exclude .log --exclude .ndjson --exclude .npy --exclude .npz --exclude .orc --exclude .parquet --exclude .pickle --exclude .pkl --exclude .psv --exclude .sqlite --exclude .sqlite3 --exclude .tfrecord --exclude .tsv --exclude .txt --exclude core/trace_exporters/src/thrift .	18	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .	19	artifacts/raw/osv-scanner.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	10	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — 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.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — 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.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — 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.	0	—
D43 · Malicious Dependencies	osv-scanner	—	osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .	0	artifacts/raw/osv-scanner.json

Run 01a17522-fbee-76c9-a085-d545c4ec0f76 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 79% · Strong ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 54% · Adequate · gated by M2 ·

At a glance — Readiness · 69% · Adequate ·

At a glance — Security · 74% · Adequate · gated by D28, D29, D36 ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Performance · 91% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts