Public report of getkyo/kyo, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 15:03 UTC · Survey ID cd_da6489ff4aa34bc3bebe39c9c30e3b9c
getkyo/kyo
Measured 14 November 2026, 15:02 UTC, at code version 31a7445
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 373,300 lines of product code in 89 projects, tests not counted · Estimated rebuild effort: about 6.7 person-years · Weakest lens: Code Health, 19
Findings by how serious they are
112 critical2393 serious123 minor
10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 15:02 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
75of 75 dimensions measured by tools.
2597of 2628 findings point to an exact file and line, so you can open each one in the code. The other 31 concern the repository as a whole, such as missing documentation.
75dimensions across 6 lenses, read from 373,300 lines of product code in 89 projects.
getkyo/kyo falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 41 out of 100 and is rated Weak, and 110 of its 112 critical findings are security problems.
Code Health, at 19, is the weakest lens and counts most in the score. The best first steps are adding type checking and splitting the oversized files, each worth about 3 points. Raising Code Health to 70 would lift the score to about 60.
Sixty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Sixteen secrets can leak from the build pipeline, and ten weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, limiting each secret to its own step and fixing the weaknesses the scanner points to would close these risks. Passing outside input through environment variables would fix the eight pipeline steps that put outside input straight into a shell command, and the four passwords or keys in the code's history need replacing, with the old ones switched off. The two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 373,300 lines, about €980,000 to rebuild.
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 forThe 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.
If Code Health rose from 19 to 70, the lowest score rated Strong, the score would rise from 41 to about 60.
Code composition: what the lines of code are
Product code 39%Tests 61%
New since the last survey: 544 findings
These 544 critical or serious findings weren't in the previous survey, on 27 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: kyo/Tag.scala kyo-data/shared/src/main/scala/kyo/Tag.scala
God Classes · FileTooLong: kyo/Markdown.scala kyo-markdown/shared/src/main/scala/kyo/Markdown.scala
God Classes · TooManyMethods: Slack kyo-slack/shared/src/main/scala/kyo/Slack.scala
Code Duplication · Near-duplicate member pair (75 shared lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala
Code Duplication · Near-duplicate member pair (29 shared lines) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala
Code Duplication · Edited copy of a member (35 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala
Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) kyo-discord/shared/src/main/scala/kyo/Discord.scala
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala
Code Duplication · Edited copy of a member (357 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala
Code Duplication · Edited copy of a member (66 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala
Code Duplication · Edited copy of a member (72 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala
Code Duplication · Edited copy of a member (72 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala
Code Duplication · Edited copies of one member (3 members, 72+ corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala
Code Duplication · Edited copies of one member (3 members, 68+ corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala
Code Duplication · Edited copy of a member (71 corresponding lines) kyo-aeron/shared/src/main/scala/kyo/Topic.scala
Code Duplication · Edited copy of a member (47 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala
Code Duplication · Edited copy of a member (78 corresponding lines) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala
Code Duplication · Edited copy of a member (51 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala
Code Duplication · Edited copy of a member (37 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala
Code Duplication · Edited copy of a member (54 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala
Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala
Code Duplication · Edited copy of a member (33 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala
Code Duplication · Edited copy of a member (33 corresponding lines) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala
Code Duplication · Edited copy of a member (121 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala
Code Duplication · Edited copy of a member (41 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala
Code Duplication · Edited copy of a member (41 corresponding lines) kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kyo-data/shared/src/main/scala/kyo/Record.scala
Code Duplication · Edited copy of a member (47 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala
Code Duplication · Edited copy of a member (55 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala
Code Duplication · Edited copy of a member (39 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala
Code Duplication · Edited copy of a member (43 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala
Code Duplication · Edited copy of a member (44 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala
Code Duplication · Edited copy of a member (21 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala
Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala
Code Duplication · Edited copy of a member (34 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala
Code Duplication · Edited copy of a member (24 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala
Code Duplication · Edited copy of a member (30 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala
Code Duplication · Edited copy of a member (34 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala
Code Duplication · Edited copy of a member (59 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala
Code Duplication · Edited copy of a member (33 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala
Code Duplication · Edited copy of a member (13 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala
Code Duplication · Edited copy of a member (15 corresponding lines) kyo-core/shared/src/main/scala/kyo/Queue.scala
Code Duplication · Edited copy of a member (18 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala
Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/SuspensionBench.scala
Code Duplication · Edited copy of a member (24 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ExtendedQueryExchange.scala
Code Duplication · Edited copy of a member (33 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala
Code Duplication · Edited copy of a member (8 corresponding lines) kyo-ui/shared/src/main/scala/kyo/Chart.scala
Code Duplication · Edited copy of a member (25 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (23 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala
Code Duplication · Edited copy of a member (26 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala
Code Duplication · Edited copy of a member (55 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala
Code Duplication · Edited copy of a member (20 corresponding lines) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala
Code Duplication · Edited copy of a member (28 corresponding lines) kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala
Code Duplication · Edited copy of a member (25 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala
Code Duplication · Edited copy of a member (33 corresponding lines) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala
Code Duplication · Edited copy of a member (27 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala
Code Duplication · Edited copy of a member (29 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala
Code Duplication · Edited copy of a member (23 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala
Code Duplication · Edited copies of one member (4 members, 34+ corresponding lines) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala
Code Duplication · Edited copy of a member (25 corresponding lines) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kyo-telegram/shared/src/main/scala/kyo/Telegram.scala
Code Duplication · Edited copy of a member (13 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/Json.scala
Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala
Code Duplication · Edited copy of a member (28 corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala
Code Duplication · Edited copy of a member (20 corresponding lines) kyo-core/shared/src/main/scala/kyo/Fiber.scala
Code Duplication · Edited copy of a member (18 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala
Code Duplication · Edited copy of a member (30 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala
Code Duplication · Edited copy of a member (17 corresponding lines) kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/UIWindow.scala
Code Duplication · Edited copy of a member (22 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala
Code Duplication · Edited copy of a member (16 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala
Code Duplication · Edited copy of a member (13 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala
Code Duplication · Edited copy of a member (18 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala
Code Duplication · Edited copy of a member (25 corresponding lines) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala
We compare 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: 151 findings
These 151 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one. The first 100 are listed here.
Exception handling · Swallowed exception (caught, then discarded) kyo-net/jvm/src/main/scala/kyo/net/internal/JdkSslEngine.scala
Rebuild cost: about €980,000 · Estimate
Cost to rebuild
€320,000 to €1,600,000, for 5,412 to 17,170 hours of work, about 6.7 person-years for 4 to 13 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.7 at a score of 41. 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: 373,300 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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.
1
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 3 points · Medium effort · Type Safety
2
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 3 points · Medium effort · Large Files
3
Resolve the 11 finding(s) in Cyclomatic Complexity.
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 €980,000 to build again, about 6.7 person-years of work. Its weakest lens is Code Health, at 19 (Critical). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.2 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 10% on every change. The history of the code shows how much it changes: about 577,084 lines over the last 90 days, which is about 2,340,396 lines a year. At that pace, the extra work comes to an estimated 267.4 to 1604.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
At a glance — Code Health · 19% · Critical · gated by D2, R1, R2, R3, X4, X5 ·
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
A05:2025 — Injection
106
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
A07:2025 — Authentication Failures
5
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Resolve the 11 finding(s) in Cyclomatic Complexity.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off.
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
Resolve the 2 `MySQL` spells `SQL` where 18 names in the project spell it `Sql` finding(s) in Naming Consistency — start with ContainerPredef.scala (2).
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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 — 112
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 — 2393
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 — 123
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
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
This survey 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. All 75 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 75 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2597 of 2628 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 or a scanner, 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
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 — We 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 (.scala) 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.
D11 Test Reliability — not measured this run — We 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 (.scala) and this repository declares an sbt build (repository root, 2491 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We 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.
D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `kyo-actor/shared/src/main/scala/kyo/Actor.scala`, `kyo-actor/shared/src/main/scala/kyo/PubSub.scala`, `kyo-aeron/shared/src/main/scala/kyo/AeronDriver.scala`, `kyo-aeron/shared/src/main/scala/kyo/Topic.scala`, `kyo-ai/shared/src/main/scala/kyo/AI.scala`, … (+746 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/NativeFacade.scala, whose lifetimes are not modelled 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.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We 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. Subject: 3 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
ED5 Idempotency — not measured this run — We 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we 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), and artefact counts an order of magnitude off. 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.
X10 Duplicated predicate — not measured this run — We 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. 72 further occurrence(s) are not listed individually; the score already reflects all 112.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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 Dockerfile (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.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
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.
310 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClasspathOrchestrator.finalizeMerge at 314. A further 66 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 TreeShow.show at 78 — they are counted neither in the figure above nor in this dimension's score. 27 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeShow.scala (TreeShow.show at 78), kyo-http/shared/src/main/scala/kyo/HttpStatus.scala (HttpStatus.standard at 60), kyo-charset/shared/src/main/scala/kyo/internal/charset/Decoders.scala (Decoders.of at 46), kyo-system/shared/src/main/scala/kyo/Path.scala (Path.dispatch at 43), kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala (Idiom.term at 41), and 22 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.
+ 304 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with ClasspathOrchestrator.finalizeMerge (cyclomatic 314), TypeUnpickler.decodeTag (cyclomatic 159), CssStyleRenderer.renderProp (cyclomatic 124). — 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 3 together lifts Cyclomatic Complexity from 4.8 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 676 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 240 down to 240 or less in Cognitive Complexity — start with ClasspathOrchestrator.finalizeMerge (cognitive 583), Eval.apply (cognitive 359), CdpBackend.initUnscoped (cognitive 276). — 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 5 together lifts Cognitive Complexity from 2.7 to about 4.0/10, projected with the scoring formula itself and assuming each lands exactly at 240; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 111 TooManyMethods finding(s) in God Classes — start with CIO.scala (5), SchemaSerializer.scala (3), PathPlatformSpecific.scala (3). — One of this dimension's main actionable groups (111 warning-level).
Resolve the 97 FileTooLong finding(s) in God Classes — start with PathPlatformSpecific.scala (2), HttpContainerBackend.scala, Schema.scala. — One of this dimension's main actionable groups (97 warning-level).
Resolve the 9 MethodTooLong finding(s) in God Classes — start with JsonRpcEndpointImpl.scala (2), LspClientEngine.scala (2), LspEngine.scala (2). — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
482 duplicated block group(s) detected. 6.1 % of the production lines (22,938 of 373,300) are in a reported copy. A further 543 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 50 of the 1025 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.
Edited copy of a member (4 corresponding lines) · ×32kyo-core/shared/src/main/scala/kyo/Signal.scala:205
+ 232 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 53 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Kyo.scala (2), MysqlTemporalDecoder.scala (2), SqliteDialect.scala (2). — One of this dimension's main actionable groups (53 warning-level).
Resolve the 49 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with Markdown.scala (6), ClasspathOrchestrator.scala (3), RouteUtil.scala (2). — One of this dimension's main actionable groups (49 warning-level).
Resolve the 45 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Http1Parser.scala (5), FocusMacro.scala (2), REDACTED (2). — One of this dimension's main actionable groups (45 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ 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.
89 production modules (npm+sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 78 of the 89 (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).
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.
Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with MysqlDialect.scala, PosixHandle.scala, ShellBackend.scala. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
19 outdated direct sbt declarations. 32 of 41 direct declarations were graded against Maven Central (9 not published there, which is what a private Nexus or Artifactory artifact looks like, 0 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 29 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 19 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 3 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 12 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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.
Resolve the 53 Hotspot finding(s) in Churn × Complexity Hotspots — start with ProcessPlatformSpecific.scala (2), ReactiveUI.scala, HtmlRenderer.scala. — One of this dimension's main actionable groups (53 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.2 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
304 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is kyo-browser/shared/src/main/scala/kyo/Browser.scala. Counted over 1092 of the 1726 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
12 deducted task-comment markers across 373300 LoC (0.0/KLoC) → score 10.0. 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.
Resolve the 12 TodoComment finding(s) in Explicit Debt — start with LayerMacros.scala (5), CommandTest.scala, ProcessTest.scala. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
3 naming inconsistencies among 39 declarations measured against a convention their peers follow.
`MySQL` spells `SQL` where 18 names in the project spell it `Sql` · ×2kyo-pod/shared/src/main/scala/kyo/ContainerPredef.scala:346
`InitSSLExchange` spells `SSL` where 18 names in the project spell it `Ssl`kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/InitSSLExchange.scala:27
What to do
Resolve the 2 `MySQL` spells `SQL` where 18 names in the project spell it `Sql` finding(s) in Naming Consistency — start with ContainerPredef.scala (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `InitSSLExchange` spells `SSL` where 18 names in the project spell it… finding(s) in Naming Consistency — start with InitSSLExchange.scala. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the nameskyo-browser/shared/src/main/resources/kyo/Readability.js:25
What to do
Resolve the 2 redundant comment finding(s) in Comment Value — start with Readability.js (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (sbt) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
106 finding(s): 0 critical, 104 high, 2 medium, 0 low. 51 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 666 file(s) — `kyo-actor/shared/src/main/scala/kyo/Actor.scala`, `kyo-actor/shared/src/main/scala/kyo/PubSub.scala`, `REDACTED` (line 14, line 35), `kyo-aeron/shared/src/main/c/kyo_aeron.h` (line 4, line 20, line 21, …), `kyo-aeron/shared/src/main/scala/kyo/AeronDriver.scala`, … (+661 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 7 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
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 REDACTED finding(s) charged to Static Analysis (SAST) — the other 51 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (68 issue-level, 17 of them charged here).
Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). — One of this dimension's main actionable groups (16 issue-level).
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
11 of 1092 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is kyo-prelude/shared/src/main/scala/kyo/Pipe.scala. Counted over 1092 of the 1726 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with Pipe.scala, AbortCombinators.scala. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with Sink.scala, ChunkBench.scala, TypeMapBench.scala. — One of this dimension's main actionable groups (9 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.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
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.
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
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.
Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`loadLoadFence` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-core/js-wasm/src/main/scala/kyo/VarHandle.scala:4
`parkNanos` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:12
`unpark` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:13
`zeroVoid` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:717
`zeroInt` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:720
`zeroLong` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:721
`zeroFloat` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:722
`zeroDouble` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:723
`zeroBoolean` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:724
`beginSlice` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:114
`endSlice` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:116
`deadline` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — kyo-kernel/jvm-native/src/main/scala/kyo/kernel/internal/Safepoint.scala:209
`init` has an empty body — confirm it's an intentional no-op and not an unfinished method. — kyo-core/js-wasm/src/main/scala/kyo/scheduler/SchedulerDiagnostics.scala:8
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×15) — kyo-core/shared/src/test/scala/kyo/ChannelTest.scala:174, kyo-core/shared/src/test/scala/kyo/ChannelTest.scala:220, kyo-core/shared/src/test/scala/kyo/ScopeTest.scala:1614, …
`mmapReadOnly`'s body only throws UnsupportedOperationException — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:49
`mmapReadWrite`'s body only throws UnsupportedOperationException — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:52
`unsafe` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — kyo-data/shared/src/main/scala/kyo/Fields.scala:171, kyo-data/shared/src/main/scala/kyo/Fields.scala:184
`ensureInitialized` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — kyo-ffi/it/jvm/src/main/scala/kyo/ffi/it/SystemLibraryImpl.scala:9, kyo-ffi/it/native/src/main/scala/kyo/ffi/it/SystemLibraryImpl.scala:8
`onSpinWait` has an empty body — confirm it's an intentional no-op and not an unfinished method. — kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:11
A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead. (×2) — kyo-scheduler/js-wasm/src/main/scala/kyo/scheduler/InternalClock.scala:12, kyo-scheduler/jvm/src/main/scala/kyo/scheduler/top/Console.scala:5
`stop` has an empty body — confirm it's an intentional no-op and not an unfinished method. — kyo-scheduler/js-wasm/src/main/scala/kyo/scheduler/InternalClock.scala:17
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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's code 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.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:16
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:7
What to do
Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `npm`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/NativeManifestPlatform.scala:71
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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.
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 each language's code 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?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 5 plain JS — the untyped files are kyo-browser/shared/src/main/resources/kyo/Readability.js, REDACTED, kyo-charset/shared/src/test/vectors/wpt-encoding/gb18030-decoder.any.js, kyo-charset/shared/src/test/vectors/wpt-encoding/iso-2022-jp-decoder.any.js, kyo-discord/shared/src/test/spacebar/tls-proxy.js.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
REDACTED:223 · REDACTED:241 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:223
kyo-browser/shared/src/main/resources/kyo/Readability.js:2150 · kyo-browser/shared/src/main/resources/kyo/Readability.js:2161 — 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. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2150
kyo-browser/shared/src/main/resources/kyo/Readability.js:2243 · kyo-browser/shared/src/main/resources/kyo/Readability.js:2253 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2243
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
_grabArticle has cyclomatic complexity 103 and cognitive complexity 232; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1031
(anonymous) has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1637
shouldRemoveNode has cyclomatic complexity 25 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2555
(anonymous) has cyclomatic complexity 24 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2335
(anonymous) has cyclomatic complexity 22 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2444
collapseWhitespace has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:456
_getArticleTitle has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:572
Readability has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:27
_markDataTables has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:2271
(anonymous) has cyclomatic complexity 12 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1917
(anonymous) has cyclomatic complexity 12 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — kyo-browser/shared/src/main/resources/kyo/Readability.js:697
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
kyo-browser/shared/src/main/resources/kyo/Readability.js has 2496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1
REDACTED has 825 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.3 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add a test runner (vitest / jest / playwright) and eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's Scala source and the Java beside it: 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 builds on an HTTP-server library (build.sbt:2168 — depends on `play`) but serves no HTTP of its own: its production source starts no server (no `newServerAt`/`bindAndHandle`, server builder, `Server.serve`, `Http.serve`, tapir server interpreter or Netty HTTP pipeline), declares no application one runs (no Play application, servlet, cask `MainRoutes`, `HttpApp` or twitter-server), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library.
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.
an `X509TrustManager` whose `checkServerTrusted` accepts every chain is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on. — kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1878
What to do
Stop accepting every TLS certificate: delete the trust manager whose `checkServerTrusted` is empty, the `HostnameVerifier` that returns `true`, `InsecureTrustManagerFactory` / `NoopHostnameVerifier` and `acceptAnyCertificate`, and trust a self-signed or private server by giving the client a trust store holding its CA — never by switching verification off.
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.
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.
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.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×3) — kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformDigest.scala:63, kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:85, kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/ZipHandlePlatform.scala:95
`Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. (×2) — kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:29, kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:80
`Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.collect` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — kyo-bench/src/main/scala/kyo/bench/arena/Registry.scala:32
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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.
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.
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 unescaped6.9 / 10Adequate✓ Tool-verified
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.
`pageCacheHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1549
`noscript.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — kyo-browser/shared/src/main/resources/kyo/Readability.js:1928
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.
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 `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. Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements 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.
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.
`case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×32) — project/CallbackShapesGen.scala:78, kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1191, kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformDigest.scala:82, …
`case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — project/CryptoDifferentialGen.scala:117, project/CryptoDifferentialGen.scala:172, kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1648
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:539, kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:419, kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:885
`case ex: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:754
`case scala.util.control.NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:267
What to do
Swallowed exception (caught, then discarded)
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.
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.
`trace` at line 50 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.trace("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:50
`trace` at line 53 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.trace("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:53
`debug` at line 56 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:56
`debug` at line 59 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:59
`info` at line 62 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:62
`info` at line 65 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:65
`warn` at line 68 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:68
`warn` at line 71 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:71
`error` at line 74 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:74
`error` at line 77 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix. — kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:77
Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
No build over this repository's 1700 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
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.
Unscored — 2 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 — 40 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.
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 — 50 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 — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, a MongoDB or Cassandra driver, JDBC) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported 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, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Slick table or in a SQL migration's CREATE TABLE or ALTER TABLE — and no database or data-store client (Slick, Doobie, Quill, ScalikeJDBC, Anorm, Skunk, JDBC, MongoDB, Cassandra, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~581280 lines of test source are present (.scala) 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 .scala 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.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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"]`.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), 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) — 751 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (4 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 2611 value object(s); 95 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a top-level kyo-examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 2 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 3 test file(s) reach none of 2 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Scala and Python were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; 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
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — 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.
Orphaned knowledge kyo-prelude/shared/src/main/scala/kyo/Pipe.scala: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 kyo-combinators/shared/src/main/scala/kyo/AbortCombinators.scala: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.
TLS certificate validation disabled kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1878— an `X509TrustManager` whose `checkServerTrusted` accepts every chain is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the override so the JVM's default trust manager and hostname check apply — that is what `SSLContext.getDefault`, Netty's `SslContextBuilder.forClient()`, sttp, Play WS and ssl-config use when nothing is set. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `KeyStore` and build a `TrustManagerFactory` from it (ssl-config: `trustManager.stores`), which keeps the chain and hostname checks on.
TooManyMethods: Browser kyo-browser/shared/src/main/scala/kyo/Browser.scala:152— TooManyMethods — 192 methods. The bar is 30 methods; this is 162 over it, 6.40× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: YamlReader kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:10— TooManyMethods — 142 methods. The bar is 30 methods; this is 112 over it, 4.73× 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: ChunkBench kyo-bench/src/main/scala/kyo/bench/ChunkBench.scala:11— TooManyMethods — 133 methods. The bar is 30 methods; this is 103 over it, 4.43× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Kyo kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:14— TooManyMethods — 133 methods. The bar is 30 methods; this is 103 over it, 4.43× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: HttpContainerBackend kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:29— TooManyMethods — 119 methods. The bar is 30 methods; this is 89 over it, 3.97× 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: Style kyo-ui/shared/src/main/scala/kyo/Style.scala:675— TooManyMethods — 112 methods. The bar is 30 methods; this is 82 over it, 3.73× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ShellBackend kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:29— TooManyMethods — 109 methods. The bar is 30 methods; this is 79 over it, 3.63× 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: Schema kyo-schema/shared/src/main/scala/kyo/Schema.scala:55— TooManyMethods — 100 methods. The bar is 30 methods; this is 70 over it, 3.33× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Term kyo-sql/shared/src/main/scala/kyo/Sql.scala:405— TooManyMethods — 98 methods. The bar is 30 methods; this is 68 over it, 3.27× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Idiom kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala:67— TooManyMethods — 98 methods. The bar is 30 methods; this is 68 over it, 3.27× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Runtime kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:181— TooManyMethods — 95 methods. The bar is 30 methods; this is 65 over it, 3.17× 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: NioIoDriver kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:38— TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× 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: PollerIoDriver kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:72— TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× 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: ImapSession kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:25— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: HtmlRenderer kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:8— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: UI kyo-ui/shared/src/main/scala/kyo/UI.scala:52— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: IoUringDriver kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:59— TooManyMethods — 71 methods. The bar is 30 methods; this is 41 over it, 2.37× 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: HttpClient kyo-http/shared/src/main/scala/kyo/HttpClient.scala:47— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: YamlWriter kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:9— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.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.
TooManyMethods: RouteUtil kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:18— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× 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: PosixTransport kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:61— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× 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: ContainerBackend kyo-pod/shared/src/main/scala/kyo/internal/ContainerBackend.scala:15— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× 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: UpcallBridge kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:32— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Parse kyo-parse/shared/src/main/scala/kyo/Parse.scala:38— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: MsgPackReader kyo-schema-msgpack/shared/src/main/scala/kyo/internal/msgpack/MsgPackReader.scala:25— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. This type is on a published API surface — a MiMa binary-compatibility gate (build.sbt) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
FileTooLong: internal/HttpContainerBackend.scala kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala— FileTooLong — 2330 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1830 over it, 4.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: kyo/Schema.scala kyo-schema/shared/src/main/scala/kyo/Schema.scala— FileTooLong — 2314 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1814 over it, 4.63× 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: kyo/Tasty.scala kyo-tasty/shared/src/main/scala/kyo/Tasty.scala— FileTooLong — 2306 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1806 over it, 4.61× 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: internal/FocusMacro.scala kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala— FileTooLong — 2290 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1790 over it, 4.58× 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: kyo/Browser.scala kyo-browser/shared/src/main/scala/kyo/Browser.scala— FileTooLong — 2179 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1679 over it, 4.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: internal/SchemaSerializer.scala kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala— FileTooLong — 2153 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1653 over it, 4.31× 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: internal/ShellBackend.scala kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala— FileTooLong — 2132 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1632 over it, 4.26× 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: query/ClasspathOrchestrator.scala kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala— FileTooLong — 2053 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1553 over it, 4.11× 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: yaml/YamlReader.scala kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala— FileTooLong — 2028 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1528 over it, 4.06× 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: internal/HtmlRenderer.scala kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala— FileTooLong — 2017 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1517 over it, 4.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: kyo/LspHandler.scala kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala— FileTooLong — 1994 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1494 over it, 3.99× 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: kyo/Discord.scala kyo-discord/shared/src/main/scala/kyo/Discord.scala— FileTooLong — 1798 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: Patch (831-2334). The bar is 500 significant lines; this is 1298 over it, 3.60× 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: kyo/Sql.scala kyo-sql/shared/src/main/scala/kyo/Sql.scala— FileTooLong — 1660 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1160 over it, 3.32× 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: internal/FromExprDerived.scala kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala— FileTooLong — 1563 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1063 over it, 3.13× 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: lsp/LspContentSchemas.scala kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspContentSchemas.scala— FileTooLong — 1494 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 994 over it, 2.99× 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: kyo/Readability.js kyo-browser/shared/src/main/resources/kyo/Readability.js— FileTooLong — 1484 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 984 over it, 2.97× 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: kyo/Kyo.scala kyo-kernel/shared/src/main/scala/kyo/Kyo.scala— FileTooLong — 1447 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 947 over it, 2.89× 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: kyo/Container.scala kyo-pod/shared/src/main/scala/kyo/Container.scala— FileTooLong — 1441 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 941 over it, 2.88× 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: classfile/ClassfileUnpickler.scala kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala— FileTooLong — 1432 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 932 over it, 2.86× 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: posix/PosixTransport.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala— FileTooLong — 1424 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 924 over it, 2.85× 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: server/RouteUtil.scala kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala— FileTooLong — 1390 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 890 over it, 2.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: snapshot/SnapshotReader.scala kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala— FileTooLong — 1377 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 877 over it, 2.75× 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: posix/PollerIoDriver.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala— FileTooLong — 1348 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 848 over it, 2.70× 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: posix/IoUringDriver.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala— FileTooLong — 1326 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 826 over it, 2.65× 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: internal/NioIoDriver.scala kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala— FileTooLong — 1325 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 825 over it, 2.65× 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.
Hotspot: kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:498— kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 95 in ReactiveUI.dispatchToElement at line 498. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:662— kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in HtmlRenderer.renderElementAttrs at line 662. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:732— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in FocusMacro.desugarProductConfig at line 732. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:268— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in JsonRpcEndpointImpl.initEngine at line 268. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-flow/shared/src/main/scala/kyo/Flow.scala kyo-flow/shared/src/main/scala/kyo/Flow.scala:1318— kyo-flow/shared/src/main/scala/kyo/Flow.scala changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 76 in Flow.run at line 1318. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-flow/shared/src/main/scala/kyo/Flow.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:300— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in HttpContainerBackend.create at line 300. 1 of those changes was a fix/bug commit, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2011— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in IoUringDriver.complete at line 2011. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:111— kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in UnsafeServerDispatch.serveH1 at line 111. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-schema-json/shared/src/main/scala/kyo/Json.scala kyo-schema-json/shared/src/main/scala/kyo/Json.scala:315— kyo-schema-json/shared/src/main/scala/kyo/Json.scala changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in JsonSchema.writeJsonSchema at line 315. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-schema-json/shared/src/main/scala/kyo/Json.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:960— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in JsTransport.upgradeConnection at line 960. 3 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:657— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in HttpClientBackend.buildBodyStream at line 657. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1647— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in PosixTransport.upgradeRole at line 1647. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:290— kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in SchemaSerializer.writeWithTransforms at line 290. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:612— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in DomBackend.setupEventDelegation at line 612. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:422— kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in NodePathLock.acquire at line 422. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala:251— kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 124 in CssStyleRenderer.renderProp at line 251. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:403— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in FromExprDerived.resolveBindings at line 403. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:370— kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in TagMacro.deriveDB at line 370. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala:362— kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Completion.sseFragments at line 362. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:2283— kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in ShellBackend.mapError at line 2283. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:472— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in JsonReader.readQuotedStringWithEscapes at line 472. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:731— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in RouteUtil.encodeStreamBodyValueWith at line 731. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2605— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in PollerIoDriver.dispatchCmd at line 2605. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala:29— kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in JsonRpcEnvelopeSchema.envelopeSchema at line 29. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:736— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in NioTransport.startTlsHandshake at line 736. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 23:08:43 -03:00' --until='2026-11-12 23:08:43 -03:00' --full-history --no-merges -- kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (7 lines × 2) kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:8-14 | kyo-bench/src/main/scala/kyo/bench/arena/TMapSingleKeyBench.scala:8-14 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:397— kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:397-403 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:417-423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:132— kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:132-139 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:185-191 — 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) kyo-data/shared/src/main/scala/kyo/Dict.scala:642— kyo-data/shared/src/main/scala/kyo/Dict.scala:642-648 | kyo-data/shared/src/main/scala/kyo/OrderedDict.scala:665-671 — 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) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:139— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:139-145 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:145-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.
Duplicated block (7 lines × 2) kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/Orchestrator.scala:270— kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/Orchestrator.scala:270-276 | kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/Orchestrator.scala:285-291 — 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) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:310— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:310-316 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:424-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-flow/shared/src/main/scala/kyo/Flow.scala:742— kyo-flow/shared/src/main/scala/kyo/Flow.scala:742-748 | kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:953-959 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-flow/shared/src/main/scala/kyo/Flow.scala:742` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-http/shared/src/main/scala/kyo/FlagSync.scala:43— kyo-http/shared/src/main/scala/kyo/FlagSync.scala:43-49 | kyo-http/shared/src/main/scala/kyo/FlagSync.scala:71-77 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/FlagSync.scala:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1466— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1466-1472 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1618-1624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1903— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1903-1909 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1926-1932 — 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) kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:288— kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:288-294 | kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:399-405 — 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) kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:69— kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:69-75 | kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:135-142 — 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) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:162— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:162-168 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:207-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:162` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:802— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:802-808 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:354-360 — 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) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:469— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:469-475 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:532-538 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:469` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:566— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:566-572 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:580-586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:165— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:165-171 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:213-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2365— kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2365-2371 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2442-2448 — 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:63— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:63-69 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:76-82 — 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/MysqlPipelineExchange.scala:54— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/MysqlPipelineExchange.scala:54-60 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/PipelineExchange.scala:161-167 — 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:167— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:167-173 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:182-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:167` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:220— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:220-226 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:233-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:220` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:193— kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:193-199 | kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala:660-666 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:193` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:240— kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:240-246 | kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala: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 (6 lines × 2) kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:38— kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:38-44 | kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:38-43 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/PercentEncoding.scala:68— kyo-http/shared/src/main/scala/kyo/internal/PercentEncoding.scala:68-73 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:563-568 — 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) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:290— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:290-295 | kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:324-329 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:331` calls `validateStreamingMultipartBoundary` and `kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:297` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:112— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:112-117 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:187-192 — 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) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:300— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:300-305 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:318-323 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:330— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:330-335 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:591-596 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:449— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:449-454 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:714-719 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:468— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:468-473 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:733-738 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:476— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:476-481 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:741-746 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 × 2) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:112— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:112-117 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:125-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:862— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:862-867 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:902-907 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:862` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:64— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:64-69 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:177-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:740— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:740-745 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:487-492 — 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) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:979— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:979-984 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:986-991 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:979` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:51— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:51-56 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresBufferReader.scala:37-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 (6 lines × 2) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:411— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:411-416 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresSqlConnection.scala:374-379 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:411` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1674— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1674-1679 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2027-2032 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/Sql.scala:1674` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1711— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1711-1716 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2064-2069 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/Sql.scala:1711` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1343— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1343-1348 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2165-2170 — 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) kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:85— kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:85-90 | kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:92-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:255— kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:255-260 | kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:262-267 — 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) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:505— kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:505-510 | kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:543-548 — 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) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:349— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:349-354 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:708-713 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:396— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:396-401 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:3070-3075 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:396` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:670— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:670-675 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:981-986 — 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) kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:11— kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:11-15 | kyo-bench/src/main/scala/kyo/bench/arena/SemaphoreContentionBench.scala:12-16 — 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) kyo-bench/src/main/scala/kyo/bench/arena/PingPongBench.scala:67— kyo-bench/src/main/scala/kyo/bench/arena/PingPongBench.scala:67-71 | kyo-bench/src/main/scala/kyo/bench/arena/ProducerConsumerBench.scala:46-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 (5 lines × 2) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:49— kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:49-54 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:123-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:735— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:735-739 | kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:757-764 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:735` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:155— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:155-159 | kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:425-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:184— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:184-190 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:222-226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:210— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:210-214 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:286-290 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:526— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:526-530 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:797-801 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:526` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:217— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:217-221 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpEngine.scala:317-321 — 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) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:778— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:778-782 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:485-489 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:778` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:154— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:154-158 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:202-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1845— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1845-1850 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2722-2726 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1845` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:359— kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:359-363 | kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:369-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 (5 lines × 2) REDACTED:371— REDACTED:371-376 | REDACTED:449-453 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4997— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4997-5001 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2834-2838 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2834` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:109— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:109-113 | kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:705-709 — 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) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:772— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:772-776 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:852-856 — 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) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1276— kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1276-1280 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1285-1289 — 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) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:726— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:726-730 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:418-422 — 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) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:734— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:734-738 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:426-430 — 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) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:742— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:742-746 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:440-444 — 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) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:784— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:784-788 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:474-478 — 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) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:793— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:793-797 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:482-486 — 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) kyo-lsp/shared/src/main/scala/kyo/Lsp.scala:76— kyo-lsp/shared/src/main/scala/kyo/Lsp.scala:76-80 | kyo-mcp/shared/src/main/scala/kyo/Mcp.scala:31-35 — 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 (5 lines × 2) kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:170— kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:170-174 | kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:51-55 — 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) kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:37— kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:37-44 | kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:24-31 — 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) kyo-bench/src/main/scala/kyo/bench/arena/HttpClientBench.scala:43— kyo-bench/src/main/scala/kyo/bench/arena/HttpClientBench.scala:43-50 | kyo-bench/src/main/scala/kyo/bench/arena/HttpServerBench.scala:92-99 — 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) kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:28— kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:28-35 | kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:50-57 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1088— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1088-1095 | kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:613-620 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1088` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2006— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2006-2013 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2134-2141 — 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) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2490— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2490-2497 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2670-2677 — 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) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:170— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:170-177 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:257-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:618— kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:618-627 | kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:324-331 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:409— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:409-416 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:672-679 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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) kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:200— kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:200-207 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:337-344 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2277— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2277-2284 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:316-323 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2285` calls `getOrElse` and `kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:324` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:446— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:446-453 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:467-474 — 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) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:316— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:316-323 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:353-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:286— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:286-293 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:539-546 — 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) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:82— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:82-89 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:159-166 — 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) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:125— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:125-132 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:199-206 — 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) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3041— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3041-3048 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3101-3108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3041` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:120— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:120-130 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:465-472 — 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) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:191— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:191-199 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:531-538 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlChannel.scala:69— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlChannel.scala:69-76 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/LocalInfileExchange.scala:201-208 — 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) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1650— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1650-1657 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2003-2010 — 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) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1688— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1688-1695 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2041-2048 — 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) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1725— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1725-1732 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2078-2085 — 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) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:838— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:838-845 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:850-857 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:838` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:459— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:459-466 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:582-589 — 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.
Swallowed exception (caught, then discarded) project/CallbackShapesGen.scala:78— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) project/CryptoDifferentialGen.scala:117— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) project/CryptoDifferentialGen.scala:172— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1191— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:754— `case ex: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1648— `case _: Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformDigest.scala:82— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:67— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:599— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:176— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:267— `case scala.util.control.NonFatal(_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:345— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:347— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:349— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:444— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:469— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:542— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:545— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:550— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:553— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:583— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:586— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:589— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:592— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:780— `case _: Throwable` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
+ 12 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×32
Edited copy of a member (4 corresponding lines) kyo-core/shared/src/main/scala/kyo/Signal.scala:205— kyo-core/shared/src/main/scala/kyo/Signal.scala:205-208 | kyo-core/shared/src/main/scala/kyo/Signal.scala:221-224 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala:2653— kyo-schema/shared/src/main/scala/kyo/Schema.scala:2653-2656 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:2675-2678 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-ai/shared/src/main/scala/kyo/Decider.scala:485— kyo-ai/shared/src/main/scala/kyo/Decider.scala:485-488 | kyo-ai/shared/src/main/scala/kyo/Decider.scala:491-497 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:887— kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:887-890 | kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:224-227 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-teams/shared/src/main/scala/kyo/internal/teams/KeyCache.scala:61— kyo-teams/shared/src/main/scala/kyo/internal/teams/KeyCache.scala:61-64 | kyo-teams/shared/src/main/scala/kyo/internal/teams/TokenCache.scala:50-53 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-combinators/shared/src/main/scala/kyo/AbortCombinators.scala:552— kyo-combinators/shared/src/main/scala/kyo/AbortCombinators.scala:552-557 | kyo-combinators/shared/src/main/scala/kyo/AbortCombinators.scala:586-589 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:350— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:350-355 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:411-414 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:425— kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:425-428 | kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:431-434 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferWriter.scala:35— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferWriter.scala:35-38 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresBufferWriter.scala:22-25 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:877— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:877-880 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:454-457 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) REDACTED:313— REDACTED:313-318 | REDACTED:394-397 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf7Decoder.scala:82— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf7Decoder.scala:82-87 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:548-551 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema-msgpack/shared/src/main/scala/kyo/internal/msgpack/MsgPackReader.scala:283— kyo-schema-msgpack/shared/src/main/scala/kyo/internal/msgpack/MsgPackReader.scala:283-286 | kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:329-333 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/mime/DateCodec.scala:168— kyo-email/shared/src/main/scala/kyo/internal/email/mime/DateCodec.scala:168-171 | kyo-schema/shared/src/main/scala/kyo/internal/TimeText.scala:82-85 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/MysqlClient.scala:181— kyo-sql-mysql/shared/src/main/scala/kyo/MysqlClient.scala:181-184 | kyo-sql-postgres/shared/src/main/scala/kyo/PostgresClient.scala:292-296 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/codec/ParsedRequestBuilder.scala:190— kyo-http/shared/src/main/scala/kyo/internal/codec/ParsedRequestBuilder.scala:190-193 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:391-394 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexWire.scala:452— kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexWire.scala:452-455 | kyo-ai/shared/src/main/scala/kyo/ai/completion/StrictSchema.scala:25-28 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:897— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:897-900 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1094-1097 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:452— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:452-455 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:281-284 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:458— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:458-461 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:288-291 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1170— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1170-1173 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1353-1356 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeCounter.scala:30— kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeCounter.scala:30-33 | kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeHistogram.scala:78-81 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:134— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:134-138 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:150-153 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:315— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:315-318 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:450-454 — These two members are one piece of code written twice and then edited apart: 4 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.
Edited copy of a member (4 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:428— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:428-431 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:439-442 — These two members are one piece of code written twice and then edited apart: 4 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.
+ 7 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×29
Edited copy of a member (8 corresponding lines) kyo-ui/shared/src/main/scala/kyo/Chart.scala:268— kyo-ui/shared/src/main/scala/kyo/Chart.scala:268-275 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:331-343 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:71— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:71-82 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:93-100 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:397— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:397-404 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:419-427 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:216— kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:216-223 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:84-91 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) REDACTED:342— REDACTED:342-349 | REDACTED:420-427 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:345— kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:345-354 | kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:373-380 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/Isolate.scala:270— kyo-kernel/shared/src/main/scala/kyo/kernel/Isolate.scala:270-277 | kyo-kernel/shared/src/main/scala/kyo/kernel/Isolate.scala:287-299 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/SectionIndex.scala:36— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/SectionIndex.scala:36-48 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/SectionIndex.scala:57-64 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-mcp/shared/src/main/scala/kyo/Mcp.scala:113— kyo-mcp/shared/src/main/scala/kyo/Mcp.scala:113-120 | kyo-mcp/shared/src/main/scala/kyo/Mcp.scala:134-141 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Abort.scala:595— kyo-prelude/shared/src/main/scala/kyo/Abort.scala:595-602 | kyo-prelude/shared/src/main/scala/kyo/Abort.scala:620-627 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-parse/shared/src/main/scala/kyo/Parse.scala:445— kyo-parse/shared/src/main/scala/kyo/Parse.scala:445-452 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:471-479 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/StoreInterpreter.scala:283— kyo-flow/shared/src/main/scala/kyo/internal/StoreInterpreter.scala:283-296 | kyo-flow/shared/src/main/scala/kyo/internal/StoreInterpreter.scala:299-306 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-data/native/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:29— kyo-data/native/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:29-36 | kyo-data/native/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:40-49 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:910— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:910-917 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:921-928 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-mcp/shared/src/main/scala/kyo/McpHandler.scala:505— kyo-mcp/shared/src/main/scala/kyo/McpHandler.scala:505-513 | kyo-mcp/shared/src/main/scala/kyo/McpHandler.scala:528-535 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:25— kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:25-32 | kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:36-46 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:62— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:62-69 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:188-195 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:288— kyo-prelude/shared/src/main/scala/kyo/Stream.scala:288-296 | kyo-prelude/shared/src/main/scala/kyo/Stream.scala:309-316 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-sql/shared/src/main/scala/kyo/SqlClient.scala:107— kyo-sql/shared/src/main/scala/kyo/SqlClient.scala:107-116 | kyo-sql/shared/src/main/scala/kyo/SqlClient.scala:604-611 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:158— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:158-165 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:170-177 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:763— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:763-772 | kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:485-492 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/Binding.scala:70— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/Binding.scala:70-77 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/Binding.scala:81-88 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:371— kyo-browser/shared/src/main/scala/kyo/Browser.scala:371-378 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:389-396 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:368— kyo-prelude/shared/src/main/scala/kyo/Stream.scala:368-376 | kyo-prelude/shared/src/main/scala/kyo/Stream.scala:428-435 — These two members are one piece of code written twice and then edited apart: 8 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.
Edited copy of a member (8 corresponding lines) kyo-sql/shared/src/main/scala/kyo/Sql.scala:117— kyo-sql/shared/src/main/scala/kyo/Sql.scala:117-124 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:152-159 — These two members are one piece of code written twice and then edited apart: 8 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.
+ 4 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×29
Edited copy of a member (6 corresponding lines) kyo-website/shared/src/main/scala/kyo/website/DocsApp.scala:247— kyo-website/shared/src/main/scala/kyo/website/DocsApp.scala:247-253 | kyo-website/shared/src/main/scala/kyo/website/DocsApp.scala:257-262 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) REDACTED:371— REDACTED:371-382 | REDACTED:449-454 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:498— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:498-503 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:511-518 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-parse/shared/src/main/scala/kyo/Parse.scala:806— kyo-parse/shared/src/main/scala/kyo/Parse.scala:806-811 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:819-824 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/mime/DateCodec.scala:175— kyo-email/shared/src/main/scala/kyo/internal/email/mime/DateCodec.scala:175-180 | kyo-schema/shared/src/main/scala/kyo/internal/TimeText.scala:89-94 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ClientConnection.scala:154— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ClientConnection.scala:154-161 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1StreamContext.scala:246-251 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/InitSSLExchange.scala:51— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/InitSSLExchange.scala:51-56 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/InitSSLExchange.scala:81-86 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/DragProtocol.scala:458— kyo-ui/shared/src/main/scala/kyo/internal/DragProtocol.scala:458-463 | kyo-ui/shared/src/main/scala/kyo/internal/DragProtocol.scala:677-682 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/BrowserEval.scala:23— kyo-browser/shared/src/main/scala/kyo/internal/BrowserEval.scala:23-28 | kyo-browser/shared/src/main/scala/kyo/internal/BrowserEval.scala:55-63 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:373— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:373-383 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:295-300 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:67— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:67-72 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:80-85 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-core/shared/src/main/scala/kyo/Stat.scala:245— kyo-core/shared/src/main/scala/kyo/Stat.scala:245-252 | kyo-core/shared/src/main/scala/kyo/Stat.scala:294-299 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/MacosDisk.scala:189— kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/MacosDisk.scala:189-194 | kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/WindowsDisk.scala:116-126 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1049— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1049-1054 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1076-1081 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-actor/shared/src/main/scala/kyo/Actor.scala:567— kyo-actor/shared/src/main/scala/kyo/Actor.scala:567-572 | kyo-actor/shared/src/main/scala/kyo/Actor.scala:606-611 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/transport/ConnectionBackedStream.scala:19— kyo-http/shared/src/main/scala/kyo/internal/transport/ConnectionBackedStream.scala:19-24 | kyo-http/shared/src/main/scala/kyo/internal/util/ChannelBackedStream.scala:22-27 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:589— kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:589-594 | kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:598-603 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteRowReader.scala:182— kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteRowReader.scala:182-189 | kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteRowReader.scala:220-225 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexWire.scala:308— kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexWire.scala:308-314 | kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexWire.scala:321-326 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:336— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:336-341 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:388-393 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxDisk.scala:96— kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxDisk.scala:96-101 | kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/MacosDisk.scala:116-121 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinContentionBench.scala:22— kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinContentionBench.scala:22-28 | kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinBench.scala:19-24 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:706— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:706-712 | kyo-prelude/shared/src/main/scala/kyo/Sink.scala:280-285 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:57— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:57-62 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:75-81 — These two members are one piece of code written twice and then edited apart: 6 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.
Edited copy of a member (6 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:75— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:75-80 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:94-100 — These two members are one piece of code written twice and then edited apart: 6 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.
+ 4 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×27
Edited copy of a member (7 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:569— kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:569-575 | kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:54-60 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-core/shared/src/main/scala/kyo/Stat.scala:275— kyo-core/shared/src/main/scala/kyo/Stat.scala:275-281 | kyo-core/shared/src/main/scala/kyo/Stat.scala:284-291 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-ai/shared/src/main/scala/kyo/Agent.scala:82— kyo-ai/shared/src/main/scala/kyo/Agent.scala:82-88 | kyo-ai/shared/src/main/scala/kyo/Agent.scala:110-116 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:803— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:803-809 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:850-857 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppMedia.scala:152— kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppMedia.scala:152-158 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppMedia.scala:181-187 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-slack/shared/src/main/scala/kyo/SlackToken.scala:70— kyo-slack/shared/src/main/scala/kyo/SlackToken.scala:70-78 | kyo-telegram/shared/src/main/scala/kyo/Telegram.scala:442-448 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxCgroupPath.scala:46— kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxCgroupPath.scala:46-52 | kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxCgroupPath.scala:74-80 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/net/LineConnection.scala:60— kyo-email/shared/src/main/scala/kyo/internal/email/net/LineConnection.scala:60-66 | kyo-email/shared/src/main/scala/kyo/internal/email/net/LineConnection.scala:91-97 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:272— kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:272-282 | kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:312-318 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/ClearPassword.scala:26— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/ClearPassword.scala:26-34 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:536-542 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:342— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:342-348 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:799-805 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:207— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:207-213 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:214-220 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:274— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:274-280 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:283-289 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:145— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:145-151 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:164-170 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:295— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:295-301 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:305-311 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:407— kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:407-413 | kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:426-432 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufWriter.scala:409— kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufWriter.scala:409-415 | kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufWriter.scala:428-434 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinBench.scala:9— kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinBench.scala:9-15 | kyo-bench/src/main/scala/kyo/bench/arena/ForkJoinContentionBench.scala:10-18 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:124— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:124-130 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:139-146 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:40— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:40-46 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresBufferReader.scala:26-32 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-discord/shared/src/main/scala/kyo/Discord.scala:322— kyo-discord/shared/src/main/scala/kyo/Discord.scala:322-328 | kyo-discord/shared/src/main/scala/kyo/Discord.scala:334-340 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:129— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:129-141 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:455-461 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1092— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1092-1098 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/TlsEngineIo.scala:82-88 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/Ion.scala:231— kyo-schema-ion/shared/src/main/scala/kyo/Ion.scala:231-240 | kyo-schema-ion/shared/src/main/scala/kyo/Ion.scala:248-254 — These two members are one piece of code written twice and then edited apart: 7 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.
Edited copy of a member (7 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyInResponseUnmarshaller.scala:17— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyInResponseUnmarshaller.scala:17-23 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyOutResponseUnmarshaller.scala:17-23 — These two members are one piece of code written twice and then edited apart: 7 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.
+ 2 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×27
Edited copy of a member (9 corresponding lines) kyo-jsonrpc/shared/src/main/scala/kyo/internal/transport/UdsBackend.scala:85— kyo-jsonrpc/shared/src/main/scala/kyo/internal/transport/UdsBackend.scala:85-93 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/transport/UdsBackend.scala:97-106 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:375— kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:375-386 | kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:412-420 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:1021— kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:1021-1029 | kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:1060-1068 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-core/shared/src/main/scala/kyo/Signal.scala:302— kyo-core/shared/src/main/scala/kyo/Signal.scala:302-310 | kyo-core/shared/src/main/scala/kyo/Signal.scala:323-331 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:46— kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:46-56 | kyo-bench/src/main/scala/kyo/bench/arena/HttpServerContentionBench.scala:97-105 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-system/shared/src/main/scala/kyo/Path.scala:403— kyo-system/shared/src/main/scala/kyo/Path.scala:403-411 | kyo-system/shared/src/main/scala/kyo/Path.scala:417-426 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:24— kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:24-32 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:46-55 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/EnqueueDequeueBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/EnqueueDequeueBench.scala:8-17 | kyo-bench/src/main/scala/kyo/bench/arena/EnqueueDequeueBench.scala:35-43 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:546— kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:546-554 | kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:558-566 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlChannel.scala:96— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlChannel.scala:96-106 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlChannel.scala:111-119 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlNumericDecoder.scala:141— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlNumericDecoder.scala:141-149 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlNumericDecoder.scala:166-174 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:122— kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:122-130 | kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:156-164 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:854— kyo-browser/shared/src/main/scala/kyo/Browser.scala:854-862 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:869-877 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2426— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2426-2434 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2450-2458 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1368— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1368-1376 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1489-1498 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:599— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:599-607 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:620-628 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:63— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:63-71 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:107-115 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Sink.scala:106— kyo-prelude/shared/src/main/scala/kyo/Sink.scala:106-115 | kyo-prelude/shared/src/main/scala/kyo/Sink.scala:150-158 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:136— kyo-prelude/shared/src/main/scala/kyo/Stream.scala:136-144 | kyo-prelude/shared/src/main/scala/kyo/Stream.scala:180-188 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:402— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:402-414 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:542-550 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/FlowRender.scala:25— kyo-flow/shared/src/main/scala/kyo/internal/FlowRender.scala:25-34 | kyo-flow/shared/src/main/scala/kyo/internal/FlowRender.scala:78-86 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixStructs.scala:261— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixStructs.scala:261-269 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixStructs.scala:285-293 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:268— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:268-276 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:289-297 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:765— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:765-773 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:457-465 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/Packager.scala:67— kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/Packager.scala:67-75 | kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/Packager.scala:84-96 — These two members are one piece of code written twice and then edited apart: 9 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.
+ 2 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×27
Edited copy of a member (3 corresponding lines) REDACTED:386— REDACTED:386-388 | REDACTED:458-460 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordWebhookConfig.scala:25— kyo-discord/shared/src/main/scala/kyo/DiscordWebhookConfig.scala:25-28 | kyo-teams/shared/src/main/scala/kyo/TeamsWebhookConfig.scala:22-24 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1745— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1745-1747 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2098-2100 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-email/shared/src/main/scala/kyo/Email.scala:515— kyo-email/shared/src/main/scala/kyo/Email.scala:515-517 | kyo-mime/shared/src/main/scala/kyo/mime/Multipart.scala:27-29 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:1124— kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:1124-1126 | kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:402-404 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspHandlerLift.scala:54— kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspHandlerLift.scala:54-56 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpHandlerLift.scala:42-44 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-discord/shared/src/main/scala/kyo/Discord.scala:630— kyo-discord/shared/src/main/scala/kyo/Discord.scala:630-632 | kyo-telegram/shared/src/main/scala/kyo/Telegram.scala:429-431 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:778— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:778-780 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:469-471 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/PostgresTypes.scala:182— kyo-sql-postgres/shared/src/main/scala/kyo/PostgresTypes.scala:182-184 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:3181-3183 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:174— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:174-177 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:174-176 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/PostgresTypes.scala:188— kyo-sql-postgres/shared/src/main/scala/kyo/PostgresTypes.scala:188-190 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:3175-3177 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:58— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:58-60 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:333-335 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala:105— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala:105-107 | kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala:748-750 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:29— kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:29-32 | kyo-bench/src/main/scala/kyo/bench/arena/HttpServerContentionBench.scala:68-70 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-email/shared/src/main/scala/kyo/EmailImapConfig.scala:144— kyo-email/shared/src/main/scala/kyo/EmailImapConfig.scala:144-146 | kyo-email/shared/src/main/scala/kyo/EmailSmtpConfig.scala:112-114 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:751— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:751-753 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:434-436 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:251— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:251-253 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppException.scala:209-211 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:70— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:70-72 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:69-72 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:413— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:413-415 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:424-426 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:443— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:443-445 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:454-456 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:315— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:315-317 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:322-324 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:325— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:325-327 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:332-334 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:334— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:334-336 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:344-346 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:346— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:346-348 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:356-358 — These two members are one piece of code written twice and then edited apart: 3 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.
Edited copy of a member (3 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:436— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:436-438 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:447-449 — These two members are one piece of code written twice and then edited apart: 3 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.
+ 2 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×25
Edited copy of a member (10 corresponding lines) kyo-http/shared/src/main/scala/kyo/HttpClient.scala:925— kyo-http/shared/src/main/scala/kyo/HttpClient.scala:925-934 | kyo-http/shared/src/main/scala/kyo/HttpClient.scala:945-954 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:847— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:847-856 | kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:895-914 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2742— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2742-2751 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2768-2777 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2204— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2204-2213 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2230-2239 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:93— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:93-103 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:113-122 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-discord/shared/src/main/scala/kyo/Discord.scala:683— kyo-discord/shared/src/main/scala/kyo/Discord.scala:683-692 | kyo-telegram/shared/src/main/scala/kyo/Telegram.scala:1750-1761 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:230— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:230-241 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:90-99 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Focus.scala:357— kyo-schema/shared/src/main/scala/kyo/Focus.scala:357-366 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:1514-1523 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:307— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:307-316 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:320-329 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1676— kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1676-1686 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1694-1703 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:608— kyo-schema-json/shared/src/main/scala/kyo/Json.scala:608-617 | kyo-schema-json/shared/src/main/scala/kyo/Json.scala:621-630 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:922— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:922-931 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:944-955 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1194— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1194-1203 | kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1209-1218 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:38— kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:38-47 | kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:38-47 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:406— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:406-415 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:426-435 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:170— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:170-184 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Stack.scala:257-266 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:776— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:776-785 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:824-833 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:230— kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:230-240 | kyo-schema-protobuf/shared/src/main/scala/kyo/internal/ProtobufReader.scala:458-467 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:25— kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:25-34 | kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:25-34 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:252— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:252-262 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1259-1268 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:68— kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:68-77 | kyo-kernel/jvm-native/src/main/scala/kyo/kernel/internal/Safepoint.scala:172-182 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:104— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:104-113 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:225-234 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:100— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:100-109 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:242-251 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:90— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:90-99 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:86-95 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:62— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:62-71 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:335-346 — These two members are one piece of code written twice and then edited apart: 10 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.
Duplicated block (9 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:56— kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:56-64 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:79-87 — 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) kyo-ffi/native/src/main/scala/kyo/ffi/internal/NativeLeakDetector.scala:212— kyo-ffi/native/src/main/scala/kyo/ffi/internal/NativeLeakDetector.scala:212-220 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/NativeLeakDetector.scala:244-252 — 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) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1133— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1133-1141 | kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:659-667 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1639— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1639-1647 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1700-1708 — 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) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:635— kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:635-643 | kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:342-350 — 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) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:547— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:547-555 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpEngine.scala:345-353 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpEngine.scala:340` calls `awaitDrain`, `evalOrThrow`, `initUnscoped` and `kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:545` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2393— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2393-2401 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2407-2415 — 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) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:497— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:497-505 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:170-178 — 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) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:239— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:239-247 | kyo-prelude/shared/src/main/scala/kyo/Sink.scala:189-197 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:239` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:385— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:385-393 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:394-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:385` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:170— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:170-178 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:206-214 — 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) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:36— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:36-44 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:671-679 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) REDACTED:135— REDACTED:135-143 | REDACTED:170-178 — 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:59— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:59-67 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:75-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/ErrorResponseUnmarshaller.scala:33— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/ErrorResponseUnmarshaller.scala:33-41 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/NoticeResponseUnmarshaller.scala:30-38 — 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) kyo-sql/shared/src/main/scala/kyo/internal/SqlBackendRegistryMacro.scala:34— kyo-sql/shared/src/main/scala/kyo/internal/SqlBackendRegistryMacro.scala:34-43 | kyo-sql/shared/src/main/scala/kyo/internal/SqlStaticMacro.scala:285-293 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/internal/SqlBackendRegistryMacro.scala:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/macros/BindFromExpr.scala:141— kyo-sql/shared/src/main/scala/kyo/internal/macros/BindFromExpr.scala:141-149 | kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:258-266 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:490— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:490-498 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:516-524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:490` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:190— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:190-198 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:203-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.
Duplicated block (9 lines × 2) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1126— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1126-1134 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1199-1207 — 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) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1480— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1480-1488 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1496-1504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1480` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:100— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:100-108 | kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala:37-45 — before extracting anything, compare `kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala` and `kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2325— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2325-2333 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:350-358 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2325` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:338— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:338-346 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:3022-3030 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:338` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:347` calls `registerPipelineDiagnostics` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:3031` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×20
Edited copy of a member (5 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/StrictSchema.scala:163— kyo-ai/shared/src/main/scala/kyo/ai/completion/StrictSchema.scala:163-167 | kyo-ai/shared/src/main/scala/kyo/ai/completion/StrictSchema.scala:173-179 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:388— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:388-392 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:306-311 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:179— kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:179-183 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppConfig.scala:121-125 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystemHandles.scala:145— kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystemHandles.scala:145-149 | kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystemHandles.scala:155-159 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-ai/shared/src/main/scala/kyo/Agent.scala:141— kyo-ai/shared/src/main/scala/kyo/Agent.scala:141-147 | kyo-ai/shared/src/main/scala/kyo/Agent.scala:169-173 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:416— kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:416-420 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:429-438 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:112— kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:112-117 | kyo-website/shared/src/main/scala/kyo/website/WebsiteContent.scala:59-63 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-system/shared/src/main/scala/kyo/Path.scala:378— kyo-system/shared/src/main/scala/kyo/Path.scala:378-382 | kyo-system/shared/src/main/scala/kyo/Path.scala:393-397 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/CurvePath.scala:39— kyo-ui/shared/src/main/scala/kyo/internal/CurvePath.scala:39-43 | kyo-ui/shared/src/main/scala/kyo/internal/CurvePath.scala:48-52 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Layer.scala:188— kyo-prelude/shared/src/main/scala/kyo/Layer.scala:188-192 | kyo-prelude/shared/src/main/scala/kyo/Layer.scala:205-209 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-data/shared/src/main/scala/kyo/Span.scala:1389— kyo-data/shared/src/main/scala/kyo/Span.scala:1389-1393 | kyo-data/shared/src/main/scala/kyo/Span.scala:1437-1441 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/Jsonl.scala:592— kyo-schema-json/shared/src/main/scala/kyo/Jsonl.scala:592-597 | kyo-schema-json/shared/src/main/scala/kyo/JsonLines.scala:661-665 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlRowReader.scala:175— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlRowReader.scala:175-181 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresRowReader.scala:147-151 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-net/js-wasm/src/main/scala/kyo/net/internal/TlsProviderPlatform.scala:50— kyo-net/js-wasm/src/main/scala/kyo/net/internal/TlsProviderPlatform.scala:50-54 | kyo-net/shared/src/main/scala/kyo/net/internal/TlsProviderPlatformBase.scala:38-42 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-data/shared/src/main/scala/kyo/Dict.scala:98— kyo-data/shared/src/main/scala/kyo/Dict.scala:98-105 | kyo-data/shared/src/main/scala/kyo/OrderedDict.scala:102-106 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-data/shared/src/main/scala/kyo/Dict.scala:83— kyo-data/shared/src/main/scala/kyo/Dict.scala:83-87 | kyo-data/shared/src/main/scala/kyo/OrderedDict.scala:88-92 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:158— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:158-162 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:182-186 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:301— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:301-305 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresSqlConnection.scala:232-236 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/ErrorResponseUnmarshaller.scala:23— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/ErrorResponseUnmarshaller.scala:23-27 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/NoticeResponseUnmarshaller.scala:20-24 — These two members are one piece of code written twice and then edited apart: 5 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.
Edited copy of a member (5 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:144— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:144-148 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:140-144 — These two members are one piece of code written twice and then edited apart: 5 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 (15 corresponding lines) · ×18
Edited copy of a member (15 corresponding lines) kyo-core/shared/src/main/scala/kyo/Queue.scala:495— kyo-core/shared/src/main/scala/kyo/Queue.scala:495-509 | kyo-core/shared/src/main/scala/kyo/Queue.scala:531-555 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:542— kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:542-556 | kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:560-576 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) REDACTED:288— REDACTED:288-307 | REDACTED:375-389 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:146— kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:146-160 | kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:230-248 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:153— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:153-167 | kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:423-437 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2277— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2277-2291 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2308-2323 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2815— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2815-2829 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2846-2861 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:295— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:295-312 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:922-936 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-core/shared/src/main/scala/kyo/Channel.scala:605— kyo-core/shared/src/main/scala/kyo/Channel.scala:605-624 | kyo-core/shared/src/main/scala/kyo/Channel.scala:628-642 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:56— kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:56-75 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:79-93 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:79— kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:79-94 | kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:98-112 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-core/shared/src/main/scala/kyo/Channel.scala:770— kyo-core/shared/src/main/scala/kyo/Channel.scala:770-788 | kyo-core/shared/src/main/scala/kyo/Channel.scala:792-806 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:94— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:94-108 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:116-130 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-http/shared/src/main/scala/kyo/FlagSync.scala:43— kyo-http/shared/src/main/scala/kyo/FlagSync.scala:43-57 | kyo-http/shared/src/main/scala/kyo/FlagSync.scala:71-90 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1669— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1669-1683 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:475-491 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-data/jvm-native/src/main/scala/kyo/internal/SpmcUnsafeQueue.scala:54— kyo-data/jvm-native/src/main/scala/kyo/internal/SpmcUnsafeQueue.scala:54-68 | kyo-data/jvm-native/src/main/scala/kyo/internal/SpmcUnsafeQueue.scala:73-90 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:727— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:727-741 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1123-1142 — These two members are one piece of code written twice and then edited apart: 15 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.
Edited copy of a member (15 corresponding lines) kyo-case-app/shared/src/main/scala/kyo/internal/KyoCaseAppSupport.scala:16— kyo-case-app/shared/src/main/scala/kyo/internal/KyoCaseAppSupport.scala:16-32 | kyo-core/shared/src/main/scala/kyo/KyoApp.scala:53-67 — These two members are one piece of code written twice and then edited apart: 15 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.
Duplicated block (11 lines × 2) kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:130— kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:130-140 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:146-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:305— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:305-315 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:337-347 — 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) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:91— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:91-101 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:557-567 — 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) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:939— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:939-949 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:647-657 — 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) kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:61— kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:61-71 | kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:75-85 — 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) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiMacro.scala:178— kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiMacro.scala:178-188 | kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiMacro.scala:341-351 — 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) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:555— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:555-565 | kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:766-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:555` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:548` calls `installCertHashFn` and `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:765` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:189— kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:189-199 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:278-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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:79— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:79-89 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:190-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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:203` calls `succeed`, `Sequence`, `removeAt` and `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:91` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:394— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:394-404 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1361-1371 — 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) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1250— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1250-1260 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2180-2190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1250` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4069— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4069-4079 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4734-4744 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:98— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:98-108 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/binary/Varint.scala:120-130 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:963— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:963-973 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1005-1015 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:963` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:169— kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:169-179 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppException.scala:137-147 — 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) kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:293— kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:293-303 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:365-375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:751— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:751-761 | kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:768-778 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:751` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) kyo-crypto/shared/src/main/scala/kyo/crypto/Sha1.scala:47— kyo-crypto/shared/src/main/scala/kyo/crypto/Sha1.scala:47-57 | kyo-crypto/shared/src/main/scala/kyo/crypto/Sha256.scala:63-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· Edited copy of a member (11 corresponding lines) · ×16
Edited copy of a member (11 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:766— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:766-797 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:473-541 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:329— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:329-339 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:656-666 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:109— kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:109-119 | kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:199-209 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:294— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:294-304 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:315-325 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:446— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:446-456 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:467-477 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/TRefMultiBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/TRefMultiBench.scala:8-18 | kyo-bench/src/main/scala/kyo/bench/arena/TRefSingleBench.scala:8-20 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:336— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:336-348 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlDocuments.scala:9-19 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/MessageReader.scala:78— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/MessageReader.scala:78-88 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/MessageReader.scala:94-107 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:327— kyo-prelude/shared/src/main/scala/kyo/Stream.scala:327-337 | kyo-prelude/shared/src/main/scala/kyo/Stream.scala:347-358 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:131— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:131-141 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:145-155 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:198— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:198-212 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ResetConnectionExchange.scala:27-37 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:82— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:82-93 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:532-542 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1329— kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1329-1341 | kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1347-1357 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1084— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1084-1094 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1104-1117 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:33— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:33-43 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:35-45 — These two members are one piece of code written twice and then edited apart: 11 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.
Edited copy of a member (11 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1633— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1633-1643 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:437-447 — These two members are one piece of code written twice and then edited apart: 11 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 (16 corresponding lines) · ×16
Edited copy of a member (16 corresponding lines) kyo-data/shared/src/main/scala/kyo/Record.scala:256— kyo-data/shared/src/main/scala/kyo/Record.scala:256-271 | kyo-data/shared/src/main/scala/kyo/Record.scala:274-289 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:230— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:230-247 | kyo-teams/shared/src/main/scala/kyo/TeamsException.scala:275-290 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-telegram/shared/src/main/scala/kyo/Telegram.scala:1860— kyo-telegram/shared/src/main/scala/kyo/Telegram.scala:1860-1875 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsApp.scala:175-193 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:548— kyo-schema-json/shared/src/main/scala/kyo/Json.scala:548-563 | kyo-schema-json/shared/src/main/scala/kyo/Json.scala:577-592 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:111— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:111-126 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:186-201 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:933— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:933-948 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:965-987 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:241— kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:241-260 | kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:288-303 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1057— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1057-1072 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1084-1099 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1909— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1909-1926 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:2155-2170 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1610— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1610-1626 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1668-1683 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:12— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:12-27 | kyo-tasty/native/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:11-26 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:2483— kyo-browser/shared/src/main/scala/kyo/Browser.scala:2483-2498 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:2502-2517 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:1993— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:1993-2008 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:2466-2481 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:29— kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:29-44 | kyo-bench/src/main/scala/kyo/bench/arena/TMapSingleKeyBench.scala:30-45 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:353— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:353-368 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:364-379 — These two members are one piece of code written twice and then edited apart: 16 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.
Edited copy of a member (16 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:373— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:373-388 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:384-399 — These two members are one piece of code written twice and then edited apart: 16 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 (12 corresponding lines) · ×15
Edited copy of a member (12 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1261— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1261-1275 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1316-1327 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/CachingSha2Shared.scala:40— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/CachingSha2Shared.scala:40-51 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/NativePasswordShared.scala:31-46 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:227— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:227-238 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1207-1221 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:450— kyo-prelude/shared/src/main/scala/kyo/Stream.scala:450-464 | kyo-prelude/shared/src/main/scala/kyo/Stream.scala:471-482 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/MysqlPipelineExchange.scala:52— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/MysqlPipelineExchange.scala:52-64 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/PipelineExchange.scala:161-172 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-system/shared/src/main/scala/kyo/internal/PathDirectories.scala:133— kyo-system/shared/src/main/scala/kyo/internal/PathDirectories.scala:133-144 | kyo-system/shared/src/main/scala/kyo/internal/PathDirectories.scala:167-178 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:755— kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:755-766 | kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:771-782 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-aeron/shared/src/main/scala/kyo/internal/FfiAeronTransport.scala:66— kyo-aeron/shared/src/main/scala/kyo/internal/FfiAeronTransport.scala:66-80 | kyo-aeron/shared/src/main/scala/kyo/internal/FfiAeronTransport.scala:107-118 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:714— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:714-725 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:972-983 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1650— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1650-1661 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:454-466 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:54— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:54-65 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:58-69 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1753— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1753-1764 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1775-1788 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:786— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:786-798 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:390-401 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/CountdownLatchBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/CountdownLatchBench.scala:8-20 | kyo-bench/src/main/scala/kyo/bench/arena/CountdownLatchBench.scala:24-35 — These two members are one piece of code written twice and then edited apart: 12 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.
Edited copy of a member (12 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3172— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3172-3183 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:3187-3198 — These two members are one piece of code written twice and then edited apart: 12 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.
Duplicated block (12 lines × 2) kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:91— kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:91-102 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:113-124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-browser/shared/src/main/scala/kyo/Browser.scala:624— kyo-browser/shared/src/main/scala/kyo/Browser.scala:624-635 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:722-733 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-browser/shared/src/main/scala/kyo/Browser.scala:624` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-core/shared/src/main/scala/kyo/Fiber.scala:1101— kyo-core/shared/src/main/scala/kyo/Fiber.scala:1101-1112 | kyo-stm/shared/src/main/scala/kyo/internal/CommitBuffer.scala:110-121 — 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) kyo-core/shared/src/main/scala/kyo/Gate.scala:304— kyo-core/shared/src/main/scala/kyo/Gate.scala:304-315 | kyo-core/shared/src/main/scala/kyo/Gate.scala:597-608 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-core/shared/src/main/scala/kyo/Gate.scala:609` calls `foreach`, `arrive` and `kyo-core/shared/src/main/scala/kyo/Gate.scala:316` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) kyo-crypto/shared/src/main/scala/kyo/crypto/Sha1.scala:93— kyo-crypto/shared/src/main/scala/kyo/crypto/Sha1.scala:93-104 | kyo-crypto/shared/src/main/scala/kyo/crypto/Sha256.scala:115-126 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-crypto/shared/src/main/scala/kyo/crypto/Sha256.scala:127` calls `writeIntBigEndian` and `kyo-crypto/shared/src/main/scala/kyo/crypto/Sha1.scala:105` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:292— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:292-303 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:324-335 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:356— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:356-367 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:616-627 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:355` calls `Closers` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:615` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:259— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:259-270 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:592-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:754— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:754-765 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:364-375 — 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 (12 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:110— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:110-121 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:184-195 — 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:406— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:406-417 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:428-439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:16— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:16-27 | kyo-tasty/native/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:15-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformMmapReader.scala:16` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2727— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2727-2738 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2757-2768 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2727` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:286— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:286-297 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:336-347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:286` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:348` calls `onRecover` and `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:299` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1136— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1136-1147 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1164-1175 — 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· Edited copy of a member (14 corresponding lines) · ×14
Edited copy of a member (14 corresponding lines) kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:19— kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:19-32 | kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:37-50 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-jsonrpc/shared/src/main/scala/kyo/internal/framing/FramerImpl.scala:12— kyo-jsonrpc/shared/src/main/scala/kyo/internal/framing/FramerImpl.scala:12-25 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/framing/FramerImpl.scala:31-44 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:237— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:237-250 | kyo-prelude/shared/src/main/scala/kyo/Sink.scala:188-201 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:8-21 | kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:8-21 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:45— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:45-64 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:74-87 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/MemoryFlowStore.scala:108— kyo-flow/shared/src/main/scala/kyo/internal/MemoryFlowStore.scala:108-122 | kyo-flow/shared/src/main/scala/kyo/internal/MemoryFlowStore.scala:138-151 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/ProducerConsumerBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/ProducerConsumerBench.scala:8-23 | kyo-bench/src/main/scala/kyo/bench/arena/ProducerConsumerBench.scala:46-59 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:561— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:561-574 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:588-602 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1013— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1013-1026 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1040-1053 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2727— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2727-2743 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2757-2770 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:649— kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:649-662 | kyo-schema-ion/shared/src/main/scala/kyo/internal/IonWriter.scala:182-195 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2203— kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2203-2223 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2546-2559 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-core/shared/src/main/scala/kyo/Gate.scala:241— kyo-core/shared/src/main/scala/kyo/Gate.scala:241-254 | kyo-core/shared/src/main/scala/kyo/Gate.scala:497-511 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:213— kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:213-226 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppConfig.scala:93-106 — These two members are one piece of code written twice and then edited apart: 14 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 (17 corresponding lines) · ×14
Edited copy of a member (17 corresponding lines) kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:300— kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:300-316 | kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:321-341 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:76— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:76-95 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlNumericDecoder.scala:294-310 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:276— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:276-292 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CancelExchange.scala:121-138 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-http/shared/src/main/scala/kyo/HttpHeaders.scala:565— kyo-http/shared/src/main/scala/kyo/HttpHeaders.scala:565-582 | kyo-http/shared/src/main/scala/kyo/HttpHeaders.scala:586-602 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-scheduler/jvm/src/main/scala/kyo/scheduler/util/ThreadUserTime.scala:58— kyo-scheduler/jvm/src/main/scala/kyo/scheduler/util/ThreadUserTime.scala:58-74 | kyo-scheduler/native/src/main/scala/kyo/scheduler/util/ThreadUserTime.scala:45-62 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/CCompiler.scala:109— kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/CCompiler.scala:109-128 | kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/CCompiler.scala:142-158 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:81— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:81-97 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:107-123 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:127— kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:127-145 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:181-197 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Changeset.scala:307— kyo-schema/shared/src/main/scala/kyo/Changeset.scala:307-324 | kyo-schema/shared/src/main/scala/kyo/Changeset.scala:328-344 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2178— kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2178-2199 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2526-2542 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:322— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:322-338 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:945-962 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:835— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:835-855 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:859-875 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:722— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:722-742 | kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:746-762 — These two members are one piece of code written twice and then edited apart: 17 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.
Edited copy of a member (17 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:170— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:170-186 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:187-203 — These two members are one piece of code written twice and then edited apart: 17 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.
Duplicated block (10 lines × 2) kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:41— kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:41-50 | kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:65-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:8-17 | kyo-bench/src/main/scala/kyo/bench/arena/StateMapBench.scala:8-17 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/arena/StateBench.scala:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-core/shared/src/main/scala/kyo/Gate.scala:241— kyo-core/shared/src/main/scala/kyo/Gate.scala:241-250 | kyo-core/shared/src/main/scala/kyo/Gate.scala:497-506 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-core/shared/src/main/scala/kyo/Gate.scala:507` calls `foreach`, `arriveAndLeave` and `kyo-core/shared/src/main/scala/kyo/Gate.scala:251` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) kyo-http/shared/src/main/scala/kyo/FlagAdmin.scala:81— kyo-http/shared/src/main/scala/kyo/FlagAdmin.scala:81-90 | kyo-http/shared/src/main/scala/kyo/FlagAdmin.scala:114-123 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:393— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:393-402 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:656-665 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:745— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:745-754 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:767-776 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:745` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2287— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2287-2296 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:324-333 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2285` calls `getOrElse` and `kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:323` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:159— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:159-168 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:195-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1633— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1633-1642 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:1986-1995 — 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) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:543— kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:543-552 | kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:561-570 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:543` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:88— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:88-97 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:114-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:195— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:195-204 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:477-486 — 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) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:1706— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:1706-1715 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:1580-1589 — 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) kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:20— kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:20-29 | kyo-bench/src/main/scala/kyo/bench/TagsBench.scala:38-47 — 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· Edited copy of a member (18 corresponding lines) · ×13
Edited copy of a member (18 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4653— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4653-4670 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4689-4707 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:132— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:132-149 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:138-155 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1789— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1789-1806 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1823-1845 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:883— kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:883-904 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:32-49 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-system-doltfs/shared/src/main/scala/kyo/internal/dolt/DoltVfsStore.scala:171— kyo-system-doltfs/shared/src/main/scala/kyo/internal/dolt/DoltVfsStore.scala:171-188 | kyo-system-doltfs/shared/src/main/scala/kyo/internal/dolt/DoltVfsStore.scala:199-219 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:351— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:351-369 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:374-391 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1310— kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1310-1330 | kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1358-1375 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:8-25 | kyo-bench/src/main/scala/kyo/bench/arena/TMapSingleKeyBench.scala:8-26 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:736— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:736-754 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:759-776 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:176— kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:176-199 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:271-288 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:367— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:367-389 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1156-1173 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:48— kyo-bench/src/main/scala/kyo/bench/arena/TMapMultiKeyBench.scala:48-66 | kyo-bench/src/main/scala/kyo/bench/arena/TMapSingleKeyBench.scala:49-66 — These two members are one piece of code written twice and then edited apart: 18 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.
Edited copy of a member (18 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/RandomBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/RandomBench.scala:8-25 | kyo-bench/src/main/scala/kyo/bench/arena/RandomBench.scala:54-71 — These two members are one piece of code written twice and then edited apart: 18 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.
TodoComment kyo-system/shared/src/test/scala/kyo/CommandTest.scala:82— // TODO: andThen pipe mechanism deadlocks on Windows — needs investigation in ProcessPlatformSpecific — 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 kyo-system/shared/src/test/scala/kyo/ProcessTest.scala:3— // TODO: Process tests use Unix commands (sleep, sh -c, kill) extensively. — 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 kyo-prelude/shared/src/main/scala/kyo/internal/LayerMacros.scala:25— // TODO: show full type of parent — 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 kyo-prelude/shared/src/main/scala/kyo/internal/LayerMacros.scala:31— // TODO: show full type of parent — 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 kyo-prelude/shared/src/main/scala/kyo/internal/LayerMacros.scala:34— // TODO: improve error message to include multiple nodes — 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 kyo-prelude/shared/src/main/scala/kyo/internal/LayerMacros.scala:75— // TODO: MAke nIcEr PlZEaz — 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 kyo-prelude/shared/src/main/scala/kyo/internal/LayerMacros.scala:198— // TODO: Maybe also trace the path. — 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 kyo-offheap/shared/src/main/scala/kyo/Memory.scala:76— // TODO inference issue without the val — 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 kyo-direct/shared/src/test/scala/kyo/CollShiftMethodSupportTest.scala:215— // TODO : catch xsValues.groupMap(i => f(i))( ... — 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 kyo-data/shared/src/test/scala/kyo/TagTest.scala:2159— // TODO: fix this to use `pendingUntilFixed` instead of `ignore` — 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 kyo-data/shared/src/main/scala/kyo/Duration.scala:265— // TODO Is this Robust enough? — 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 kyo-bench/src/main/scala/kyo/bench/ParseBench.scala:124— // TODO: real escaping support — 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×12
Edited copy of a member (13 corresponding lines) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:250— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:250-262 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:260-284 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:298— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:298-310 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:316-328 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:449— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:449-461 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:714-726 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:3833— kyo-browser/shared/src/main/scala/kyo/Browser.scala:3833-3845 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:3856-3873 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:112— kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:112-127 | kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:242-254 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:587— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:587-601 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:643-655 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:237— kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:237-249 | kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:270-283 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:46— kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:46-61 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/BufferFactory.scala:41-53 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-sql-dolt/shared/src/main/scala/kyo/internal/dolt/DoltConnection.scala:41— kyo-sql-dolt/shared/src/main/scala/kyo/internal/dolt/DoltConnection.scala:41-56 | kyo-sql-doltlite/shared/src/main/scala/kyo/internal/doltlite/DoltLiteConnection.scala:30-42 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:200— kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:200-212 | kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:220-232 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:575— kyo-browser/shared/src/main/scala/kyo/Browser.scala:575-587 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:592-604 — These two members are one piece of code written twice and then edited apart: 13 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.
Edited copy of a member (13 corresponding lines) kyo-core/shared/src/main/scala/kyo/Signal.scala:681— kyo-core/shared/src/main/scala/kyo/Signal.scala:681-693 | kyo-core/shared/src/main/scala/kyo/Signal.scala:697-709 — These two members are one piece of code written twice and then edited apart: 13 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 (2 corresponding lines) · ×11
Edited copy of a member (2 corresponding lines) kyo-data/shared/src/main/scala/kyo/internal/Ascii.scala:39— kyo-data/shared/src/main/scala/kyo/internal/Ascii.scala:39-40 | kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:72-73 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:875— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:875-876 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1079-1080 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala:397— kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala:397-398 | kyo-ui/shared/src/main/scala/kyo/internal/ChartLegend.scala:507-508 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-telegram/shared/src/main/scala/kyo/TelegramWebhookConfig.scala:36— kyo-telegram/shared/src/main/scala/kyo/TelegramWebhookConfig.scala:36-37 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppWebhookConfig.scala:36-37 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/CachingSha2Shared.scala:73— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/CachingSha2Shared.scala:73-74 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/auth/Sha256Password.scala:65-66 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:104— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:104-105 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresSqlConnection.scala:88-95 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:91— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:91-92 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:96-97 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:573— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:573-574 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:929-930 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyInResponseUnmarshaller.scala:29— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyInResponseUnmarshaller.scala:29-30 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/unmarshaller/CopyOutResponseUnmarshaller.scala:29-30 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-mime/shared/src/main/scala/kyo/mime/Disposition.scala:19— kyo-mime/shared/src/main/scala/kyo/mime/Disposition.scala:19-20 | kyo-mime/shared/src/main/scala/kyo/mime/MediaType.scala:26-27 — These two members are one piece of code written twice and then edited apart: 2 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.
Edited copy of a member (2 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:143— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:143-144 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:402-403 — These two members are one piece of code written twice and then edited apart: 2 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.
Duplicated block (15 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:305— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:305-319 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:304-318 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:305` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:738— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:738-752 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:758-772 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:738` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:705— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:705-719 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:746-760 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:705` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:448— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:448-462 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1217-1231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:448` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/transport/WritePump.scala:122— kyo-net/shared/src/main/scala/kyo/net/internal/transport/WritePump.scala:122-136 | kyo-net/shared/src/main/scala/kyo/net/internal/transport/WritePump.scala:145-159 — 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) kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:106— kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:106-120 | kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala:123-137 — before extracting anything, compare `kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala` and `kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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. Note first that the copies are not typed on the same thing: `Empty` names `IntLongMap.Empty` in one and `IntRefMap.Empty` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) REDACTED:292— REDACTED:292-306 | REDACTED:375-389 — 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 (15 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:173— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:173-187 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:196-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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:194` calls `readNat` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:171` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1369— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1369-1383 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1403-1417 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1179— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1179-1193 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1512-1526 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
MethodTooLong: JsonRpcEndpointImpl.finalizer kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:250— MethodTooLong — finalizer runs 466 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 366 over it, 4.66× 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: JsonRpcEndpointImpl.initEngine kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:268— MethodTooLong — initEngine runs 453 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 353 over it, 4.53× 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: LspClientEngine.initClientRefs kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:55— MethodTooLong — initClientRefs runs 438 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 338 over it, 4.38× 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: LspClientEngine.initClient kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:64— MethodTooLong — initClient runs 430 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 330 over it, 4.30× 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: LspEngine.initServerRefs kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:43— MethodTooLong — initServerRefs runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: LspEngine.initServer kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:68— MethodTooLong — initServer runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× 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: PathWatch.select kyo-system/shared/src/main/scala/kyo/PathWatch.scala:167— MethodTooLong — select runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: DomBackend.setupEventDelegation kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:612— MethodTooLong — setupEventDelegation runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: PathWatch.polling kyo-system/shared/src/main/scala/kyo/PathWatch.scala:189— MethodTooLong — polling runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×9
Members sharing a duplicated core (4 members, 50+ identical tokens) kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:86— kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:86-102 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:108-124 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:249-299 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:310-360 — 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) kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:31— kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:31-50 | kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:54-74 | kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:20-38 | kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:42-60 — 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) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:261— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:261-275 | kyo-teams/shared/src/main/scala/kyo/TeamsException.scala:255-269 | kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:265-279 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppException.scala:242-256 — 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) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:505— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:505-517 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:535-547 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:567-579 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:601-613 — 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) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:152— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:152-266 | kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:509-534 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:410-525 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:780-805 — 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) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:198— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:198-218 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:228-246 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:416-450 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:462-485 — 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) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1672— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1672-1679 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:1709-1716 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2025-2032 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2062-2069 — 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) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:483— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:483-499 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:509-525 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1123-1234 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1448-1568 — 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) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:97— kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:97-152 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:160-217 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:222-252 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:261-315 — 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· Edited copy of a member (22 corresponding lines) · ×9
Edited copy of a member (22 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:468— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:468-489 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:733-754 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:384— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:384-407 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1354-1375 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:143— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:143-164 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:212-233 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:69— kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:69-90 | kyo-net/shared/src/main/scala/kyo/net/internal/backend/IoBackend.scala:135-160 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/UIWindow.scala:216— kyo-ui/js-wasm/src/main/scala/kyo/UIWindow.scala:216-241 | kyo-ui/js-wasm/src/main/scala/kyo/UIWindow.scala:247-268 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:290— kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:290-311 | kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:324-346 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ExtendedQueryExchange.scala:123— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ExtendedQueryExchange.scala:123-144 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/SimpleQueryExchange.scala:97-120 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:542— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:542-563 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:606-629 — These two members are one piece of code written twice and then edited apart: 22 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.
Edited copy of a member (22 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1245— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1245-1266 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1280-1306 — These two members are one piece of code written twice and then edited apart: 22 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.
Duplicated block (16 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:183— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:183-198 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:307-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:701— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:701-716 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:398-413 — 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 (16 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:509— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:509-524 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:780-795 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:271— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:271-286 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:373-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:271` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1399— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1399-1414 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2293-2308 — 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) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:411— kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:411-426 | kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:113-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:459— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:459-474 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:970-985 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:459` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:173— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:173-188 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:221-236 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:173` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:140— kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspClientEngine.scala:140-155 | kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:179-194 — 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 (13 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:168— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:168-180 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:293-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:168` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:800— kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:800-812 | kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:1090-1102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:800` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:93— kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:93-105 | kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:128-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:434— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:434-446 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1393-1405 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:434` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:355— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:355-367 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:721-733 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:355` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/BuilderMacro.scala:99— kyo-schema/shared/src/main/scala/kyo/internal/BuilderMacro.scala:99-111 | kyo-schema/shared/src/main/scala/kyo/internal/BuilderMacro.scala:142-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1089— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1089-1101 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1963-1975 — 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) kyo-sql/shared/src/main/scala/kyo/internal/client/SqlConnectionPool.scala:139— kyo-sql/shared/src/main/scala/kyo/internal/client/SqlConnectionPool.scala:139-151 | kyo-sql/shared/src/main/scala/kyo/internal/client/SqlConnectionPool.scala:417-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/internal/client/SqlConnectionPool.scala:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:461— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:461-473 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:476-488 — 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) kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:562— kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:562-575 | kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:580-593 — 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) kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:275— kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:275-288 | kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:336-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1749— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1749-1762 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1469-1482 — 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) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:137— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:137-150 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:479-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:974— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:974-987 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1799-1812 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1813` calls `Select`, `Ident` and `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:988` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:1995— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:1995-2008 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:2468-2481 — 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) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:767— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:767-780 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1302-1315 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:767` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2635— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2635-2648 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2844-2857 — 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 × 3) kyo-ui/shared/src/main/scala/kyo/Chart.scala:831— kyo-ui/shared/src/main/scala/kyo/Chart.scala:831-835 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:842-846 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:853-857 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/Chart.scala:831` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) kyo-ui/shared/src/main/scala/kyo/Chart.scala:836— kyo-ui/shared/src/main/scala/kyo/Chart.scala:836-840 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:847-851 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:860-864 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/Chart.scala:836` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:667— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:667-671 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:798-802 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1439-1443 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:667` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:591— kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:591-600 | kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:925-929 | kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:983-989 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:591` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:931` calls `rule`, `flexWrap`, `gap` and `kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:600` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:776— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:776-783 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:787-791 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:796-802 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1330— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1330-1334 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2882-2886 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1575-1579 — 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 (5 lines × 3) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1196— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1196-1200 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:918-922 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:864-868 — 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 (5 lines × 3) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:388— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstBuilder.scala:388-392 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:306-310 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:309-313 — 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.
Low cohesion: MysqlDialect (LCOM4 9) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala:15— MysqlDialect's methods fall into 9 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 9 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: PosixHandle (LCOM4 8) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixHandle.scala:27— PosixHandle's methods fall into 8 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 8 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: ShellBackend (LCOM4 6) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:29— ShellBackend'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: IOPromise (LCOM4 4) kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:12— IOPromise'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: JsIoDriver (LCOM4 4) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsIoDriver.scala:23— JsIoDriver'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: SqliteDialect (LCOM4 4) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteDialect.scala:16— SqliteDialect'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: NodeRawChannel (LCOM4 4) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1181— NodeRawChannel'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: LocalExchange (LCOM4 4) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:178— LocalExchange'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.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×7
Edited copy of a member (1 corresponding lines) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:135— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:135-135 | kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala:72-72 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:88— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:88-89 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpHandlerLift.scala:63-63 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) REDACTED:321— REDACTED:321-321 | REDACTED:400-400 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) kyo-data/shared/src/main/scala/kyo/internal/Ascii.scala:24— kyo-data/shared/src/main/scala/kyo/internal/Ascii.scala:24-24 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:341-341 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:127— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:127-127 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:385-385 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:738— kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:738-738 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:246-246 — These two members are one piece of code written twice and then edited apart: 1 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.
Edited copy of a member (1 corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:523— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:523-523 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:548-548 — These two members are one piece of code written twice and then edited apart: 1 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.
Duplicated block (23 lines × 2) kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:167— kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:167-189 | kyo-flow/shared/src/main/scala/kyo/internal/FlowGraph.scala:222-244 — 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 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:424— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:424-446 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1191-1213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:424` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:774— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:774-796 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:805-827 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:774` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:233— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:233-255 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:492-514 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:76— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:76-98 | kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala:13-35 — before extracting anything, compare `kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala` and `kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1899— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1899-1921 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2771-2793 — 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 lines × 2) kyo-system/shared/src/main/scala/kyo/Path.scala:494— kyo-system/shared/src/main/scala/kyo/Path.scala:494-516 | kyo-system/shared/src/main/scala/kyo/Path.scala:540-562 — 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.
Hollow method — returns a constant without doing the work kyo-core/js-wasm/src/main/scala/kyo/VarHandle.scala:4— `loadLoadFence` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:720— `zeroInt` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:721— `zeroLong` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:722— `zeroFloat` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:723— `zeroDouble` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:724— `zeroBoolean` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:114— `beginSlice` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×6
Edited copy of a member (23 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:754— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:754-776 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:364-386 — These two members are one piece of code written twice and then edited apart: 23 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.
Edited copy of a member (23 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:602— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:602-629 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1258-1280 — These two members are one piece of code written twice and then edited apart: 23 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.
Edited copy of a member (23 corresponding lines) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:238— kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:238-264 | kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:273-295 — These two members are one piece of code written twice and then edited apart: 23 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.
Edited copy of a member (23 corresponding lines) kyo-core/shared/src/main/scala/kyo/Gate.scala:300— kyo-core/shared/src/main/scala/kyo/Gate.scala:300-322 | kyo-core/shared/src/main/scala/kyo/Gate.scala:593-617 — These two members are one piece of code written twice and then edited apart: 23 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.
Edited copy of a member (23 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:263— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:263-285 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:289-312 — These two members are one piece of code written twice and then edited apart: 23 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.
Edited copy of a member (23 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:288— kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:288-313 | kyo-net/shared/src/main/scala/kyo/net/internal/ConnectionPool.scala:399-421 — These two members are one piece of code written twice and then edited apart: 23 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 (19 corresponding lines) · ×6
Edited copy of a member (19 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/ExtendedQueryExchange.scala:308— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/ExtendedQueryExchange.scala:308-326 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/StreamQueryExchange.scala:366-384 — These two members are one piece of code written twice and then edited apart: 19 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.
Edited copy of a member (19 corresponding lines) REDACTED:148— REDACTED:148-166 | REDACTED:186-218 — These two members are one piece of code written twice and then edited apart: 19 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.
Edited copy of a member (19 corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/SemaphoreContentionBench.scala:10— kyo-bench/src/main/scala/kyo/bench/arena/SemaphoreContentionBench.scala:10-31 | kyo-bench/src/main/scala/kyo/bench/arena/SemaphoreContentionBench.scala:35-53 — These two members are one piece of code written twice and then edited apart: 19 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.
Edited copy of a member (19 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:102— kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:102-120 | kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala:119-137 — These two members are one piece of code written twice and then edited apart: 19 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.
Edited copy of a member (19 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/AnthropicCompletion.scala:90— kyo-ai/shared/src/main/scala/kyo/ai/completion/AnthropicCompletion.scala:90-108 | kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:142-166 — These two members are one piece of code written twice and then edited apart: 19 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.
Edited copy of a member (19 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:128— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:128-146 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:174-192 — These two members are one piece of code written twice and then edited apart: 19 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 copies of one member (3 members, 10+ corresponding lines) · ×6
Edited copies of one member (3 members, 10+ corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:511— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:511-522 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:525-538 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:551-560 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1186— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1186-1195 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1343-1352 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1328-1337 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:533— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:533-542 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:641-653 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:691-703 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1414— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1414-1423 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1436-1445 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1563-1572 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:178— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:178-188 | kyo-slack/shared/src/main/scala/kyo/SlackException.scala:156-166 | kyo-teams/shared/src/main/scala/kyo/TeamsException.scala:189-198 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:351— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:351-360 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:130-139 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:126-135 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×6
Edited copies of one member (3 members, 9+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:62— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:62-70 | kyo-kernel/shared/src/main/scala/kyo/kernel/ContextEffect.scala:48-56 | kyo-kernel/shared/src/main/scala/kyo/kernel/ContextEffect.scala:83-92 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/ModifierParser.scala:167— kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/ModifierParser.scala:167-175 | kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/ModifierParser.scala:209-217 | kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/ModifierParser.scala:236-244 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:64— kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:64-73 | kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:171-180 | kyo-core/shared/src/main/scala/kyo/scheduler/IOPromise.scala:184-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2512— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2512-2521 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2609-2617 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2694-2703 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:310— kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:310-319 | kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:322-330 | kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:336-344 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) kyo-http/shared/src/main/scala/kyo/HttpClient.scala:703— kyo-http/shared/src/main/scala/kyo/HttpClient.scala:703-711 | kyo-http/shared/src/main/scala/kyo/HttpClient.scala:736-744 | kyo-http/shared/src/main/scala/kyo/HttpClient.scala:771-779 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×6
Edited copies of one member (3 members, 8+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:8— kyo-bench/src/main/scala/kyo/bench/arena/DeepBindMapBench.scala:8-27 | kyo-bench/src/main/scala/kyo/bench/arena/NarrowBindMapBench.scala:8-16 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:90-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:379— kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:379-386 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:397-405 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:417-426 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:51— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:51-58 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlBufferReader.scala:63-71 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresBufferReader.scala:37-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:821— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:821-828 | kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:832-839 | kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:882-891 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:506— kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:506-513 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:524-531 | kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:542-549 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:199— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:199-206 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:231-239 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:244-251 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the function that made it · ×6
Disposable created and abandoned in the function that made it kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/snapshot/PlatformDigest.scala:63— `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Disposable created and abandoned in the function that made it kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:29— `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Disposable created and abandoned in the function that made it kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:80— `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Disposable created and abandoned in the function that made it kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:85— `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Disposable created and abandoned in the function that made it kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/ZipHandlePlatform.scala:95— `Files.walk(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.iterator` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.walk(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
Disposable created and abandoned in the function that made it kyo-bench/src/main/scala/kyo/bench/arena/Registry.scala:32— `Files.list(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.collect` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.list(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×5
Edited copy of a member (20 corresponding lines) kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:56— kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:56-76 | kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:218-238 — These two members are one piece of code written twice and then edited apart: 20 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.
Edited copy of a member (20 corresponding lines) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:1473— kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:1473-1492 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:1689-1713 — These two members are one piece of code written twice and then edited apart: 20 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.
Edited copy of a member (20 corresponding lines) kyo-core/shared/src/main/scala/kyo/Fiber.scala:1085— kyo-core/shared/src/main/scala/kyo/Fiber.scala:1085-1115 | kyo-stm/shared/src/main/scala/kyo/internal/CommitBuffer.scala:104-123 — These two members are one piece of code written twice and then edited apart: 20 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.
Edited copy of a member (20 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:105— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:105-124 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:150-170 — These two members are one piece of code written twice and then edited apart: 20 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.
Edited copy of a member (20 corresponding lines) kyo-core/shared/src/main/scala/kyo/Gate.scala:161— kyo-core/shared/src/main/scala/kyo/Gate.scala:161-187 | kyo-core/shared/src/main/scala/kyo/Gate.scala:191-210 — These two members are one piece of code written twice and then edited apart: 20 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 (33 corresponding lines) · ×5
Edited copy of a member (33 corresponding lines) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:96— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:96-128 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:102-134 — These two members are one piece of code written twice and then edited apart: 33 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.
Edited copy of a member (33 corresponding lines) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:76— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:76-108 | kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala:13-45 — These two members are one piece of code written twice and then edited apart: 33 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.
Edited copy of a member (33 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:256— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:256-288 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:292-324 — These two members are one piece of code written twice and then edited apart: 33 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.
Edited copy of a member (33 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:159— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:159-191 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:195-227 — These two members are one piece of code written twice and then edited apart: 33 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.
Edited copy of a member (33 corresponding lines) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:269— kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:269-303 | kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:315-347 — These two members are one piece of code written twice and then edited apart: 33 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 (21 corresponding lines) · ×5
Edited copy of a member (21 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1122— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1122-1148 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlSource.scala:245-265 — These two members are one piece of code written twice and then edited apart: 21 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.
Edited copy of a member (21 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:402— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:402-427 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:434-454 — These two members are one piece of code written twice and then edited apart: 21 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.
Edited copy of a member (21 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1369— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1369-1389 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1403-1423 — These two members are one piece of code written twice and then edited apart: 21 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.
Edited copy of a member (21 corresponding lines) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:83— kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:83-103 | kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:107-127 — These two members are one piece of code written twice and then edited apart: 21 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.
Edited copy of a member (21 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:1868— kyo-browser/shared/src/main/scala/kyo/Browser.scala:1868-1888 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:1897-1918 — These two members are one piece of code written twice and then edited apart: 21 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 copies of one member (3 members, 7+ corresponding lines) · ×5
Edited copies of one member (3 members, 7+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/SuspensionBench.scala:6— kyo-bench/src/main/scala/kyo/bench/arena/SuspensionBench.scala:6-13 | kyo-bench/src/main/scala/kyo/bench/arena/SuspensionBench.scala:17-24 | kyo-bench/src/main/scala/kyo/bench/arena/SuspensionBench.scala:28-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:572— kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:572-586 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:594-608 | kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:267-273 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:54— kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:54-63 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:67-73 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:77-85 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2370— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2370-2376 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2384-2390 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2402-2408 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxDisk.scala:54— kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/LinuxDisk.scala:54-63 | kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/MacosDisk.scala:33-39 | kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/WindowsDisk.scala:25-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×5
Edited copy of a member (25 corresponding lines) REDACTED:175— REDACTED:175-203 | REDACTED:227-251 — These two members are one piece of code written twice and then edited apart: 25 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.
Edited copy of a member (25 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala:188— kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala:188-212 | kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:58-87 — These two members are one piece of code written twice and then edited apart: 25 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.
Edited copy of a member (25 corresponding lines) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:860— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:860-896 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:901-925 — These two members are one piece of code written twice and then edited apart: 25 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.
Edited copy of a member (25 corresponding lines) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:272— kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:272-299 | kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:425-449 — These two members are one piece of code written twice and then edited apart: 25 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.
Edited copy of a member (25 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:955— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:955-982 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1000-1024 — These two members are one piece of code written twice and then edited apart: 25 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 copies of one member (3 members, 4+ corresponding lines) · ×5
Edited copies of one member (3 members, 4+ corresponding lines) kyo-teams/shared/src/main/scala/kyo/Teams.scala:258— kyo-teams/shared/src/main/scala/kyo/Teams.scala:258-261 | kyo-teams/shared/src/main/scala/kyo/internal/teams/KeyCache.scala:117-120 | kyo-teams/shared/src/main/scala/kyo/internal/teams/TokenCache.scala:161-164 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:210— kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:210-213 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:93-96 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/PortableInflate.scala:337-340 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:230— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:230-233 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1693-1696 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:509-515 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) REDACTED:45— REDACTED:45-48 | REDACTED:44-47 | kyo-system-doltfs/shared/src/main/scala/kyo/internal/dolt/DoltVfsStore.scala:46-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:458— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:458-464 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:469-475 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:488-491 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (17 lines × 2) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:529— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:529-545 | kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:749-765 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:548` calls `installCertHashFn` and `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:766` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:828— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:828-844 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:406-422 — 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 (17 lines × 2) kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:392— kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:392-408 | kyo-whatsapp/shared/src/main/scala/kyo/internal/whatsapp/Graph.scala:128-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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:87— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:87-103 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:160-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) kyo-tasty/js-wasm/src/main/scala/kyo/internal/tasty/query/ZipHandlePlatform.scala:9— kyo-tasty/js-wasm/src/main/scala/kyo/internal/tasty/query/ZipHandlePlatform.scala:9-25 | kyo-tasty/native/src/main/scala/kyo/internal/tasty/query/ZipHandlePlatform.scala:9-25 — 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 × 3) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:751— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:751-758 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1295-1302 | kyo-sql/shared/src/main/scala/kyo/internal/SqlMacros.scala:249-256 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 3) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:975— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:975-982 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1344-1351 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1800-1807 — 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 (8 lines × 3) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1035— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1035-1042 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1889-1896 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2166-2173 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1901` calls `NamedArg`, `unwrap` and `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1043` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 3) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:311— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:311-318 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:326-333 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:342-349 — 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 (8 lines × 3) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:753— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:753-760 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1154-1161 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/TlsEngineIo.scala:226-233 — 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 (7–8 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:832— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:832-838 | kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:882-889 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:381— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:381-388 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:3060-3066 — 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–8 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:596— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:596-603 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:640-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:596` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1562— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1562-1568 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1692-1699 — 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–8 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:24— kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:24-31 | kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:46-52 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:52` calls `copyWith` and `kyo-schema/shared/src/main/scala/kyo/internal/SchemaValidation.scala:31` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
IC1 · Incompleteness & stubs· Empty method body · ×5
Empty method body — does nothing with its inputs kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:12— `parkNanos` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:13— `unpark` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:717— `zeroVoid` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs kyo-kernel/js-wasm/src/main/scala/kyo/kernel/internal/Safepoint.scala:116— `endSlice` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs kyo-kernel/jvm-native/src/main/scala/kyo/kernel/internal/Safepoint.scala:209— `deadline` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×4
Edited copy of a member (24 corresponding lines) kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:348— kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:348-383 | kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:411-464 — These two members are one piece of code written twice and then edited apart: 24 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.
Edited copy of a member (24 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala:47— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlDialect.scala:47-73 | kyo-sql/shared/src/main/scala/kyo/db/Idiom.scala:104-127 — These two members are one piece of code written twice and then edited apart: 24 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.
Edited copy of a member (24 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ExtendedQueryExchange.scala:410— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ExtendedQueryExchange.scala:410-447 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/ResultSetExchange.scala:160-183 — These two members are one piece of code written twice and then edited apart: 24 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.
Edited copy of a member (24 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1393— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1393-1416 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:507-531 — These two members are one piece of code written twice and then edited apart: 24 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 (30 corresponding lines) · ×4
Edited copy of a member (30 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:858— kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:858-887 | kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:891-923 — These two members are one piece of code written twice and then edited apart: 30 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.
Edited copy of a member (30 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:3159— kyo-browser/shared/src/main/scala/kyo/Browser.scala:3159-3192 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:3274-3303 — These two members are one piece of code written twice and then edited apart: 30 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.
Edited copy of a member (30 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:2278— kyo-browser/shared/src/main/scala/kyo/Browser.scala:2278-2307 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:2328-2362 — These two members are one piece of code written twice and then edited apart: 30 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.
Edited copy of a member (30 corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/SimpleQueryExchange.scala:50— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/SimpleQueryExchange.scala:50-79 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/SimpleQueryExchange.scala:91-124 — These two members are one piece of code written twice and then edited apart: 30 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 (26 corresponding lines) · ×4
Edited copy of a member (26 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:33— kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:33-58 | kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:72-98 — These two members are one piece of code written twice and then edited apart: 26 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.
Edited copy of a member (26 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:338— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSqlConnection.scala:338-364 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresSqlConnection.scala:291-316 — These two members are one piece of code written twice and then edited apart: 26 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.
Edited copy of a member (26 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:64— kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:64-89 | kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala:61-88 — These two members are one piece of code written twice and then edited apart: 26 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.
Edited copy of a member (26 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:573— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:573-598 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:986-1017 — These two members are one piece of code written twice and then edited apart: 26 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.
Duplicated block (21 lines × 2) kyo-ffi/shared/src/main/scala/kyo/ffi/internal/GuardCore.scala:135— kyo-ffi/shared/src/main/scala/kyo/ffi/internal/GuardCore.scala:135-155 | kyo-ffi/shared/src/main/scala/kyo/ffi/internal/GuardCore.scala:197-217 — 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 (21 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:280— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:280-300 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:540-560 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:280` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:638— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:638-658 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1381-1401 — 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 (21 lines × 2) kyo-schema/shared/src/main/scala/kyo/Schema.scala:2096— kyo-schema/shared/src/main/scala/kyo/Schema.scala:2096-2116 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:2171-2191 — 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· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (9 members, 50+ identical tokens) kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:181— kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:181-196 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:217-259 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:269-286 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:290-303 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:309-320 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:330-335 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:339-348 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:353-358 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:362-375 — These 9 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 9 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 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:775— kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:775-781 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:875-881 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1074-1080 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1127-1133 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1154-1160 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1460-1466 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1500-1506 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1750-1756 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:2099-2107 — These 9 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 9 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 9 times.
Members sharing a duplicated core (9 members, 50+ identical tokens) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:913— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:913-2233 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2242-2279 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1041-1113 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:267-987 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1494-1758 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:375-1210 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotWriter.scala:88-354 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/SymbolSignature.scala:74-93 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:73-271 — These 9 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 9 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 9 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) kyo-core/shared/src/main/scala/kyo/Async.scala:609— kyo-core/shared/src/main/scala/kyo/Async.scala:609-611 | kyo-core/shared/src/main/scala/kyo/Async.scala:625-634 | kyo-core/shared/src/main/scala/kyo/Async.scala:649-659 | kyo-core/shared/src/main/scala/kyo/Async.scala:675-686 | kyo-core/shared/src/main/scala/kyo/Async.scala:703-715 | kyo-core/shared/src/main/scala/kyo/Async.scala:733-746 — These 6 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 6 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 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:368— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:368-389 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3456-3474 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3567-3585 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3600-3634 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3642-3657 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3664-3682 — These 6 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 6 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 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaAnnotationUnpickler.scala:205— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaAnnotationUnpickler.scala:205-221 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:22-37 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:56-71 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:257-280 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:65-93 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1440-1455 — These 6 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 6 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 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) kyo-discord/shared/src/main/scala/kyo/Discord.scala:764— kyo-discord/shared/src/main/scala/kyo/Discord.scala:764-787 | kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:129-137 | kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:149-159 | kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:64-72 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppPath.scala:44-46 — 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) kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:137— kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:137-149 | kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:192-199 | kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:34-42 | kyo-telegram/shared/src/main/scala/kyo/TelegramConfig.scala:149-155 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppConfig.scala:132-140 — 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) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:212— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:212-228 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:234-246 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:256-268 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:301-399 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2016-2045 — 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· Edited copy of a member (41 corresponding lines) · ×3
Edited copy of a member (41 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:322— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:322-362 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:445-488 — These two members are one piece of code written twice and then edited apart: 41 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.
Edited copy of a member (41 corresponding lines) kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:236— kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:236-288 | kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:309-349 — These two members are one piece of code written twice and then edited apart: 41 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.
Edited copy of a member (41 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:874— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:874-918 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:933-973 — These two members are one piece of code written twice and then edited apart: 41 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 copies of one member (3 members, 15+ corresponding lines) · ×3
Edited copies of one member (3 members, 15+ corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:533— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:533-548 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:552-566 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlSource.scala:74-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:303— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:303-318 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:355-369 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:420-434 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1282— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1282-1299 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1313-1328 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1383-1397 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×3
Edited copies of one member (3 members, 16+ corresponding lines) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:440— kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:440-455 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:459-475 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:479-495 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:90— kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:90-105 | kyo-kernel/shared/src/main/scala/kyo/kernel/Arrow.scala:125-140 | kyo-kernel/shared/src/main/scala/kyo/kernel/Effect.scala:82-98 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) kyo-pod/shared/src/main/scala/kyo/Container.scala:1266— kyo-pod/shared/src/main/scala/kyo/Container.scala:1266-1281 | kyo-pod/shared/src/main/scala/kyo/Container.scala:1294-1315 | kyo-pod/shared/src/main/scala/kyo/Container.scala:1325-1346 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×3
Edited copies of one member (4 members, 11+ corresponding lines) kyo-ui/shared/src/main/scala/kyo/Style.scala:350— kyo-ui/shared/src/main/scala/kyo/Style.scala:350-360 | kyo-ui/shared/src/main/scala/kyo/Style.scala:365-375 | kyo-ui/shared/src/main/scala/kyo/Style.scala:380-390 | kyo-ui/shared/src/main/scala/kyo/Style.scala:395-405 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 11+ corresponding lines) kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:264— kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:264-274 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:298-308 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:337-347 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:354-364 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 11+ corresponding lines) kyo-flow/shared/src/main/scala/kyo/Flow.scala:259— kyo-flow/shared/src/main/scala/kyo/Flow.scala:259-269 | kyo-flow/shared/src/main/scala/kyo/Flow.scala:314-324 | kyo-flow/shared/src/main/scala/kyo/Flow.scala:523-533 | kyo-flow/shared/src/main/scala/kyo/Flow.scala:575-585 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×3
Edited copies of one member (4 members, 9+ corresponding lines) kyo-compat/bindings/twitter-future/jvm/src/main/scala/kyo/compat/CIO.scala:275— kyo-compat/bindings/twitter-future/jvm/src/main/scala/kyo/compat/CIO.scala:275-283 | kyo-compat/bindings/twitter-future/jvm/src/main/scala/kyo/compat/CIO.scala:305-313 | kyo-compat/bindings/twitter-future/jvm/src/main/scala/kyo/compat/CIO.scala:321-331 | kyo-compat/bindings/twitter-future/jvm/src/main/scala/kyo/compat/CIO.scala:338-346 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CancelExchange.scala:155— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CancelExchange.scala:155-163 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:307-318 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:323-333 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:338-349 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) kyo-teams/shared/src/main/scala/kyo/Teams.scala:79— kyo-teams/shared/src/main/scala/kyo/Teams.scala:79-88 | kyo-teams/shared/src/main/scala/kyo/Teams.scala:96-105 | kyo-teams/shared/src/main/scala/kyo/Teams.scala:117-126 | kyo-teams/shared/src/main/scala/kyo/Teams.scala:210-218 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 5+ corresponding lines) · ×3
Edited copies of one member (4 members, 5+ corresponding lines) kyo-prelude/shared/src/main/scala/kyo/Layer.scala:222— kyo-prelude/shared/src/main/scala/kyo/Layer.scala:222-226 | kyo-prelude/shared/src/main/scala/kyo/Layer.scala:239-243 | kyo-prelude/shared/src/main/scala/kyo/Layer.scala:268-272 | kyo-prelude/shared/src/main/scala/kyo/Layer.scala:296-300 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 5+ corresponding lines) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:82— kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:82-87 | kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:92-96 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/BufferFactory.scala:60-65 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/BufferFactory.scala:70-75 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 5+ corresponding lines) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:93— kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:93-97 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:154-158 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:217-221 | kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpBuiltInRoutes.scala:224-228 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×3
Edited copies of one member (3 members, 6+ corresponding lines) kyo-ui/shared/src/main/scala/kyo/Chart.scala:1306— kyo-ui/shared/src/main/scala/kyo/Chart.scala:1306-1311 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:1330-1335 | kyo-ui/shared/src/main/scala/kyo/Chart.scala:1354-1359 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2700— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2700-2707 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2101-2106 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/TlsEngineIo.scala:96-101 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:481— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:481-487 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:492-498 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:510-515 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×3
Edited copies of one member (3 members, 5+ corresponding lines) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:700— kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:700-704 | kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:707-711 | kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:820-824 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:658— kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:658-664 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:667-673 | kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:676-680 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:273— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:273-277 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:323-330 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:489-493 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (30 lines × 2) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:346— kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:346-375 | kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:409-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:346` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:174— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:174-203 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:433-462 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 (30 lines × 2) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:206— kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:206-235 | kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:2169-2198 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) kyo-browser/shared/src/main/scala/kyo/Browser.scala:1871— kyo-browser/shared/src/main/scala/kyo/Browser.scala:1871-1888 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:1901-1918 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-browser/shared/src/main/scala/kyo/Browser.scala:1871` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-browser/shared/src/main/scala/kyo/Browser.scala:1900` calls `escapeJsString` and `kyo-browser/shared/src/main/scala/kyo/Browser.scala:1870` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:41— kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:41-58 | kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:81-98 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:80` calls `charAt` and `kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:40` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:230— kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:230-247 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppException.scala:215-233 — 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 (15–16 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1331— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1331-1346 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1365-1379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–16 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2304— kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2304-2318 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2499-2514 — 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–16 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:932— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:932-946 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1006-1021 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1004` calls `discard`, `readTypeNode`, `goto` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:931` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 3) kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:61— kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:61-73 | kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:223-235 | kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:257-269 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:58` calls `Chunk`, `onStep`, `onSleep` and `kyo-flow/shared/src/main/scala/kyo/internal/FlowLint.scala:256` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:143— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:143-155 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:233-245 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:350-362 — 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 (13 lines × 3) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:219— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:219-231 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:297-309 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:408-420 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:90— kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:90-99 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:112-121 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:290-299 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:351-360 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:90` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:185— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:185-194 | kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:515-524 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:444-453 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:786-795 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 × 4) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:49— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:49-58 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:65-74 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:81-90 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:270-279 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:59` calls `SymbolId` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:91` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:42— kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:42-50 | kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:82-90 | kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:121-129 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:80` calls `charAt` and `kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:40` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304— kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304-312 | kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:464-472 | kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:548-556 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:452— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:452-460 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:261-269 | kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:260-268 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:452` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `Kind` names `DiscordTransportException.Kind` in one and `TeamsTransportException.Kind` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7–9 lines × 2) kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:142— kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:142-148 | kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:230-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–9 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:571— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:571-579 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:591-597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:571` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:598` calls `Panic` and `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:580` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–9 lines × 2) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:95— kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:95-103 | kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:115-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:52— kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:52-58 | kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:55-61 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/BufferFactory.scala:47-53 — 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.
Duplicated block (7 lines × 3) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:72— kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:72-78 | kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:80-86 | kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:88-94 — 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) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:442— kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:442-448 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:461-467 | kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:481-487 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:442` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Swallowed exception (empty catch) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:539— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:419— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:885— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
ClassTooLong: SqlConnectionException kyo-sql/shared/src/main/scala/kyo/SqlException.scala:78— ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 35 over it, 1.09× 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: Variance kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:2525— ClassTooLong — 414 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 14 over it, 1.04× 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· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1558— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1558-1600 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1605-1636 — These two members are one piece of code written twice and then edited apart: 27 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.
Edited copy of a member (27 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:825— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:825-852 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala:405-431 — These two members are one piece of code written twice and then edited apart: 27 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 (72 corresponding lines) · ×2
Edited copy of a member (72 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1214— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1214-1285 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2134-2223 — These two members are one piece of code written twice and then edited apart: 72 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.
Edited copy of a member (72 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:231— kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:231-310 | kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:562-633 — These two members are one piece of code written twice and then edited apart: 72 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 (47 corresponding lines) · ×2
Edited copy of a member (47 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:967— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:967-1013 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1786-1844 — These two members are one piece of code written twice and then edited apart: 47 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.
Edited copy of a member (47 corresponding lines) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:332— kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:332-385 | kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:399-445 — These two members are one piece of code written twice and then edited apart: 47 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 (55 corresponding lines) · ×2
Edited copy of a member (55 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala:2004— kyo-schema/shared/src/main/scala/kyo/Schema.scala:2004-2058 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:4014-4071 — These two members are one piece of code written twice and then edited apart: 55 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.
Edited copy of a member (55 corresponding lines) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:659— kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:659-713 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:790-860 — These two members are one piece of code written twice and then edited apart: 55 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 (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala:81— kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala:81-114 | kyo-website-bundle/js/src/main/scala/kyo/website/DocsClient.scala:456-493 — These two members are one piece of code written twice and then edited apart: 34 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.
Edited copy of a member (34 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:199— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:199-232 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:236-269 — These two members are one piece of code written twice and then edited apart: 34 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 (28 corresponding lines) · ×2
Edited copy of a member (28 corresponding lines) kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:45— kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:45-72 | kyo-config/shared/src/main/scala/kyo/internal/XXHash.scala:110-141 — These two members are one piece of code written twice and then edited apart: 28 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.
Edited copy of a member (28 corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:300— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:300-333 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:489-516 — These two members are one piece of code written twice and then edited apart: 28 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 copies of one member (3 members, 18+ corresponding lines) · ×2
Edited copies of one member (3 members, 18+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:10— kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:10-28 | kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:32-49 | kyo-bench/src/main/scala/kyo/bench/arena/ForkSpawnBench.scala:53-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 18+ corresponding lines) kyo-parse/shared/src/main/scala/kyo/Parse.scala:499— kyo-parse/shared/src/main/scala/kyo/Parse.scala:499-516 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:537-556 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:578-599 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×2
Edited copies of one member (3 members, 11+ corresponding lines) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:416— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:416-426 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:227-237 | kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:221-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 11+ corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:566— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:566-576 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1475-1493 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1497-1513 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×2
Edited copies of one member (3 members, 13+ corresponding lines) kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:448— kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:448-460 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:471-486 | kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CIO.scala:498-516 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:10— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:10-22 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:26-38 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:42-54 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×2
Edited copies of one member (4 members, 7+ corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:281— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:281-287 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:297-303 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:350-365 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:375-381 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 7+ corresponding lines) kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:221— kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:221-229 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:236-244 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:251-257 | kyo-compat/bindings/ox/jvm/src/main/scala/kyo/compat/CIO.scala:280-287 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×2
Edited copies of one member (4 members, 10+ corresponding lines) kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeCounter.scala:39— kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeCounter.scala:39-48 | kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeGauge.scala:30-42 | kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeGauge.scala:74-86 | kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/UnsafeHistogram.scala:84-93 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 10+ corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala:1033— kyo-schema/shared/src/main/scala/kyo/Schema.scala:1033-1042 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:1052-1061 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:1071-1080 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:1090-1099 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 9+ corresponding lines) · ×2
Edited copies of one member (6 members, 9+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2379— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2379-2387 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2403-2411 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2490-2499 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2561-2570 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2589-2598 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2670-2679 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
Edited copies of one member (6 members, 9+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1903— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1903-1911 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1926-1934 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1947-1955 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2006-2015 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2053-2062 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:2134-2143 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
Duplicated block (27 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1567— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1567-1593 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1608-1634 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1635` calls `dispatchKeysLoop` and `kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1594` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (27 lines × 2) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:357— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:357-383 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:437-463 — 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 (22 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:205— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:205-226 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:464-485 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 (22 lines × 2) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:873— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:873-894 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:910-931 — 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 × 3) kyo-schema/shared/src/main/scala/kyo/Schema.scala:3342— kyo-schema/shared/src/main/scala/kyo/Schema.scala:3342-3361 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3617-3636 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3764-3783 — 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 (20 lines × 3) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:178— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:178-197 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:527-546 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:616-635 — 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 (19–20 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:152— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:152-170 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:410-429 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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 (19–20 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:202— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:202-220 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:260-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 2) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:113— kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:113-131 | kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala:50-68 — before extracting anything, compare `kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala` and `kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 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 (19 lines × 2) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:424— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:424-442 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:689-707 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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–16 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:222— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:222-237 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:339-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:339` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 2) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:276— kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:276-291 | kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:318-331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:276` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:396— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:396-410 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:201-215 | kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:201-215 — 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.
Duplicated block (15 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:275— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:275-289 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:325-339 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:547-561 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:74— kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala:74-88 | kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala:74-86 — before extracting anything, compare `kyo-net/shared/src/main/scala/kyo/net/internal/util/IntLongMap.scala` and `kyo-net/shared/src/main/scala/kyo/net/internal/util/IntRefMap.scala` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13–15 lines × 2) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:533— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:533-547 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:625-637 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:533` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) kyo-sql/shared/src/main/scala/kyo/internal/SqlBackendRegistryMacro.scala:57— kyo-sql/shared/src/main/scala/kyo/internal/SqlBackendRegistryMacro.scala:57-70 | kyo-sql/shared/src/main/scala/kyo/internal/SqlClientInitMacro.scala:164-177 | kyo-sql/shared/src/main/scala/kyo/internal/SqlStaticMacro.scala:341-354 — 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 (14 lines × 3) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2799— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2799-2812 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2820-2833 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2847-2860 — 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 (13–14 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:206— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:206-219 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:325-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:430— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:430-443 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:446-458 — 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–14 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2348— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2348-2358 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:368-381 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2348` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–14 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:643— kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:643-653 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:713-726 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:643` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:215— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:215-225 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:102-114 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:94— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:94-106 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:170-180 — 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–13 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:564— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:564-575 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1337-1349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1337` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:866— kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:866-878 | kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:901-912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:866` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:121— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:121-132 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:231-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:230` calls `OutboundReq` and `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:120` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–12 lines × 2) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:447— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:447-457 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:520-531 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:447` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:984— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:984-993 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1045-1054 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1906-1915 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1901` calls `NamedArg`, `unwrap` and `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1042` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:489— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:489-498 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1184-1193 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1517-1526 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:489` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:487` calls `Name` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 6) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:107— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:107-115 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:196-204 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:299-307 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:715-723 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:745-753 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:783-791 — 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.
Duplicated block (9 lines × 6) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:378— kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:378-386 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3463-3471 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3574-3582 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3606-3614 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3646-3654 | kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3672-3680 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:378` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3452` calls `findClass` and `kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3564` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–9 lines × 2) kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:46— kyo-bench/src/main/scala/kyo/bench/arena/HttpClientContentionBench.scala:46-54 | kyo-bench/src/main/scala/kyo/bench/arena/HttpServerContentionBench.scala:97-104 — 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–9 lines × 2) kyo-config/shared/src/main/scala/kyo/Rollout.scala:393— kyo-config/shared/src/main/scala/kyo/Rollout.scala:393-401 | kyo-config/shared/src/main/scala/kyo/Rollout.scala:526-533 — 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 × 6) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:694— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:694-700 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1179-1185 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:972-978 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1040-1046 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:683-696 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:777-783 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:694` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 6) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:175— kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:175-181 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:183-189 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:192-198 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:275-281 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:283-289 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:291-297 — 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.
Duplicated block (6–7 lines × 2) REDACTED:149— REDACTED:149-154 | REDACTED: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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) kyo-system/shared/src/main/scala/kyo/Path.scala:403— kyo-system/shared/src/main/scala/kyo/Path.scala:403-408 | kyo-system/shared/src/main/scala/kyo/Path.scala:417-423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-system/shared/src/main/scala/kyo/Path.scala:403` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 4) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:511— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:511-516 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:541-546 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:573-578 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:607-612 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:511` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) kyo-sql/shared/src/main/scala/kyo/Sql.scala:1672— kyo-sql/shared/src/main/scala/kyo/Sql.scala:1672-1677 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:1709-1714 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2025-2030 | kyo-sql/shared/src/main/scala/kyo/Sql.scala:2062-2067 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/Sql.scala:1672` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:97— kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:97-101 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:160-164 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:222-226 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:261-265 — 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 (5 lines × 4) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:148— kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:148-152 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:213-217 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:248-252 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:311-315 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (12 members, 50+ identical tokens) kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:11— kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:11-18 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:21-28 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:31-38 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:41-48 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:51-58 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:61-68 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:71-78 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:81-88 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:91-98 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:101-108 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:111-118 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:121-128 — These 12 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 12 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 12 times.
Members sharing a duplicated core (12 members, 50+ identical tokens) kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:11— kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:11-16 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:19-24 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:27-32 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:35-40 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:43-48 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:51-56 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:59-64 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:67-72 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:75-80 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:83-88 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:91-96 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:99-104 — These 12 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 12 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 12 times.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×2
Untrusted text written into markup unescaped kyo-browser/shared/src/main/resources/kyo/Readability.js:1549— `pageCacheHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped kyo-browser/shared/src/main/resources/kyo/Readability.js:1928— `noscript.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
ClasspathOrchestrator.finalizeMerge (cyclomatic 314) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:905— ClasspathOrchestrator.finalizeMerge has cyclomatic complexity 314 (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.
TypeUnpickler.decodeTag (cyclomatic 159) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:374— TypeUnpickler.decodeTag has cyclomatic complexity 159 (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.
CssStyleRenderer.renderProp (cyclomatic 124) kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala:251— CssStyleRenderer.renderProp has cyclomatic complexity 124 (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.
TreeUnpickler.decodeTreeTag (cyclomatic 120) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:266— TreeUnpickler.decodeTreeTag has cyclomatic complexity 120 (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.
_grabArticle (cyclomatic 115) kyo-browser/shared/src/main/resources/kyo/Readability.js:1031— _grabArticle has cyclomatic complexity 115 (threshold 15). Of this number, 103 points are the body's own statements and 12 belong to 4 function literals 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.
Eval.apply (cyclomatic 114) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:53— Eval.apply has cyclomatic complexity 114 (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.
ReactiveUI.dispatchToElement (cyclomatic 95) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:498— ReactiveUI.dispatchToElement has cyclomatic complexity 95 (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.
Tree.visit (cyclomatic 84) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:2288— Tree.visit has cyclomatic complexity 84 (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.
JsonRpcEndpointImpl.initEngine (cyclomatic 83) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:268— JsonRpcEndpointImpl.initEngine has cyclomatic complexity 83 (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.
Flow.run (cyclomatic 76) kyo-flow/shared/src/main/scala/kyo/Flow.scala:1318— Flow.run has cyclomatic complexity 76 (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.
YamlReader.sourceAnchorStats (cyclomatic 76) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1715— YamlReader.sourceAnchorStats has cyclomatic complexity 76 (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.
FocusMacro.desugarProductConfig (cyclomatic 76) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:732— FocusMacro.desugarProductConfig has cyclomatic complexity 76 (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.
FocusMacro.emitProductSchemaStatic (cyclomatic 69) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2088— FocusMacro.emitProductSchemaStatic has cyclomatic complexity 69 (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.
ShallowTagMacro.derive (cyclomatic 63) kyo-data/shared/src/main/scala/kyo/internal/ShallowTagMacro.scala:69— ShallowTagMacro.derive has cyclomatic complexity 63 (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.
JvmEmitter.emitPlainMethodBody (cyclomatic 63) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:94— JvmEmitter.emitPlainMethodBody has cyclomatic complexity 63 (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.
LspCapabilityGate.missingCapability (cyclomatic 61) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspGate.scala:172— LspCapabilityGate.missingCapability has cyclomatic complexity 61 (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.
HtmlRenderer.renderElementAttrs (cyclomatic 60) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:662— HtmlRenderer.renderElementAttrs has cyclomatic complexity 60 (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: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
IoUringDriver.complete (cyclomatic 55) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2011— IoUringDriver.complete has cyclomatic complexity 55 (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.
Subtyping.isSubtype (cyclomatic 55) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:67— Subtyping.isSubtype has cyclomatic complexity 55 (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.
TypeKey.structuralEquals (cyclomatic 55) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:361— TypeKey.structuralEquals has cyclomatic complexity 55 (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.
Validate.apply (cyclomatic 54) kyo-direct/shared/src/main/scala/kyo/internal/Validate.scala:46— Validate.apply has cyclomatic complexity 54 (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.
FocusMacro.desugarSumConfig (cyclomatic 53) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1286— FocusMacro.desugarSumConfig has cyclomatic complexity 53 (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.
FromExprDerived.resolveBindings (cyclomatic 49) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:403— FromExprDerived.resolveBindings has cyclomatic complexity 49 (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.
JsonRpcEnvelopeSchema.envelopeSchema (cyclomatic 47) kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala:29— JsonRpcEnvelopeSchema.envelopeSchema 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.
ProtoSchema.fromStructure (cyclomatic 46) kyo-schema-protobuf/shared/src/main/scala/kyo/Protobuf.scala:324— ProtoSchema.fromStructure has cyclomatic complexity 46 (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.
Classpath.allMembersOf (cyclomatic 46) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4710— Classpath.allMembersOf has cyclomatic complexity 46 (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.
SnapshotReader.readErrors (cyclomatic 46) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1585— SnapshotReader.readErrors has cyclomatic complexity 46 (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.
DomBackend.setupEventDelegation (cyclomatic 46) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:612— DomBackend.setupEventDelegation has cyclomatic complexity 46 (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.
HtmlRenderer.renderEventAttr (cyclomatic 46) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:886— HtmlRenderer.renderEventAttr has cyclomatic complexity 46 (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. This is NOT this file's highest cyclomatic complexity: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
StreamCompression.gunzipStream (cyclomatic 45) kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:404— StreamCompression.gunzipStream has cyclomatic complexity 45 (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.
SnapshotReader.deserializeMapped (cyclomatic 44) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:718— SnapshotReader.deserializeMapped 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.
Iso2022JpDecoder.run (cyclomatic 43) kyo-charset/shared/src/main/scala/kyo/internal/charset/Iso2022JpDecoder.scala:22— Iso2022JpDecoder.run has cyclomatic complexity 43 (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.
ClasspathOrchestrator.mergeOneInto (cyclomatic 43) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:675— ClasspathOrchestrator.mergeOneInto has cyclomatic complexity 43 (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.
Markdown.splitBlocks (cyclomatic 42) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:151— Markdown.splitBlocks has cyclomatic complexity 42 (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.
PathWatch.polling (cyclomatic 42) kyo-system/shared/src/main/scala/kyo/PathWatch.scala:189— PathWatch.polling has cyclomatic complexity 42 (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.
SnapshotReader.deserialize (cyclomatic 42) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:205— SnapshotReader.deserialize has cyclomatic complexity 42 (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.
TreeUnpickler.decodeTptAsType (cyclomatic 41) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1488— TreeUnpickler.decodeTptAsType has cyclomatic complexity 41 (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.
TypeArena.merge (cyclomatic 41) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeArena.scala:33— TypeArena.merge has cyclomatic complexity 41 (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.
NativeEmitter.emitBodyInner (cyclomatic 40) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:166— NativeEmitter.emitBodyInner has cyclomatic complexity 40 (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.
SchemaSerializer.writeWithTransforms (cyclomatic 40) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:290— SchemaSerializer.writeWithTransforms has cyclomatic complexity 40 (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.
FromExprDerived.deriveChunk (cyclomatic 40) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1847— FromExprDerived.deriveChunk has cyclomatic complexity 40 (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.
NativeArtifactFormat.archReadingOfHeader (cyclomatic 39) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/NativeArtifactFormat.scala:95— NativeArtifactFormat.archReadingOfHeader has cyclomatic complexity 39 (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.
DocsMarkdownRender.splitBlocks (cyclomatic 39) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:409— DocsMarkdownRender.splitBlocks has cyclomatic complexity 39 (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.
JsEmitter.emitPlainMethodBody (cyclomatic 38) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:212— JsEmitter.emitPlainMethodBody has cyclomatic complexity 38 (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.
UnsafeServerDispatch.serveH1 (cyclomatic 38) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:111— UnsafeServerDispatch.serveH1 has cyclomatic complexity 38 (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.
JsonSchema.writeJsonSchema (cyclomatic 38) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:315— JsonSchema.writeJsonSchema has cyclomatic complexity 38 (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.
TimeText.instant (cyclomatic 37) kyo-schema/shared/src/main/scala/kyo/internal/TimeText.scala:16— TimeText.instant has cyclomatic complexity 37 (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.
ChartMarks.lowerPoint (cyclomatic 37) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1373— ChartMarks.lowerPoint has cyclomatic complexity 37 (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.
internal.isSubType (cyclomatic 36) kyo-data/shared/src/main/scala/kyo/Tag.scala:446— internal.isSubType has cyclomatic complexity 36 (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.
LspCatalog.deriveFromKinds (cyclomatic 36) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspCatalog.scala:102— LspCatalog.deriveFromKinds has cyclomatic complexity 36 (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.
TypeKey.pushHashWork (cyclomatic 36) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:156— TypeKey.pushHashWork has cyclomatic complexity 36 (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.
DomBackend.setupInputMasking (cyclomatic 36) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:950— DomBackend.setupInputMasking 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.
_getJSONLD (cyclomatic 36) kyo-browser/shared/src/main/resources/kyo/Readability.js:1632— _getJSONLD has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 1637, 1651, 1675, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
NonZeroCapacityUnsafe.flush (cyclomatic 35) kyo-core/shared/src/main/scala/kyo/Channel.scala:837— NonZeroCapacityUnsafe.flush has cyclomatic complexity 35 (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.
YamlParser.unescapeDoubleQuoted (cyclomatic 35) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:911— YamlParser.unescapeDoubleQuoted has cyclomatic complexity 35 (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.
FocusMacro.summonAnnotationPolicy (cyclomatic 35) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:522— FocusMacro.summonAnnotationPolicy has cyclomatic complexity 35 (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.
RyuDouble.writeImpl (cyclomatic 35) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:75— RyuDouble.writeImpl has cyclomatic complexity 35 (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. This shape REPEATS in the file: one other method here (RyuFloat.writeImpl) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RyuFloat.writeImpl (cyclomatic 35) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:423— RyuFloat.writeImpl has cyclomatic complexity 35 (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. This shape REPEATS in the file: one other method here (RyuDouble.writeImpl) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Classpath.typeFullNameString (cyclomatic 35) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4182— Classpath.typeFullNameString has cyclomatic complexity 35 (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: Classpath.unresolvedTypeReferenceCount (cyclomatic 43) 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 method is counted neither in this dimension's figures nor in its score.
_getArticleMetadata (cyclomatic 35) kyo-browser/shared/src/main/resources/kyo/Readability.js:1757— _getArticleMetadata has cyclomatic complexity 35 (threshold 15). Of this number, 28 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LLM.eval (cyclomatic 34) kyo-ai/shared/src/main/scala/kyo/LLM.scala:627— LLM.eval has cyclomatic complexity 34 (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.
TagMacro.deriveDB (cyclomatic 34) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:370— TagMacro.deriveDB 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.
NodeCommandUnsafe.spawn (cyclomatic 34) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:655— NodeCommandUnsafe.spawn 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.
ChartMarks.lowerBarStacked (cyclomatic 34) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:403— ChartMarks.lowerBarStacked has cyclomatic complexity 34 (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.
Graph.describe (cyclomatic 34) kyo-whatsapp/shared/src/main/scala/kyo/internal/whatsapp/Graph.scala:101— Graph.describe 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.
NativeEmitter.emitStructRead (cyclomatic 33) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:641— NativeEmitter.emitStructRead has cyclomatic complexity 33 (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.
RouteUtil.multipartBoundaryFromHeaders (cyclomatic 33) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:813— RouteUtil.multipartBoundaryFromHeaders has cyclomatic complexity 33 (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.
JsonReader.readQuotedStringWithEscapes (cyclomatic 32) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:472— JsonReader.readQuotedStringWithEscapes 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.
TypedSymbolFactory.from (cyclomatic 32) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:37— TypedSymbolFactory.from has cyclomatic complexity 32 (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.
TypeOps.applied (cyclomatic 32) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeOps.scala:68— TypeOps.applied 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.
MpmcUnboundedUnsafeQueue.peek (cyclomatic 31) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:266— MpmcUnboundedUnsafeQueue.peek has cyclomatic complexity 31 (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.
Http1Parser.parseRequestLine (cyclomatic 31) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:349— Http1Parser.parseRequestLine has cyclomatic complexity 31 (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.
JvmCommandUnsafe.toJProcessBuilder (cyclomatic 31) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:179— JvmCommandUnsafe.toJProcessBuilder 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.
AstUnpickler.walkStats (cyclomatic 31) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:281— AstUnpickler.walkStats has cyclomatic complexity 31 (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.
Subtyping.checkArgPairs (cyclomatic 31) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:405— Subtyping.checkArgPairs has cyclomatic complexity 31 (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.
MpmcUnboundedUnsafeQueue.poll (cyclomatic 30) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:138— MpmcUnboundedUnsafeQueue.poll has cyclomatic complexity 30 (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.
JvmEmitter.emitVariadicMethodBody (cyclomatic 30) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:554— JvmEmitter.emitVariadicMethodBody has cyclomatic complexity 30 (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.
JsTransport.upgradeConnection (cyclomatic 30) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:960— JsTransport.upgradeConnection has cyclomatic complexity 30 (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.
NioTransport.driveHandshake (cyclomatic 30) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:953— NioTransport.driveHandshake has cyclomatic complexity 30 (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.
IonSchema.fromStructure (cyclomatic 30) kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:177— IonSchema.fromStructure has cyclomatic complexity 30 (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.
FastFloat.readFloat (cyclomatic 30) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:226— FastFloat.readFloat has cyclomatic complexity 30 (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.
WireLayout.apply (cyclomatic 30) kyo-schema/shared/src/main/scala/kyo/internal/WireLayout.scala:161— WireLayout.apply has cyclomatic complexity 30 (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.
FromExprDerived.buildChunk (cyclomatic 30) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1016— FromExprDerived.buildChunk has cyclomatic complexity 30 (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.
Runtime.snapshot (cyclomatic 30) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1194— Runtime.snapshot has cyclomatic complexity 30 (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.
ChartMarks.lowerAreaStacked (cyclomatic 30) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1195— ChartMarks.lowerAreaStacked has cyclomatic complexity 30 (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.
ConcreteTagMacro.derive (cyclomatic 29) kyo-data/shared/src/main/scala/kyo/internal/ConcreteTagMacro.scala:20— ConcreteTagMacro.derive has cyclomatic complexity 29 (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.
NativeEmitter.emitStructWrite (cyclomatic 29) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:473— NativeEmitter.emitStructWrite has cyclomatic complexity 29 (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.
UnsafeServerDispatch.serveRequest (cyclomatic 29) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:691— UnsafeServerDispatch.serveRequest has cyclomatic complexity 29 (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.
Completion.sseFragments (cyclomatic 28) kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala:362— Completion.sseFragments has cyclomatic complexity 28 (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.
Rollout.parseRolloutChoices (cyclomatic 28) kyo-config/shared/src/main/scala/kyo/Rollout.scala:281— Rollout.parseRolloutChoices 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.
PathWatch.scan (cyclomatic 28) kyo-system/shared/src/main/scala/kyo/PathWatch.scala:40— PathWatch.scan has cyclomatic complexity 28 (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.
ChartLayout.buildLayout (cyclomatic 28) kyo-ui/shared/src/main/scala/kyo/internal/ChartLayout.scala:144— ChartLayout.buildLayout has cyclomatic complexity 28 (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.
Frame.extractCalleeName (cyclomatic 27) kyo-data/shared/src/main/scala/kyo/Frame.scala:266— Frame.extractCalleeName has cyclomatic complexity 27 (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.
TagMacro.refuseCollapsed (cyclomatic 27) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:246— TagMacro.refuseCollapsed 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.
PollerIoDriver.dispatchReadTls (cyclomatic 27) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2125— PollerIoDriver.dispatchReadTls 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.
YamlReader.unescapeSourceDoubleQuoted (cyclomatic 27) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1404— YamlReader.unescapeSourceDoubleQuoted has cyclomatic complexity 27 (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.
SchemaSerializer.readWithTransforms (cyclomatic 27) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1172— SchemaSerializer.readWithTransforms has cyclomatic complexity 27 (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.
FromExprDerived.buildDirect (cyclomatic 27) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:844— FromExprDerived.buildDirect 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.
JvmCommandUnsafe.spawn (cyclomatic 27) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:418— JvmCommandUnsafe.spawn has cyclomatic complexity 27 (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.
Runtime.probe (cyclomatic 27) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1121— Runtime.probe 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.
HzGb2312Decoder.run (cyclomatic 26) kyo-charset/shared/src/main/scala/kyo/internal/charset/HzGb2312Decoder.scala:20— HzGb2312Decoder.run has cyclomatic complexity 26 (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.
Context.extractType (cyclomatic 26) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:929— Context.extractType has cyclomatic complexity 26 (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.
TypeValidator.validate (cyclomatic 26) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:28— TypeValidator.validate has cyclomatic complexity 26 (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.
UnsafeServerDispatch.dispatchHandler (cyclomatic 26) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:913— UnsafeServerDispatch.dispatchHandler has cyclomatic complexity 26 (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.
HttpContainerBackend.create (cyclomatic 26) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:300— HttpContainerBackend.create has cyclomatic complexity 26 (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.
MsgPackReader.skip (cyclomatic 26) kyo-schema-msgpack/shared/src/main/scala/kyo/internal/msgpack/MsgPackReader.scala:457— MsgPackReader.skip has cyclomatic complexity 26 (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.
SchemaSerializer.writeStructureValue (cyclomatic 26) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1418— SchemaSerializer.writeStructureValue has cyclomatic complexity 26 (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.
ChartLayout.leftAxisMargin (cyclomatic 26) kyo-ui/shared/src/main/scala/kyo/internal/ChartLayout.scala:84— ChartLayout.leftAxisMargin has cyclomatic complexity 26 (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.
Request.apply (cyclomatic 25) kyo-ai/shared/src/main/scala/kyo/ai/completion/AnthropicCompletion.scala:276— Request.apply has cyclomatic complexity 25 (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.
Structure.conform (cyclomatic 25) kyo-schema/shared/src/main/scala/kyo/Structure.scala:93— Structure.conform has cyclomatic complexity 25 (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.
WalkContext.walkDictChain (cyclomatic 25) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:131— WalkContext.walkDictChain has cyclomatic complexity 25 (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.
ConstantPool.read (cyclomatic 25) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ConstantPool.scala:295— ConstantPool.read has cyclomatic complexity 25 (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.
SnapshotWriter.serialize (cyclomatic 25) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotWriter.scala:86— SnapshotWriter.serialize has cyclomatic complexity 25 (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: SnapshotWriter.serializeErrors (cyclomatic 40) 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 method is counted neither in this dimension's figures nor in its score.
ChartScales.yLeftExtent (cyclomatic 25) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:96— ChartScales.yLeftExtent has cyclomatic complexity 25 (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.
ChartTransitions.renderPathDataStr (cyclomatic 25) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:203— ChartTransitions.renderPathDataStr has cyclomatic complexity 25 (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.
HtmlRenderer.renderTo (cyclomatic 25) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:235— HtmlRenderer.renderTo has cyclomatic complexity 25 (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: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
HtmlRenderer.pathCmd (cyclomatic 25) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:2168— HtmlRenderer.pathCmd has cyclomatic complexity 25 (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: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
_cleanConditionally::(anonymous)::shouldRemoveNode (cyclomatic 25) kyo-browser/shared/src/main/resources/kyo/Readability.js:2555— _cleanConditionally::(anonymous)::shouldRemoveNode has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ClaudeCodeCompletion.runClaudeCommand (cyclomatic 24) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:200— ClaudeCodeCompletion.runClaudeCommand 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.
CdpBackend.initUnscoped (cyclomatic 24) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:228— CdpBackend.initUnscoped has cyclomatic complexity 24 (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.
Gb18030Decoder.run (cyclomatic 24) kyo-charset/shared/src/main/scala/kyo/internal/charset/Gb18030Decoder.scala:16— Gb18030Decoder.run 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.
Unsafe.add (cyclomatic 24) kyo-core/shared/src/main/scala/kyo/Cache.scala:498— Unsafe.add 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.
internal.isSameType (cyclomatic 24) kyo-data/shared/src/main/scala/kyo/Tag.scala:593— internal.isSameType 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.
Http1Parser.matchMethod (cyclomatic 24) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:803— Http1Parser.matchMethod has cyclomatic complexity 24 (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.
YamlScalars.isFloatNumber (cyclomatic 24) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:255— YamlScalars.isFloatNumber 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.
Walk.column (cyclomatic 24) kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:80— Walk.column has cyclomatic complexity 24 (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.
_fixLazyImages (cyclomatic 24) kyo-browser/shared/src/main/resources/kyo/Readability.js:2332— _fixLazyImages has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to one function literal inside it that branches (line 2335). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Actionability.decodeReason (cyclomatic 23) kyo-browser/shared/src/main/scala/kyo/internal/Actionability.scala:315— Actionability.decodeReason has cyclomatic complexity 23 (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.
Iso2022KrDecoder.run (cyclomatic 23) kyo-charset/shared/src/main/scala/kyo/internal/charset/Iso2022KrDecoder.scala:23— Iso2022KrDecoder.run 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.
Utf7Decoder.run (cyclomatic 23) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf7Decoder.scala:18— Utf7Decoder.run 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.
Context.extractMethodSpec (cyclomatic 23) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:441— Context.extractMethodSpec 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.
JvmEmitter.emitStructReadExpr (cyclomatic 23) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:930— JvmEmitter.emitStructReadExpr has cyclomatic complexity 23 (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.
Progress.build (cyclomatic 23) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:1661— Progress.build has cyclomatic complexity 23 (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.
StoreInterpreter.withTimeoutAndRetry (cyclomatic 23) kyo-flow/shared/src/main/scala/kyo/internal/StoreInterpreter.scala:159— StoreInterpreter.withTimeoutAndRetry has cyclomatic complexity 23 (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.
Path.setAt (cyclomatic 23) kyo-schema/shared/src/main/scala/kyo/Structure.scala:1153— Path.setAt 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.
Wire.decodeEvent (cyclomatic 23) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:348— Wire.decodeEvent has cyclomatic complexity 23 (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.
NodePathLock.acquire (cyclomatic 23) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:422— NodePathLock.acquire has cyclomatic complexity 23 (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.
NameUnpickler.readUnsafe (cyclomatic 23) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:90— NameUnpickler.readUnsafe has cyclomatic complexity 23 (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.
DomBackend.mountInto (cyclomatic 23) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:78— DomBackend.mountInto has cyclomatic complexity 23 (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.
Runtime.handleSensor (cyclomatic 23) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:323— Runtime.handleSensor 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.
ChartMarks.lowerErrorBar (cyclomatic 23) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:838— ChartMarks.lowerErrorBar 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.
ReactiveUI.walkStatic (cyclomatic 23) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:192— ReactiveUI.walkStatic has cyclomatic complexity 23 (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. This is NOT this file's highest cyclomatic complexity: ReactiveUI.rebuildSvgElement (cyclomatic 48) 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 method is counted neither in this dimension's figures nor in its score.
LLM.completeElements (cyclomatic 22) kyo-ai/shared/src/main/scala/kyo/LLM.scala:331— LLM.completeElements 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.
CdpBackend.initUnscoped (cyclomatic 22) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:553— CdpBackend.initUnscoped has cyclomatic complexity 22 (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.
ShiftJisDecoder.run (cyclomatic 22) kyo-charset/shared/src/main/scala/kyo/internal/charset/ShiftJisDecoder.scala:15— ShiftJisDecoder.run 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.
SegmentParser.parseSequence (cyclomatic 22) kyo-data/shared/src/main/scala/kyo/Glob.scala:361— SegmentParser.parseSequence has cyclomatic complexity 22 (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.
TagMacro.bindUnderlying (cyclomatic 22) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:156— TagMacro.bindUnderlying has cyclomatic complexity 22 (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.
Gateway.connection (cyclomatic 22) kyo-discord/shared/src/main/scala/kyo/internal/discord/Gateway.scala:81— Gateway.connection has cyclomatic complexity 22 (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.
SmtpSession.transfer (cyclomatic 22) kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:140— SmtpSession.transfer 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.
FlagAdmin.routes (cyclomatic 22) kyo-http/shared/src/main/scala/kyo/FlagAdmin.scala:47— FlagAdmin.routes has cyclomatic complexity 22 (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.
PosixTransport.upgradeRole (cyclomatic 22) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1647— PosixTransport.upgradeRole 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.
ShellBackend.mapError (cyclomatic 22) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:2283— ShellBackend.mapError 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.
FocusMacro.givenSchema (cyclomatic 22) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:388— FocusMacro.givenSchema has cyclomatic complexity 22 (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.
FocusMacro.reifyAnnotation (cyclomatic 22) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:625— FocusMacro.reifyAnnotation has cyclomatic complexity 22 (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.
SchemaTransformMacro.flattenFieldsImpl (cyclomatic 22) kyo-schema/shared/src/main/scala/kyo/internal/SchemaTransformMacro.scala:335— SchemaTransformMacro.flattenFieldsImpl has cyclomatic complexity 22 (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.
Wire.decodeInteraction (cyclomatic 22) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:440— Wire.decodeInteraction has cyclomatic complexity 22 (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.
Subtyping.typeEquivAlpha (cyclomatic 22) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:510— Subtyping.typeEquivAlpha has cyclomatic complexity 22 (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.
ChartMarks.lowerText (cyclomatic 22) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:752— ChartMarks.lowerText has cyclomatic complexity 22 (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.
ChartTransitions.rowKey (cyclomatic 22) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:107— ChartTransitions.rowKey has cyclomatic complexity 22 (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.
DocsMarkdownRender.tokenizeBash (cyclomatic 22) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1244— DocsMarkdownRender.tokenizeBash 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.
Readability.Readability (cyclomatic 22) kyo-browser/shared/src/main/resources/kyo/Readability.js:27— Readability.Readability has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Utf16Decoder.run (cyclomatic 21) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf16Decoder.scala:21— Utf16Decoder.run has cyclomatic complexity 21 (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.
HttpClientBackend.buildBodyStream (cyclomatic 21) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:657— HttpClientBackend.buildBodyStream has cyclomatic complexity 21 (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.
Http1ResponseParser.packResponse (cyclomatic 21) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:210— Http1ResponseParser.packResponse has cyclomatic complexity 21 (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.
RouteUtil.feedMultipart (cyclomatic 21) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1310— RouteUtil.feedMultipart has cyclomatic complexity 21 (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.
PollerIoDriver.dispatchCmd (cyclomatic 21) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2605— PollerIoDriver.dispatchCmd has cyclomatic complexity 21 (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.
ShellBackend.logs (cyclomatic 21) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:835— ShellBackend.logs has cyclomatic complexity 21 (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.
IonSchema.applyConstraints (cyclomatic 21) kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:350— IonSchema.applyConstraints has cyclomatic complexity 21 (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.
Parser.parseValue (cyclomatic 21) kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:392— Parser.parseValue has cyclomatic complexity 21 (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.
SchemaSerializer.readTables (cyclomatic 21) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:54— SchemaSerializer.readTables has cyclomatic complexity 21 (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.
HstoreReader.parseText (cyclomatic 21) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/HstoreReader.scala:190— HstoreReader.parseText has cyclomatic complexity 21 (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.
Classpath.findObject (cyclomatic 21) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:3599— Classpath.findObject has cyclomatic complexity 21 (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: Classpath.unresolvedTypeReferenceCount (cyclomatic 43) 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 method is counted neither in this dimension's figures nor in its score.
ChartMarks.marksRegion (cyclomatic 21) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:44— ChartMarks.marksRegion has cyclomatic complexity 21 (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.
ChartMarks.lowerBarGrouped (cyclomatic 21) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:268— ChartMarks.lowerBarGrouped has cyclomatic complexity 21 (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.
ChartMarks.lowerArea (cyclomatic 21) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1035— ChartMarks.lowerArea has cyclomatic complexity 21 (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.
ChartScales.resolveAllScales (cyclomatic 21) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:419— ChartScales.resolveAllScales has cyclomatic complexity 21 (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.
WebsiteBundleMain.build (cyclomatic 21) kyo-website-bundle/js/src/main/scala/kyo/website/WebsiteBundleMain.scala:102— WebsiteBundleMain.build has cyclomatic complexity 21 (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.
(anonymous)::collapseWhitespace (cyclomatic 21) REDACTED:456— (anonymous)::collapseWhitespace has cyclomatic complexity 21 (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.
Utf8.run (cyclomatic 20) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:20— Utf8.run has cyclomatic complexity 20 (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.
Rollout.validateNonEmpty (cyclomatic 20) kyo-config/shared/src/main/scala/kyo/Rollout.scala:538— Rollout.validateNonEmpty has cyclomatic complexity 20 (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.
IOTask.run (cyclomatic 20) kyo-core/shared/src/main/scala/kyo/scheduler/IOTask.scala:259— IOTask.run has cyclomatic complexity 20 (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.
ImapSession.idling (cyclomatic 20) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:507— ImapSession.idling has cyclomatic complexity 20 (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.
Context.extractParentArgs (cyclomatic 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:165— Context.extractParentArgs 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.
JsEmitter.emitStructReadExpr (cyclomatic 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:665— JsEmitter.emitStructReadExpr 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.
JvmEmitter.emitStructWrite (cyclomatic 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:754— JvmEmitter.emitStructWrite 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.
UpcallBridge.zeroHandlerName (cyclomatic 20) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:692— UpcallBridge.zeroHandlerName has cyclomatic complexity 20 (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.
FlowEngine.finish (cyclomatic 20) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:1023— FlowEngine.finish 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.
Http1Parser.detectSpecialHeader (cyclomatic 20) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:631— Http1Parser.detectSpecialHeader has cyclomatic complexity 20 (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.
CallEngine.callEncoded (cyclomatic 20) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:207— CallEngine.callEncoded 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.
NioIoDriver.dispatchReadTls (cyclomatic 20) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1906— NioIoDriver.dispatchReadTls has cyclomatic complexity 20 (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.
Parse.runWith (cyclomatic 20) kyo-parse/shared/src/main/scala/kyo/Parse.scala:882— Parse.runWith 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.
JsonSchema.fromStructure (cyclomatic 20) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:725— JsonSchema.fromStructure 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.
YamlScalars.isYaml11DecimalFloat (cyclomatic 20) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:291— YamlScalars.isYaml11DecimalFloat has cyclomatic complexity 20 (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.
JarCentralDirectory.parseCenRecordsFull (cyclomatic 20) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:520— JarCentralDirectory.parseCenRecordsFull has cyclomatic complexity 20 (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.
ClassfileUnpickler.readClassAttrList (cyclomatic 20) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:457— ClassfileUnpickler.readClassAttrList 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.
SnapshotReader.readSymbolsMapped (cyclomatic 20) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1108— SnapshotReader.readSymbolsMapped has cyclomatic complexity 20 (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. This shape REPEATS in the file: one other method here (SnapshotReader.readSymbols) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SnapshotReader.readSymbols (cyclomatic 20) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1433— SnapshotReader.readSymbols has cyclomatic complexity 20 (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. This shape REPEATS in the file: one other method here (SnapshotReader.readSymbolsMapped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ChartTransitions.marksRegionWithTransitions (cyclomatic 20) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:554— ChartTransitions.marksRegionWithTransitions 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.
ReactiveRegion.isValidHtmlId (cyclomatic 20) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveRegion.scala:143— ReactiveRegion.isValidHtmlId has cyclomatic complexity 20 (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.
ReactiveUI.dragDispatch (cyclomatic 20) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:918— ReactiveUI.dragDispatch has cyclomatic complexity 20 (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. This is NOT this file's highest cyclomatic complexity: ReactiveUI.rebuildSvgElement (cyclomatic 48) 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 method is counted neither in this dimension's figures nor in its score.
CodexCompletion.run (cyclomatic 19) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:131— CodexCompletion.run has cyclomatic complexity 19 (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.
Big5Decoder.run (cyclomatic 19) kyo-charset/shared/src/main/scala/kyo/internal/charset/Big5Decoder.scala:15— Big5Decoder.run has cyclomatic complexity 19 (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.
CompatLibrary.addRows (cyclomatic 19) kyo-compat/plugin/src/main/scala/io/getkyo/compat/CompatLibrary.scala:103— CompatLibrary.addRows 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.
internal.conforms (cyclomatic 19) kyo-data/shared/src/main/scala/kyo/Tag.scala:564— internal.conforms 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.
Type.render (cyclomatic 19) kyo-data/shared/src/main/scala/kyo/Tag.scala:225— Type.render has cyclomatic complexity 19 (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.
HeaderCodec.octetText (cyclomatic 19) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:114— HeaderCodec.octetText has cyclomatic complexity 19 (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.
TransferEncoding.quotedPrintableDecoding (cyclomatic 19) kyo-email/shared/src/main/scala/kyo/internal/email/mime/TransferEncoding.scala:209— TransferEncoding.quotedPrintableDecoding has cyclomatic complexity 19 (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.
JvmEmitter.structLayoutExpr (cyclomatic 19) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1136— JvmEmitter.structLayoutExpr 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.
RouteUtil.encodeStreamBodyValueWith (cyclomatic 19) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:731— RouteUtil.encodeStreamBodyValueWith 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.
NioIoDriver.rebuildSelector (cyclomatic 19) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1674— NioIoDriver.rebuildSelector has cyclomatic complexity 19 (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.
Parser.parseElement (cyclomatic 19) kyo-schema-bson/shared/src/main/scala/kyo/internal/bson/BsonReader.scala:437— Parser.parseElement 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.
Protobuf.auditStructure (cyclomatic 19) kyo-schema-protobuf/shared/src/main/scala/kyo/Protobuf.scala:234— Protobuf.auditStructure 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.
YamlParser.readFlowText (cyclomatic 19) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:270— YamlParser.readFlowText has cyclomatic complexity 19 (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.
YamlParser.foldTopLevel (cyclomatic 19) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:810— YamlParser.foldTopLevel 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.
Ryu.digitCount (cyclomatic 19) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:25— Ryu.digitCount 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.
Tasty.bodyTree (cyclomatic 19) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:666— Tasty.bodyTree has cyclomatic complexity 19 (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. This is NOT this file's highest cyclomatic complexity: Classpath.unresolvedTypeReferenceCount (cyclomatic 43) 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 method is counted neither in this dimension's figures nor in its score.
Constant.show (cyclomatic 19) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:1417— Constant.show 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: Classpath.unresolvedTypeReferenceCount (cyclomatic 43) 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 method is counted neither in this dimension's figures nor in its score.
ClasspathOrchestrator.buildCompanionIndex (cyclomatic 19) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2298— ClasspathOrchestrator.buildCompanionIndex has cyclomatic complexity 19 (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.
ClasspathOrchestrator.decodeTastyBytes (cyclomatic 19) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2543— ClasspathOrchestrator.decodeTastyBytes has cyclomatic complexity 19 (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.
BotApi.mapResponse (cyclomatic 19) kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:273— BotApi.mapResponse 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.
ChartMarks.buildSimpleAreaPath (cyclomatic 19) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:960— ChartMarks.buildSimpleAreaPath 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.
ChartScales.foldExtent (cyclomatic 19) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:27— ChartScales.foldExtent 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.
Request.apply (cyclomatic 18) kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:366— Request.apply has cyclomatic complexity 18 (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.
Rest.run (cyclomatic 18) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:148— Rest.run has cyclomatic complexity 18 (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: Rest.leafFor (cyclomatic 20) 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 method is counted neither in this dimension's figures nor in its score.
AddressCodec.parse (cyclomatic 18) kyo-email/shared/src/main/scala/kyo/internal/email/mime/AddressCodec.scala:26— AddressCodec.parse 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.
Context.extractReturnShape (cyclomatic 18) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:611— Context.extractReturnShape 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.
JsEmitter.emitVariadicMethodBody (cyclomatic 18) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:89— JsEmitter.emitVariadicMethodBody has cyclomatic complexity 18 (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.
OpenApiGenerator.jsonSchemaToHttpOpenApi (cyclomatic 18) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:243— OpenApiGenerator.jsonSchemaToHttpOpenApi has cyclomatic complexity 18 (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.
McpEngine.initServer (cyclomatic 18) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpEngine.scala:25— McpEngine.initServer has cyclomatic complexity 18 (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.
NioTransport.startTlsHandshake (cyclomatic 18) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:736— NioTransport.startTlsHandshake 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.
SockAddr.parseIpv6 (cyclomatic 18) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixStructs.scala:361— SockAddr.parseIpv6 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.
JsonReader.integral (cyclomatic 18) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:232— JsonReader.integral has cyclomatic complexity 18 (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.
YamlDocuments.split (cyclomatic 18) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlDocuments.scala:22— YamlDocuments.split 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.
YamlReader.structureFromEvents (cyclomatic 18) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:49— YamlReader.structureFromEvents has cyclomatic complexity 18 (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.
SchemaSerializer.zeroForField (cyclomatic 18) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1596— SchemaSerializer.zeroForField has cyclomatic complexity 18 (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. This is NOT this file's highest cyclomatic complexity: SchemaSerializer.anyToStructureValue (cyclomatic 20) 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 method is counted neither in this dimension's figures nor in its score.
PostgresRowCodec.decoderFor (cyclomatic 18) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresRowCodec.scala:69— PostgresRowCodec.decoderFor has cyclomatic complexity 18 (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.
PipelineExchange.readOneStatementResult (cyclomatic 18) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/PipelineExchange.scala:186— PipelineExchange.readOneStatementResult has cyclomatic complexity 18 (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.
Url.parse (cyclomatic 18) kyo-sql/shared/src/main/scala/kyo/SqlConfig.scala:539— Url.parse 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.
FromExprDerived.applyAnyToFreeParams (cyclomatic 18) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:659— FromExprDerived.applyAnyToFreeParams has cyclomatic complexity 18 (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.
FromExprDerived.deriveFor (cyclomatic 18) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1442— FromExprDerived.deriveFor has cyclomatic complexity 18 (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.
JarCentralDirectory.readAllCenEntries (cyclomatic 18) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:176— JarCentralDirectory.readAllCenEntries 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. This shape REPEATS in the file: one other method here (JarCentralDirectory.parseCenRecordsAll) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
JarCentralDirectory.parseCenRecordsAll (cyclomatic 18) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:610— JarCentralDirectory.parseCenRecordsAll 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. This shape REPEATS in the file: one other method here (JarCentralDirectory.readAllCenEntries) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Tasty.occurrencesInFile (cyclomatic 18) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:765— Tasty.occurrencesInFile has cyclomatic complexity 18 (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. This is NOT this file's highest cyclomatic complexity: Classpath.unresolvedTypeReferenceCount (cyclomatic 43) 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 method is counted neither in this dimension's figures nor in its score.
AstUnpickler.decodeTemplateParents (cyclomatic 18) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:843— AstUnpickler.decodeTemplateParents 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.
Runtime.install (cyclomatic 18) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:241— Runtime.install 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.
ChartLower.lowerLive (cyclomatic 18) kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:232— ChartLower.lowerLive has cyclomatic complexity 18 (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.
Service.readDirectory (cyclomatic 18) kyo-ui/shared/src/main/scala/kyo/internal/DragFiles.scala:84— Service.readDirectory 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.
ReactiveUI.targetSatisfies (cyclomatic 18) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:433— ReactiveUI.targetSatisfies 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. This is NOT this file's highest cyclomatic complexity: ReactiveUI.rebuildSvgElement (cyclomatic 48) 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 method is counted neither in this dimension's figures nor in its score.
_unwrapNoscriptImages (cyclomatic 18) kyo-browser/shared/src/main/resources/kyo/Readability.js:1892— _unwrapNoscriptImages has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 1917, 1896). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: _initializeNode (cyclomatic 20) 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 method is counted neither in this dimension's figures nor in its score.
CodexCompletion.streamFragments (cyclomatic 17) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:77— CodexCompletion.streamFragments 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.
SelectorJs.resolveElementJsScoped (cyclomatic 17) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:246— SelectorJs.resolveElementJsScoped has cyclomatic complexity 17 (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. This shape REPEATS in the file: one other method here (SelectorJs.resolveAllElementsJsScoped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SelectorJs.resolveAllElementsJsScoped (cyclomatic 17) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:381— SelectorJs.resolveAllElementsJsScoped has cyclomatic complexity 17 (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. This shape REPEATS in the file: one other method here (SelectorJs.resolveElementJsScoped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
EucJpDecoder.run (cyclomatic 17) kyo-charset/shared/src/main/scala/kyo/internal/charset/EucJpDecoder.scala:14— EucJpDecoder.run has cyclomatic complexity 17 (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.
Rollout.matchSelector (cyclomatic 17) kyo-config/shared/src/main/scala/kyo/Rollout.scala:637— Rollout.matchSelector has cyclomatic complexity 17 (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.
SegmentParser.parseClass (cyclomatic 17) kyo-data/shared/src/main/scala/kyo/Glob.scala:429— SegmentParser.parseClass has cyclomatic complexity 17 (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.
internal.readEntry (cyclomatic 17) kyo-data/shared/src/main/scala/kyo/Tag.scala:910— internal.readEntry 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.
Orchestrator.toRuntimeOutcome (cyclomatic 17) kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/Orchestrator.scala:252— Orchestrator.toRuntimeOutcome 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.
MimeRenderer.isLineForm (cyclomatic 17) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeRenderer.scala:195— MimeRenderer.isLineForm has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TransferEncoding.decodeBase64Pieces (cyclomatic 17) kyo-email/shared/src/main/scala/kyo/internal/email/mime/TransferEncoding.scala:96— TransferEncoding.decodeBase64Pieces 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.
JsEmitter.emitKoffiFn (cyclomatic 17) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:876— JsEmitter.emitKoffiFn 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.
RouteUtil.decodeParam (cyclomatic 17) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:629— RouteUtil.decodeParam has cyclomatic complexity 17 (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.
CallEngine.callPartialResultsEffect (cyclomatic 17) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:476— CallEngine.callPartialResultsEffect 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.
Eval.release (cyclomatic 17) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:639— Eval.release 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.
PollerIoDriver.runCycle (cyclomatic 17) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:533— PollerIoDriver.runCycle has cyclomatic complexity 17 (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.
ContainerImage.parse (cyclomatic 17) kyo-pod/shared/src/main/scala/kyo/ContainerImage.scala:90— ContainerImage.parse has cyclomatic complexity 17 (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.
JsonReader.readStructure (cyclomatic 17) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:787— JsonReader.readStructure has cyclomatic complexity 17 (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.
YamlReader.sourceFlowEntryEnd (cyclomatic 17) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1121— YamlReader.sourceFlowEntryEnd has cyclomatic complexity 17 (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.
MysqlSessionTracking.read (cyclomatic 17) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSessionTracking.scala:30— MysqlSessionTracking.read has cyclomatic complexity 17 (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.
PostgresDecoder.readIntervalWords (cyclomatic 17) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:859— PostgresDecoder.readIntervalWords has cyclomatic complexity 17 (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.
PostgresDecoder.expandIpv6 (cyclomatic 17) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1043— PostgresDecoder.expandIpv6 has cyclomatic complexity 17 (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.
FromExprDerived.buildField (cyclomatic 17) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1129— FromExprDerived.buildField 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.
FromExprDerived.buildProduct (cyclomatic 17) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1213— FromExprDerived.buildProduct 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.
SqlJsonArray.unquote (cyclomatic 17) kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala:80— SqlJsonArray.unquote 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.
NodePathUnsafe.copy (cyclomatic 17) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:759— NodePathUnsafe.copy has cyclomatic complexity 17 (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.
TeamsConfig.problemOf (cyclomatic 17) kyo-teams/shared/src/main/scala/kyo/TeamsConfig.scala:193— TeamsConfig.problemOf has cyclomatic complexity 17 (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.
DomReactiveRegions.replaceContent (cyclomatic 17) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:93— DomReactiveRegions.replaceContent 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.
Sortable.move (cyclomatic 17) kyo-ui/shared/src/main/scala/kyo/Sortable.scala:40— Sortable.move has cyclomatic complexity 17 (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.
HtmlRenderer.renderDropdownWithValue (cyclomatic 17) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:443— HtmlRenderer.renderDropdownWithValue has cyclomatic complexity 17 (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. This is NOT this file's highest cyclomatic complexity: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
Resolvers.buildHandlers (cyclomatic 16) kyo-caliban/src/main/scala/kyo/Resolvers.scala:261— Resolvers.buildHandlers has cyclomatic complexity 16 (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.
Unsafe.initInline (cyclomatic 16) kyo-core/shared/src/main/scala/kyo/Scope.scala:404— Unsafe.initInline 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.
Rsa.encryptionKeyFromSpkiArray (cyclomatic 16) kyo-crypto/shared/src/main/scala/kyo/crypto/Rsa.scala:213— Rsa.encryptionKeyFromSpkiArray has cyclomatic complexity 16 (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.
FieldsMacros.fromObjectImpl (cyclomatic 16) kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:267— FieldsMacros.fromObjectImpl has cyclomatic complexity 16 (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.
Driver.run (cyclomatic 16) kyo-discord/shared/src/main/scala/kyo/internal/discord/Session.scala:121— Driver.run has cyclomatic complexity 16 (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.
MimeModel.classify (cyclomatic 16) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeModel.scala:74— MimeModel.classify has cyclomatic complexity 16 (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.
MemoryFlowStore.matches (cyclomatic 16) kyo-flow/shared/src/main/scala/kyo/internal/MemoryFlowStore.scala:443— MemoryFlowStore.matches has cyclomatic complexity 16 (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.
ChunkedBodyDecoder.parseChunkSizeLine (cyclomatic 16) kyo-http/shared/src/main/scala/kyo/internal/http1/ChunkedBodyDecoder.scala:556— ChunkedBodyDecoder.parseChunkSizeLine 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.
RouteUtil.feedSse (cyclomatic 16) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1197— RouteUtil.feedSse 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.
WebSocketCodec.readRawFrameWith (cyclomatic 16) kyo-http/shared/src/main/scala/kyo/internal/websocket/WebSocketCodec.scala:380— WebSocketCodec.readRawFrameWith 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.
Markdown.parseArticle (cyclomatic 16) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:276— Markdown.parseArticle has cyclomatic complexity 16 (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.
McpCapabilityGate.missingCapability (cyclomatic 16) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpCapabilityGate.scala:70— McpCapabilityGate.missingCapability 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.
PosixTransport.startAcceptLoop (cyclomatic 16) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1042— PosixTransport.startAcceptLoop 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.
ShellBackend.execOnce (cyclomatic 16) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:641— ShellBackend.execOnce has cyclomatic complexity 16 (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.
JsonReader.scanNumber (cyclomatic 16) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:580— JsonReader.scanNumber 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.
YamlReader.captureSourceRootFlow (cyclomatic 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:531— YamlReader.captureSourceRootFlow 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.
YamlSource.foldFlowScalarText (cyclomatic 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlSource.scala:124— YamlSource.foldFlowScalarText 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.
SchemaSerializer.readCatchAllTree (cyclomatic 16) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:819— SchemaSerializer.readCatchAllTree has cyclomatic complexity 16 (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: SchemaSerializer.anyToStructureValue (cyclomatic 20) 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 method is counted neither in this dimension's figures nor in its score.
TransformAwareReader.parseNamedKey (cyclomatic 16) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2741— TransformAwareReader.parseNamedKey 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. This is NOT this file's highest cyclomatic complexity: SchemaSerializer.anyToStructureValue (cyclomatic 20) 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 method is counted neither in this dimension's figures nor in its score.
ServerErrors.mkServerError (cyclomatic 16) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/ServerErrors.scala:36— ServerErrors.mkServerError 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.
FromExprDerived.resolveStableGiven (cyclomatic 16) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:231— FromExprDerived.resolveStableGiven has cyclomatic complexity 16 (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.
FromExprDerived.buildMaybe (cyclomatic 16) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:966— FromExprDerived.buildMaybe has cyclomatic complexity 16 (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.
FromExprDerived.deriveMaybe (cyclomatic 16) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1782— FromExprDerived.deriveMaybe has cyclomatic complexity 16 (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.
FromExprDerived.deriveProduct (cyclomatic 16) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2130— FromExprDerived.deriveProduct has cyclomatic complexity 16 (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.
WalkContext.walkRecord (cyclomatic 16) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:63— WalkContext.walkRecord has cyclomatic complexity 16 (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.
JarMappedReader.readEntry (cyclomatic 16) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarMappedReader.scala:35— JarMappedReader.readEntry 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.
ClasspathOrchestrator.walkRoot (cyclomatic 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:497— ClasspathOrchestrator.walkRoot 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.
BotApi.describe (cyclomatic 16) kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:240— BotApi.describe has cyclomatic complexity 16 (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.
HtmlRenderer.renderCommonAttrs (cyclomatic 16) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:589— HtmlRenderer.renderCommonAttrs 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. This is NOT this file's highest cyclomatic complexity: HtmlRenderer.tagName (cyclomatic 61) 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 method is counted neither in this dimension's figures nor in its score.
InputMasking.filterStr (cyclomatic 16) kyo-ui/shared/src/main/scala/kyo/internal/InputMasking.scala:37— InputMasking.filterStr 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.
ReactiveUI.normalizeAt (cyclomatic 16) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:51— ReactiveUI.normalizeAt has cyclomatic complexity 16 (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. This is NOT this file's highest cyclomatic complexity: ReactiveUI.rebuildSvgElement (cyclomatic 48) 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 method is counted neither in this dimension's figures nor in its score.
ClasspathOrchestrator.finalizeMerge (cognitive 583) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:905— ClasspathOrchestrator.finalizeMerge has cognitive complexity 583 (threshold 15). Drivers by points: if/else 163 (377 pts), match/switch 37 (95 pts), loops 38 (63 pts), boolean chains 47, error handling 1 (nesting depth added 297). 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.
Eval.apply (cognitive 359) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:53— Eval.apply has cognitive complexity 359 (threshold 15). Drivers by points: if/else 107 (270 pts), match/switch 19 (68 pts), boolean chains 11, loops 4 (6 pts), error handling 2 (4 pts) (nesting depth added 216). 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.
CdpBackend.initUnscoped (cognitive 276) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:228— CdpBackend.initUnscoped has cognitive complexity 276 (threshold 15). Drivers by points: loops 22 (253 pts), match/switch 1 (22 pts), if/else 1 (nesting depth added 252). 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.
LLM.eval (cognitive 265) kyo-ai/shared/src/main/scala/kyo/LLM.scala:627— LLM.eval has cognitive complexity 265 (threshold 15). Drivers by points: loops 16 (136 pts), match/switch 7 (85 pts), if/else 10 (42 pts), boolean chains 2 (nesting depth added 230). 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.
_grabArticle (cognitive 254) kyo-browser/shared/src/main/resources/kyo/Readability.js:1031— _grabArticle has cognitive complexity 254 (threshold 15). Drivers by points: if/else 64 (173 pts), loops 15 (48 pts), boolean chains 25, ternaries 3 (7 pts), other 1 (nesting depth added 146). Of this number, 232 points are the body's own statements and 22 belong to 4 function literals 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.
CdpBackend.initUnscoped (cognitive 231) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:553— CdpBackend.initUnscoped has cognitive complexity 231 (threshold 15). Drivers by points: loops 20 (210 pts), match/switch 1 (20 pts), if/else 1 (nesting depth added 209). 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.
DomBackend.mountInto (cognitive 223) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:78— DomBackend.mountInto has cognitive complexity 223 (threshold 15). Drivers by points: loops 20 (210 pts), match/switch 1 (13 pts) (nesting depth added 202). 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.
ReactiveUI.dispatchToElement (cognitive 185) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:498— ReactiveUI.dispatchToElement has cognitive complexity 185 (threshold 15). Drivers by points: if/else 56 (78 pts), match/switch 23 (78 pts), boolean chains 29 (nesting depth added 77). 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.
TypeUnpickler.decodeTag (cognitive 184) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:374— TypeUnpickler.decodeTag has cognitive complexity 184 (threshold 15). Drivers by points: match/switch 41 (121 pts), if/else 32 (52 pts), error handling 2 (6 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 105). 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.
WebsiteBundleMain.build (cognitive 172) kyo-website-bundle/js/src/main/scala/kyo/website/WebsiteBundleMain.scala:102— WebsiteBundleMain.build has cognitive complexity 172 (threshold 15). Drivers by points: loops 17 (153 pts), if/else 2 (12 pts), match/switch 1 (7 pts) (nesting depth added 152). 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.
JsonRpcEndpointImpl.initEngine (cognitive 168) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:268— JsonRpcEndpointImpl.initEngine has cognitive complexity 168 (threshold 15). Drivers by points: match/switch 34 (130 pts), if/else 16 (38 pts) (nesting depth added 118). 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.
Flow.run (cognitive 167) kyo-flow/shared/src/main/scala/kyo/Flow.scala:1318— Flow.run has cognitive complexity 167 (threshold 15). Drivers by points: if/else 68 (93 pts), match/switch 30 (74 pts) (nesting depth added 69). 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.
Runtime.install (cognitive 153) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:241— Runtime.install has cognitive complexity 153 (threshold 15). Drivers by points: loops 17 (153 pts) (nesting depth added 136). 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.
YamlReader.sourceAnchorStats (cognitive 141) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1715— YamlReader.sourceAnchorStats has cognitive complexity 141 (threshold 15). Drivers by points: if/else 34 (90 pts), boolean chains 31, loops 9 (17 pts), match/switch 1 (3 pts) (nesting depth added 66). 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.
Gateway.connection (cognitive 138) kyo-discord/shared/src/main/scala/kyo/internal/discord/Gateway.scala:81— Gateway.connection has cognitive complexity 138 (threshold 15). Drivers by points: loops 16 (112 pts), match/switch 2 (15 pts), if/else 2 (11 pts) (nesting depth added 118). 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.
IoUringDriver.complete (cognitive 128) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2011— IoUringDriver.complete has cognitive complexity 128 (threshold 15). Drivers by points: if/else 40 (87 pts), match/switch 5 (17 pts), boolean chains 12, error handling 2 (12 pts) (nesting depth added 69). 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.
Subtyping.isSubtype (cognitive 127) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:67— Subtyping.isSubtype has cognitive complexity 127 (threshold 15). Drivers by points: match/switch 15 (66 pts), if/else 22 (59 pts), boolean chains 2 (nesting depth added 88). 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.
FocusMacro.emitProductSchemaStatic (cognitive 125) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2088— FocusMacro.emitProductSchemaStatic has cognitive complexity 125 (threshold 15). Drivers by points: if/else 50 (62 pts), match/switch 31 (54 pts), boolean chains 8, error handling 1 (nesting depth added 35). 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.
Service.readDirectory (cognitive 124) kyo-ui/shared/src/main/scala/kyo/internal/DragFiles.scala:84— Service.readDirectory has cognitive complexity 124 (threshold 15). Drivers by points: loops 15 (120 pts), match/switch 1 (4 pts) (nesting depth added 108). 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.
ImapSession.idling (cognitive 116) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapSession.scala:507— ImapSession.idling has cognitive complexity 116 (threshold 15). Drivers by points: loops 10 (55 pts), if/else 10 (39 pts), match/switch 2 (22 pts) (nesting depth added 94). 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.
FocusMacro.desugarProductConfig (cognitive 115) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:732— FocusMacro.desugarProductConfig has cognitive complexity 115 (threshold 15). Drivers by points: match/switch 28 (57 pts), if/else 47 (56 pts), boolean chains 2 (nesting depth added 38). 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.
StreamCompression.gunzipStream (cognitive 110) kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:404— StreamCompression.gunzipStream has cognitive complexity 110 (threshold 15). Drivers by points: if/else 45 (72 pts), match/switch 12 (37 pts), boolean chains 1 (nesting depth added 52). 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.
DomBackend.setupEventDelegation (cognitive 109) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:612— DomBackend.setupEventDelegation has cognitive complexity 109 (threshold 15). Drivers by points: loops 11 (66 pts), if/else 22 (28 pts), boolean chains 15 (nesting depth added 61). 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.
TypeKey.structuralEquals (cognitive 105) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeKey.scala:361— TypeKey.structuralEquals has cognitive complexity 105 (threshold 15). Drivers by points: if/else 28 (74 pts), loops 6 (26 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 68). 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.
DomBackend.setupInputMasking (cognitive 103) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:950— DomBackend.setupInputMasking has cognitive complexity 103 (threshold 15). Drivers by points: if/else 32 (84 pts), boolean chains 8, match/switch 1 (6 pts), loops 1 (5 pts) (nesting depth added 61). 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.
Http1Parser.parseRequestLine (cognitive 101) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:349— Http1Parser.parseRequestLine has cognitive complexity 101 (threshold 15). Drivers by points: if/else 33 (92 pts), boolean chains 9 (nesting depth added 59). 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.
MpmcUnboundedUnsafeQueue.peek (cognitive 97) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:266— MpmcUnboundedUnsafeQueue.peek has cognitive complexity 97 (threshold 15). Drivers by points: if/else 45 (94 pts), boolean chains 3 (nesting depth added 49). 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.
MpmcUnboundedUnsafeQueue.poll (cognitive 96) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:138— MpmcUnboundedUnsafeQueue.poll has cognitive complexity 96 (threshold 15). Drivers by points: if/else 45 (94 pts), boolean chains 2 (nesting depth added 49). 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.
LspCapabilityGate.missingCapability (cognitive 92) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspGate.scala:172— LspCapabilityGate.missingCapability has cognitive complexity 92 (threshold 15). Drivers by points: if/else 61 (91 pts), match/switch 1 (nesting depth added 30). 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.
NodeCommandUnsafe.spawn (cognitive 92) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:655— NodeCommandUnsafe.spawn has cognitive complexity 92 (threshold 15). Drivers by points: match/switch 11 (54 pts), if/else 12 (25 pts), error handling 2 (8 pts), loops 1 (5 pts) (nesting depth added 66). 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.
RyuDouble.writeImpl (cognitive 90) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:75— RyuDouble.writeImpl has cognitive complexity 90 (threshold 15). Drivers by points: if/else 43 (79 pts), boolean chains 11 (nesting depth added 36). 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. This shape REPEATS in the file: one other method here (RyuFloat.writeImpl) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RyuFloat.writeImpl (cognitive 90) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:423— RyuFloat.writeImpl has cognitive complexity 90 (threshold 15). Drivers by points: if/else 43 (79 pts), boolean chains 11 (nesting depth added 36). 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. This shape REPEATS in the file: one other method here (RyuDouble.writeImpl) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Rollout.parseRolloutChoices (cognitive 86) kyo-config/shared/src/main/scala/kyo/Rollout.scala:281— Rollout.parseRolloutChoices has cognitive complexity 86 (threshold 15). Drivers by points: if/else 35 (72 pts), error handling 2 (10 pts), boolean chains 4 (nesting depth added 45). 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.
Service.readFile (cognitive 86) kyo-ui/shared/src/main/scala/kyo/internal/DragFiles.scala:50— Service.readFile has cognitive complexity 86 (threshold 15). Drivers by points: loops 12 (78 pts), match/switch 1 (8 pts) (nesting depth added 73). 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.
FromExprDerived.deriveChunk (cognitive 84) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1847— FromExprDerived.deriveChunk has cognitive complexity 84 (threshold 15). Drivers by points: match/switch 9 (27 pts), loops 4 (22 pts), if/else 14 (20 pts), error handling 3 (11 pts), boolean chains 4 (nesting depth added 50). 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.
NonZeroCapacityUnsafe.flush (cognitive 83) kyo-core/shared/src/main/scala/kyo/Channel.scala:837— NonZeroCapacityUnsafe.flush has cognitive complexity 83 (threshold 15). Drivers by points: if/else 21 (41 pts), match/switch 9 (35 pts), boolean chains 7 (nesting depth added 46). 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.
JsonSchema.writeJsonSchema (cognitive 83) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:315— JsonSchema.writeJsonSchema has cognitive complexity 83 (threshold 15). Drivers by points: match/switch 27 (53 pts), if/else 28 (30 pts) (nesting depth added 28). 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.
ClasspathOrchestrator.mergeOneInto (cognitive 81) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:675— ClasspathOrchestrator.mergeOneInto has cognitive complexity 81 (threshold 15). Drivers by points: if/else 17 (47 pts), match/switch 5 (15 pts), boolean chains 13, loops 3 (6 pts) (nesting depth added 43). 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.
Rsa.encryptionKeyFromSpkiArray (cognitive 79) kyo-crypto/shared/src/main/scala/kyo/crypto/Rsa.scala:213— Rsa.encryptionKeyFromSpkiArray has cognitive complexity 79 (threshold 15). Drivers by points: loops 12 (78 pts), match/switch 1 (nesting depth added 66). 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.
ShallowTagMacro.derive (cognitive 79) kyo-data/shared/src/main/scala/kyo/internal/ShallowTagMacro.scala:69— ShallowTagMacro.derive has cognitive complexity 79 (threshold 15). Drivers by points: if/else 45 (59 pts), match/switch 9 (12 pts), boolean chains 8 (nesting depth added 17). 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.
TreeUnpickler.decodeTptAsType (cognitive 79) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1488— TreeUnpickler.decodeTptAsType has cognitive complexity 79 (threshold 15). Drivers by points: if/else 23 (45 pts), match/switch 8 (24 pts), loops 3 (6 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 43). 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.
Iso2022JpDecoder.run (cognitive 78) kyo-charset/shared/src/main/scala/kyo/internal/charset/Iso2022JpDecoder.scala:22— Iso2022JpDecoder.run has cognitive complexity 78 (threshold 15). Drivers by points: if/else 30 (61 pts), boolean chains 11, match/switch 2 (5 pts), loops 1 (nesting depth added 34). 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.
NioTransport.driveHandshake (cognitive 78) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:953— NioTransport.driveHandshake has cognitive complexity 78 (threshold 15). Drivers by points: if/else 25 (42 pts), match/switch 5 (23 pts), error handling 4 (10 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 42). 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.
DoltStatements.readCommit (cognitive 78) REDACTED:66— DoltStatements.readCommit has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). 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. This shape REPEATS in the file: one other method here (DoltStatements.readBranch) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DoltStatements.readBranch (cognitive 78) REDACTED:174— DoltStatements.readBranch has cognitive complexity 78 (threshold 15). Drivers by points: loops 12 (78 pts) (nesting depth added 66). 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. This shape REPEATS in the file: one other method here (DoltStatements.readCommit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RouteUtil.multipartBoundaryFromHeaders (cognitive 77) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:813— RouteUtil.multipartBoundaryFromHeaders has cognitive complexity 77 (threshold 15). Drivers by points: if/else 20 (34 pts), loops 5 (19 pts), boolean chains 13, match/switch 2 (11 pts) (nesting depth added 37). 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.
ShellBackend.logs (cognitive 76) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:835— ShellBackend.logs has cognitive complexity 76 (threshold 15). Drivers by points: if/else 18 (52 pts), loops 5 (20 pts), boolean chains 3, match/switch 1 (nesting depth added 49). 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.
ChartMarks.lowerBarStacked (cognitive 76) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:403— ChartMarks.lowerBarStacked has cognitive complexity 76 (threshold 15). Drivers by points: if/else 27 (44 pts), match/switch 11 (31 pts), boolean chains 1 (nesting depth added 37). 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.
ChartMarks.lowerPoint (cognitive 76) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1373— ChartMarks.lowerPoint has cognitive complexity 76 (threshold 15). Drivers by points: match/switch 13 (51 pts), if/else 15 (24 pts), boolean chains 1 (nesting depth added 47). 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.
FromExprDerived.resolveBindings (cognitive 74) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:403— FromExprDerived.resolveBindings has cognitive complexity 74 (threshold 15). Drivers by points: if/else 26 (33 pts), error handling 10 (20 pts), match/switch 9 (15 pts), boolean chains 6 (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.
ClaudeCodeCompletion.withMcpBridge (cognitive 73) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:327— ClaudeCodeCompletion.withMcpBridge has cognitive complexity 73 (threshold 15). Drivers by points: loops 11 (66 pts), match/switch 1 (7 pts) (nesting depth added 61). 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.
ImapCodec.internalDate (cognitive 72) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:457— ImapCodec.internalDate has cognitive complexity 72 (threshold 15). Drivers by points: loops 8 (52 pts), if/else 6 (17 pts), boolean chains 3 (nesting depth added 55). 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.
FocusMacro.desugarSumConfig (cognitive 72) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:1286— FocusMacro.desugarSumConfig has cognitive complexity 72 (threshold 15). Drivers by points: if/else 27 (33 pts), match/switch 16 (29 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 24). 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.
JarCentralDirectory.parseCenRecordsFull (cognitive 72) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:520— JarCentralDirectory.parseCenRecordsFull has cognitive complexity 72 (threshold 15). Drivers by points: if/else 15 (55 pts), loops 3 (11 pts), boolean chains 6 (nesting depth added 48). 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.
SchemaSerializer.writeWithTransforms (cognitive 71) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:290— SchemaSerializer.writeWithTransforms has cognitive complexity 71 (threshold 15). Drivers by points: if/else 32 (45 pts), match/switch 14 (23 pts), boolean chains 3 (nesting depth added 22). 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.
Runtime.snapshot (cognitive 71) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1194— Runtime.snapshot has cognitive complexity 71 (threshold 15). Drivers by points: if/else 20 (39 pts), match/switch 6 (24 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 40). 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.
CodexCompletion.run (cognitive 70) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:131— CodexCompletion.run has cognitive complexity 70 (threshold 15). Drivers by points: loops 12 (62 pts), match/switch 1 (8 pts) (nesting depth added 57). 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.
Url.parse (cognitive 70) kyo-sql/shared/src/main/scala/kyo/SqlConfig.scala:539— Url.parse has cognitive complexity 70 (threshold 15). Drivers by points: if/else 17 (35 pts), match/switch 8 (35 pts) (nesting depth added 45). 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.
WebsiteGenerator.emit (cognitive 70) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:70— WebsiteGenerator.emit has cognitive complexity 70 (threshold 15). Drivers by points: loops 11 (66 pts), if/else 2 (4 pts) (nesting depth added 57). 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.
Markdown.splitBlocks (cognitive 69) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:151— Markdown.splitBlocks has cognitive complexity 69 (threshold 15). Drivers by points: if/else 18 (27 pts), loops 10 (25 pts), boolean chains 17 (nesting depth added 24). 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.
Completion.sseFragments (cognitive 68) kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala:362— Completion.sseFragments has cognitive complexity 68 (threshold 15). Drivers by points: loops 8 (26 pts), match/switch 5 (23 pts), if/else 6 (19 pts) (nesting depth added 49). 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.
Rollout.validateNonEmpty (cognitive 68) kyo-config/shared/src/main/scala/kyo/Rollout.scala:538— Rollout.validateNonEmpty has cognitive complexity 68 (threshold 15). Drivers by points: if/else 23 (53 pts), error handling 2 (12 pts), boolean chains 2, match/switch 1 (nesting depth added 40). 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.
LspCatalog.deriveFromKinds (cognitive 67) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspCatalog.scala:102— LspCatalog.deriveFromKinds has cognitive complexity 67 (threshold 15). Drivers by points: if/else 64, boolean chains 3. 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.
Path.setAt (cognitive 67) kyo-schema/shared/src/main/scala/kyo/Structure.scala:1153— Path.setAt has cognitive complexity 67 (threshold 15). Drivers by points: match/switch 11 (37 pts), if/else 17 (29 pts), boolean chains 1 (nesting depth added 38). 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.
SqliteConnectionFactory.configured (cognitive 67) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteConnectionFactory.scala:49— SqliteConnectionFactory.configured has cognitive complexity 67 (threshold 15). Drivers by points: loops 10 (65 pts), if/else 2 (nesting depth added 55). 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.
ReactiveUI.subscribe (cognitive 67) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:846— ReactiveUI.subscribe has cognitive complexity 67 (threshold 15). Drivers by points: loops 10 (55 pts), match/switch 1 (11 pts), if/else 1 (nesting depth added 55). 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.
JsonRpcEnvelopeSchema.envelopeSchema (cognitive 66) kyo-jsonrpc/shared/src/main/scala/kyo/internal/codec/JsonRpcEnvelopeSchema.scala:29— JsonRpcEnvelopeSchema.envelopeSchema has cognitive complexity 66 (threshold 15). Drivers by points: match/switch 16 (31 pts), if/else 22 (28 pts), boolean chains 7 (nesting depth added 21). 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.
ClasspathOrchestrator.decodeTastyBytes (cognitive 66) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2543— ClasspathOrchestrator.decodeTastyBytes has cognitive complexity 66 (threshold 15). Drivers by points: match/switch 5 (30 pts), loops 7 (28 pts), if/else 1 (8 pts) (nesting depth added 53). 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.
Subtyping.checkArgPairs (cognitive 66) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:405— Subtyping.checkArgPairs has cognitive complexity 66 (threshold 15). Drivers by points: if/else 16 (34 pts), match/switch 8 (32 pts) (nesting depth added 42). 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.
DocsMarkdownRender.splitBlocks (cognitive 66) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:409— DocsMarkdownRender.splitBlocks has cognitive complexity 66 (threshold 15). Drivers by points: if/else 18 (27 pts), loops 10 (25 pts), boolean chains 14 (nesting depth added 24). 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.
SocketEngine.initUnscoped (cognitive 63) kyo-slack/shared/src/main/scala/kyo/internal/slack/SocketEngine.scala:391— SocketEngine.initUnscoped has cognitive complexity 63 (threshold 15). Drivers by points: loops 8 (36 pts), match/switch 2 (17 pts), if/else 3 (10 pts) (nesting depth added 50). 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.
PathWatch.polling (cognitive 63) kyo-system/shared/src/main/scala/kyo/PathWatch.scala:189— PathWatch.polling has cognitive complexity 63 (threshold 15). Drivers by points: match/switch 13 (45 pts), if/else 10 (16 pts), boolean chains 2 (nesting depth added 38). 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.
Session.open (cognitive 62) kyo-discord/shared/src/main/scala/kyo/internal/discord/Session.scala:69— Session.open has cognitive complexity 62 (threshold 15). Drivers by points: loops 9 (45 pts), if/else 2 (10 pts), match/switch 1 (7 pts) (nesting depth added 50). 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.
TimeText.instant (cognitive 61) kyo-schema/shared/src/main/scala/kyo/internal/TimeText.scala:16— TimeText.instant has cognitive complexity 61 (threshold 15). Drivers by points: if/else 38 (45 pts), boolean chains 16 (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.
Wire.decodeEvent (cognitive 61) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:348— Wire.decodeEvent has cognitive complexity 61 (threshold 15). Drivers by points: loops 16 (56 pts), match/switch 2 (3 pts), if/else 2 (nesting depth added 41). 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.
Markdown.linkedImage (cognitive 60) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:746— Markdown.linkedImage has cognitive complexity 60 (threshold 15). Drivers by points: loops 8 (36 pts), if/else 6 (24 pts) (nesting depth added 46). 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.
JarCentralDirectory.readAllCenEntries (cognitive 60) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:176— JarCentralDirectory.readAllCenEntries has cognitive complexity 60 (threshold 15). Drivers by points: if/else 13 (48 pts), boolean chains 6, loops 2 (6 pts) (nesting depth added 39). 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. This shape REPEATS in the file: one other method here (JarCentralDirectory.parseCenRecordsAll) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
JarCentralDirectory.parseCenRecordsAll (cognitive 60) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:610— JarCentralDirectory.parseCenRecordsAll has cognitive complexity 60 (threshold 15). Drivers by points: if/else 13 (48 pts), boolean chains 6, loops 2 (6 pts) (nesting depth added 39). 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. This shape REPEATS in the file: one other method here (JarCentralDirectory.readAllCenEntries) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SockAddr.parseIpv6 (cognitive 59) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixStructs.scala:361— SockAddr.parseIpv6 has cognitive complexity 59 (threshold 15). Drivers by points: if/else 18 (41 pts), loops 2 (7 pts), error handling 1 (6 pts), boolean chains 5 (nesting depth added 33). 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.
AstUnpickler.walkStats (cognitive 59) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:281— AstUnpickler.walkStats has cognitive complexity 59 (threshold 15). Drivers by points: if/else 12 (36 pts), match/switch 6 (18 pts), error handling 1 (4 pts), loops 1 (nesting depth added 39). 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.
SmtpSession.transfer (cognitive 58) kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:140— SmtpSession.transfer has cognitive complexity 58 (threshold 15). Drivers by points: if/else 27 (53 pts), boolean chains 4, match/switch 1 (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.
IonSchema.fromStructure (cognitive 58) kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:177— IonSchema.fromStructure has cognitive complexity 58 (threshold 15). Drivers by points: if/else 22 (38 pts), match/switch 6 (18 pts), boolean chains 2 (nesting depth added 28). 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.
HzGb2312Decoder.run (cognitive 57) kyo-charset/shared/src/main/scala/kyo/internal/charset/HzGb2312Decoder.scala:20— HzGb2312Decoder.run has cognitive complexity 57 (threshold 15). Drivers by points: if/else 26 (52 pts), boolean chains 4, loops 1 (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.
NativeArtifactFormat.archReadingOfHeader (cognitive 57) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/NativeArtifactFormat.scala:95— NativeArtifactFormat.archReadingOfHeader has cognitive complexity 57 (threshold 15). Drivers by points: if/else 25 (34 pts), match/switch 7 (15 pts), boolean chains 8 (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.
UnsafeServerDispatch.serveH1 (cognitive 57) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:111— UnsafeServerDispatch.serveH1 has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (36 pts), match/switch 8 (16 pts), boolean chains 5 (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.
PosixTransport.upgradeRole (cognitive 57) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1647— PosixTransport.upgradeRole has cognitive complexity 57 (threshold 15). Drivers by points: if/else 14 (34 pts), match/switch 6 (17 pts), error handling 2 (5 pts), boolean chains 1 (nesting depth added 34). 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.
JsonReader.readQuotedStringWithEscapes (cognitive 57) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:472— JsonReader.readQuotedStringWithEscapes has cognitive complexity 57 (threshold 15). Drivers by points: if/else 21 (49 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 30). 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.
ChartMarks.lowerAreaStacked (cognitive 57) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1195— ChartMarks.lowerAreaStacked has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (36 pts), match/switch 10 (21 pts) (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.
TagMacro.deriveDB (cognitive 56) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:370— TagMacro.deriveDB has cognitive complexity 56 (threshold 15). Drivers by points: match/switch 10 (29 pts), if/else 16 (25 pts), boolean chains 2 (nesting depth added 28). 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.
UnsafeServerDispatch.dispatchHandler (cognitive 56) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:913— UnsafeServerDispatch.dispatchHandler has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (44 pts), match/switch 4 (10 pts), boolean chains 2 (nesting depth added 31). 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.
CodexCompletion.withSession (cognitive 55) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:185— CodexCompletion.withSession has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). 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.
Browser.withNewTab (cognitive 55) kyo-browser/shared/src/main/scala/kyo/Browser.scala:3754— Browser.withNewTab has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). 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.
DateCodec.parse (cognitive 55) kyo-email/shared/src/main/scala/kyo/internal/email/mime/DateCodec.scala:22— DateCodec.parse has cognitive complexity 55 (threshold 15). Drivers by points: loops 7 (35 pts), if/else 8 (19 pts), boolean chains 1 (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.
LspEngine.initServerRefs (cognitive 55) kyo-lsp/shared/src/main/scala/kyo/internal/lsp/LspEngine.scala:43— LspEngine.initServerRefs has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). 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.
NioIoDriver.dispatchReadTls (cognitive 55) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1906— NioIoDriver.dispatchReadTls has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (45 pts), match/switch 2 (8 pts), error handling 1 (2 pts) (nesting depth added 36). 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.
FastFloat.readFloat (cognitive 55) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:226— FastFloat.readFloat has cognitive complexity 55 (threshold 15). Drivers by points: if/else 26 (45 pts), boolean chains 6, 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.
FromExprDerived.buildChunk (cognitive 55) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1016— FromExprDerived.buildChunk has cognitive complexity 55 (threshold 15). Drivers by points: match/switch 8 (24 pts), if/else 14 (20 pts), error handling 2 (7 pts), boolean chains 4 (nesting depth added 27). 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.
Jwt.verify (cognitive 55) kyo-teams/shared/src/main/scala/kyo/internal/teams/Jwt.scala:26— Jwt.verify has cognitive complexity 55 (threshold 15). Drivers by points: loops 10 (55 pts) (nesting depth added 45). 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.
Gb18030Decoder.run (cognitive 54) kyo-charset/shared/src/main/scala/kyo/internal/charset/Gb18030Decoder.scala:16— Gb18030Decoder.run has cognitive complexity 54 (threshold 15). Drivers by points: if/else 23 (46 pts), boolean chains 7, loops 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.
JvmEmitter.emitPlainMethodBody (cognitive 54) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:94— JvmEmitter.emitPlainMethodBody has cognitive complexity 54 (threshold 15). Drivers by points: match/switch 17 (26 pts), if/else 23 (25 pts), boolean chains 3 (nesting depth added 11). 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.
Wire.decodeInteraction (cognitive 54) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:440— Wire.decodeInteraction has cognitive complexity 54 (threshold 15). Drivers by points: loops 16 (52 pts), if/else 1, match/switch 1 (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.
SnapshotReader.deserializeMapped (cognitive 54) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:718— SnapshotReader.deserializeMapped has cognitive complexity 54 (threshold 15). Drivers by points: if/else 28, match/switch 19 (22 pts), loops 3, boolean chains 1 (nesting depth added 3). 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.
Tasty.bodyTree (cognitive 53) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:666— Tasty.bodyTree has cognitive complexity 53 (threshold 15). Drivers by points: error handling 5 (25 pts), if/else 6 (13 pts), match/switch 4 (13 pts), boolean chains 2 (nesting depth added 36). 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.
ClaudeCodeCompletion.runClaudeCommand (cognitive 52) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:200— ClaudeCodeCompletion.runClaudeCommand has cognitive complexity 52 (threshold 15). Drivers by points: match/switch 7 (30 pts), loops 6 (21 pts), if/else 1 (nesting depth added 38). 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.
PollerIoDriver.dispatchCmd (cognitive 52) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2605— PollerIoDriver.dispatchCmd has cognitive complexity 52 (threshold 15). Drivers by points: if/else 17 (46 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 30). 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.
Iso2022KrDecoder.run (cognitive 51) kyo-charset/shared/src/main/scala/kyo/internal/charset/Iso2022KrDecoder.scala:23— Iso2022KrDecoder.run has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (45 pts), boolean chains 5, loops 1 (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.
Rollout.matchSelector (cognitive 51) kyo-config/shared/src/main/scala/kyo/Rollout.scala:637— Rollout.matchSelector has cognitive complexity 51 (threshold 15). Drivers by points: if/else 21 (46 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 26). 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.
PollerIoDriver.runCycle (cognitive 51) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:533— PollerIoDriver.runCycle has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (37 pts), match/switch 2 (7 pts), error handling 2 (6 pts), boolean chains 1 (nesting depth added 29). 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.
ShellBackend.execOnce (cognitive 51) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:641— ShellBackend.execOnce has cognitive complexity 51 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 5 (20 pts), match/switch 2 (9 pts), boolean chains 1 (nesting depth added 35). 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.
TypeOps.applied (cognitive 51) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeOps.scala:68— TypeOps.applied has cognitive complexity 51 (threshold 15). Drivers by points: if/else 24 (37 pts), boolean chains 12, match/switch 1 (2 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.
Unsafe.add (cognitive 50) kyo-core/shared/src/main/scala/kyo/Cache.scala:498— Unsafe.add has cognitive complexity 50 (threshold 15). Drivers by points: if/else 27 (43 pts), boolean chains 7 (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.
JvmCommandUnsafe.toJProcessBuilder (cognitive 50) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:179— JvmCommandUnsafe.toJProcessBuilder has cognitive complexity 50 (threshold 15). Drivers by points: match/switch 11 (27 pts), if/else 15 (23 pts) (nesting depth added 24). 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.
SnapshotReader.deserialize (cognitive 50) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:205— SnapshotReader.deserialize has cognitive complexity 50 (threshold 15). Drivers by points: if/else 24, match/switch 19 (22 pts), loops 3, boolean chains 1 (nesting depth added 3). 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.
_getJSONLD (cognitive 50) kyo-browser/shared/src/main/resources/kyo/Readability.js:1632— _getJSONLD has cognitive complexity 50 (threshold 15). Drivers by points: if/else 17 (32 pts), boolean chains 15, error handling 1 (2 pts), ternaries 1 (nesting depth added 16). Most of this is not in the body itself: 1 of the 50 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 1637, 1651, 1675, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TypeValidator.validate (cognitive 49) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:28— TypeValidator.validate has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (31 pts), match/switch 7 (15 pts), loops 3 (nesting depth added 24). 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.
ReactiveUI.dispatch (cognitive 49) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:281— ReactiveUI.dispatch has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 4 (14 pts), match/switch 4 (14 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.
IOTask.run (cognitive 48) kyo-core/shared/src/main/scala/kyo/scheduler/IOTask.scala:259— IOTask.run has cognitive complexity 48 (threshold 15). Drivers by points: if/else 19 (42 pts), boolean chains 2, error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 25). 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.
Handler.answersLoop (cognitive 48) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:331— Handler.answersLoop has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 4 (16 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 29). 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. This shape REPEATS in the file: one other method here (Handler.answersLoopState) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Handler.answersLoopState (cognitive 48) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:408— Handler.answersLoopState has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 4 (16 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 29). 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. This shape REPEATS in the file: one other method here (Handler.answersLoop) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
FromExprDerived.buildDirect (cognitive 48) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:844— FromExprDerived.buildDirect has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (28 pts), match/switch 6 (17 pts), boolean chains 3 (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.
DocsMarkdownRender.tokenizeBash (cognitive 48) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1244— DocsMarkdownRender.tokenizeBash has cognitive complexity 48 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 5 (13 pts), boolean chains 6 (nesting depth added 22). 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.
Utf7Decoder.run (cognitive 47) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf7Decoder.scala:18— Utf7Decoder.run has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (41 pts), boolean chains 5, loops 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.
Validate.apply (cognitive 47) kyo-direct/shared/src/main/scala/kyo/internal/Validate.scala:46— Validate.apply has cognitive complexity 47 (threshold 15). Drivers by points: match/switch 19 (34 pts), if/else 11 (12 pts), boolean chains 1 (nesting depth added 16). 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.
RouteUtil.feedMultipart (cognitive 47) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1310— RouteUtil.feedMultipart has cognitive complexity 47 (threshold 15). Drivers by points: if/else 22 (42 pts), boolean chains 4, match/switch 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.
ShellBackend.mapError (cognitive 47) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:2283— ShellBackend.mapError has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (25 pts), match/switch 5 (15 pts), boolean chains 7 (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.
ClasspathOrchestrator.buildCompanionIndex (cognitive 47) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2298— ClasspathOrchestrator.buildCompanionIndex has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (31 pts), match/switch 3 (13 pts), boolean chains 2, loops 1 (nesting depth added 28). 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.
ChartMarks.collectLineSegments (cognitive 47) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:643— ChartMarks.collectLineSegments has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (37 pts), match/switch 3 (9 pts), boolean chains 1 (nesting depth added 26). 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.
ReactiveUI.normalizeAt (cognitive 47) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:51— ReactiveUI.normalizeAt has cognitive complexity 47 (threshold 15). Drivers by points: loops 11 (42 pts), if/else 3 (4 pts), match/switch 1 (nesting depth added 32). 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.
Context.extractConfig (cognitive 46) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:124— Context.extractConfig has cognitive complexity 46 (threshold 15). Drivers by points: loops 8 (44 pts), if/else 2 (nesting depth added 36). 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.
PollerIoDriver.dispatchReadTls (cognitive 46) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2125— PollerIoDriver.dispatchReadTls has cognitive complexity 46 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 5, error handling 2 (4 pts), loops 1 (2 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.
SchemaSerializer.readWithTransforms (cognitive 46) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1172— SchemaSerializer.readWithTransforms has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (23 pts), match/switch 8 (15 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 11). 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.
TreeUnpickler.decodeTreeTag (cognitive 46) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:266— TreeUnpickler.decodeTreeTag has cognitive complexity 46 (threshold 15). Drivers by points: if/else 24 (39 pts), match/switch 3 (5 pts), boolean chains 2 (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.
Runtime.probe (cognitive 46) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:1121— Runtime.probe has cognitive complexity 46 (threshold 15). Drivers by points: if/else 16 (29 pts), match/switch 2 (8 pts), boolean chains 5, 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.
ReactiveRegion.isValidHtmlId (cognitive 46) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveRegion.scala:143— ReactiveRegion.isValidHtmlId has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 4 (14 pts), boolean chains 8 (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.
LLM.completeElements (cognitive 45) kyo-ai/shared/src/main/scala/kyo/LLM.scala:331— LLM.completeElements has cognitive complexity 45 (threshold 15). Drivers by points: if/else 19 (37 pts), boolean chains 5, match/switch 1 (3 pts) (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.
BrowserTabSetup.attachAndSetupTab (cognitive 45) kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:240— BrowserTabSetup.attachAndSetupTab has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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. This shape REPEATS in the file: one other method here (BrowserTabSetup.createChildTab) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BrowserTabSetup.createChildTab (cognitive 45) kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:287— BrowserTabSetup.createChildTab has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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. This shape REPEATS in the file: one other method here (BrowserTabSetup.attachAndSetupTab) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DoltLiteStatements.readBranch (cognitive 45) REDACTED:226— DoltLiteStatements.readBranch has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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.
MachineSampler.runWith (cognitive 45) kyo-stats-machine/shared/src/main/scala/kyo/stats/machine/MachineSampler.scala:143— MachineSampler.runWith has cognitive complexity 45 (threshold 15). Drivers by points: loops 9 (45 pts) (nesting depth added 36). 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.
Tasty.occurrencesInFile (cognitive 45) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:765— Tasty.occurrencesInFile has cognitive complexity 45 (threshold 15). Drivers by points: error handling 5 (25 pts), match/switch 5 (17 pts), if/else 2, boolean chains 1 (nesting depth added 32). 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.
ReactiveUI.walkStatic (cognitive 45) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:192— ReactiveUI.walkStatic has cognitive complexity 45 (threshold 15). Drivers by points: loops 7 (17 pts), match/switch 8 (16 pts), if/else 9 (11 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.
Frame.extractCalleeName (cognitive 44) kyo-data/shared/src/main/scala/kyo/Frame.scala:266— Frame.extractCalleeName has cognitive complexity 44 (threshold 15). Drivers by points: if/else 26 (31 pts), boolean chains 10, match/switch 2 (3 pts) (nesting depth added 6). 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.
ImapModel.single (cognitive 44) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapModel.scala:125— ImapModel.single has cognitive complexity 44 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 5 (15 pts), match/switch 1 (7 pts), boolean chains 1 (nesting depth added 31). 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.
Structure.conform (cognitive 44) kyo-schema/shared/src/main/scala/kyo/Structure.scala:93— Structure.conform has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 6 (13 pts), boolean chains 2 (nesting depth added 21). 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.
FocusMacro.summonAnnotationPolicy (cognitive 44) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:522— FocusMacro.summonAnnotationPolicy has cognitive complexity 44 (threshold 15). Drivers by points: match/switch 13 (21 pts), if/else 16 (20 pts), error handling 2, boolean chains 1 (nesting depth added 12). 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.
TelegramConfig.init (cognitive 44) kyo-telegram/shared/src/main/scala/kyo/TelegramConfig.scala:76— TelegramConfig.init has cognitive complexity 44 (threshold 15). Drivers by points: loops 7 (28 pts), if/else 6 (15 pts), boolean chains 1 (nesting depth added 30). 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.
ChartMarks.lowerErrorBar (cognitive 44) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:838— ChartMarks.lowerErrorBar has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (23 pts), match/switch 8 (19 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.
HeaderCodec.octetText (cognitive 43) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:114— HeaderCodec.octetText has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 5, loops 1 (nesting depth added 22). 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.
RouteUtil.feedSse (cognitive 43) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1197— RouteUtil.feedSse has cognitive complexity 43 (threshold 15). Drivers by points: if/else 21 (39 pts), boolean chains 4 (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.
Walk.column (cognitive 43) kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:80— Walk.column has cognitive complexity 43 (threshold 15). Drivers by points: loops 9 (27 pts), match/switch 5 (11 pts), boolean chains 3, if/else 2 (nesting depth added 24). 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.
NioIoDriver.rebuildSelector (cognitive 42) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1674— NioIoDriver.rebuildSelector has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (22 pts), error handling 5 (12 pts), match/switch 3 (6 pts), loops 1 (2 pts) (nesting depth added 24). 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.
HtmlRenderer.renderEventAttr (cognitive 42) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:886— HtmlRenderer.renderEventAttr has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 20, if/else 19, match/switch 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ShiftJisDecoder.run (cognitive 41) kyo-charset/shared/src/main/scala/kyo/internal/charset/ShiftJisDecoder.scala:15— ShiftJisDecoder.run has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (32 pts), boolean chains 8, 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.
DiscordConfig.init (cognitive 41) kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:55— DiscordConfig.init has cognitive complexity 41 (threshold 15). Drivers by points: loops 7 (28 pts), if/else 6 (12 pts), boolean chains 1 (nesting depth added 27). 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.
StreamPublisher.apply (cognitive 41) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamPublisher.scala:30— StreamPublisher.apply has cognitive complexity 41 (threshold 15). Drivers by points: loops 10 (31 pts), if/else 3 (8 pts), match/switch 1 (2 pts) (nesting depth added 27). 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.
Worker.run (cognitive 41) kyo-scheduler/jvm-native/src/main/scala/kyo/scheduler/Worker.scala:307— Worker.run has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (39 pts), boolean chains 1, loops 1 (nesting depth added 22). 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.
ChartScales.yLeftExtent (cognitive 41) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:96— ChartScales.yLeftExtent has cognitive complexity 41 (threshold 15). Drivers by points: match/switch 8 (27 pts), if/else 7 (14 pts) (nesting depth added 26). 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.
RuntimeExecutor.execute (cognitive 40) kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/RuntimeExecutor.scala:45— RuntimeExecutor.execute has cognitive complexity 40 (threshold 15). Drivers by points: loops 8 (30 pts), match/switch 2 (10 pts) (nesting depth added 30). 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.
HttpClientBackend.timeoutWith (cognitive 40) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1323— HttpClientBackend.timeoutWith has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 3 (12 pts), boolean chains 1 (nesting depth added 25). 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.
UnsafeServerDispatch.serveRequest (cognitive 40) kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:691— UnsafeServerDispatch.serveRequest has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (23 pts), match/switch 6 (15 pts), boolean chains 2 (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.
WireLayout.apply (cognitive 40) kyo-schema/shared/src/main/scala/kyo/internal/WireLayout.scala:161— WireLayout.apply has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (15 pts), match/switch 8 (15 pts), boolean chains 10 (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.
HtmlRenderer.renderTo (cognitive 40) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:235— HtmlRenderer.renderTo has cognitive complexity 40 (threshold 15). Drivers by points: match/switch 8 (24 pts), if/else 8 (10 pts), loops 3 (6 pts) (nesting depth added 21). 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.
PingPongBench.kyoBenchFiber (cognitive 39) kyo-bench/src/main/scala/kyo/bench/arena/PingPongBench.scala:37— PingPongBench.kyoBenchFiber has cognitive complexity 39 (threshold 15). Drivers by points: loops 10 (30 pts), if/else 4 (9 pts) (nesting depth added 25). 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.
Utf8.run (cognitive 39) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:20— Utf8.run has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (33 pts), boolean chains 5, loops 1 (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.
TagMacro.refuseCollapsed (cognitive 39) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:246— TagMacro.refuseCollapsed has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 5 (11 pts), boolean chains 5 (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.
Context.extractMethodSpec (cognitive 39) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:441— Context.extractMethodSpec has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (24 pts), match/switch 9 (14 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.
NativeEmitter.emitBodyInner (cognitive 39) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:166— NativeEmitter.emitBodyInner has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (26 pts), match/switch 10 (13 pts) (nesting depth added 8). 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.
NativeLoader.assertBundledPresent (cognitive 39) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/NativeLoader.scala:201— NativeLoader.assertBundledPresent has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (28 pts), match/switch 3 (11 pts) (nesting depth added 22). 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.
Http1Parser.classifyPathSegment (cognitive 39) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:527— Http1Parser.classifyPathSegment has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (36 pts), boolean chains 3 (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.
JsTransport.upgradeConnection (cognitive 39) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:960— JsTransport.upgradeConnection has cognitive complexity 39 (threshold 15). Drivers by points: if/else 21 (27 pts), match/switch 5 (7 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 8). 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.
Sortable.move (cognitive 39) kyo-ui/shared/src/main/scala/kyo/Sortable.scala:40— Sortable.move has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (32 pts), match/switch 1 (4 pts), boolean chains 3 (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.
Request.apply (cognitive 38) kyo-ai/shared/src/main/scala/kyo/ai/completion/AnthropicCompletion.scala:276— Request.apply has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (20 pts), match/switch 7 (14 pts), boolean chains 4 (nesting depth added 10). 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.
Big5Decoder.run (cognitive 38) kyo-charset/shared/src/main/scala/kyo/internal/charset/Big5Decoder.scala:15— Big5Decoder.run has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (30 pts), boolean chains 4, match/switch 1 (3 pts), loops 1 (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.
ZeroCapacityUnsafe.flush (cognitive 38) kyo-core/shared/src/main/scala/kyo/Channel.scala:662— ZeroCapacityUnsafe.flush has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 4 (15 pts), boolean chains 4 (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.
TransferEncoding.quotedPrintableDecoding (cognitive 38) kyo-email/shared/src/main/scala/kyo/internal/email/mime/TransferEncoding.scala:209— TransferEncoding.quotedPrintableDecoding has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 4 (7 pts), boolean chains 6 (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.
NioIoDriver.dispatchReadyKeys (cognitive 38) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1557— NioIoDriver.dispatchReadyKeys has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (31 pts), error handling 1 (4 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 28). 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.
YamlScalars.isFloatNumber (cognitive 38) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:255— YamlScalars.isFloatNumber has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 13, loops 1 (2 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.
TransformAwareReader.hasNextField (cognitive 38) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2925— TransformAwareReader.hasNextField has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (30 pts), match/switch 2 (7 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.
NodeCommandUnsafe.checkCommandExists (cognitive 38) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:586— NodeCommandUnsafe.checkCommandExists has cognitive complexity 38 (threshold 15). Drivers by points: if/else 17 (31 pts), error handling 2 (4 pts), boolean chains 3 (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.
ChartMarks.lowerBarGrouped (cognitive 38) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:268— ChartMarks.lowerBarGrouped has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 7 (12 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.
ReactiveUI.dispatchTarget (cognitive 38) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1068— ReactiveUI.dispatchTarget has cognitive complexity 38 (threshold 15). Drivers by points: loops 6 (33 pts), if/else 3 (4 pts), match/switch 1 (nesting depth added 28). 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.
ReactiveUI.subscribeScoped (cognitive 38) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1125— ReactiveUI.subscribeScoped has cognitive complexity 38 (threshold 15). Drivers by points: loops 6 (27 pts), match/switch 1 (6 pts), if/else 4 (5 pts) (nesting depth added 27). 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.
WebsiteMain.program (cognitive 38) kyo-website/jvm/src/main/scala/kyo/website/WebsiteMain.scala:43— WebsiteMain.program has cognitive complexity 38 (threshold 15). Drivers by points: loops 8 (32 pts), match/switch 1 (6 pts) (nesting depth added 29). 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.
Base64.decodeWith (cognitive 37) kyo-data/shared/src/main/scala/kyo/Base64.scala:147— Base64.decodeWith has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 3, loops 1 (3 pts) (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.
Progress.build (cognitive 37) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:1661— Progress.build has cognitive complexity 37 (threshold 15). Drivers by points: if/else 23 (25 pts), match/switch 5 (10 pts), boolean chains 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.
StoreInterpreter.withTimeoutAndRetry (cognitive 37) kyo-flow/shared/src/main/scala/kyo/internal/StoreInterpreter.scala:159— StoreInterpreter.withTimeoutAndRetry has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (20 pts), match/switch 10 (17 pts) (nesting depth added 10). 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.
RouteUtil.parseMultipartBody (cognitive 37) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1532— RouteUtil.parseMultipartBody has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (34 pts), boolean chains 2, match/switch 1 (nesting depth added 23). 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.
ClasspathOrchestrator.coldLoadBinding (cognitive 37) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2785— ClasspathOrchestrator.coldLoadBinding has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (30 pts), match/switch 3 (7 pts) (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.
ChartScales.foldExtent (cognitive 37) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:27— ChartScales.foldExtent has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 5 (19 pts), if/else 8 (18 pts) (nesting depth added 24). 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.
ClaudeCodeCompletion.run (cognitive 36) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:115— ClaudeCodeCompletion.run has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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.
FlowEngine.attemptOne (cognitive 36) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:832— FlowEngine.attemptOne has cognitive complexity 36 (threshold 15). Drivers by points: loops 4 (18 pts), match/switch 3 (14 pts), if/else 4 (nesting depth added 25). 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.
RouteUtil.parseMultipartSectionBytes (cognitive 36) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1459— RouteUtil.parseMultipartSectionBytes has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (35 pts), boolean chains 1 (nesting depth added 18). 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.
ProgressEngine.buildProgressSink (cognitive 36) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/ProgressEngine.scala:80— ProgressEngine.buildProgressSink has cognitive complexity 36 (threshold 15). Drivers by points: match/switch 7 (28 pts), if/else 5 (8 pts) (nesting depth added 24). 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.
PollerIoDriver.drainReady (cognitive 36) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1623— PollerIoDriver.drainReady has cognitive complexity 36 (threshold 15). Drivers by points: if/else 14 (33 pts), boolean chains 2, loops 1 (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.
SchemaSerializer.readStringKeyed (cognitive 36) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:667— SchemaSerializer.readStringKeyed has cognitive complexity 36 (threshold 15). Drivers by points: error handling 4 (15 pts), match/switch 5 (15 pts), if/else 5 (6 pts) (nesting depth added 22). 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.
SchemaSerializer.writeStructureValue (cognitive 36) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1418— SchemaSerializer.writeStructureValue has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 8 (17 pts), boolean chains 2 (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.
MysqlConnection.mkConnection (cognitive 36) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:536— MysqlConnection.mkConnection has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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. This shape REPEATS in the file: one other method here (MysqlConnection.withConnection) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MysqlConnection.withConnection (cognitive 36) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlConnection.scala:605— MysqlConnection.withConnection has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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. This shape REPEATS in the file: one other method here (MysqlConnection.mkConnection) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
JvmCommandUnsafe.spawn (cognitive 36) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:418— JvmCommandUnsafe.spawn has cognitive complexity 36 (threshold 15). Drivers by points: match/switch 7 (23 pts), error handling 2 (7 pts), if/else 3 (6 pts) (nesting depth added 24). 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.
UIServer.serveSession (cognitive 36) kyo-ui/shared/src/main/scala/kyo/internal/UIServer.scala:77— UIServer.serveSession has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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.
WebsiteGenerator.emitIntroPage (cognitive 36) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:261— WebsiteGenerator.emitIntroPage has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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. This shape REPEATS in the file: one other method here (WebsiteGenerator.emitModulePage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
WebsiteGenerator.emitModulePage (cognitive 36) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:306— WebsiteGenerator.emitModulePage has cognitive complexity 36 (threshold 15). Drivers by points: loops 8 (36 pts) (nesting depth added 28). 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. This shape REPEATS in the file: one other method here (WebsiteGenerator.emitIntroPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
internal.enrichedContext (cognitive 35) kyo-ai/shared/src/main/scala/kyo/Prompt.scala:90— internal.enrichedContext has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 4 (10 pts) (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.
BrowserSnapshot.restoreSnapshot (cognitive 35) kyo-browser/shared/src/main/scala/kyo/internal/BrowserSnapshot.scala:150— BrowserSnapshot.restoreSnapshot has cognitive complexity 35 (threshold 15). Drivers by points: loops 7 (28 pts), if/else 6, boolean chains 1 (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.
GuardCore.closeWithPolicy (cognitive 35) kyo-ffi/shared/src/main/scala/kyo/ffi/internal/GuardCore.scala:172— GuardCore.closeWithPolicy has cognitive complexity 35 (threshold 15). Drivers by points: error handling 6 (22 pts), if/else 6 (11 pts), loops 1 (2 pts) (nesting depth added 22). 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.
Http1Parser.detectSpecialHeader (cognitive 35) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:631— Http1Parser.detectSpecialHeader has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (35 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.
ContainerImage.parse (cognitive 35) kyo-pod/shared/src/main/scala/kyo/ContainerImage.scala:90— ContainerImage.parse has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (26 pts), match/switch 4 (9 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.
TypedSymbolFactory.from (cognitive 35) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:37— TypedSymbolFactory.from has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 7 (16 pts) (nesting depth added 19). 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.
ReactiveUI.dragDispatch (cognitive 35) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:918— ReactiveUI.dragDispatch has cognitive complexity 35 (threshold 15). Drivers by points: loops 5 (25 pts), if/else 4 (5 pts), match/switch 3 (5 pts) (nesting depth added 23). 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.
DocsMarkdownRender.removeDocTestBlocks (cognitive 35) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:288— DocsMarkdownRender.removeDocTestBlocks has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 20). 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.
_fixLazyImages (cognitive 35) kyo-browser/shared/src/main/resources/kyo/Readability.js:2332— _fixLazyImages has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 14). None of this is in the body itself: all 35 points belong to one function literal inside it that branches (line 2335). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CodexCompletion.isolatedCodexHome (cognitive 34) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:224— CodexCompletion.isolatedCodexHome has cognitive complexity 34 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 4 (13 pts) (nesting depth added 24). 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.
Ed25519Scalar.slide (cognitive 34) kyo-crypto/shared/src/main/scala/kyo/internal/crypto/Ed25519Scalar.scala:84— Ed25519Scalar.slide has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 4 (11 pts), boolean chains 2 (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.
HttpClientBackend.buildBodyStream (cognitive 34) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:657— HttpClientBackend.buildBodyStream has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (25 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.
Http1Parser.matchMethod (cognitive 34) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:803— Http1Parser.matchMethod has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 9 (nesting depth added 5). 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.
Http1ResponseParser.packResponse (cognitive 34) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:210— Http1ResponseParser.packResponse has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 6 (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.
RouteUtil.encodeRequestParams (cognitive 34) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:542— RouteUtil.encodeRequestParams has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (25 pts), match/switch 3 (9 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.
HstoreReader.parseText (cognitive 34) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/HstoreReader.scala:190— HstoreReader.parseText has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 7, loops 4 (6 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.
Scala2PickleReader.resolveExtFullName (cognitive 34) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/scala2/Scala2PickleReader.scala:439— Scala2PickleReader.resolveExtFullName has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 18). 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.
ClaudeCodeCompletion.withResultBridge (cognitive 33) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeCompletion.scala:394— ClaudeCodeCompletion.withResultBridge has cognitive complexity 33 (threshold 15). Drivers by points: loops 7 (28 pts), match/switch 1 (5 pts) (nesting depth added 25). 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.
NativeEmitter.emitStructRead (cognitive 33) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:641— NativeEmitter.emitStructRead has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 6 (13 pts) (nesting depth added 15). 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.
Markdown.link (cognitive 33) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:801— Markdown.link has cognitive complexity 33 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 4 (11 pts), boolean chains 1 (nesting depth added 22). 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.
PollerIoDriver.flushPending (cognitive 33) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1177— PollerIoDriver.flushPending has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 2 (5 pts), match/switch 2 (4 pts), boolean chains 1 (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.
YamlScalars.isYaml11DecimalFloat (cognitive 33) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:291— YamlScalars.isYaml11DecimalFloat has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 11, loops 1 (2 pts) (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.
YamlSource.foldFlowScalarText (cognitive 33) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlSource.scala:124— YamlSource.foldFlowScalarText has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 5 (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.
Jwt.decoded (cognitive 33) kyo-teams/shared/src/main/scala/kyo/internal/teams/Jwt.scala:62— Jwt.decoded has cognitive complexity 33 (threshold 15). Drivers by points: loops 6 (21 pts), match/switch 2 (12 pts) (nesting depth added 25). 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.
ChartMarks.lowerText (cognitive 33) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:752— ChartMarks.lowerText has cognitive complexity 33 (threshold 15). Drivers by points: match/switch 8 (18 pts), if/else 9 (14 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.
ChartMarks.buildSimpleAreaPath (cognitive 33) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:960— ChartMarks.buildSimpleAreaPath has cognitive complexity 33 (threshold 15). Drivers by points: match/switch 8 (23 pts), if/else 5 (9 pts), boolean chains 1 (nesting depth added 19). 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.
ChartMarks.lowerArea (cognitive 33) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1035— ChartMarks.lowerArea has cognitive complexity 33 (threshold 15). Drivers by points: match/switch 10 (33 pts) (nesting depth added 23). 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.
TagMacro.bindUnderlying (cognitive 32) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:156— TagMacro.bindUnderlying has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 7 (15 pts), if/else 8 (11 pts), boolean chains 6 (nesting depth added 11). 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.
HttpClientBackend.readBufferedBody (cognitive 32) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:462— HttpClientBackend.readBufferedBody has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (28 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 17). 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.
NioIoDriver.drainPendingRegistrations (cognitive 32) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1497— NioIoDriver.drainPendingRegistrations has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 4 (12 pts), boolean chains 1, loops 1 (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.
OccurrenceScanner.scanFile (cognitive 32) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/OccurrenceScanner.scala:79— OccurrenceScanner.scanFile has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 2 (8 pts), boolean chains 4 (nesting depth added 18). 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.
SnapshotReader.readSymbolsMapped (cognitive 32) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1108— SnapshotReader.readSymbolsMapped has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4, loops 4, match/switch 1 (4 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. This shape REPEATS in the file: one other method here (SnapshotReader.readSymbols) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SnapshotReader.readSymbols (cognitive 32) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1433— SnapshotReader.readSymbols has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4, loops 4, match/switch 1 (4 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. This shape REPEATS in the file: one other method here (SnapshotReader.readSymbolsMapped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ChartLayout.buildLayout (cognitive 32) kyo-ui/shared/src/main/scala/kyo/internal/ChartLayout.scala:144— ChartLayout.buildLayout has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 9, match/switch 3 (4 pts) (nesting depth added 3). 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.
CodexCompletion.streamFragments (cognitive 31) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:77— CodexCompletion.streamFragments has cognitive complexity 31 (threshold 15). Drivers by points: loops 7 (24 pts), match/switch 2 (7 pts) (nesting depth added 22). 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.
EucJpDecoder.run (cognitive 31) kyo-charset/shared/src/main/scala/kyo/internal/charset/EucJpDecoder.scala:14— EucJpDecoder.run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 5, loops 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.
Utf16Decoder.run (cognitive 31) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf16Decoder.scala:21— Utf16Decoder.run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 7, loops 1, 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.
Unsafe.initInline (cognitive 31) kyo-core/shared/src/main/scala/kyo/Scope.scala:404— Unsafe.initInline has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (27 pts), match/switch 2 (4 pts) (nesting depth added 8). 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.
EmailSmtpConfig.isIpv6 (cognitive 31) kyo-email/shared/src/main/scala/kyo/EmailSmtpConfig.scala:149— EmailSmtpConfig.isIpv6 has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 4 (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.
HeaderCodec.fold (cognitive 31) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:338— HeaderCodec.fold has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 4 (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.
Context.extractType (cognitive 31) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:929— Context.extractType has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 3 (7 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.
OpenApiMacro.buildRequestDef (cognitive 31) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiMacro.scala:154— OpenApiMacro.buildRequestDef has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 7 (15 pts), 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.
YamlCstEdits.insertNode (cognitive 31) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:109— YamlCstEdits.insertNode has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 5 (13 pts), boolean chains 2 (nesting depth added 15). 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.
YamlParser.readFlowText (cognitive 31) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:270— YamlParser.readFlowText has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 6, match/switch 1 (4 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.
Hold.acquire (cognitive 31) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteWriteGate.scala:85— Hold.acquire has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 3 (9 pts), match/switch 2 (8 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.
WalkContext.extractValue (cognitive 31) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:250— WalkContext.extractValue has cognitive complexity 31 (threshold 15). Drivers by points: loops 9 (27 pts), boolean chains 2, if/else 1, 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.
ClasspathOrchestrator.decodeOneEntry (cognitive 31) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:576— ClasspathOrchestrator.decodeOneEntry has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 2 (4 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.
AstUnpickler.decodeTemplateParents (cognitive 31) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:843— AstUnpickler.decodeTemplateParents has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (18 pts), error handling 2 (6 pts), boolean chains 5, 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.
SnapshotReader.readErrors (cognitive 31) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1585— SnapshotReader.readErrors has cognitive complexity 31 (threshold 15). Drivers by points: loops 7 (19 pts), if/else 5 (7 pts), match/switch 2 (5 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.
HtmlRenderer.renderElementAttrs (cognitive 31) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:662— HtmlRenderer.renderElementAttrs has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 10 (20 pts), loops 2 (6 pts), if/else 5 (nesting depth added 14). 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.
(anonymous)::collapseWhitespace (cognitive 31) REDACTED:456— (anonymous)::collapseWhitespace has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 7, loops 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.
Config.reasoningMismatch (cognitive 30) kyo-ai/shared/src/main/scala/kyo/ai/Config.scala:189— Config.reasoningMismatch has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 4 (10 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.
Driver.reconnect (cognitive 30) kyo-discord/shared/src/main/scala/kyo/internal/discord/Session.scala:233— Driver.reconnect has cognitive complexity 30 (threshold 15). Drivers by points: loops 5 (20 pts), if/else 4 (9 pts), match/switch 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.
Pipeline.render (cognitive 30) kyo-schema-yaml/shared/src/main/scala/kyo/Yaml.scala:965— Pipeline.render has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (23 pts), match/switch 2 (4 pts), boolean chains 3 (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.
MysqlSessionTracking.read (cognitive 30) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlSessionTracking.scala:30— MysqlSessionTracking.read has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 9). 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.
FromExprDerived.buildField (cognitive 30) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1129— FromExprDerived.buildField has cognitive complexity 30 (threshold 15). Drivers by points: match/switch 6 (16 pts), if/else 8 (10 pts), error handling 1 (4 pts) (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.
PathWatch.scan (cognitive 30) kyo-system/shared/src/main/scala/kyo/PathWatch.scala:40— PathWatch.scan has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 5 (7 pts), boolean chains 3, 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.
internal.gather (cognitive 29) kyo-core/shared/src/main/scala/kyo/Fiber.scala:955— internal.gather has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, match/switch 1 (3 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.
DecoderState.drain (cognitive 29) kyo-http/shared/src/main/scala/kyo/internal/http1/ChunkedBodyDecoder.scala:336— DecoderState.drain has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 1 (3 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.
RouteUtil.encodeRequestWithBoundary (cognitive 29) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:80— RouteUtil.encodeRequestWithBoundary has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (22 pts), match/switch 3 (7 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.
RouteUtil.encodeResponseParams (cognitive 29) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:594— RouteUtil.encodeResponseParams has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (20 pts), if/else 7 (9 pts) (nesting depth added 17). 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.
StreamSubscriber.await (cognitive 29) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:115— StreamSubscriber.await has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (28 pts), match/switch 1 (nesting depth added 12). 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.
YamlParser.unescapeDoubleQuoted (cognitive 29) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:911— YamlParser.unescapeDoubleQuoted has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 4 (15 pts), if/else 8 (13 pts), boolean chains 1 (nesting depth added 16). 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.
SchemaSerializer.readTables (cognitive 29) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:54— SchemaSerializer.readTables has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (19 pts), match/switch 6 (8 pts), boolean chains 2 (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.
FromExprDerived.buildMaybe (cognitive 29) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:966— FromExprDerived.buildMaybe has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 8 (10 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 12). 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.
WalkContext.walkDictChain (cognitive 29) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:131— WalkContext.walkDictChain has cognitive complexity 29 (threshold 15). Drivers by points: loops 8 (20 pts), boolean chains 7, if/else 1, match/switch 1 (nesting depth added 12). 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.
JarCentralDirectory.parseCenRecords (cognitive 29) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:430— JarCentralDirectory.parseCenRecords has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (6 pts) (nesting depth added 18). 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.
NameUnpickler.readUnsafe (cognitive 29) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/NameUnpickler.scala:90— NameUnpickler.readUnsafe has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (7 pts), match/switch 2 (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.
LocalExchange.tryMorphRange (cognitive 29) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomBackend.scala:219— LocalExchange.tryMorphRange has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (6 pts), boolean chains 3 (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.
Runtime.handleSensor (cognitive 29) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:323— Runtime.handleSensor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 2 (5 pts), boolean chains 4 (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.
HtmlRenderer.renderDropdownWithValue (cognitive 29) kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:443— HtmlRenderer.renderDropdownWithValue has cognitive complexity 29 (threshold 15). Drivers by points: if/else 26 (27 pts), boolean chains 1, match/switch 1 (nesting depth added 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.
Request.apply (cognitive 28) kyo-ai/shared/src/main/scala/kyo/ai/completion/OpenAICompletion.scala:366— Request.apply has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 5 (9 pts), boolean chains 4 (nesting depth added 5). 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.
BrowserTabSetup.mkBrowserTab (cognitive 28) kyo-browser/shared/src/main/scala/kyo/internal/BrowserTab.scala:78— BrowserTabSetup.mkBrowserTab has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 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.
internal.isSubType (cognitive 28) kyo-data/shared/src/main/scala/kyo/Tag.scala:446— internal.isSubType has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 7 (9 pts), boolean chains 6 (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.
internal.isSameType (cognitive 28) kyo-data/shared/src/main/scala/kyo/Tag.scala:593— internal.isSameType has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 8 (15 pts), if/else 7, boolean chains 6 (nesting depth added 7). 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.
AddressCodec.parse (cognitive 28) kyo-email/shared/src/main/scala/kyo/internal/email/mime/AddressCodec.scala:26— AddressCodec.parse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (6 pts), boolean chains 3, loops 2 (3 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.
JsEmitter.emitPlainMethodBody (cognitive 28) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:212— JsEmitter.emitPlainMethodBody has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (16 pts), match/switch 8 (12 pts) (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.
NativeManifestPlatform.readManifestsAt (cognitive 28) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/NativeManifestPlatform.scala:57— NativeManifestPlatform.readManifestsAt has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 3 (6 pts), loops 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (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.
FlowEngine.initImpl (cognitive 28) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:1271— FlowEngine.initImpl has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 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.
JsonRpcHttpTransport.webSocket (cognitive 28) kyo-jsonrpc-http/src/main/scala/kyo/JsonRpcHttpTransport.scala:73— JsonRpcHttpTransport.webSocket has cognitive complexity 28 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 2 (13 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.
Eval.release (cognitive 28) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:639— Eval.release has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (10 pts), match/switch 3 (6 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.
McpCapabilityGate.missingCapability (cognitive 28) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpCapabilityGate.scala:70— McpCapabilityGate.missingCapability has cognitive complexity 28 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 6). 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.
PosixTransport.listenImpl (cognitive 28) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:969— PosixTransport.listenImpl has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (22 pts), match/switch 2 (6 pts) (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.
JsonReader.readStructure (cognitive 28) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:787— JsonReader.readStructure has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 2, 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.
PostgresArrayReader.parseTextElements (cognitive 28) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresArrayReader.scala:194— PostgresArrayReader.parseTextElements has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 3, loops 1 (2 pts) (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.
FromExprDerived.applyAnyToFreeParams (cognitive 28) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:659— FromExprDerived.applyAnyToFreeParams has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (21 pts), match/switch 4, boolean chains 3 (nesting depth added 5). 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.
FromExprDerived.deriveMaybe (cognitive 28) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1782— FromExprDerived.deriveMaybe has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 8 (10 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 12). 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.
NodePathLock.acquire (cognitive 28) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:422— NodePathLock.acquire has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 6 (17 pts), if/else 6 (9 pts), error handling 2 (nesting depth added 14). 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.
ReactiveUI.targetSatisfies (cognitive 28) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:433— ReactiveUI.targetSatisfies has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 4 (10 pts), boolean chains 3 (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.
DocsClient.extractBracketed (cognitive 28) kyo-website-bundle/js/src/main/scala/kyo/website/DocsClient.scala:508— DocsClient.extractBracketed has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 3, loops 1 (3 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.
DocsMarkdownRender.linkedBadge (cognitive 28) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:1001— DocsMarkdownRender.linkedBadge has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (28 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.
SiteApp.handleKey (cognitive 28) kyo-website/shared/src/main/scala/kyo/website/SiteApp.scala:278— SiteApp.handleKey has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (9 pts), boolean chains 1, match/switch 1 (nesting depth added 14). 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.
Readability (cognitive 28) kyo-browser/shared/src/main/resources/kyo/Readability.js:27— Readability has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 13, if/else 8 (12 pts), ternaries 1 (3 pts) (nesting depth added 6). Of this number, 14 points are the body's own statements and 14 belong to 7 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.
RendezvousBench.catsBench (cognitive 27) kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:9— RendezvousBench.catsBench has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (11 pts), loops 4 (10 pts), if/else 6 (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. This shape REPEATS in the file: one other method here (RendezvousBench.zioBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RendezvousBench.zioBench (cognitive 27) kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:110— RendezvousBench.zioBench has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (11 pts), loops 4 (10 pts), if/else 6 (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. This shape REPEATS in the file: one other method here (RendezvousBench.catsBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CdpBackend.handleDialogOpening (cognitive 27) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:796— CdpBackend.handleDialogOpening has cognitive complexity 27 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 2 (9 pts), if/else 3 (7 pts), boolean chains 1 (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.
Discord.open (cognitive 27) kyo-discord/shared/src/main/scala/kyo/Discord.scala:116— Discord.open has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 2 (6 pts) (nesting depth added 19). 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.
TransferEncoding.quotedPrintableEncoding (cognitive 27) kyo-email/shared/src/main/scala/kyo/internal/email/mime/TransferEncoding.scala:255— TransferEncoding.quotedPrintableEncoding has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 1, 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.
TlsEngineIo.decryptInbound (cognitive 27) kyo-net/shared/src/main/scala/kyo/net/internal/posix/TlsEngineIo.scala:163— TlsEngineIo.decryptInbound has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 1 (3 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.
Stream.zip (cognitive 27) kyo-prelude/shared/src/main/scala/kyo/Stream.scala:680— Stream.zip has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 3 (6 pts) (nesting depth added 14). 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.
MacroUtils.sumCaseType (cognitive 27) kyo-schema/shared/src/main/scala/kyo/internal/MacroUtils.scala:126— MacroUtils.sumCaseType has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 4 (10 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.
SchemaSerializer.flattenFields (cognitive 27) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1275— SchemaSerializer.flattenFields has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 10 (12 pts) (nesting depth added 12). 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.
NodePathUnsafe.copy (cognitive 27) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:759— NodePathUnsafe.copy has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 3 (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.
PositionsUnpickler.readSync (cognitive 27) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:198— PositionsUnpickler.readSync has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 2 (4 pts), loops 3 (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.
TeamsConfig.problemOf (cognitive 27) kyo-teams/shared/src/main/scala/kyo/TeamsConfig.scala:193— TeamsConfig.problemOf has cognitive complexity 27 (threshold 15). Drivers by points: if/else 24 (25 pts), boolean chains 1, match/switch 1 (nesting depth added 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.
_unwrapNoscriptImages (cognitive 27) kyo-browser/shared/src/main/resources/kyo/Readability.js:1892— _unwrapNoscriptImages has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 14). None of this is in the body itself: all 27 points belong to 2 function literals inside it that branch (lines 1917, 1896). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CodexCompletion.collectTurn (cognitive 26) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:485— CodexCompletion.collectTurn has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 4, match/switch 1 (3 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.
Completion.fitSystemMessages (cognitive 26) kyo-ai/shared/src/main/scala/kyo/ai/completion/Completion.scala:92— Completion.fitSystemMessages has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 3 (9 pts), loops 1 (3 pts), boolean chains 2 (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.
FieldsMacros.fromObjectImpl (cognitive 26) kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:267— FieldsMacros.fromObjectImpl has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 10 (19 pts), if/else 5 (6 pts), boolean chains 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.
Context.extractParentArgs (cognitive 26) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:165— Context.extractParentArgs has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 9 (12 pts) (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.
Http1ResponseParser.parse (cognitive 26) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:114— Http1ResponseParser.parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (25 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.
RouteUtil.decodeParam (cognitive 26) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:629— RouteUtil.decodeParam has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (19 pts), match/switch 4 (6 pts), boolean chains 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.
WebSocketCodec.readRawFrameWith (cognitive 26) kyo-http/shared/src/main/scala/kyo/internal/websocket/WebSocketCodec.scala:380— WebSocketCodec.readRawFrameWith has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 3 (nesting depth added 5). 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.
McpEngine.initServer (cognitive 26) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpEngine.scala:25— McpEngine.initServer has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (19 pts), match/switch 5, boolean chains 2 (nesting depth added 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.
Parameters.rawParameters (cognitive 26) kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:102— Parameters.rawParameters has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 2 (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.
NioIoDriver.dispatchGraceProbe (cognitive 26) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:612— NioIoDriver.dispatchGraceProbe has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), error handling 1 (2 pts), loops 1 (2 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.
IoUringDriver.runCycle (cognitive 26) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1711— IoUringDriver.runCycle has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (14 pts), error handling 2 (5 pts), match/switch 2 (5 pts), boolean chains 2 (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.
PosixTransport.handleAccepted (cognitive 26) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1181— PosixTransport.handleAccepted has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (6 pts), error handling 1 (3 pts) (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.
PosixTransport.driveUpgradeRead (cognitive 26) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:2329— PosixTransport.driveUpgradeRead has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 5 (11 pts) (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.
HttpContainerBackend.stats (cognitive 26) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:724— HttpContainerBackend.stats has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 2 (7 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.
PostgresDecoder.expandIpv6 (cognitive 26) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1043— PostgresDecoder.expandIpv6 has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 5, error handling 2 (4 pts) (nesting depth added 5). 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.
JarCentralDirectory.readCenLocationBuf (cognitive 26) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:728— JarCentralDirectory.readCenLocationBuf has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (24 pts), boolean chains 2 (nesting depth added 16). 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.
ClasspathOrchestrator.readAndDecodeTastyFile (cognitive 26) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2413— ClasspathOrchestrator.readAndDecodeTastyFile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 4 (10 pts) (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.
Context.extractReturnShape (cognitive 25) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:611— Context.extractReturnShape has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), match/switch 2 (7 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.
FlagAdmin.routes (cognitive 25) kyo-http/shared/src/main/scala/kyo/FlagAdmin.scala:47— FlagAdmin.routes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 5 (9 pts), error handling 1 (4 pts), boolean chains 2 (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.
ChunkedBodyDecoder.parseChunkSizeLine (cognitive 25) kyo-http/shared/src/main/scala/kyo/internal/http1/ChunkedBodyDecoder.scala:556— ChunkedBodyDecoder.parseChunkSizeLine has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 6 (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.
Http1Parser.parseHeaders (cognitive 25) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:572— Http1Parser.parseHeaders has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 1 (nesting depth added 13). 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.
CallEngine.callEncoded (cognitive 25) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:207— CallEngine.callEncoded has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 8 (18 pts), if/else 6, boolean chains 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.
Contextual.join (cognitive 25) kyo-kernel/shared/src/main/scala/kyo/kernel/Isolate.scala:324— Contextual.join has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (8 pts), match/switch 1 (2 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.
NioIoDriver.deliverStaged (cognitive 25) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:693— NioIoDriver.deliverStaged has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (7 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.
IoUringDriver.flushTls (cognitive 25) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:786— IoUringDriver.flushTls has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (6 pts), loops 1 (4 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.
HttpContainerBackend.mapHttpError (cognitive 25) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:101— HttpContainerBackend.mapHttpError has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 5 (9 pts), boolean chains 1 (nesting depth added 14). 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.
JsonReader.integral (cognitive 25) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:232— JsonReader.integral has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 4). 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.
YamlCstEdits.replaceNode (cognitive 25) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:57— YamlCstEdits.replaceNode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 4 (8 pts), boolean chains 1 (nesting depth added 12). 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.
YamlReader.readSourceQuotedScalar (cognitive 25) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1283— YamlReader.readSourceQuotedScalar has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 2 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). 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.
Log.apply (cognitive 25) kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:230— Log.apply has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (24 pts), match/switch 1 (nesting depth added 12). 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.
DocsClient.splitJsonArray (cognitive 25) kyo-website-bundle/js/src/main/scala/kyo/website/DocsClient.scala:402— DocsClient.splitJsonArray has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (5 pts), loops 1 (3 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.
LLM.completePartialJson (cognitive 24) kyo-ai/shared/src/main/scala/kyo/LLM.scala:152— LLM.completePartialJson has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 1 (3 pts), boolean chains 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.
CodexCompletion.eventText (cognitive 24) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:592— CodexCompletion.eventText has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), match/switch 2 (4 pts), boolean chains 3 (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.
Saslprep.prepare (cognitive 24) kyo-crypto/shared/src/main/scala/kyo/crypto/Saslprep.scala:65— Saslprep.prepare has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (6 pts), boolean chains 2 (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.
UnicodeNormalization.compose (cognitive 24) kyo-crypto/shared/src/main/scala/kyo/internal/crypto/UnicodeNormalization.scala:101— UnicodeNormalization.compose has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 2, loops 1 (2 pts) (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.
Glob.fromEncodedV1 (cognitive 24) kyo-data/shared/src/main/scala/kyo/Glob.scala:129— Glob.fromEncodedV1 has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 2 (7 pts), if/else 2 (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.
SegmentParser.parseSequence (cognitive 24) kyo-data/shared/src/main/scala/kyo/Glob.scala:361— SegmentParser.parseSequence has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 3 (8 pts), boolean chains 3, loops 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.
MimeRenderer.tree (cognitive 24) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeRenderer.scala:123— MimeRenderer.tree has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (3 pts), match/switch 1 (3 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.
FfiGenerator.collectWarnings (cognitive 24) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiGenerator.scala:148— FfiGenerator.collectWarnings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 3, loops 2 (3 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.
JvmEmitter.emitVariadicMethodBody (cognitive 24) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:554— JvmEmitter.emitVariadicMethodBody has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (17 pts), match/switch 6 (7 pts) (nesting depth added 4). 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.
HttpHeaders.findCookieValue (cognitive 24) kyo-http/shared/src/main/scala/kyo/HttpHeaders.scala:564— HttpHeaders.findCookieValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (23 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.
Http1ResponseParser.parseHeaders (cognitive 24) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:337— Http1ResponseParser.parseHeaders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 1 (nesting depth added 13). 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.
Safepoint.resolve (cognitive 24) kyo-kernel/jvm-native/src/main/scala/kyo/kernel/internal/Safepoint.scala:118— Safepoint.resolve has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 9). 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.
Markdown.image (cognitive 24) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:772— Markdown.image has cognitive complexity 24 (threshold 15). Drivers by points: loops 6 (21 pts), if/else 2 (3 pts) (nesting depth added 16). 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.
JdkSslEngine.doHandshakeStep (cognitive 24) kyo-net/jvm/src/main/scala/kyo/net/internal/JdkSslEngine.scala:133— JdkSslEngine.doHandshakeStep has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (21 pts), loops 1 (2 pts), boolean chains 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.
JdkSslEngine.readPlain (cognitive 24) kyo-net/jvm/src/main/scala/kyo/net/internal/JdkSslEngine.scala:194— JdkSslEngine.readPlain has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (24 pts) (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.
NioTransport.startTlsHandshake (cognitive 24) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:736— NioTransport.startTlsHandshake has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 2 (4 pts), boolean chains 2, error handling 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.
NioTransport.acceptAllPendingTls (cognitive 24) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1246— NioTransport.acceptAllPendingTls has cognitive complexity 24 (threshold 15). Drivers by points: error handling 5 (11 pts), if/else 6 (7 pts), match/switch 2 (5 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.
IonTextParser.validRealBody (cognitive 24) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:609— IonTextParser.validRealBody has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5 (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.
ProtoSchema.fromStructure (cognitive 24) kyo-schema-protobuf/shared/src/main/scala/kyo/Protobuf.scala:324— ProtoSchema.fromStructure has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 8 (13 pts), if/else 9 (10 pts), boolean chains 1 (nesting depth added 6). 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.
YamlParser.closingQuoteIndex (cognitive 24) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:383— YamlParser.closingQuoteIndex has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 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.
YamlParser.foldTopLevel (cognitive 24) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:810— YamlParser.foldTopLevel has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (12 pts), match/switch 2 (7 pts), boolean chains 5 (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.
Path.stepGet (cognitive 24) kyo-schema/shared/src/main/scala/kyo/Structure.scala:1127— Path.stepGet has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 7 (15 pts), if/else 6 (8 pts), boolean chains 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.
FromExprDerived.deriveField (cognitive 24) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2035— FromExprDerived.deriveField has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 6 (19 pts), if/else 5 (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.
SqlJsonArray.elements (cognitive 24) kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala:42— SqlJsonArray.elements has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (4 pts), boolean chains 2, loops 1 (2 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.
DomReactiveRegions.scan (cognitive 24) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:349— DomReactiveRegions.scan has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 1 (3 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.
ChartScales.yLeftExtentNoZero (cognitive 24) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:159— ChartScales.yLeftExtentNoZero has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 6 (17 pts), if/else 7 (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (ChartScales.yRightExtentNoZero) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ChartScales.yRightExtentNoZero (cognitive 24) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:260— ChartScales.yRightExtentNoZero has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 6 (17 pts), if/else 7 (nesting depth added 11). 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. This shape REPEATS in the file: one other method here (ChartScales.yLeftExtentNoZero) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DragProtocol.validateBase64 (cognitive 24) kyo-ui/shared/src/main/scala/kyo/internal/DragProtocol.scala:747— DragProtocol.validateBase64 has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, loops 2 (4 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.
ReactiveUI.childAt (cognitive 24) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1390— ReactiveUI.childAt has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 7 (17 pts), if/else 5, boolean chains 2 (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.
Topic.stream (cognitive 23) kyo-aeron/shared/src/main/scala/kyo/Topic.scala:329— Topic.stream has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 4 (11 pts) (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.
SegmentParser.parseClass (cognitive 23) kyo-data/shared/src/main/scala/kyo/Glob.scala:429— SegmentParser.parseClass has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 4, loops 2, match/switch 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.
ConcreteTagMacro.derive (cognitive 23) kyo-data/shared/src/main/scala/kyo/internal/ConcreteTagMacro.scala:20— ConcreteTagMacro.derive has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 7 (14 pts), if/else 9 (nesting depth added 7). 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.
FieldsMacros.deriveImpl (cognitive 23) kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:47— FieldsMacros.deriveImpl has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 9 (16 pts), if/else 6 (7 pts) (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.
Parameters.extendedSegments (cognitive 23) kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:320— Parameters.extendedSegments has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (22 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.
PollerIoDriver.dispatchRead (cognitive 23) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1765— PollerIoDriver.dispatchRead has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 3 (8 pts) (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.
HttpContainerBackend.create (cognitive 23) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:300— HttpContainerBackend.create has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 9 (10 pts) (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.
ShellBackend.imageHistory (cognitive 23) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:1738— ShellBackend.imageHistory has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (22 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.
StreamSubscriber.poll (cognitive 23) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:190— StreamSubscriber.poll has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 2 (5 pts) (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.
Scheduler.selectWorker (cognitive 23) kyo-scheduler/jvm-native/src/main/scala/kyo/scheduler/Scheduler.scala:340— Scheduler.selectWorker has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 5, loops 1 (2 pts) (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.
IonSchema.applyConstraints (cognitive 23) kyo-schema-ion/shared/src/main/scala/kyo/IonSchema.scala:350— IonSchema.applyConstraints has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 2 (5 pts), boolean chains 3 (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.
JsonSchema.fromOneOf (cognitive 23) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:644— JsonSchema.fromOneOf has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (10 pts), match/switch 5 (10 pts), boolean chains 3 (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.
YamlReader.captureSourceRootFlow (cognitive 23) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:531— YamlReader.captureSourceRootFlow has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, match/switch 1 (3 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.
SchemaSerializer.readCatchAllTree (cognitive 23) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:819— SchemaSerializer.readCatchAllTree has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 9 (10 pts) (nesting depth added 7). 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.
Wire.decodeSlash (cognitive 23) kyo-slack/shared/src/main/scala/kyo/internal/slack/Wire.scala:517— Wire.decodeSlash has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (20 pts), match/switch 2 (3 pts) (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.
WalkContext.walkRecord (cognitive 23) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:63— WalkContext.walkRecord has cognitive complexity 23 (threshold 15). Drivers by points: loops 8 (20 pts), boolean chains 1, if/else 1, match/switch 1 (nesting depth added 12). 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.
PositionsUnpickler.readSpansSync (cognitive 23) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:87— PositionsUnpickler.readSpansSync has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 3, 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.
ChartAxes.buildYAxis (cognitive 23) kyo-ui/shared/src/main/scala/kyo/internal/ChartAxes.scala:277— ChartAxes.buildYAxis has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (20 pts), match/switch 2 (3 pts) (nesting depth added 5). 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.
ChartMarks.buildBandRibbon (cognitive 23) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1121— ChartMarks.buildBandRibbon has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 6 (9 pts), boolean chains 1 (nesting depth added 11). 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.
ReactiveUI.cycleSelectOption (cognitive 23) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:385— ReactiveUI.cycleSelectOption has cognitive complexity 23 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 6 (8 pts), match/switch 3 (6 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.
WebsiteGenerator.emitLanding (cognitive 23) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:616— WebsiteGenerator.emitLanding has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 2 (5 pts), match/switch 1 (3 pts) (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.
CodexCompletion.realCodexHome (cognitive 22) kyo-ai/shared/src/main/scala/kyo/ai/completion/CodexCompletion.scala:241— CodexCompletion.realCodexHome has cognitive complexity 22 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (7 pts), match/switch 1 (5 pts) (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.
ChromeDownloader.ensureWith (cognitive 22) kyo-browser/shared/src/main/scala/kyo/internal/ChromeDownloader.scala:67— ChromeDownloader.ensureWith has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 2 (6 pts), match/switch 1 (nesting depth added 14). 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.
MpmcUnsafeQueue.drain (cognitive 22) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnsafeQueue.scala:121— MpmcUnsafeQueue.drain has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (4 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.
Path.problemOf (cognitive 22) kyo-discord/shared/src/main/scala/kyo/Discord.scala:763— Path.problemOf has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5, match/switch 1 (nesting depth added 4). 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.
ImapModifiedUtf7.decode (cognitive 22) kyo-email/shared/src/main/scala/kyo/internal/email/charset/ImapModifiedUtf7.scala:41— ImapModifiedUtf7.decode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, match/switch 1 (4 pts) (nesting depth added 6). 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.
MimeRenderer.isLineForm (cognitive 22) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeRenderer.scala:195— MimeRenderer.isLineForm has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, if/else 8 (11 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
HttpUrl.parseChecked (cognitive 22) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:225— HttpUrl.parseChecked has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 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.
OpenApiGenerator.buildParameters (cognitive 22) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:67— OpenApiGenerator.buildParameters has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3, 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.
Kyo.groupMap (cognitive 22) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1820— Kyo.groupMap has cognitive complexity 22 (threshold 15). Drivers by points: loops 4 (12 pts), match/switch 2 (6 pts), if/else 3 (4 pts) (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.
Parameters.joinSegments (cognitive 22) kyo-mime/shared/src/main/scala/kyo/mime/Parameters.scala:230— Parameters.joinSegments has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (2 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.
NioIoDriver.writeTls (cognitive 22) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:984— NioIoDriver.writeTls has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), error handling 1, match/switch 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.
PollerIoDriver.writeRaw (cognitive 22) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:1043— PollerIoDriver.writeRaw has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 pts), match/switch 1 (2 pts) (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.
Container.runHealthCheck (cognitive 22) kyo-pod/shared/src/main/scala/kyo/Container.scala:2417— Container.runHealthCheck has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 6 (10 pts) (nesting depth added 12). 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.
Protobuf.auditStructure (cognitive 22) kyo-schema-protobuf/shared/src/main/scala/kyo/Protobuf.scala:234— Protobuf.auditStructure has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 7 (14 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 9). 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.
YamlCstRenderer.stream (cognitive 22) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstRenderer.scala:17— YamlCstRenderer.stream has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 3, match/switch 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.
YamlDocuments.split (cognitive 22) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlDocuments.scala:22— YamlDocuments.split has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 7, 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.
MacroUtils.removeField (cognitive 22) kyo-schema/shared/src/main/scala/kyo/internal/MacroUtils.scala:221— MacroUtils.removeField has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 3, match/switch 1 (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.
TransformAwareReader.parseNamedKey (cognitive 22) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2741— TransformAwareReader.parseNamedKey has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4, match/switch 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.
SchemaTransformMacro.flattenFieldsImpl (cognitive 22) kyo-schema/shared/src/main/scala/kyo/internal/SchemaTransformMacro.scala:335— SchemaTransformMacro.flattenFieldsImpl has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8, boolean chains 7, match/switch 6 (7 pts) (nesting depth added 1). 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.
PostgresDecoder.readIntervalWords (cognitive 22) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:859— PostgresDecoder.readIntervalWords has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 2 (5 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.
WalkContext.extractPair (cognitive 22) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:201— WalkContext.extractPair has cognitive complexity 22 (threshold 15). Drivers by points: loops 8 (20 pts), if/else 1, match/switch 1 (nesting depth added 12). 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.
JsonStructureCounter.countArrayElements (cognitive 22) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:71— JsonStructureCounter.countArrayElements has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, match/switch 1 (3 pts), loops 2 (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.
JarCentralDirectory.readCenLocation (cognitive 22) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:370— JarCentralDirectory.readCenLocation has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (19 pts), boolean chains 3 (nesting depth added 12). 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.
ClasspathOrchestrator.walkRoot (cognitive 22) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:497— ClasspathOrchestrator.walkRoot has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 4, match/switch 1 (2 pts) (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.
SnapshotReader.readBytes (cognitive 22) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:135— SnapshotReader.readBytes has cognitive complexity 22 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 5 (6 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.
Color.hex (cognitive 22) kyo-ui/shared/src/main/scala/kyo/Style.scala:921— Color.hex has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 8 (nesting depth added 4). 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.
ChartLayout.leftAxisMargin (cognitive 22) kyo-ui/shared/src/main/scala/kyo/internal/ChartLayout.scala:84— ChartLayout.leftAxisMargin has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 9 (19 pts), if/else 2 (3 pts) (nesting depth added 11). 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.
InputMasking.filterStr (cognitive 22) kyo-ui/shared/src/main/scala/kyo/internal/InputMasking.scala:37— InputMasking.filterStr has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7 (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.
WebsiteBundleMain.showContentRoute (cognitive 22) kyo-website-bundle/js/src/main/scala/kyo/website/WebsiteBundleMain.scala:515— WebsiteBundleMain.showContentRoute has cognitive complexity 22 (threshold 15). Drivers by points: loops 7 (20 pts), match/switch 1 (2 pts) (nesting depth added 14). 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.
LLM.streamUnder (cognitive 21) kyo-ai/shared/src/main/scala/kyo/LLM.scala:202— LLM.streamUnder has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 1 (2 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.
RendezvousBench.kyoBenchFiber (cognitive 21) kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:63— RendezvousBench.kyoBenchFiber has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 3 (7 pts), if/else 4 (nesting depth added 10). 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.
EucKrDecoder.run (cognitive 21) kyo-charset/shared/src/main/scala/kyo/internal/charset/EucKrDecoder.scala:14— EucKrDecoder.run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, 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.
Unsafe.stats (cognitive 21) kyo-core/shared/src/main/scala/kyo/Cache.scala:643— Unsafe.stats has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 4 (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.
Type.render (cognitive 21) kyo-data/shared/src/main/scala/kyo/Tag.scala:225— Type.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1, match/switch 1 (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.
ImapModel.summaryFields (cognitive 21) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapModel.scala:52— ImapModel.summaryFields has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
AddressCodec.tokenize (cognitive 21) kyo-email/shared/src/main/scala/kyo/internal/email/mime/AddressCodec.scala:140— AddressCodec.tokenize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (6 pts), boolean chains 3, match/switch 1 (2 pts) (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.
HeaderCodec.value (cognitive 21) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:157— HeaderCodec.value has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, 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.
NativeLoader.tryCleanupStaleLock (cognitive 21) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/NativeLoader.scala:367— NativeLoader.tryCleanupStaleLock has cognitive complexity 21 (threshold 15). Drivers by points: error handling 4 (12 pts), if/else 6 (9 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.
HttpUrl.splitPathQuery (cognitive 21) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:358— HttpUrl.splitPathQuery has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (19 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.
OpenApiGenerator.jsonSchemaToHttpOpenApi (cognitive 21) kyo-http/shared/src/main/scala/kyo/internal/codec/OpenApiGenerator.scala:243— OpenApiGenerator.jsonSchemaToHttpOpenApi has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 3 (6 pts), boolean chains 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.
ByteStream.readUntilWith (cognitive 21) kyo-http/shared/src/main/scala/kyo/internal/util/ByteStream.scala:24— ByteStream.readUntilWith has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (2 pts) (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.
FtlParser.parsePattern (cognitive 21) kyo-i18n/shared/src/main/scala/kyo/internal/Ftl.scala:90— FtlParser.parsePattern has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 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.
Kyo.groupMap (cognitive 21) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:962— Kyo.groupMap has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (12 pts), match/switch 3 (8 pts), if/else 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.
McpCatalog.autoDeriveServerCapabilities (cognitive 21) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpCatalog.scala:63— McpCatalog.autoDeriveServerCapabilities has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 2 (4 pts), boolean chains 1 (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.
McpClientEngine.initClient (cognitive 21) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpClientEngine.scala:88— McpClientEngine.initClient has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
NioIoDriver.dispatchKeysLoop (cognitive 21) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1603— NioIoDriver.dispatchKeysLoop has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 1 (2 pts) (nesting depth added 13). 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.
Parse.andIs (cognitive 21) kyo-parse/shared/src/main/scala/kyo/Parse.scala:777— Parse.andIs has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
ShellBackend.mapInspectToInfo (cognitive 21) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:304— ShellBackend.mapInspectToInfo has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17 (18 pts), match/switch 2 (3 pts) (nesting depth added 2). 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.
ShellBackend.runWithStreams (cognitive 21) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:2192— ShellBackend.runWithStreams has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
IonTextParser.skipWhitespace (cognitive 21) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:833— IonTextParser.skipWhitespace has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (5 pts), boolean chains 4, match/switch 1 (3 pts) (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.
JsonReader.skipContainer (cognitive 21) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:386— JsonReader.skipContainer has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 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.
YamlCstEdits.removeNode (cognitive 21) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:171— YamlCstEdits.removeNode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 4 (8 pts), boolean chains 1 (nesting depth added 9). 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.
YamlReader.sourceFlowEntryEnd (cognitive 21) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1121— YamlReader.sourceFlowEntryEnd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 4). 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.
FocusMacro.givenSchema (cognitive 21) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:388— FocusMacro.givenSchema has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts), match/switch 3, error handling 1 (nesting depth added 1). 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.
SchemaSerializer.catchAllFit (cognitive 21) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:743— SchemaSerializer.catchAllFit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 5). 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.
DoltStatements.readTag (cognitive 21) REDACTED:341— DoltStatements.readTag has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
DoltLiteStatements.readTag (cognitive 21) REDACTED:419— DoltLiteStatements.readTag has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
PostgresConnection.mkConnection (cognitive 21) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:706— PostgresConnection.mkConnection has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (21 pts) (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.
SqlJsonArray.unquote (cognitive 21) kyo-sql/shared/src/main/scala/kyo/internal/SqlJsonArray.scala:80— SqlJsonArray.unquote has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (4 pts), match/switch 1 (3 pts), boolean chains 1, loops 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.
JsonStructureCounter.splitArrayElements (cognitive 21) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:111— JsonStructureCounter.splitArrayElements has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (3 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.
NodePathLock.create (cognitive 21) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:327— NodePathLock.create has cognitive complexity 21 (threshold 15). Drivers by points: error handling 6 (9 pts), if/else 6, match/switch 3 (6 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.
JvmCommandUnsafe.validateProgram (cognitive 21) kyo-system/jvm-native/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:375— JvmCommandUnsafe.validateProgram has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 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.
JarMappedReader.readEntry (cognitive 21) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarMappedReader.scala:35— JarMappedReader.readEntry has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, loops 1 (2 pts), match/switch 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.
Runtime.resolve (cognitive 21) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomDragRuntime.scala:219— Runtime.resolve has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (7 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.
ChartTransitions.rowKey (cognitive 21) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:107— ChartTransitions.rowKey has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 8 (21 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.
CssStyleRenderer.renderProp (cognitive 21) kyo-ui/shared/src/main/scala/kyo/internal/CssStyleRenderer.scala:251— CssStyleRenderer.renderProp has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 11 (21 pts) (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.
DocsMarkdownRender.stripInlineMarkdown (cognitive 21) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:613— DocsMarkdownRender.stripInlineMarkdown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 2, 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.
_replaceBrs (cognitive 21) kyo-browser/shared/src/main/resources/kyo/Readability.js:696— _replaceBrs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 10). None of this is in the body itself: all 21 points belong to one function literal inside it that branches (line 697). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Topic.addPublicationDeadline (cognitive 20) kyo-aeron/shared/src/main/scala/kyo/Topic.scala:405— Topic.addPublicationDeadline has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3 (5 pts), boolean chains 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. This shape REPEATS in the file: one other method here (Topic.addSubscriptionDeadline) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Topic.addSubscriptionDeadline (cognitive 20) kyo-aeron/shared/src/main/scala/kyo/Topic.scala:507— Topic.addSubscriptionDeadline has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 3 (5 pts), boolean chains 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. This shape REPEATS in the file: one other method here (Topic.addPublicationDeadline) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ChromeDownloader.replacePartial (cognitive 20) kyo-browser/shared/src/main/scala/kyo/internal/ChromeDownloader.scala:136— ChromeDownloader.replacePartial has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (6 pts), match/switch 1 (4 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.
MpscUnboundedUnsafeQueue.peekElement (cognitive 20) kyo-data/jvm-native/src/main/scala/kyo/internal/MpscUnboundedUnsafeQueue.scala:200— MpscUnboundedUnsafeQueue.peekElement has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (20 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.
Chunk.foreach (cognitive 20) kyo-data/shared/src/main/scala/kyo/Chunk.scala:410— Chunk.foreach has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 1 (2 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.
Rest.failureOf (cognitive 20) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:261— Rest.failureOf has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (6 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.
Reader.statusText (cognitive 20) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:200— Reader.statusText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (5 pts), boolean chains 3 (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.
MimeModel.classify (cognitive 20) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeModel.scala:74— MimeModel.classify has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 6, boolean chains 3 (nesting depth added 6). 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.
SmtpSession.prepared (cognitive 20) kyo-email/shared/src/main/scala/kyo/internal/email/smtp/SmtpSession.scala:316— SmtpSession.prepared has cognitive complexity 20 (threshold 15). Drivers by points: loops 3 (12 pts), if/else 4, boolean chains 2, match/switch 1 (2 pts) (nesting depth added 10). 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.
Context.extractBorrowedReturn (cognitive 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/FfiInspector.scala:853— Context.extractBorrowedReturn has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 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.
JsEmitter.emitVariadicMethodBody (cognitive 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:89— JsEmitter.emitVariadicMethodBody has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 4 (nesting depth added 4). 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.
NativeEmitter.emitStructWrite (cognitive 20) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:473— NativeEmitter.emitStructWrite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 3 (7 pts) (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.
UpcallBridge.zeroHandlerName (cognitive 20) kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/UpcallBridge.scala:692— UpcallBridge.zeroHandlerName has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 9. 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.
NativeLeakDetector.sweep (cognitive 20) kyo-ffi/native/src/main/scala/kyo/ffi/internal/NativeLeakDetector.scala:198— NativeLeakDetector.sweep has cognitive complexity 20 (threshold 15). Drivers by points: error handling 2 (9 pts), loops 2 (5 pts), if/else 2 (4 pts), match/switch 1 (2 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.
HttpUrl.hostAndPortEnd (cognitive 20) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:272— HttpUrl.hostAndPortEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 4 (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.
HttpUrl.parseQueryParam (cognitive 20) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:458— HttpUrl.parseQueryParam has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 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. This shape REPEATS in the file: one other method here (HttpUrl.parseQueryParamAll) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
HttpUrl.parseQueryParamAll (cognitive 20) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:478— HttpUrl.parseQueryParamAll has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (19 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. This shape REPEATS in the file: one other method here (HttpUrl.parseQueryParam) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Http1Parser.parsePathSegments (cognitive 20) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:487— Http1Parser.parsePathSegments has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (4 pts), boolean chains 3 (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.
RouteUtil.sseLine (cognitive 20) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:1243— RouteUtil.sseLine has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), match/switch 2 (4 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.
Markdown.inlineCode (cognitive 20) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:853— Markdown.inlineCode has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (15 pts), match/switch 1 (3 pts), if/else 2 (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.
McpHandshakeGate.server (cognitive 20) kyo-mcp/shared/src/main/scala/kyo/internal/mcp/McpHandshakeGate.scala:24— McpHandshakeGate.server has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (5 pts), match/switch 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.
IoUringDriver.onInboundClosedDuringRead (cognitive 20) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2495— IoUringDriver.onInboundClosedDuringRead has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (5 pts), error handling 1 (4 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.
PollerIoDriver.applyRegistration (cognitive 20) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2531— PollerIoDriver.applyRegistration has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 4 (5 pts), boolean chains 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.
PosixTransport.completeOrTls (cognitive 20) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:665— PosixTransport.completeOrTls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (6 pts), error handling 1 (2 pts) (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.
Parser.parseDocument (cognitive 20) kyo-schema-bson/shared/src/main/scala/kyo/internal/bson/BsonReader.scala:396— Parser.parseDocument has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts), boolean chains 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.
JsonReader.scanNumber (cognitive 20) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:580— JsonReader.scanNumber has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 6 (nesting depth added 4). 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.
YamlParser.foldBlockScalarLines (cognitive 20) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:635— YamlParser.foldBlockScalarLines has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (2 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.
YamlReader.closingSourceQuoteIndex (cognitive 20) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1353— YamlReader.closingSourceQuoteIndex has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 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.
YamlReader.foldSourceScalarLines (cognitive 20) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1378— YamlReader.foldSourceScalarLines has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (2 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.
FocusMacro.emitSealedSchemaStatic (cognitive 20) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2696— FocusMacro.emitSealedSchemaStatic has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 7 (12 pts), if/else 7, boolean chains 1 (nesting depth added 5). 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.
FromExprDerived.deriveFor (cognitive 20) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1442— FromExprDerived.deriveFor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13, match/switch 2 (4 pts), boolean chains 3 (nesting depth added 2). 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.
JsonStructureCounter.countObjectEntries (cognitive 20) kyo-sql/shared/src/main/scala/kyo/internal/reader/JsonStructureCounter.scala:32— JsonStructureCounter.countObjectEntries has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (3 pts), boolean chains 2, loops 2 (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.
STM.commit (cognitive 20) kyo-stm/shared/src/main/scala/kyo/STM.scala:193— STM.commit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 2 (3 pts) (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.
PathPlatformSpecific.make (cognitive 20) kyo-system/js-wasm/src/main/scala/kyo/internal/PathPlatformSpecific.scala:1294— PathPlatformSpecific.make has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 6 (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.
ReadHandle.parseLeadingLong (cognitive 20) kyo-system/shared/src/main/scala/kyo/Path.scala:1760— ReadHandle.parseLeadingLong has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 3 (nesting depth added 4). 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.
_fixRelativeUris (cognitive 20) kyo-browser/shared/src/main/resources/kyo/Readability.js:456— _fixRelativeUris has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 6). None of this is in the body itself: all 20 points belong to 4 function items inside it that branch (a function literal at line 475, toAbsoluteURI, a function literal at line 511, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
_markDataTables (cognitive 20) kyo-browser/shared/src/main/resources/kyo/Readability.js:2271— _markDataTables has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, 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.
internal.handle (cognitive 19) kyo-ai/shared/src/main/scala/kyo/Tool.scala:332— internal.handle has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 6 (7 pts) (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.
ClaudeCodeWire.transcriptMessages (cognitive 19) kyo-ai/shared/src/main/scala/kyo/ai/completion/ClaudeCodeWire.scala:314— ClaudeCodeWire.transcriptMessages has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 6 (12 pts), if/else 6 (7 pts) (nesting depth added 7). 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.
Rollout.select (cognitive 19) kyo-config/shared/src/main/scala/kyo/Rollout.scala:135— Rollout.select has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 1 (5 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.
StaticFlag.resolveValue (cognitive 19) kyo-config/shared/src/main/scala/kyo/StaticFlag.scala:60— StaticFlag.resolveValue has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 3 (8 pts), error handling 2 (6 pts), if/else 4 (5 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.
DerReader.readLength (cognitive 19) kyo-crypto/shared/src/main/scala/kyo/internal/crypto/DerReader.scala:25— DerReader.readLength has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (4 pts), boolean chains 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.
UnsafeBufferPlatform.mmapImpl (cognitive 19) kyo-data/native/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:84— UnsafeBufferPlatform.mmapImpl has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 1 (nesting depth added 4). 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.
Chunk.copyTo (cognitive 19) kyo-data/shared/src/main/scala/kyo/Chunk.scala:478— Chunk.copyTo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (2 pts), boolean chains 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.
Indexed.from (cognitive 19) kyo-data/shared/src/main/scala/kyo/Chunk.scala:645— Indexed.from has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 6 (9 pts) (nesting depth added 9). 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.
SegmentParser.parseAlternatives (cognitive 19) kyo-data/shared/src/main/scala/kyo/Glob.scala:402— SegmentParser.parseAlternatives has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (15 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.
Formatter.rewrite (cognitive 19) kyo-doctest/plugin/src/main/scala/kyo/doctest/sbt/Formatter.scala:82— Formatter.rewrite has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 2 (6 pts), loops 2 (4 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.
ConfigJson.extractArrayLength (cognitive 19) kyo-doctest/plugin/src/main/scala/kyo/doctest/sbt/Runner.scala:200— ConfigJson.extractArrayLength has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 1 (3 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.
HeaderCodec.recognize (cognitive 19) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:633— HeaderCodec.recognize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (4 pts), boolean chains 3 (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.
HttpUrl.fromUri (cognitive 19) kyo-http/shared/src/main/scala/kyo/HttpUrl.scala:207— HttpUrl.fromUri has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (17 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.
ByteStream.readExactWith (cognitive 19) kyo-http/shared/src/main/scala/kyo/internal/util/ByteStream.scala:63— ByteStream.readExactWith has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (19 pts) (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.
WebSocketCodec.writeUpgradeRequestWith (cognitive 19) kyo-http/shared/src/main/scala/kyo/internal/websocket/WebSocketCodec.scala:188— WebSocketCodec.writeUpgradeRequestWith has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), match/switch 3 (8 pts), boolean chains 3 (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.
Markdown.inlineHtml (cognitive 19) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:881— Markdown.inlineHtml has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (9 pts) (nesting depth added 11). 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.
Disposition.parseFormData (cognitive 19) kyo-mime/shared/src/main/scala/kyo/mime/Disposition.scala:64— Disposition.parseFormData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 3 (8 pts) (nesting depth added 7). 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.
IoUringDriver.flushRaw (cognitive 19) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:656— IoUringDriver.flushRaw has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (6 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.
PosixTransport.startAcceptLoop (cognitive 19) kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala:1042— PosixTransport.startAcceptLoop has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 2 (5 pts), boolean chains 3, error handling 1 (nesting depth added 5). 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.
Parse.runWith (cognitive 19) kyo-parse/shared/src/main/scala/kyo/Parse.scala:882— Parse.runWith has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 7 (14 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 9). 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.
YamlParser.parseInlineScalar (cognitive 19) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:140— YamlParser.parseInlineScalar has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 7 (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.
YamlReader.structureFromEvents (cognitive 19) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:49— YamlReader.structureFromEvents has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 4 (9 pts), boolean chains 1 (nesting depth added 9). 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.
MacroUtils.sumCaseReference (cognitive 19) kyo-schema/shared/src/main/scala/kyo/internal/MacroUtils.scala:62— MacroUtils.sumCaseReference has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, match/switch 4 (5 pts), boolean chains 2 (nesting depth added 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.
Ryu.digitCount (cognitive 19) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:25— Ryu.digitCount 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.
RyuDouble.formatDouble (cognitive 19) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:267— RyuDouble.formatDouble has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3 (nesting depth added 4). 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. This shape REPEATS in the file: one other method here (RyuFloat.formatFloat) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RyuFloat.formatFloat (cognitive 19) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:601— RyuFloat.formatFloat has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3 (nesting depth added 4). 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. This shape REPEATS in the file: one other method here (RyuDouble.formatDouble) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
WebApi.mapResponse (cognitive 19) kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:174— WebApi.mapResponse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (8 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.
PostgresDecoder.splitOffset (cognitive 19) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:1334— PostgresDecoder.splitOffset has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 3, loops 1 (nesting depth added 4). 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.
SystemPlatformSpecific.nodeProcessors (cognitive 19) kyo-system/js-wasm/src/main/scala/kyo/internal/SystemPlatformSpecific.scala:93— SystemPlatformSpecific.nodeProcessors has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, error handling 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.
NioAtomicMovePlatform.move (cognitive 19) kyo-system/native/src/main/scala/kyo/internal/NioAtomicMovePlatform.scala:34— NioAtomicMovePlatform.move has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 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.
PlatformModuleOps.listJdkClassFiles (cognitive 19) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/PlatformModuleOps.scala:63— PlatformModuleOps.listJdkClassFiles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, error handling 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.
ChartLegend.buildLegendItems (cognitive 19) kyo-ui/shared/src/main/scala/kyo/internal/ChartLegend.scala:431— ChartLegend.buildLegendItems has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 2 (3 pts) (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.
Linear.ticks (cognitive 19) kyo-ui/shared/src/main/scala/kyo/internal/Scale.scala:168— Linear.ticks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 1, match/switch 1 (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.
DocsClient.unescapeJson (cognitive 19) kyo-website-bundle/js/src/main/scala/kyo/website/DocsClient.scala:455— DocsClient.unescapeJson has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 1 (5 pts), match/switch 1 (4 pts), loops 1 (2 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.
_getArticleTitle (cognitive 19) kyo-browser/shared/src/main/resources/kyo/Readability.js:572— _getArticleTitle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, error handling 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.
_cleanConditionally::(anonymous)::shouldRemoveNode (cognitive 19) kyo-browser/shared/src/main/resources/kyo/Readability.js:2555— _cleanConditionally::(anonymous)::shouldRemoveNode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 9. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PingPongBench.catsBench (cognitive 18) kyo-bench/src/main/scala/kyo/bench/arena/PingPongBench.scala:7— PingPongBench.catsBench has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 4 (6 pts) (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. This shape REPEATS in the file: one other method here (PingPongBench.zioBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
PingPongBench.zioBench (cognitive 18) kyo-bench/src/main/scala/kyo/bench/arena/PingPongBench.scala:66— PingPongBench.zioBench has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 4 (6 pts) (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. This shape REPEATS in the file: one other method here (PingPongBench.catsBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ChromeDownloader.install (cognitive 18) kyo-browser/shared/src/main/scala/kyo/internal/ChromeDownloader.scala:106— ChromeDownloader.install has cognitive complexity 18 (threshold 15). Drivers by points: loops 5 (15 pts), if/else 2 (3 pts) (nesting depth added 11). 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.
Resolver.resolveAll (cognitive 18) kyo-browser/shared/src/main/scala/kyo/internal/Resolver.scala:90— Resolver.resolveAll has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4 (7 pts), boolean chains 1 (nesting depth added 9). 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.
CMeter.drainWaiters (cognitive 18) kyo-compat/bindings/future/shared/src/main/scala/kyo/compat/CMeter.scala:89— CMeter.drainWaiters has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (nesting depth added 10). 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.
StreamCompression.inflateStream (cognitive 18) kyo-core/jvm/src/main/scala/kyo/StreamCompression.scala:328— StreamCompression.inflateStream has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 5 (6 pts) (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.
Unsafe.get (cognitive 18) kyo-core/shared/src/main/scala/kyo/Cache.scala:453— Unsafe.get has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 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.
IOTask.currentFrame (cognitive 18) kyo-core/shared/src/main/scala/kyo/scheduler/IOTask.scala:225— IOTask.currentFrame has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 1 (2 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.
MpmcUnboundedUnsafeQueue.producerChunkForIndex (cognitive 18) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:68— MpmcUnboundedUnsafeQueue.producerChunkForIndex has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (18 pts) (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.
TagMacro.deriveImpl (cognitive 18) kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala:43— TagMacro.deriveImpl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 2). 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.
HeaderCodec.decodeQ (cognitive 18) kyo-email/shared/src/main/scala/kyo/internal/email/mime/HeaderCodec.scala:716— HeaderCodec.decodeQ has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 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.
JvmEmitter.emitStructReadExpr (cognitive 18) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:930— JvmEmitter.emitStructReadExpr has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 4 (6 pts) (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.
NativeManifest.parse (cognitive 18) kyo-ffi/shared/src/main/scala/kyo/ffi/internal/NativeManifest.scala:56— NativeManifest.parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3 (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.
FlowApi.signalExecution (cognitive 18) kyo-flow/shared/src/main/scala/kyo/internal/FlowApi.scala:211— FlowApi.signalExecution has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (14 pts), if/else 4 (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.
HttpHeaders.parseCookieHeader (cognitive 18) kyo-http/shared/src/main/scala/kyo/HttpHeaders.scala:585— HttpHeaders.parseCookieHeader has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 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.
PercentEncoding.decode (cognitive 18) kyo-http/shared/src/main/scala/kyo/internal/PercentEncoding.scala:39— PercentEncoding.decode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4 (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.
Http1Parser.parse (cognitive 18) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:158— Http1Parser.parse 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.
RouteUtil.decodeBufferedBodyValue (cognitive 18) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:954— RouteUtil.decodeBufferedBodyValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, match/switch 1 (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.
CallEngine.callPartialResultsEffect (cognitive 18) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:476— CallEngine.callPartialResultsEffect has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 7 (17 pts), if/else 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.
NioIoDriver.awaitReadAdmitted (cognitive 18) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:305— NioIoDriver.awaitReadAdmitted has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (6 pts) (nesting depth added 9). 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.
NioIoDriver.dispatchRead (cognitive 18) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1790— NioIoDriver.dispatchRead has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 3 (7 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.
NioIoDriver.dispatchReadPlainSocket (cognitive 18) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:1844— NioIoDriver.dispatchReadPlainSocket has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, error handling 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.
NioTransport.acceptAllPending (cognitive 18) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:512— NioTransport.acceptAllPending has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 3 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 5). 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.
KqueuePollerBackend.decodeReady (cognitive 18) kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:364— KqueuePollerBackend.decodeReady has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, 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.
ShellBackend.logStream (cognitive 18) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:942— ShellBackend.logStream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 2). 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.
JsonSchema.fromStructure (cognitive 18) kyo-schema-json/shared/src/main/scala/kyo/Json.scala:725— JsonSchema.fromStructure has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 4 (6 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.
YamlParser.inferredBlockScalarIndent (cognitive 18) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:601— YamlParser.inferredBlockScalarIndent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2 (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.
YamlScalars.parseSexagesimalFloat (cognitive 18) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlScalars.scala:165— YamlScalars.parseSexagesimalFloat has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 1 (4 pts), boolean chains 2, loops 1 (2 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.
YamlSource.findTopLevel (cognitive 18) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlSource.scala:244— YamlSource.findTopLevel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, match/switch 1 (3 pts) (nesting depth added 3). 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.
ExpandMacro.expandType (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/ExpandMacro.scala:30— ExpandMacro.expandType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, match/switch 1 (3 pts) (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.
FastFloat.eiselLemire64 (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:75— FastFloat.eiselLemire64 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (FastFloat.eiselLemire32) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
FastFloat.eiselLemire32 (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:153— FastFloat.eiselLemire32 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4 (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. This shape REPEATS in the file: one other method here (FastFloat.eiselLemire64) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
FocusMacro.metaApplyImpl (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:318— FocusMacro.metaApplyImpl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (6 pts) (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.
FocusMacro.inlineVariantKeys (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:2909— FocusMacro.inlineVariantKeys has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 7). 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.
SchemaSerializer.zeroForField (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:1596— SchemaSerializer.zeroForField has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. 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.
SchemaTransformMacro.typeNameImpl (cognitive 18) kyo-schema/shared/src/main/scala/kyo/internal/SchemaTransformMacro.scala:39— SchemaTransformMacro.typeNameImpl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 3 (5 pts), boolean chains 2 (nesting depth added 4). 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.
MysqlPacket.readOne (cognitive 18) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/MysqlPacket.scala:80— MysqlPacket.readOne has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 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.
PostgresTypes.decodeRange (cognitive 18) kyo-sql-postgres/shared/src/main/scala/kyo/PostgresTypes.scala:289— PostgresTypes.decodeRange has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 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.
SqlConnectionPool.acquireOrReserve (cognitive 18) kyo-sql/shared/src/main/scala/kyo/internal/client/SqlConnectionPool.scala:559— SqlConnectionPool.acquireOrReserve has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 4 (6 pts) (nesting depth added 9). 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.
Summary.percentile (cognitive 18) kyo-stats-registry/shared/src/main/scala/kyo/stats/internal/Summary.scala:13— Summary.percentile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 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.
ClassfileUnpickler.readClassAttrList (cognitive 18) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ClassfileUnpickler.scala:457— ClassfileUnpickler.readClassAttrList has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 5 (7 pts), 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.
SnapshotWriter.tyconFullName (cognitive 18) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotWriter.scala:1035— SnapshotWriter.tyconFullName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (7 pts) (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.
ChartScales.resolveAllScales (cognitive 18) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:419— ChartScales.resolveAllScales has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, match/switch 5. 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.
ChartTransitions.lowerBarSimpleWithTransitions (cognitive 18) kyo-ui/shared/src/main/scala/kyo/internal/ChartTransitions.scala:285— ChartTransitions.lowerBarSimpleWithTransitions has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 3 (10 pts), if/else 5 (8 pts) (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.
ReactiveUI.resolveReactives (cognitive 18) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1178— ReactiveUI.resolveReactives has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3 (4 pts), match/switch 2 (4 pts) (nesting depth added 9). 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.
Actor.run (cognitive 17) kyo-actor/shared/src/main/scala/kyo/Actor.scala:734— Actor.run has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (10 pts), match/switch 2 (7 pts) (nesting depth added 11). 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.
Utf32Decoder.run (cognitive 17) kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf32Decoder.scala:19— Utf32Decoder.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, match/switch 1 (nesting depth added 3). 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.
CompatLibrary.addRows (cognitive 17) kyo-compat/plugin/src/main/scala/io/getkyo/compat/CompatLibrary.scala:103— CompatLibrary.addRows has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, match/switch 4, loops 2 (3 pts), boolean chains 2 (nesting depth added 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.
UnicodeNormalization.decompose (cognitive 17) kyo-crypto/shared/src/main/scala/kyo/internal/crypto/UnicodeNormalization.scala:35— UnicodeNormalization.decompose has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (6 pts), boolean chains 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.
Base64.encodeWith (cognitive 17) kyo-data/shared/src/main/scala/kyo/Base64.scala:108— Base64.encodeWith has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 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.
Hex.decode (cognitive 17) kyo-data/shared/src/main/scala/kyo/Hex.scala:61— Hex.decode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 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.
FieldsMacros.comparableImpl (cognitive 17) kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:156— FieldsMacros.comparableImpl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 3 (6 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.
FieldsMacros.sameNamesImpl (cognitive 17) kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:189— FieldsMacros.sameNamesImpl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, match/switch 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.
Rest.fieldErrors (cognitive 17) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:365— Rest.fieldErrors has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 3 (nesting depth added 9). 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.
MimeRenderer.contentLeaf (cognitive 17) kyo-email/shared/src/main/scala/kyo/internal/email/mime/MimeRenderer.scala:152— MimeRenderer.contentLeaf has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), loops 3 (6 pts), boolean chains 1 (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.
TransferEncoding.decodeBase64Pieces (cognitive 17) kyo-email/shared/src/main/scala/kyo/internal/email/mime/TransferEncoding.scala:96— TransferEncoding.decodeBase64Pieces has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (5 pts), boolean chains 1, 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.
MemoryFlowStore.claimReady (cognitive 17) kyo-flow/shared/src/main/scala/kyo/internal/MemoryFlowStore.scala:224— MemoryFlowStore.claimReady has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, match/switch 3 (5 pts), boolean chains 4 (nesting depth added 2). 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.
Http1Parser.parseContentLength (cognitive 17) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:700— Http1Parser.parseContentLength has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3 (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.
Http1ResponseParser.parseContentLength (cognitive 17) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:397— Http1ResponseParser.parseContentLength has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3 (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.
IoUringDriver.submitRecv (cognitive 17) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:298— IoUringDriver.submitRecv has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (4 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.
IoUringDriver.closeWakeGuarded (cognitive 17) kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:1668— IoUringDriver.closeWakeGuarded has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (2 pts) (nesting depth added 10). 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.
FrameAssembler.pipe (cognitive 17) kyo-pod/shared/src/main/scala/kyo/internal/FrameAssembler.scala:31— FrameAssembler.pipe has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 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.
BlockingMonitor.process (cognitive 17) kyo-scheduler/jvm-native/src/main/scala/kyo/scheduler/BlockingMonitor.scala:259— BlockingMonitor.process has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2 (nesting depth added 10). 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.
Parser.parseElement (cognitive 17) kyo-schema-bson/shared/src/main/scala/kyo/internal/bson/BsonReader.scala:437— Parser.parseElement has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (3 pts) (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.
IonTextParser.parseAnnotationToken (cognitive 17) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:544— IonTextParser.parseAnnotationToken has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 1 (3 pts) (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.
JsonReader.hasNext (cognitive 17) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:162— JsonReader.hasNext has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), 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.
JsonSchemaEnricher.enrichObj (cognitive 17) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonSchemaEnricher.scala:17— JsonSchemaEnricher.enrichObj has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 2). 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.
JsonWriter.writeQuotedStringSlow (cognitive 17) kyo-schema-json/shared/src/main/scala/kyo/internal/JsonWriter.scala:341— JsonWriter.writeQuotedStringSlow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 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.
YamlCstParser.explicitDocumentBodyStart (cognitive 17) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstParser.scala:108— YamlCstParser.explicitDocumentBodyStart has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 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.
YamlReader.sourceBlockScalarHeader (cognitive 17) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:1206— YamlReader.sourceBlockScalarHeader has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (2 pts) (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.
Schema.writerWithAnnotations (cognitive 17) kyo-schema/shared/src/main/scala/kyo/Schema.scala:1775— Schema.writerWithAnnotations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (2 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.
TransformAwareReader.skip (cognitive 17) kyo-schema/shared/src/main/scala/kyo/internal/SchemaSerializer.scala:2837— TransformAwareReader.skip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (2 pts) (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.
WebApi.answer (cognitive 17) kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:257— WebApi.answer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (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.
FromExprDerived.buildProduct (cognitive 17) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1213— FromExprDerived.buildProduct has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 5, error handling 2 (3 pts), boolean chains 2 (nesting depth added 2). 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.
FromExprDerived.buildSingleton (cognitive 17) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1389— FromExprDerived.buildSingleton has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 3 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 3). 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.
FromExprDerived.deriveProduct (cognitive 17) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2130— FromExprDerived.deriveProduct has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 5, error handling 2 (3 pts), boolean chains 2 (nesting depth added 2). 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.
Walk.projectedValue (cognitive 17) kyo-sql/shared/src/main/scala/kyo/internal/macros/ColumnFromExpr.scala:189— Walk.projectedValue has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (11 pts), loops 1 (3 pts), if/else 2, 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.
NodeCommandUnsafe.waitForSuccess (cognitive 17) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:890— NodeCommandUnsafe.waitForSuccess has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 1 (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.
NioPathUnsafe.lockAttempt (cognitive 17) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:407— NioPathUnsafe.lockAttempt has cognitive complexity 17 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 2 (3 pts), match/switch 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.
NioPathLockRegistry.release (cognitive 17) kyo-system/jvm-native/src/main/scala/kyo/internal/PathPlatformSpecific.scala:806— NioPathLockRegistry.release has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (4 pts) (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.
ConstantPool.read (cognitive 17) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ConstantPool.scala:295— ConstantPool.read has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (8 pts), match/switch 2 (5 pts), if/else 3, 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.
ModuleInfoReader.readAttributesForModule (cognitive 17) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/ModuleInfoReader.scala:150— ModuleInfoReader.readAttributesForModule has cognitive complexity 17 (threshold 15). Drivers by points: loops 2 (7 pts), if/else 4 (6 pts), match/switch 2 (4 pts) (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.
AstUnpickler.decodeAnnotationBlock (cognitive 17) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1034— AstUnpickler.decodeAnnotationBlock has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 2 (3 pts), error handling 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.
Subtyping.checkOneParent (cognitive 17) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:317— Subtyping.checkOneParent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (6 pts) (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.
Subtyping.typeEquivAlpha (cognitive 17) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:510— Subtyping.typeEquivAlpha has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (8 pts), match/switch 1 (nesting depth added 2). 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.
BotApi.mapResponse (cognitive 17) kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:273— BotApi.mapResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 5 (8 pts) (nesting depth added 5). 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.
DomReactiveRegions.replaceContent (cognitive 17) kyo-ui/js-wasm/src/main/scala/kyo/internal/DomReactiveRegions.scala:93— DomReactiveRegions.replaceContent has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (7 pts), boolean chains 4, if/else 3, loops 1 (3 pts) (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.
ChartLegend.buildLegend (cognitive 17) kyo-ui/shared/src/main/scala/kyo/internal/ChartLegend.scala:42— ChartLegend.buildLegend has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 4 (6 pts) (nesting depth added 9). 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.
DocsMarkdownRender.sectionSnippets (cognitive 17) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:189— DocsMarkdownRender.sectionSnippets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6, match/switch 2 (6 pts), loops 2 (4 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.
DocsSearch.filter (cognitive 17) kyo-website/shared/src/main/scala/kyo/website/DocsSearch.scala:120— DocsSearch.filter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3 (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.
ForkManyBench.catsBench (cognitive 16) kyo-bench/src/main/scala/kyo/bench/arena/ForkManyBench.scala:7— ForkManyBench.catsBench has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (6 pts) (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. This shape REPEATS in the file: one other method here (ForkManyBench.zioBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ForkManyBench.kyoBenchFiber (cognitive 16) kyo-bench/src/main/scala/kyo/bench/arena/ForkManyBench.scala:26— ForkManyBench.kyoBenchFiber has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 3, match/switch 1 (3 pts) (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.
ForkManyBench.zioBench (cognitive 16) kyo-bench/src/main/scala/kyo/bench/arena/ForkManyBench.scala:48— ForkManyBench.zioBench has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4 (6 pts) (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. This shape REPEATS in the file: one other method here (ForkManyBench.catsBench) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NavigationWatcher.awaitSettle (cognitive 16) kyo-browser/shared/src/main/scala/kyo/internal/NavigationWatcher.scala:294— NavigationWatcher.awaitSettle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 5). 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.
SelectorJs.resolveElementJsScoped (cognitive 16) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:246— SelectorJs.resolveElementJsScoped has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). 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. This shape REPEATS in the file: one other method here (SelectorJs.resolveAllElementsJsScoped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SelectorJs.resolveAllElementsJsScoped (cognitive 16) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:381— SelectorJs.resolveAllElementsJsScoped has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 1 (nesting depth added 5). 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. This shape REPEATS in the file: one other method here (SelectorJs.resolveElementJsScoped) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
internal.foreachIndexed (cognitive 16) kyo-core/shared/src/main/scala/kyo/Fiber.scala:801— internal.foreachIndexed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (16 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.
Unsafe.leave (cognitive 16) kyo-core/shared/src/main/scala/kyo/Gate.scala:456— Unsafe.leave has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (16 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.
Unsafe.arriveAndLeave (cognitive 16) kyo-core/shared/src/main/scala/kyo/Gate.scala:534— Unsafe.arriveAndLeave has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (16 pts) (nesting depth added 9). 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.
Closeable.close (cognitive 16) kyo-core/shared/src/main/scala/kyo/Queue.scala:640— Closeable.close has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 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.
UnicodeNormalization.primaryComposite (cognitive 16) kyo-crypto/shared/src/main/scala/kyo/internal/crypto/UnicodeNormalization.scala:134— UnicodeNormalization.primaryComposite has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 3). 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.
Glob.matchSegments (cognitive 16) kyo-data/shared/src/main/scala/kyo/Glob.scala:526— Glob.matchSegments has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 3 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 6). 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.
Automaton.matches (cognitive 16) kyo-data/shared/src/main/scala/kyo/Glob.scala:199— Automaton.matches has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (7 pts), match/switch 1 (5 pts), if/else 2 (4 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.
DiscordConfig.urlProblemOf (cognitive 16) kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:136— DiscordConfig.urlProblemOf has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 4 (nesting depth added 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.
Orchestrator.run (cognitive 16) kyo-doctest/jvm/src/main/scala/kyo/doctest/internal/Orchestrator.scala:33— Orchestrator.run has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 2 (nesting depth added 10). 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.
Reader.value (cognitive 16) kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala:336— Reader.value has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 1 (3 pts), boolean chains 2, match/switch 1 (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.
LineConnection.readLine (cognitive 16) kyo-email/shared/src/main/scala/kyo/internal/email/net/LineConnection.scala:25— LineConnection.readLine has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, match/switch 1 (nesting depth added 5). 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.
EmitterBase.layoutRequiredStructs (cognitive 16) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/EmitterBase.scala:157— EmitterBase.layoutRequiredStructs has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 5 (6 pts), loops 1 (nesting depth added 6). 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.
KoffiAbiProbe.isSupported (cognitive 16) kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/KoffiAbiProbe.scala:89— KoffiAbiProbe.isSupported has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 4). 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.
executions.signal (cognitive 16) kyo-flow/shared/src/main/scala/kyo/FlowEngine.scala:223— executions.signal has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 2 (5 pts) (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.
RouteUtil.decodeBufferedResponse (cognitive 16) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:171— RouteUtil.decodeBufferedResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 3 (5 pts) (nesting depth added 4). 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.
RouteUtil.encodeStreamBodyValueWith (cognitive 16) kyo-http/shared/src/main/scala/kyo/internal/server/RouteUtil.scala:731— RouteUtil.encodeStreamBodyValueWith has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 7 (13 pts), if/else 2 (3 pts) (nesting depth added 7). 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.
CancellationEngine.handleInboundCancel (cognitive 16) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CancellationEngine.scala:95— CancellationEngine.handleInboundCancel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 3 (7 pts) (nesting depth added 9). 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.
Markdown.parseBlockquoteContent (cognitive 16) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:508— Markdown.parseBlockquoteContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 3 (7 pts), boolean chains 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.
SslLibProvider.applyConfig (cognitive 16) kyo-net/shared/src/main/scala/kyo/net/internal/SslLibProvider.scala:69— SslLibProvider.applyConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 2, 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.
EpollPollerBackend.decodeReady (cognitive 16) kyo-net/shared/src/main/scala/kyo/net/internal/posix/EpollPollerBackend.scala:227— EpollPollerBackend.decodeReady has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (nesting depth added 4). 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.
KqueuePollerBackend.pollFresh (cognitive 16) kyo-net/shared/src/main/scala/kyo/net/internal/posix/KqueuePollerBackend.scala:397— KqueuePollerBackend.pollFresh has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 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.
HttpContainerBackend.stat (cognitive 16) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:1223— HttpContainerBackend.stat has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 2 (6 pts) (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.
HttpContainerBackend.imageBuildFromPath (cognitive 16) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:1748— HttpContainerBackend.imageBuildFromPath has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 1 (nesting depth added 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.
ShellBackend.buildNetworkSettings (cognitive 16) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:402— ShellBackend.buildNetworkSettings has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 pts), 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.
ShellBackend.volumeList (cognitive 16) kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:2005— ShellBackend.volumeList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (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.
Pipe.collectWhilePure (cognitive 16) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:560— Pipe.collectWhilePure has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (4 pts) (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. This shape REPEATS in the file: one other method here (Pipe.collectWhile) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Pipe.collectWhile (cognitive 16) kyo-prelude/shared/src/main/scala/kyo/Pipe.scala:585— Pipe.collectWhile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (4 pts) (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. This shape REPEATS in the file: one other method here (Pipe.collectWhilePure) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
StreamSubscriber.onNext (cognitive 16) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscriber.scala:55— StreamSubscriber.onNext has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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.
StreamSubscription.poll (cognitive 16) kyo-reactive-streams/shared/src/main/scala/kyo/interop/flow/StreamSubscription.scala:97— StreamSubscription.poll has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 3 (6 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.
Regulator.adjust (cognitive 16) kyo-scheduler/jvm-native/src/main/scala/kyo/scheduler/regulator/Regulator.scala:170— Regulator.adjust has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), error handling 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.
IonTextParser.validDigits (cognitive 16) kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:670— IonTextParser.validDigits has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 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.
Parser.parseValue (cognitive 16) kyo-schema-ion/shared/src/main/scala/kyo/internal/ionbinary/IonBinaryReader.scala:392— Parser.parseValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 3 (7 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.
Protobuf.validateCanonical (cognitive 16) kyo-schema-protobuf/shared/src/main/scala/kyo/Protobuf.scala:123— Protobuf.validateCanonical has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (3 pts), boolean chains 1 (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.
Renderer.startBlockCollection (cognitive 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:143— Renderer.startBlockCollection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, match/switch 1 (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.
YamlParser.parseBlockSequence (cognitive 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlParser.scala:87— YamlParser.parseBlockSequence has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 1 (3 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.
YamlReader.trySourceNil (cognitive 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:366— YamlReader.trySourceNil has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 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.
YamlReader.checkDecimalExponent (cognitive 16) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlReader.scala:692— YamlReader.checkDecimalExponent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 1 (2 pts) (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.
DoltStatements.interpretMerge (cognitive 16) REDACTED:254— DoltStatements.interpretMerge has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 5 (6 pts) (nesting depth added 7). 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.
PipelineExchange.readOneStatementResult (cognitive 16) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/PipelineExchange.scala:186— PipelineExchange.readOneStatementResult has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (8 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 5). 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.
SqliteText.intervalFields (cognitive 16) kyo-sql-sqlite-driver/shared/src/main/scala/kyo/internal/sqlite/SqliteText.scala:108— SqliteText.intervalFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 3, 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.
Connection.openSocket (cognitive 16) kyo-sql/shared/src/main/scala/kyo/db/Connection.scala:388— Connection.openSocket has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 4 (8 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.
SqlStaticMacro.renderLifted (cognitive 16) kyo-sql/shared/src/main/scala/kyo/internal/SqlStaticMacro.scala:182— SqlStaticMacro.renderLifted has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), 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.
SqlValueRender.interval (cognitive 16) kyo-sql/shared/src/main/scala/kyo/internal/SqlValueRender.scala:176— SqlValueRender.interval has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (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.
WalkContext.sqlNameValue (cognitive 16) kyo-sql/shared/src/main/scala/kyo/internal/macros/RecordFromExpr.scala:339— WalkContext.sqlNameValue has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (10 pts), loops 2 (5 pts), if/else 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.
DoltFileSystem.resolved (cognitive 16) kyo-system-doltfs/shared/src/main/scala/kyo/DoltFileSystem.scala:63— DoltFileSystem.resolved has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 3 (8 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.
Classpath.computeFullName (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/Tasty.scala:4264— Classpath.computeFullName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, match/switch 1 (3 pts) (nesting depth added 4). 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.
ClasspathOrchestrator.classfilePathToFullName (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2648— ClasspathOrchestrator.classfilePathToFullName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (nesting depth added 4). 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.
AstUnpickler.decodeOneTypeIfPresent (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:630— AstUnpickler.decodeOneTypeIfPresent has cognitive complexity 16 (threshold 15). Drivers by points: error handling 3 (9 pts), if/else 6 (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.
DigestComputer.collectFiles (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/DigestComputer.scala:247— DigestComputer.collectFiles has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 2 (6 pts), loops 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.
SnapshotReader.deserializeAnnotationsByIdx (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:634— SnapshotReader.deserializeAnnotationsByIdx has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), loops 3 (6 pts), boolean chains 4 (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.
TypeArena.merge (cognitive 16) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/TypeArena.scala:33— TypeArena.merge has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 5 (6 pts), loops 2 (nesting depth added 6). 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.
ReactiveUI.findPathById (cognitive 16) kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala:1309— ReactiveUI.findPathById has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), match/switch 3 (5 pts) (nesting depth added 4). 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.
DocsMarkdownRender.parseBlockquoteContent (cognitive 16) kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:779— DocsMarkdownRender.parseBlockquoteContent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 3 (7 pts), boolean chains 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.
WebsiteVersion.parse (cognitive 16) kyo-website/shared/src/main/scala/kyo/website/WebsiteVersion.scala:31— WebsiteVersion.parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). 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.
_getArticleMetadata (cognitive 16) kyo-browser/shared/src/main/resources/kyo/Readability.js:1757— _getArticleMetadata has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, ternaries 1 (nesting depth added 2). Of this number, 8 points are the body's own statements and 8 belong to one function literal inside it that branches. 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.
Near-duplicate member pair (107 shared lines) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:76— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:76-263 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:424-598 — These two members are variants of one another: 107 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.
Near-duplicate member pair (78 shared lines) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:139— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:139-237 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:270-352 — These two members are variants of one another: 78 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.
Near-duplicate member pair (75 shared lines) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1017— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1017-1126 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1851-2032 — These two members are variants of one another: 75 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.
Near-duplicate member pair (39 shared lines) kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:77— kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:77-137 | kyo-schema/shared/src/main/scala/kyo/internal/FastFloat.scala:155-211 — These two members are variants of one another: 39 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.
Near-duplicate member pair (34 shared lines) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:277— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:277-342 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:537-603 — These two members are variants of one another: 34 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.
Near-duplicate member pair (29 shared lines) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1059— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1059-1152 | kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:581-678 — These two members are variants of one another: 29 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.
Near-duplicate member pair (28 shared lines) kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:154— kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:154-188 | kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala:202-236 — These two members are variants of one another: 28 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:466— kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:466-526 | kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:656-813 — These two members are one piece of code written twice and then edited apart: 35 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) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:294— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:294-321 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:339-366 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:386-413 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:435-462 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:627-653 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:697-721 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:736-764 — 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· Edited copy of a member (357 corresponding lines) · ×1
Edited copy of a member (357 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:210— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:210-575 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:725-1081 — These two members are one piece of code written twice and then edited apart: 357 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 (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:340— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:340-405 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Handler.scala:418-486 — These two members are one piece of code written twice and then edited apart: 66 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 copies of one member (3 members, 72+ corresponding lines) · ×1
Edited copies of one member (3 members, 72+ corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala:3332— kyo-schema/shared/src/main/scala/kyo/Schema.scala:3332-3404 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3608-3679 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3755-3826 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 72 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 68+ corresponding lines) · ×1
Edited copies of one member (3 members, 68+ corresponding lines) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:177— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:177-244 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:526-602 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:615-684 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 68 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (71 corresponding lines) · ×1
Edited copy of a member (71 corresponding lines) kyo-aeron/shared/src/main/scala/kyo/Topic.scala:411— kyo-aeron/shared/src/main/scala/kyo/Topic.scala:411-500 | kyo-aeron/shared/src/main/scala/kyo/Topic.scala:513-583 — These two members are one piece of code written twice and then edited apart: 71 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 (78 corresponding lines) · ×1
Edited copy of a member (78 corresponding lines) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:630— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:630-715 | kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:874-951 — These two members are one piece of code written twice and then edited apart: 78 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 (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:268— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:268-324 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:602-652 — These two members are one piece of code written twice and then edited apart: 51 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:64— kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:64-106 | kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlCstEdits.scala:177-213 — These two members are one piece of code written twice and then edited apart: 37 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 (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:92— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:92-145 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:205-293 — These two members are one piece of code written twice and then edited apart: 54 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 copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:435— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:435-460 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:246-269 | kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:241-268 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (121 corresponding lines) · ×1
Edited copy of a member (121 corresponding lines) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:247— kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:247-374 | kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:382-510 — These two members are one piece of code written twice and then edited apart: 121 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 (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:424— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:424-462 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1191-1231 — These two members are one piece of code written twice and then edited apart: 39 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 (43 corresponding lines) · ×1
Edited copy of a member (43 corresponding lines) kyo-browser/shared/src/main/scala/kyo/Browser.scala:624— kyo-browser/shared/src/main/scala/kyo/Browser.scala:624-666 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:719-767 — These two members are one piece of code written twice and then edited apart: 43 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 copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:391— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:391-427 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:545-583 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:600-640 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:324— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:324-367 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:664-733 — 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· Edited copies of one member (3 members, 44+ corresponding lines) · ×1
Edited copies of one member (3 members, 44+ corresponding lines) kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:10— kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:10-60 | kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:64-107 | kyo-bench/src/main/scala/kyo/bench/arena/RendezvousBench.scala:111-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (59 corresponding lines) · ×1
Edited copy of a member (59 corresponding lines) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:251— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:251-309 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:583-646 — These two members are one piece of code written twice and then edited apart: 59 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 (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:258— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:258-286 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/exchange/HandshakeExchange.scala:356-388 — These two members are one piece of code written twice and then edited apart: 29 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 copies of one member (4 members, 34+ corresponding lines) · ×1
Edited copies of one member (4 members, 34+ corresponding lines) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:586— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:586-627 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1118-1160 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:880-913 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:825-859 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1639— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1639-1655 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1700-1716 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1733-1749 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:528— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:528-547 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:609-637 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:666-697 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 18+ corresponding lines) · ×1
Edited copies of one member (6 members, 18+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:98— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:98-115 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:131-155 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:183-204 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:706-723 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:735-753 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:774-791 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) kyo-schema/shared/src/main/scala/kyo/Schema.scala:2091— kyo-schema/shared/src/main/scala/kyo/Schema.scala:2091-2121 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:2166-2197 — These two members are one piece of code written twice and then edited apart: 31 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 copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:798— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:798-811 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:850-863 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:880-893 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 12+ corresponding lines) · ×1
Edited copies of one member (5 members, 12+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1341— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1341-1353 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1389-1401 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1458-1474 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1514-1530 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:1541-1552 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 1+ corresponding lines) · ×1
Edited copies of one member (4 members, 1+ corresponding lines) kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:118— kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:118-118 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:132-136 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:151-157 | kyo-kernel/shared/src/main/scala/kyo/Kyo.scala:173-185 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 1 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:24— kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:24-31 | kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:23-28 | kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/BufferFactory.scala:34-39 | kyo-ffi/native/src/main/scala/kyo/ffi/internal/BufferFactory.scala:24-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 4+ corresponding lines) · ×1
Edited copies of one member (5 members, 4+ corresponding lines) kyo-data/shared/src/main/scala/kyo/Hex.scala:95— kyo-data/shared/src/main/scala/kyo/Hex.scala:95-98 | kyo-data/shared/src/main/scala/kyo/UUID.scala:120-123 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:345-348 | kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:819-822 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/types/PostgresDecoder.scala:566-569 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×1
Edited copies of one member (3 members, 3+ corresponding lines) kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:253— kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:253-255 | kyo-teams/shared/src/main/scala/kyo/internal/teams/Connector.scala:194-196 | kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:419-421 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (110–116 lines × 2) kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:247— kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:247-356 | kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:382-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-browser/shared/src/main/scala/kyo/internal/Selector.scala:247` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (61–64 lines × 2) kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:247— kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:247-310 | kyo-browser/shared/src/main/scala/kyo/internal/CdpBackend.scala:573-633 — 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 (49 lines × 2) kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:250— kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:250-298 | kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:311-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala:250` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (40–41 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1195— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1195-1234 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1528-1568 — 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 (38–39 lines × 3) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:199— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:199-236 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:548-586 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:639-676 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (47–55 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1123— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1123-1169 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:1448-1502 — 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 (36–37 lines × 2) kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:648— kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:648-684 | kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:893-928 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:648` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:646` calls `discard`, `setNoDelay` and `kyo-net/js-wasm/src/main/scala/kyo/net/internal/JsTransport.scala:890` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (32–34 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:81— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:81-114 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:429-460 — 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 (28–33 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:517— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:517-544 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:574-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:517` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30–33 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:132— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:132-164 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:304-333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/CallEngine.scala:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28–29 lines × 2) kyo-browser/shared/src/main/scala/kyo/Browser.scala:637— kyo-browser/shared/src/main/scala/kyo/Browser.scala:637-664 | kyo-browser/shared/src/main/scala/kyo/Browser.scala:734-762 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-browser/shared/src/main/scala/kyo/Browser.scala:637` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–28 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1049— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1049-1076 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1085-1110 — 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 (22–27 lines × 2) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:139— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:139-165 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:270-291 — 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–27 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:701— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:701-727 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:732-749 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:701` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–26 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1043— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1043-1064 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1902-1927 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1043` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1901` calls `NamedArg`, `unwrap` and `kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1042` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21–26 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:99— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:99-119 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:221-246 — 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–25 lines × 2) kyo-browser/shared/src/main/scala/kyo/internal/Resolver.scala:43— kyo-browser/shared/src/main/scala/kyo/internal/Resolver.scala:43-62 | kyo-browser/shared/src/main/scala/kyo/internal/Resolver.scala:103-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-browser/shared/src/main/scala/kyo/internal/Resolver.scala:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:96— kyo-data/shared/src/main/scala/kyo/DictBuilder.scala:96-121 | kyo-data/shared/src/main/scala/kyo/OrderedDictBuilder.scala:102-127 — 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 (22–23 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:279— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:279-301 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:610-631 — 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 (22 lines × 3) kyo-schema/shared/src/main/scala/kyo/Schema.scala:3369— kyo-schema/shared/src/main/scala/kyo/Schema.scala:3369-3390 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3644-3665 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:3791-3812 — 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 (34–35 lines × 2) kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:470— kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:470-504 | kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:724-757 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-system/js-wasm/src/main/scala/kyo/internal/ProcessPlatformSpecific.scala:724` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:214— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:214-234 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:553-572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:214` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–21 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:122— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:122-138 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/PositionsUnpickler.scala:256-276 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–20 lines × 3) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:711— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:711-728 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:996-1015 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:736-752 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:996` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–20 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1017— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1017-1027 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1852-1871 — 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 (24 lines × 2) kyo-schema/shared/src/main/scala/kyo/Schema.scala:2035— kyo-schema/shared/src/main/scala/kyo/Schema.scala:2035-2058 | kyo-schema/shared/src/main/scala/kyo/Schema.scala:4048-4071 — 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–19 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:156— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:156-174 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:498-514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21–31 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1066— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1066-1086 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1930-1960 — 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–18 lines × 3) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1118— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1118-1135 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:880-893 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:825-838 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1118` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 3) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:151— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:151-168 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:181-198 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:236-253 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:199` calls `getOrElse`, `TypeBounds` and `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/TypedSymbolFactory.scala:169` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13–18 lines × 2) kyo-core/shared/src/main/scala/kyo/Channel.scala:694— kyo-core/shared/src/main/scala/kyo/Channel.scala:694-706 | kyo-core/shared/src/main/scala/kyo/Channel.scala:949-966 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-core/shared/src/main/scala/kyo/Channel.scala:694` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–18 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:271— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:271-288 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1442-1456 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:307— kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:307-324 | kyo-schema/shared/src/main/scala/kyo/internal/Ryu.scala:636-652 — 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–18 lines × 2) kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:559— kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:559-572 | kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:880-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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:559` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–17 lines × 3) kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:280— kyo-markdown/shared/src/main/scala/kyo/Markdown.scala:280-296 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:196-206 | kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala:540-556 — before extracting anything, compare `kyo-markdown/shared/src/main/scala/kyo/Markdown.scala` and `kyo-website/jvm/src/main/scala/kyo/website/DocsMarkdownRender.scala` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 256 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–17 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:249— kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:249-265 | kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:317-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:249` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–17 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:527— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:527-539 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1259-1275 — 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–17 lines × 2) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:607— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:607-620 | kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:223-239 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/ShellBackend.scala:223` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17–20 lines × 2) kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:638— kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:638-657 | kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:677-693 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/shared/src/main/scala/kyo/website/WebsiteStyles.scala:638` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 4) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:203— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:203-218 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:233-246 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:436-450 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:472-485 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/CopyExchange.scala:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–24 lines × 2) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:845— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:845-863 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1446-1469 — 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 (1–16 lines × 28) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1235— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1235-1235 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1372-1373 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1514-1515 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1538-1539 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1760-1761 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:1797-1798 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/query/ClasspathOrchestrator.scala:2255-2256 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1107-1108 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:352-353 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:369-369 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1548-1548 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1561-1561 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1592-1593 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:542-542 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:653-653 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:736-736 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:854-855 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:956-970 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala:1031-1046 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotWriter.scala:189-189 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotWriter.scala:207-207 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/symbol/SymbolSignature.scala:87-87 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:132-133 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:161-163 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:175-176 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:214-215 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:238-239 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/type_/Subtyping.scala:257-258 — there are 28 copies across 7 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 28 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (3–16 lines × 3) kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:243— kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:243-245 | kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:364-379 | kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:418-433 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartLower.scala:243` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–16 lines × 2) kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:403— kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:403-418 | kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:440-452 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:439` calls `find`, `getOrElse` and `kyo-website/jvm/src/main/scala/kyo/website/WebsiteGenerator.scala:402` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 4) kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:261— kyo-discord/shared/src/main/scala/kyo/DiscordException.scala:261-275 | kyo-teams/shared/src/main/scala/kyo/TeamsException.scala:255-269 | kyo-telegram/shared/src/main/scala/kyo/TelegramException.scala:265-279 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppException.scala:242-256 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (14–15 lines × 3) kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:175— kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:175-188 | kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:258-272 | kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:321-335 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-jsonrpc/shared/src/main/scala/kyo/JsonRpcRoute.scala:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–15 lines × 3) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:120— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:120-134 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:136-150 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:151-159 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/TypeValidator.scala:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–15 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:51— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:51-65 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:55-64 — 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 (12–15 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:601— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:601-612 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:1137-1151 — 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–15 lines × 2) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:502— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:502-516 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:555-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:555` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–14 lines × 4) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:719— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:719-729 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1004-1017 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:709-719 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:744-754 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:719` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 3) kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:252— kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:252-263 | kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:284-295 | kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:353-366 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:252` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:277` calls `extract`, `appendWithSession`, `Seq` and `kyo-ffi/plugin/src/main/scala/kyo/ffi/sbt/KyoFfiPlugin.scala:250` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:392— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:392-416 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:448-472 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:602-626 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:392` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:473` calls `onRecover` and `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:417` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–13 lines × 2) kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:554— kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:554-566 | kyo-jsonrpc/shared/src/main/scala/kyo/internal/engine/JsonRpcEndpointImpl.scala:775-783 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7–12 lines × 3) kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:531— kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:531-537 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:622-629 | kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:673-684 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/PostgresConnection.scala:531` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–12 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:573— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:573-582 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala:339-350 — 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–12 lines × 2) kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:43— kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:43-54 | kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:133-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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-sql-mysql/shared/src/main/scala/kyo/internal/mysql/types/MysqlTemporalDecoder.scala:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 6) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaAnnotationUnpickler.scala:211— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaAnnotationUnpickler.scala:211-221 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:27-37 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:61-71 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaSignatures.scala:263-273 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:79-90 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TreeUnpickler.scala:1445-1455 — there are 6 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/classfile/JavaAnnotationUnpickler.scala:211` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:205— kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:205-217 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:293-303 | kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:325-335 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-data/jvm-native/src/main/scala/kyo/internal/MpmcUnboundedUnsafeQueue.scala:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (4–11 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:515— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:515-524 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:568-578 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:633-636 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:568` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) REDACTED:186— REDACTED:186-196 | REDACTED:235-244 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–11 lines × 2) kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:304— kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala:304-314 | kyo-tasty/jvm/src/main/scala/kyo/internal/tasty/query/JarCentralDirectory.scala: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 (20 lines × 2) kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:437— kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:437-456 | kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:948-967 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-tasty/shared/src/main/scala/kyo/internal/tasty/snapshot/SnapshotReader.scala:437` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (1–11 lines × 4) kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:147— kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:147-147 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:201-211 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:247-247 | kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:299-309 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-ui/shared/src/main/scala/kyo/internal/ChartScales.scala:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–10 lines × 5) kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:221— kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:221-228 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:238-246 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:261-268 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:389-398 | kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:2037-2045 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/internal/HttpContainerBackend.scala:221` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:105— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:105-113 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:296-305 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:781-789 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1094— kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1094-1102 | kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1165-1174 — 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–10 lines × 2) kyo-pod/shared/src/main/scala/kyo/Container.scala:475— kyo-pod/shared/src/main/scala/kyo/Container.scala:475-484 | kyo-pod/shared/src/main/scala/kyo/Container.scala:597-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-pod/shared/src/main/scala/kyo/Container.scala:475` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 5) kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:980— kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JsEmitter.scala:980-988 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1358-1366 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1370-1378 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1380-1388 | kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/NativeEmitter.scala:1036-1044 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 4) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:312— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:312-320 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:357-365 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:404-412 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:453-461 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:312` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8–9 lines × 4) kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:170— kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:170-177 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:218-226 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:247-254 | kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:295-303 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/internal/Eval.scala:218` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–17 lines × 3) kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:837— kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala:837-853 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala:2453-2468 | kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala:2055-2070 — 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. Note first that the copies are not typed on the same thing: `UpgradeHandoff` names `NioHandle.UpgradeHandoff` in one and `PosixHandle.UpgradeHandoff` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8–9 lines × 3) kyo-parse/shared/src/main/scala/kyo/Parse.scala:506— kyo-parse/shared/src/main/scala/kyo/Parse.scala:506-514 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:545-552 | kyo-parse/shared/src/main/scala/kyo/Parse.scala:587-594 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-parse/shared/src/main/scala/kyo/Parse.scala:506` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-parse/shared/src/main/scala/kyo/Parse.scala:552` calls `s` and `kyo-parse/shared/src/main/scala/kyo/Parse.scala:514` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–9 lines × 2) kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1062— kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1062-1067 | kyo-http/shared/src/main/scala/kyo/internal/server/UnsafeServerDispatch.scala:584-592 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/client/HttpClientBackend.scala:1062` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–17 lines × 2) kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:411— kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:411-427 | kyo-ui/shared/src/main/scala/kyo/internal/ChartMarks.scala:1205-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 (8 lines × 4) kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304— kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304-311 | kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:464-471 | kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:548-555 | kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:720-727 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-website/shared/src/main/scala/kyo/website/LandingApp.scala:304` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (1–7 lines × 6) kyo-core/shared/src/main/scala/kyo/Async.scala:610— kyo-core/shared/src/main/scala/kyo/Async.scala:610-610 | kyo-core/shared/src/main/scala/kyo/Async.scala:626-632 | kyo-core/shared/src/main/scala/kyo/Async.scala:650-655 | kyo-core/shared/src/main/scala/kyo/Async.scala:676-681 | kyo-core/shared/src/main/scala/kyo/Async.scala:704-709 | kyo-core/shared/src/main/scala/kyo/Async.scala:734-739 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-core/shared/src/main/scala/kyo/Async.scala:626` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-core/shared/src/main/scala/kyo/Async.scala:655` calls `s` and `kyo-core/shared/src/main/scala/kyo/Async.scala:632` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 5) kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:977— kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:977-983 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1346-1352 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1415-1421 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:1802-1808 | kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:2049-2055 — 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.
Duplicated block (2–6 lines × 5) kyo-discord/shared/src/main/scala/kyo/Discord.scala:766— kyo-discord/shared/src/main/scala/kyo/Discord.scala:766-767 | kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:132-137 | kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala:151-153 | kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:67-72 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppPath.scala:44-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 9) kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:776— kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:776-780 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:876-880 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1075-1079 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1128-1132 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1155-1159 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1461-1465 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1501-1505 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:1751-1755 | kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:2100-2105 — all 9 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala:776` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 7) kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:306— kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:306-310 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:351-355 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:398-402 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:447-451 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:639-643 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:707-711 | kyo-kernel/shared/src/main/scala/kyo/kernel/Loop.scala:748-752 — 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.
Duplicated block (4–5 lines × 9) kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:184— kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:184-188 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:238-241 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:269-272 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:290-293 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:309-312 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:330-333 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:341-345 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:353-356 | kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:362-365 — all 9 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/HttpFilter.scala:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–5 lines × 3) kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:820— kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:820-824 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:826-828 | kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:832-836 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:826` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:820` calls `buf` and `kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:826` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (4–5 lines × 3) kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:98— kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:98-102 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:134-137 | kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:508-512 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-kernel/shared/src/main/scala/kyo/kernel/ArrowEffect.scala:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (2–5 lines × 5) kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:140— kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:140-141 | kyo-slack/shared/src/main/scala/kyo/SlackConfig.scala:195-199 | kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:35-36 | kyo-telegram/shared/src/main/scala/kyo/TelegramConfig.scala:152-153 | kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppConfig.scala:136-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `UrlProblem` names `DiscordInvalidConfigException.UrlProblem` in one and `SlackInvalidConfigException.UrlProblem` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `kyo-discord/shared/src/main/scala/kyo/DiscordConfig.scala:144` calls `endsWith`, `Present` and `kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala:39` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (30 lines × 4) kyo-data/js-wasm/src/main/scala/kyo/internal/MpmcUnsafeQueue.scala:17— kyo-data/js-wasm/src/main/scala/kyo/internal/MpmcUnsafeQueue.scala:17-46 | kyo-data/js-wasm/src/main/scala/kyo/internal/MpscUnsafeQueue.scala:17-46 | kyo-data/js-wasm/src/main/scala/kyo/internal/SpmcUnsafeQueue.scala:17-46 | kyo-data/js-wasm/src/main/scala/kyo/internal/SpscUnsafeQueue.scala:17-46 — before extracting anything, compare `kyo-data/js-wasm/src/main/scala/kyo/internal/MpscUnsafeQueue.scala` and `kyo-data/js-wasm/src/main/scala/kyo/internal/SpmcUnsafeQueue.scala` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (85 lines × 2) kyo-direct/shared/src/main/scala/kyo/internal/ChunkAsyncShift.scala:12— kyo-direct/shared/src/main/scala/kyo/internal/ChunkAsyncShift.scala:12-96 | kyo-direct/shared/src/main/scala/kyo/internal/ListAsyncShift.scala:13-97 — 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 (19 lines × 3) kyo-net/js-wasm/src/main/scala/kyo/net/internal/backend/IoBackendPlatform.scala:21— kyo-net/js-wasm/src/main/scala/kyo/net/internal/backend/IoBackendPlatform.scala:21-70 | kyo-net/jvm/src/main/scala/kyo/net/internal/backend/IoBackendPlatform.scala:33-51 | kyo-net/native/src/main/scala/kyo/net/internal/backend/IoBackendPlatform.scala:31-49 — 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· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:436— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:436-445 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:191-202 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:211-220 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:208-219 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:228-237 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 2+ corresponding lines) · ×1
Edited copies of one member (4 members, 2+ corresponding lines) kyo-kernel/jvm/src/jmh/resources/fixtures/HandleSites.scala:52— kyo-kernel/jvm/src/jmh/resources/fixtures/HandleSites.scala:52-53 | kyo-kernel/jvm/src/jmh/resources/fixtures/HandleSites.scala:57-58 | kyo-kernel/jvm/src/jmh/resources/fixtures/HandleSites.scala:62-63 | kyo-kernel/jvm/src/jmh/resources/fixtures/HandleSites.scala:67-68 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 2 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 4+ corresponding lines) · ×1
Edited copies of one member (6 members, 4+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:153— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:153-156 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:169-172 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:177-183 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:188-191 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:290-296 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/KernelBench.scala:621-627 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 3+ corresponding lines) · ×1
Edited copies of one member (4 members, 3+ corresponding lines) kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:239— kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:239-242 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/CatsEffectBench.scala:247-250 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:256-259 | kyo-kernel/jvm/src/jmh/scala/kyo/kernel/bench/cross/ZioBench.scala:503-505 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 3 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (8 lines × 12) kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:11— kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:11-18 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:21-28 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:31-38 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:41-48 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:51-58 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:61-68 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:71-78 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:81-88 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:91-98 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:101-108 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:111-118 | kyo-kernel/jvm/src/jmh/resources/fixtures/ForComprehensions.scala:121-128 — all 12 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 × 12) kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:11— kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:11-16 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:19-24 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:27-32 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:35-40 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:43-48 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:51-56 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:59-64 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:67-72 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:75-80 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:83-88 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:91-96 | kyo-kernel/jvm/src/jmh/resources/fixtures/NestedMaps.scala:99-104 — all 12 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.
Outbound HTTP without resilience kyo-ffi/jvm/src/main/scala/kyo/ffi/internal/NativeManifestPlatform.scala:71— `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Type Safety — 0 typed · 5 plain JS — the untyped files are kyo-browser/shared/src/main/resources/kyo/Readability.js, REDACTED, kyo-charset/shared/src/test/vectors/wpt-encoding/gb18030-decoder.any.js, kyo-charset/shared/src/test/vectors/wpt-encoding/iso-2022-jp-decoder.any.js, kyo-discord/shared/src/test/spacebar/tls-proxy.js.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) REDACTED:223— REDACTED:223 · REDACTED:241 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 2 locations) kyo-browser/shared/src/main/resources/kyo/Readability.js:2150— kyo-browser/shared/src/main/resources/kyo/Readability.js:2150 · kyo-browser/shared/src/main/resources/kyo/Readability.js:2161 — 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 locations) kyo-browser/shared/src/main/resources/kyo/Readability.js:2243— kyo-browser/shared/src/main/resources/kyo/Readability.js:2243 · kyo-browser/shared/src/main/resources/kyo/Readability.js:2253 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function _grabArticle (cyclomatic 103, cognitive 232) kyo-browser/shared/src/main/resources/kyo/Readability.js:1031— _grabArticle has cyclomatic complexity 103 and cognitive complexity 232; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 32, cognitive 46) kyo-browser/shared/src/main/resources/kyo/Readability.js:1637— (anonymous) has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function shouldRemoveNode (cyclomatic 25, cognitive 19) kyo-browser/shared/src/main/resources/kyo/Readability.js:2555— shouldRemoveNode has cyclomatic complexity 25 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 35) kyo-browser/shared/src/main/resources/kyo/Readability.js:2335— (anonymous) has cyclomatic complexity 24 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 22, cognitive 38) kyo-browser/shared/src/main/resources/kyo/Readability.js:2444— (anonymous) has cyclomatic complexity 22 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collapseWhitespace (cyclomatic 21, cognitive 31) REDACTED:456— collapseWhitespace has cyclomatic complexity 21 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _getArticleTitle (cyclomatic 15, cognitive 19) kyo-browser/shared/src/main/resources/kyo/Readability.js:572— _getArticleTitle has cyclomatic complexity 15 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Readability (cyclomatic 14, cognitive 14) kyo-browser/shared/src/main/resources/kyo/Readability.js:27— Readability has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _markDataTables (cyclomatic 13, cognitive 20) kyo-browser/shared/src/main/resources/kyo/Readability.js:2271— _markDataTables has cyclomatic complexity 13 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 22) kyo-browser/shared/src/main/resources/kyo/Readability.js:1917— (anonymous) has cyclomatic complexity 12 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 21) kyo-browser/shared/src/main/resources/kyo/Readability.js:697— (anonymous) has cyclomatic complexity 12 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· kyo-browser/shared/src/main/resources/kyo/Readability.js · ×1
kyo-browser/shared/src/main/resources/kyo/Readability.js: 2496 lines of code kyo-browser/shared/src/main/resources/kyo/Readability.js:1— kyo-browser/shared/src/main/resources/kyo/Readability.js has 2496 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 825 lines of code REDACTED:1— REDACTED has 825 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No test or lint script — test ✗ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Duplicated predicate kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala:1236— `!method.blocking && method.hasArrayParam` appears character-identically in 2 files — kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/JvmEmitter.scala, kyo-ffi/codegen/src/main/scala/kyo/ffi/codegen/emitters/ReachabilityMetadataEmitter.scala. 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 kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala:230— `!sym.isClassDef || !sym.flags.is(Flags.Case)` appears character-identically in 4 files — kyo-data/shared/src/main/scala/kyo/internal/FieldsMacros.scala, kyo-schema/shared/src/main/scala/kyo/internal/BuilderMacro.scala, kyo-schema/shared/src/main/scala/kyo/internal/FocusMacro.scala, kyo-schema/shared/src/main/scala/kyo/internal/SchemaTransformMacro.scala. 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 project/TestVectorsGen.scala:40— `!target.exists || IO.read(target, StandardCharsets.UTF_8) != source` appears character-identically in 2 files — project/TestVectorsGen.scala, project/UnicodeTablesGen.scala. 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 kyo-mime/shared/src/main/scala/kyo/internal/mime/Grammar.scala:31— `(c >= '0' && c <= '9') || (c >= 'a' && c <= 'f') || (c >= 'A' && c <= 'F')` appears character-identically in 3 files — kyo-mime/shared/src/main/scala/kyo/internal/mime/Grammar.scala, kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala, kyo-ui/shared/src/main/scala/kyo/Style.scala. 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 kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala:131— `(c >= 'A' && c <= 'Z') || (c >= 'a' && c <= 'z') || (c >= '0' && c <= '9') || c == '-' || c == '.' || c == '_' || c == '~'` appears character-identically in 3 files — kyo-discord/shared/src/main/scala/kyo/internal/discord/Rest.scala, kyo-slack/shared/src/main/scala/kyo/internal/slack/WebApi.scala, kyo-teams/shared/src/main/scala/kyo/internal/teams/ServiceUrls.scala. 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 kyo-slack/shared/src/main/scala/kyo/SlackMethod.scala:35— `(c >= 'a' && c <= 'z') || (c >= 'A' && c <= 'Z') || (c >= '0' && c <= '9') || c == '.' || c == '_'` appears character-identically in 2 files — kyo-slack/shared/src/main/scala/kyo/SlackMethod.scala, kyo-telegram/shared/src/main/scala/kyo/Telegram.scala. 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 kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala:188— `(c >= 'a' && c <= 'z') || (c >= 'A' && c <= 'Z') || (c >= '0' && c <= '9') || c == '.' || c == '_' || c == '-'` appears character-identically in 2 files — kyo-telegram/shared/src/main/scala/kyo/internal/telegram/BotApi.scala, kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppMedia.scala. 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 kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala:914— `(c >= 'a' && c <= 'z') || (c >= 'A' && c <= 'Z') || c == '_' || c == '$'` appears character-identically in 2 files — kyo-schema-ion/shared/src/main/scala/kyo/internal/IonReader.scala, kyo-schema-ion/shared/src/main/scala/kyo/internal/IonWriter.scala. 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 kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala:1170— `(tag >= 1 && tag <= 59) || tag == TastyFormat.PRIVATEqualified || tag == TastyFormat.PROTECTEDqualified || tag == TastyFormat.ANNOTATION` appears character-identically in 2 files — kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/AstUnpickler.scala, kyo-tasty/shared/src/main/scala/kyo/internal/tasty/reader/TypeUnpickler.scala. 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 kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala:135— `Character.isHighSurrogate(text.charAt(i)) && i + 1 < text.length && Character.isLowSurrogate(text.charAt(i + 1))` appears character-identically in 2 files — kyo-charset/shared/src/main/scala/kyo/internal/charset/Utf8.scala, kyo-mime/shared/src/main/scala/kyo/internal/mime/Utf8.scala. 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 kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:713— `acc > 214748364 || (acc == 214748364 && digit > 7)` appears character-identically in 2 files — kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala, kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala. 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 kyo-data/shared/src/main/scala/kyo/internal/DeclaredBounds.scala:79— `args.nonEmpty && lambda.paramNames.size == args.size` appears character-identically in 2 files — kyo-data/shared/src/main/scala/kyo/internal/DeclaredBounds.scala, kyo-data/shared/src/main/scala/kyo/internal/TagMacro.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:900— `attrs.onDragEnd.nonEmpty || attrs.onDragEndEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:899— `attrs.onDragStart.nonEmpty || attrs.onDragStartEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:904— `attrs.onDrop.nonEmpty || attrs.onDropEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:896— `attrs.onHover.nonEmpty || attrs.onHoverEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:898— `attrs.onScroll.nonEmpty || attrs.onScrollEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:905— `attrs.onSortMove.nonEmpty || attrs.onSortMoveEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala:897— `attrs.onUnhover.nonEmpty || attrs.onUnhoverEvt.nonEmpty` appears character-identically in 2 files — kyo-ui/shared/src/main/scala/kyo/internal/HtmlRenderer.scala, kyo-ui/shared/src/main/scala/kyo/internal/ReactiveUI.scala. 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 kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala:191— `b == ' ' || b == '\t' || b == '\n' || b == '\r'` appears character-identically in 2 files — kyo-schema-json/shared/src/main/scala/kyo/internal/JsonReader.scala, kyo-system/shared/src/main/scala/kyo/Path.scala. 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 kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:91— `bodyLength == 0 || out.charAt(out.length - 1) != '\n'` appears character-identically in 2 files — kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala, kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala. 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 kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala:786— `buf(i) == b1.toByte && buf(i + 1) == b2.toByte` appears character-identically in 2 files — kyo-http/shared/src/main/scala/kyo/internal/http1/Http1Parser.scala, kyo-http/shared/src/main/scala/kyo/internal/http1/Http1ResponseParser.scala. 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 kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala:806— `c < ' ' || c == '\n' || c == '\r' || c == '\t'` appears character-identically in 2 files — kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlEvents.scala, kyo-schema-yaml/shared/src/main/scala/kyo/internal/yaml/YamlWriter.scala. 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 kyo-discord/shared/src/main/scala/kyo/DiscordWebhookConfig.scala:25— `c <= ' ' || c > '~' || c == '?' || c == '#'` appears character-identically in 4 files — kyo-discord/shared/src/main/scala/kyo/DiscordWebhookConfig.scala, kyo-teams/shared/src/main/scala/kyo/TeamsWebhookConfig.scala, kyo-telegram/shared/src/main/scala/kyo/TelegramWebhookConfig.scala, kyo-whatsapp/shared/src/main/scala/kyo/WhatsAppWebhookConfig.scala. 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 kyo-email/shared/src/main/scala/kyo/Email.scala:355— `c > ' ' && c < '\u007f' && "(){%*\"\\]".indexOf(c.toInt) < 0` appears character-identically in 2 files — kyo-email/shared/src/main/scala/kyo/Email.scala, kyo-email/shared/src/main/scala/kyo/internal/email/imap/ImapCodec.scala. 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.
Disabled test kyo-core/shared/src/test/scala/kyo/ChannelTest.scala:174— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-core/shared/src/test/scala/kyo/ChannelTest.scala:220— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-core/shared/src/test/scala/kyo/ScopeTest.scala:1614— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-http/shared/src/test/scala/kyo/internal/WebSocketCodecTest.scala:247— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-tasty/shared/src/test/scala/kyo/SnapshotParamListsRoundTripTest.scala:240— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/IgnoreDecoratorTest.scala:35— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/IgnoreDecoratorTest.scala:51— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/IgnoreDecoratorTest.scala:67— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/IgnoreDecoratorTest.scala:89— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/TestBaseTest.scala:217— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/api/shared/src/test/scala/kyo/test/TestBaseTest.scala:232— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/runner/shared/src/test/scala/kyo/LiveCoverageTest.scala:163— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-test/runner/shared/src/test/scala/kyo/LiveCoverageTest.scala:171— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-ui/shared/src/test/scala/kyo/internal/ReactiveUITeardownTest.scala:120— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test kyo-ui/shared/src/test/scala/kyo/internal/ReactiveUITeardownTest.scala:345— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:50— `trace` at line 50 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.trace("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:53— `trace` at line 53 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.trace("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:56— `debug` at line 56 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:59— `debug` at line 59 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:62— `info` at line 62 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:65— `info` at line 65 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:68— `warn` at line 68 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:71— `warn` at line 71 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:74— `error` at line 74 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Interpolated log message defeats structured logging kyo-logging-slf4j/jvm/src/main/scala/kyo/SLF4JLog.scala:77— `error` at line 77 is handed an interpolated string as its message through SLF4J, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. scala-logging's `LazyLogging` logger takes an `s"…"` message apart into that pattern at compile time, so switching to it is also a fix.
Orphaned file kyo-prelude/shared/src/main/scala/kyo/Sink.scala: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 kyo-bench/src/main/scala/kyo/bench/ChunkBench.scala: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 kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala: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 kyo-bench/src/main/scala/kyo/bench/ParseBench.scala: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 project/TestVariant.scala: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 kyo-combinators/shared/src/main/scala/kyo/EmitCombinators.scala: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 kyo-direct/shared/src/main/scala/kyo/internal/ChunkAsyncShift.scala: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 kyo-direct/shared/src/main/scala/kyo/internal/ListAsyncShift.scala: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 kyo-core/jvm/src/main/scala/kyo/internal/OSSignalPlatformSpecific.scala: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.
IC1 · Incompleteness & stubs· Empty method body · ×7
Empty method body kyo-core/js-wasm/src/main/scala/kyo/scheduler/SchedulerDiagnostics.scala:8— `init` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-data/shared/src/main/scala/kyo/Fields.scala:171— `unsafe` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-data/shared/src/main/scala/kyo/Fields.scala:184— `unsafe` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-ffi/it/jvm/src/main/scala/kyo/ffi/it/SystemLibraryImpl.scala:9— `ensureInitialized` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-ffi/it/native/src/main/scala/kyo/ffi/it/SystemLibraryImpl.scala:8— `ensureInitialized` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-ffi/js-wasm/src/main/scala/kyo/ffi/internal/GuardDrainSupport.scala:11— `onSpinWait` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body kyo-scheduler/js-wasm/src/main/scala/kyo/scheduler/InternalClock.scala:17— `stop` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 300 significant file(s) lose their only recent owner: kyo-browser/shared/src/main/scala/kyo/Browser.scala, kyo-net/shared/src/main/scala/kyo/net/internal/posix/PollerIoDriver.scala, kyo-net/shared/src/main/scala/kyo/net/internal/posix/IoUringDriver.scala, kyo-net/shared/src/main/scala/kyo/net/internal/posix/PosixTransport.scala, kyo-sql/shared/src/main/scala/kyo/Sql.scala, kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala, kyo-lsp/shared/src/main/scala/kyo/LspHandler.scala, kyo-net/jvm/src/main/scala/kyo/net/internal/NioIoDriver.scala (+292 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: kyo-data/shared/src/main/scala/kyo/Glob.scala, kyo-system/shared/src/main/scala/kyo/HostFileSystem.scala, kyo-system/shared/src/main/scala/kyo/FileSystem.scala, kyo-data/shared/src/main/scala/kyo/ByteSize.scala. Pair on, review, or document these before any departure.
D21 · Naming Consistency· `MySQL` spells `SQL` where 18 names in the project spell it `Sql` · ×2
`MySQL` spells `SQL` where 18 names in the project spell it `Sql` kyo-pod/shared/src/main/scala/kyo/ContainerPredef.scala:346— 18 of 20 names in project repository spell the token `Sql` (18 of 20; unit: names in project repository containing `Sql`). Peers: SqlConformanceBackend.tableNotFoundSqlState (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:240); SqlConformanceBackend.uniqueViolationSqlState (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:243); SqlConformanceBackend.sessionIdSql (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:251); SqlConformanceBackend.isolationIntrospectionSql (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:271); SqlRunConformanceTest.assertRunUsesPinnedConnection(sessionIdSql) (kyo-sql-conformance/shared/src/main/scala/kyo/SqlRunConformanceTest.scala:55). Rename to `MySql`. [rule N6]
`MySQL` spells `SQL` where 18 names in the project spell it `Sql` kyo-pod/shared/src/main/scala/kyo/ContainerPredef.scala:388— 18 of 20 names in project repository spell the token `Sql` (18 of 20; unit: names in project repository containing `Sql`). Peers: SqlConformanceBackend.tableNotFoundSqlState (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:240); SqlConformanceBackend.uniqueViolationSqlState (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:243); SqlConformanceBackend.sessionIdSql (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:251); SqlConformanceBackend.isolationIntrospectionSql (kyo-sql-conformance/shared/src/main/scala/kyo/SqlConformanceBackend.scala:271); SqlRunConformanceTest.assertRunUsesPinnedConnection(sessionIdSql) (kyo-sql-conformance/shared/src/main/scala/kyo/SqlRunConformanceTest.scala:55). Rename to `MySql`. [rule N6]
redundant comment kyo-browser/shared/src/main/resources/kyo/Readability.js:2525— "For embed with <object> tag, check inner HTML as well." repeats the code it sits on: 6 of its 7 words (embed, object, tag, check, inner, html) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment kyo-browser/shared/src/main/resources/kyo/Readability.js:2732— "Unwrap image from noscript" repeats the code it sits on: 3 of its 3 words (unwrap, image, noscript) are already in `this._unwrapNoscriptImages(this._doc);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Method throws UnsupportedOperationException kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:49— `mmapReadOnly`'s body only throws UnsupportedOperationException — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Method throws UnsupportedOperationException kyo-data/js-wasm/src/main/scala/kyo/internal/UnsafeBufferPlatform.scala:52— `mmapReadWrite`'s body only throws UnsupportedOperationException — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Blanket warning suppression kyo-scheduler/js-wasm/src/main/scala/kyo/scheduler/InternalClock.scala:12— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Blanket warning suppression kyo-scheduler/jvm/src/main/scala/kyo/scheduler/top/Console.scala:5— A bare `// scalastyle:off`, `// scalafix:off` or `@nowarn` (or Wartremover's `warts.All`) switches every rule or warning off — hidden debt. Suppress the specific rule on the specific line, with a justification, instead.
Silent fallback default in catch kyo-core/shared/src/main/scala/kyo/scheduler/IOTask.scala:223— `fiberTrace` swallows every exception into `""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch case or in the Scaladoc, and the row stops firing.
Silent fallback default in catch kyo-sql/shared/src/main/scala/kyo/internal/FromExprDerived.scala:592— `safeCaseFields` (in `resolveBindings`) swallows every exception into `Nil` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch case or in the Scaladoc, and the row stops firing.
D21 · Naming Consistency· `InitSSLExchange` spells `SSL` where 18 names in the project spell it `Ssl` · ×1
`InitSSLExchange` spells `SSL` where 18 names in the project spell it `Ssl` kyo-sql-postgres/shared/src/main/scala/kyo/internal/postgres/exchange/InitSSLExchange.scala:27— 18 of 19 names in project repository spell the token `Ssl` (18 of 19; unit: names in project repository containing `Ssl`). Peers: kyo.net.internal.JdkSslEngine (kyo-net/jvm/src/main/scala/kyo/net/internal/JdkSslEngine.scala:32); kyo.net.internal.JdkSslEngine (kyo-net/jvm/src/main/scala/kyo/net/internal/JdkSslEngine.scala:297); NioTransport.createSslContext (kyo-net/jvm/src/main/scala/kyo/net/internal/NioTransport.scala:1694); kyo.net.internal.BoringSslBindings (kyo-net/shared/src/main/scala/kyo/net/internal/BoringSslBindings.scala:22); kyo.net.internal.BoringSslBindings (kyo-net/shared/src/main/scala/kyo/net/internal/BoringSslBindings.scala:49). Rename to `InitSslExchange`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (373368 LoC, 6980 module-visible types across 251 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
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 9 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: kyo-prelude/shared/src/main/scala/kyo/Sink.scala, kyo-bench/src/main/scala/kyo/bench/ChunkBench.scala, kyo-bench/src/main/scala/kyo/bench/TypeMapBench.scala, kyo-bench/src/main/scala/kyo/bench/ParseBench.scala, project/TestVariant.scala, kyo-combinators/shared/src/main/scala/kyo/EmitCombinators.scala, kyo-direct/shared/src/main/scala/kyo/internal/ChunkAsyncShift.scala, kyo-direct/shared/src/main/scala/kyo/internal/ListAsyncShift.scala (and 1 more) (11 orphaned of 1092 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; 1092 of the 1726 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.
No SAST REDACTED:16— No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 8 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling· Dependabot does not watch npm/gitsubmodule · ×1
Dependabot does not watch npm/gitsubmodule REDACTED:7— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
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.)
X5 · Nullable reference types· Scala's null is not held to the type system everywhere · ×1
Scala's null is not held to the type system everywhere — No build over this repository's 1700 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Outdated: com.github.ghostdogpr:caliban_2.12 — `com.github.ghostdogpr %% caliban_2.12` is declared at 3.1.5 in build.sbt, but 3.2.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.1.5 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core_2.12 — `com.github.plokhotnyuk.jsoniter-scala %% jsoniter-scala-core_2.12` is declared at 2.40.1 in build.sbt, but 2.43.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.40.1 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:izumi-reflect_2.12 — `dev.zio %% izumi-reflect_2.12` is declared at 3.0.10 in build.sbt, but 3.0.11 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.0.10 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-concurrent_2.12 — `dev.zio %% zio-concurrent_2.12` is declared at 2.1.26 in build.sbt, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.1.26 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-json_2.12 — `dev.zio %% zio-json_2.12` is declared at 1.1.0 in build.sbt, but 1.1.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.1.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-logging-slf4j2_2.12 — `dev.zio %% zio-logging-slf4j2_2.12` is declared at 2.5.3 in build.sbt, but 2.5.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.3 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-logging_2.12 — `dev.zio %% zio-logging_2.12` is declared at 2.5.3 in build.sbt, but 2.5.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.3 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-parser_2.12 — `dev.zio %% zio-parser_2.12` is declared at 0.1.11 in build.sbt, but 0.1.12 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.1.11 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio-query_2.12 — `dev.zio %% zio-query_2.12` is declared at 0.7.8 in build.sbt, but 0.7.9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.7.8 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: dev.zio:zio_2.12 — `dev.zio %% zio_2.12` is declared at 2.1.26 in build.sbt, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.1.26 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.circe:circe-core_2.12 — `io.circe %% circe-core_2.12` is declared at 0.14.16 in build.sbt, but 0.14.17 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.14.16 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.circe:circe-generic_2.12 — `io.circe %% circe-generic_2.12` is declared at 0.14.16 in build.sbt, but 0.14.17 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.14.16 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.circe:circe-parser_2.12 — `io.circe %% circe-parser_2.12` is declared at 0.14.16 in build.sbt, but 0.14.17 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.14.16 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.vertx:vertx-core — `io.vertx %% vertx-core` is declared at 5.2.0 in build.sbt, but 5.2.3 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 5.2.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: io.vertx:vertx-web — `io.vertx %% vertx-web` is declared at 5.2.0 in build.sbt, but 5.2.3 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 5.2.0 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.http4s:http4s-dsl_2.12 — `org.http4s %% http4s-dsl_2.12` is declared at 1.0.0-M48 in build.sbt, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.0-M48 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.http4s:http4s-ember-client_2.12 — `org.http4s %% http4s-ember-client_2.12` is declared at 1.0.0-M48 in build.sbt, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.0-M48 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.http4s:http4s-ember-server_2.12 — `org.http4s %% http4s-ember-server_2.12` is declared at 1.0.0-M48 in build.sbt, but 1.0-4-a7fc4a9 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.0-M48 until the declaration is edited — there is no lockfile refresh that would move it.
Outdated: org.slf4j:slf4j-api — `org.slf4j %% slf4j-api` is declared at 2.0.19 in build.sbt, but 2.0.20 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.0.19 until the declaration is edited — there is no lockfile refresh that would move it.
doc comments repeat the names kyo-browser/shared/src/main/resources/kyo/Readability.js:25— 7 of 61 documented parameters and 2 of 59 summaries in `.` only repeat the member or parameter name (e.g. "The options object." for `options`). 18 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
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.
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. semgrep could not parse 751 file(s) — `kyo-actor/shared/src/main/scala/kyo/Actor.scala`, `kyo-actor/shared/src/main/scala/kyo/PubSub.scala`, `kyo-aeron/shared/src/main/scala/kyo/AeronDriver.scala`, `kyo-aeron/shared/src/main/scala/kyo/Topic.scala`, `kyo-ai/shared/src/main/scala/kyo/AI.scala`, … (+746 more) — so the PII/GDPR sweep did not cover them at all.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a1da94-c7b1-7b18-8671-37c0742a6893 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 112 · Warnings: 2393 · Recommendations: 103 · Info: 20 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 15:02 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.