Public report of SeaQL/sea-orm, 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, 16:41 UTC · Survey ID cd_ed8d22a417724be59367fdfd60f5a976
SeaQL/sea-orm
Measured 14 November 2026, 16:35 UTC, at code version 1d4b138
CAI scoreAt riskUp 4 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: 111,166 lines of product code in 29 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Security and Compliance, 57
Findings by how serious they are
125 critical1020 serious90 minor
21 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, 16:35 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
50of 50 dimensions measured by tools.
1199of 1235 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
50dimensions across 7 lenses, read from 111,166 lines of product code in 29 projects.
SeaQL/sea-orm is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 64 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 57, is the weakest lens and counts most in the score. The best first step for the work it takes is adding tests for untested code, worth about 3 points. Serving traffic only over an encrypted connection would lift Security and Compliance itself, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 67.
Seventy pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fifty-two known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 111,166 lines, about €190,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 Security and Compliance rose from 57 to 70, the lowest score rated Strong, the score would rise from 64 to about 67.
Code composition: what the lines of code are
Product code 66%Tests 34%
New since the last survey: 407 findings
These 407 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 · MethodTooLong: DeriveActiveModel.impl_from_json sea-orm-macros/src/derives/active_model.rs
Code Duplication · Near-duplicate member family (6 members, 16 shared lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Near-duplicate member family (4 members, 54 shared lines) sea-orm-sync/src/database/stream/query.rs
Code Duplication · Near-duplicate member family (4 members, 17 shared lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Near-duplicate member pair (133 shared lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Near-duplicate member pair (33 shared lines) sea-orm-macros/src/derives/entity_loader.rs
Code Duplication · Edited copy of a member (33 corresponding lines) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) sea-orm-macros/src/derives/active_model_ex.rs
Code Duplication · Edited copy of a member (127 corresponding lines) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Edited copy of a member (93 corresponding lines) sea-orm-sync/src/driver/sqlx_postgres.rs
Code Duplication · Edited copy of a member (84 corresponding lines) sea-orm-sync/src/database/transaction.rs
Code Duplication · Edited copy of a member (52 corresponding lines) sea-orm-sync/src/database/db_connection.rs
Code Duplication · Edited copy of a member (37 corresponding lines) sea-orm-arrow/src/lib.rs
Code Duplication · Edited copy of a member (45 corresponding lines) sea-orm-sync/src/executor/insert.rs
Code Duplication · Edited copies of one member (4 members, 58+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Edited copy of a member (40 corresponding lines) sea-orm-migration/src/migrator/exec.rs
Code Duplication · Edited copy of a member (36 corresponding lines) sea-orm-sync/src/database/mod.rs
Code Duplication · Edited copy of a member (49 corresponding lines) sea-orm-macros/src/derives/entity_loader.rs
Code Duplication · Edited copies of one member (4 members, 33+ corresponding lines) sea-orm-sync/src/database/db_connection.rs
Code Duplication · Edited copy of a member (33 corresponding lines) sea-orm-sync/src/executor/update.rs
Code Duplication · Edited copy of a member (32 corresponding lines) sea-orm-sync/src/rbac/context.rs
Code Duplication · Edited copy of a member (35 corresponding lines) sea-orm-sync/src/rbac/context.rs
Code Duplication · Edited copy of a member (28 corresponding lines) sea-orm-arrow/src/lib.rs
Code Duplication · Edited copy of a member (22 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Edited copy of a member (22 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Edited copies of one member (6 members, 21+ corresponding lines) sea-orm-sync/src/database/db_connection.rs
Code Duplication · Edited copies of one member (8 members, 25+ corresponding lines) sea-orm-sync/src/database/db_connection.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Edited copy of a member (20 corresponding lines) sea-orm-arrow/src/lib.rs
Code Duplication · Edited copy of a member (31 corresponding lines) sea-orm-sync/src/rbac/context.rs
Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) sea-orm-migration/src/manager.rs
Code Duplication · Edited copy of a member (24 corresponding lines) sea-orm-sync/src/executor/insert.rs
Code Duplication · Edited copy of a member (16 corresponding lines) sea-orm-sync/src/driver/mock.rs
Code Duplication · Edited copy of a member (23 corresponding lines) sea-orm-sync/src/executor/update.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-macros/src/derives/entity_loader.rs
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) src/database/db_connection.rs
Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) sea-orm-sync/src/database/db_connection.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-sync/src/rbac/context.rs
Code Duplication · Edited copy of a member (17 corresponding lines) sea-orm-sync/src/executor/update.rs
Code Duplication · Edited copy of a member (19 corresponding lines) sea-orm-arrow/src/lib.rs
Code Duplication · Edited copy of a member (27 corresponding lines) sea-orm-sync/src/driver/sqlx_common.rs
Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) sea-orm-sync/src/executor/cursor.rs
Code Duplication · Edited copy of a member (7 corresponding lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Edited copy of a member (14 corresponding lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Edited copy of a member (15 corresponding lines) sea-orm-migration/src/migrator/queries.rs
Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) sea-orm-sync/src/executor/paginator.rs
Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/entity/relation.rs
Code Duplication · Edited copy of a member (16 corresponding lines) sea-orm-sync/src/rbac/schema.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Edited copy of a member (17 corresponding lines) sea-orm-arrow/src/lib.rs
Code Duplication · Edited copy of a member (7 corresponding lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Edited copies of one member (5 members, 18+ corresponding lines) sea-orm-sync/src/rbac/context.rs
Code Duplication · Edited copy of a member (13 corresponding lines) sea-orm-sync/src/database/transaction.rs
Code Duplication · Edited copy of a member (15 corresponding lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) sea-orm-sync/src/database/sea_schema_shim.rs
Code Duplication · Edited copy of a member (16 corresponding lines) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Edited copy of a member (15 corresponding lines) sea-orm-sync/src/executor/paginator.rs
Code Duplication · Edited copy of a member (12 corresponding lines) sea-orm-sync/src/driver/proxy.rs
Code Duplication · Edited copy of a member (9 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) src/executor/insert.rs
Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) sea-orm-sync/src/executor/insert.rs
Code Duplication · Edited copy of a member (12 corresponding lines) sea-orm-sync/src/executor/update.rs
Code Duplication · Edited copy of a member (13 corresponding lines) sea-orm-macros/src/derives/value_type_match.rs
Code Duplication · Edited copy of a member (14 corresponding lines) sea-orm-sync/src/executor/insert.rs
Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) sea-orm-sync/src/executor/select.rs
Code Duplication · Edited copy of a member (9 corresponding lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-codegen/src/entity/writer/dense.rs
Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) sea-orm-macros/src/derives/active_enum_display.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/query/helper.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/query/helper.rs
Code Duplication · Edited copy of a member (9 corresponding lines) sea-orm-sync/src/database/tracing_spans.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/entity/active_value.rs
Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) sea-orm-sync/src/entity/column.rs
Code Duplication · Edited copy of a member (9 corresponding lines) sea-orm-sync/src/value/text_uuid.rs
Code Duplication · Edited copies of one member (6 members, 12+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/entity/relation.rs
Code Duplication · Edited copy of a member (7 corresponding lines) sea-orm-sync/src/schema/entity.rs
Code Duplication · Edited copy of a member (13 corresponding lines) sea-orm-sync/src/database/executor.rs
Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) sea-orm-sync/src/entity/active_model_ex.rs
Code Duplication · Edited copy of a member (7 corresponding lines) sea-orm-sync/src/value/text_uuid.rs
Code Duplication · Edited copy of a member (9 corresponding lines) sea-orm-codegen/src/entity/writer.rs
Code Duplication · Edited copy of a member (17 corresponding lines) sea-orm-macros/src/lib.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/database/transaction.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/database/executor.rs
Code Duplication · Edited copy of a member (11 corresponding lines) sea-orm-sync/src/driver/proxy.rs
Code Duplication · Edited copy of a member (7 corresponding lines) src/entity/active_model.rs
Code Duplication · Edited copy of a member (8 corresponding lines) sea-orm-sync/src/executor/insert.rs
Code Duplication · Edited copy of a member (5 corresponding lines) src/entity/active_model.rs
Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) sea-orm-sync/src/dynamic/execute.rs
Code Duplication · Edited copy of a member (11 corresponding lines) sea-orm-migration/src/migrator.rs
Code Duplication · Edited copies of one member (6 members, 6+ corresponding lines) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Edited copy of a member (10 corresponding lines) issues/262/src/main.rs
Code Duplication · Edited copy of a member (4 corresponding lines) sea-orm-sync/src/executor/select.rs
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.
Code Duplication · Near-duplicate member family (6 members, 16 shared lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Near-duplicate member family (4 members, 16 shared lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Near-duplicate member pair (131 shared lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Near-duplicate member pair (42 shared lines) sea-orm-sync/src/schema/json.rs
Code Duplication · Near-duplicate member pair (38 shared lines) sea-orm-sync/src/executor/cursor.rs
Code Duplication · Near-duplicate member pair (33 shared lines) sea-orm-macros/src/derives/entity_loader.rs
Code Duplication · Near-duplicate member pair (28 shared lines) sea-orm-sync/src/executor/cursor.rs
Code Duplication · Edited copy of a member (529 corresponding lines) sea-orm-sync/src/driver/sqlx_postgres.rs
Code Duplication · Edited copy of a member (155 corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Edited copy of a member (85 corresponding lines) sea-orm-sync/src/dynamic/model.rs
Code Duplication · Edited copy of a member (97 corresponding lines) sea-orm-sync/src/driver/sqlx_sqlite.rs
Code Duplication · Edited copy of a member (53 corresponding lines) sea-orm-sync/src/executor/query.rs
Code Duplication · Edited copy of a member (50 corresponding lines) sea-orm-sync/src/schema/entity.rs
Code Duplication · Edited copy of a member (49 corresponding lines) sea-orm-sync/src/executor/consolidate.rs
Code Duplication · Edited copy of a member (33 corresponding lines) sea-orm-sync/src/rbac/engine/mod.rs
Code Duplication · Edited copy of a member (35 corresponding lines) sea-orm-sync/src/query/combine.rs
Code Duplication · Edited copy of a member (19 corresponding lines) sea-orm-sync/src/query/loader.rs
Code Duplication · Edited copy of a member (21 corresponding lines) sea-orm-sync/src/schema/builder.rs
Code Duplication · Edited copy of a member (33 corresponding lines) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) sea-orm-sync/src/driver/rusqlite.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) sea-orm-sync/src/driver/sqlx_mysql.rs
Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) sea-orm-sync/src/entity/active_model.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) sea-orm-macros/src/derives/active_model_ex.rs
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) sea-orm-sync/src/database/stream/query.rs
€65,000 to €320,000, for 1,078 to 3,420 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.9 at a score of 64. 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: 111,166 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
Resolve the 94 Low coverage finding(s) in Code Coverage — start with users.rs (3), model.rs (3), lib.rs (2).
Raises the score by about 3 points · Medium effort · Code Coverage
2
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Files that change often carry extra risk · Combined risk
One file is changed often and is hard to read, which makes it the likeliest place for a mistake. It also has under half its code tested, or was written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to this file therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (2 files) · Code Coverage (78 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: entity_model.rs
What to do: Add tests to these files and have a second person review every change to them, starting with entity_model.rs.
Where the investment is most exposed · Value at risk
This code would cost about €190,000 to build again, about 1.3 person-years of work. Its weakest lens is Security and Compliance, at 57 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 94 Low coverage finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort, because it clears the 94 Code Coverage findings. 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 5.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 12% on every change. The history of the code shows how much it changes: about 10,320 lines over the last 90 days, which is about 41,853 lines a year. At that pace, the extra work comes to an estimated 5.6 to 33.8 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.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
313 modules, with 491 dependencies between them. 5 loops run through 61 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 273 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
sea_orm.database.statement uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm.database.statement, while a change to sea_orm.database.statement can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm.database.statement uses a module listed above it, which is the healthy direction.
9→35 sea_orm.query.helper uses sea_orm.entity.relationpart of a loop✕
Connections
1 pair of types, where a type in sea_orm.query.helper uses a type in sea_orm.entity.relation.
sea_orm.query.helper uses sea_orm.entity.relation, so a change to sea_orm.entity.relation can break sea_orm.query.helper, while a change to sea_orm.query.helper can't break sea_orm.entity.relation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.database.statement uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm_sync.database.statement, while a change to sea_orm_sync.database.statement can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm_sync.database.statement uses a module listed above it, which is the healthy direction.
sea_orm.database.connection uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.database.connection, while a change to sea_orm.database.connection can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.database.connection uses a module listed above it, which is the healthy direction.
sea_orm.database.connection uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm.database.connection, while a change to sea_orm.database.connection can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm.database.connection uses a module listed above it, which is the healthy direction.
sea_orm.database.connection uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.connection, while a change to sea_orm.database.connection can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.connection uses a module listed above it, which is the healthy direction.
sea_orm.executor.select uses sea_orm.error, so a change to sea_orm.error can break sea_orm.executor.select, while a change to sea_orm.executor.select can't break sea_orm.error.
Position
Below the diagonal: sea_orm.executor.select uses a module listed above it, which is the healthy direction.
sea_orm.executor.select uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.executor.select, while a change to sea_orm.executor.select can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.executor.select uses a module listed above it, which is the healthy direction.
12→21 sea_orm.executor.select uses sea_orm.executor.querypart of a loop✕
Connections
10 pairs of types, where a type in sea_orm.executor.select uses a type in sea_orm.executor.query.
sea_orm.executor.select uses sea_orm.executor.query, so a change to sea_orm.executor.query can break sea_orm.executor.select, while a change to sea_orm.executor.select can't break sea_orm.executor.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.database.connection uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm_sync.database.connection, while a change to sea_orm_sync.database.connection can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm_sync.database.connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.connection uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.database.connection, while a change to sea_orm_sync.database.connection can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.database.connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.connection uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.connection, while a change to sea_orm_sync.database.connection can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.executor.select uses sea_orm_sync.error, so a change to sea_orm_sync.error can break sea_orm_sync.executor.select, while a change to sea_orm_sync.executor.select can't break sea_orm_sync.error.
Position
Below the diagonal: sea_orm_sync.executor.select uses a module listed above it, which is the healthy direction.
sea_orm_sync.executor.select uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.executor.select, while a change to sea_orm_sync.executor.select can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.executor.select uses a module listed above it, which is the healthy direction.
14→18 sea_orm_sync.executor.select uses sea_orm_sync.executor.querypart of a loop✕
Connections
10 pairs of types, where a type in sea_orm_sync.executor.select uses a type in sea_orm_sync.executor.query.
sea_orm_sync.executor.select uses sea_orm_sync.executor.query, so a change to sea_orm_sync.executor.query can break sea_orm_sync.executor.select, while a change to sea_orm_sync.executor.select can't break sea_orm_sync.executor.query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.database.transaction uses sea_orm.error, so a change to sea_orm.error can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.error.
Position
Below the diagonal: sea_orm.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm.database.transaction uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm.database.transaction uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm.database.transaction uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm.database.transaction uses sea_orm.database.connection, so a change to sea_orm.database.connection can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.database.connection.
Position
Below the diagonal: sea_orm.database.transaction uses a module listed above it, which is the healthy direction.
15→19 sea_orm.database.transaction uses sea_orm.database.executorpart of a loop✕
Connections
2 pairs of types, where a type in sea_orm.database.transaction uses a type in sea_orm.database.executor.
sea_orm.database.transaction uses sea_orm.database.executor, so a change to sea_orm.database.executor can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.database.executor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→26 sea_orm.database.transaction uses sea_orm.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm.database.transaction uses a type in sea_orm.database.db_connection.
sea_orm.database.transaction uses sea_orm.database.db_connection, so a change to sea_orm.database.db_connection can break sea_orm.database.transaction, while a change to sea_orm.database.transaction can't break sea_orm.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.driver.rusqlite uses sea_orm.error, so a change to sea_orm.error can break sea_orm.driver.rusqlite, while a change to sea_orm.driver.rusqlite can't break sea_orm.error.
Position
Below the diagonal: sea_orm.driver.rusqlite uses a module listed above it, which is the healthy direction.
sea_orm.driver.rusqlite uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.driver.rusqlite, while a change to sea_orm.driver.rusqlite can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.driver.rusqlite uses a module listed above it, which is the healthy direction.
sea_orm.driver.rusqlite uses sea_orm.database.connection, so a change to sea_orm.database.connection can break sea_orm.driver.rusqlite, while a change to sea_orm.driver.rusqlite can't break sea_orm.database.connection.
Position
Below the diagonal: sea_orm.driver.rusqlite uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.transaction uses sea_orm_macros.derives.active_enum_display, so a change to sea_orm_macros.derives.active_enum_display can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_macros.derives.active_enum_display.
Position
Below the diagonal: sea_orm_sync.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.transaction uses sea_orm_sync.error, so a change to sea_orm_sync.error can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.error.
Position
Below the diagonal: sea_orm_sync.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.transaction uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.transaction uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.transaction uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.transaction uses sea_orm_sync.database.connection, so a change to sea_orm_sync.database.connection can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.database.connection.
Position
Below the diagonal: sea_orm_sync.database.transaction uses a module listed above it, which is the healthy direction.
17→22 sea_orm_sync.database.transaction uses sea_orm_sync.database.executorpart of a loop✕
Connections
2 pairs of types, where a type in sea_orm_sync.database.transaction uses a type in sea_orm_sync.database.executor.
sea_orm_sync.database.transaction uses sea_orm_sync.database.executor, so a change to sea_orm_sync.database.executor can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.database.executor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→29 sea_orm_sync.database.transaction uses sea_orm_sync.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm_sync.database.transaction uses a type in sea_orm_sync.database.db_connection.
sea_orm_sync.database.transaction uses sea_orm_sync.database.db_connection, so a change to sea_orm_sync.database.db_connection can break sea_orm_sync.database.transaction, while a change to sea_orm_sync.database.transaction can't break sea_orm_sync.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.executor.query uses sea_orm_sync.error, so a change to sea_orm_sync.error can break sea_orm_sync.executor.query, while a change to sea_orm_sync.executor.query can't break sea_orm_sync.error.
Position
Below the diagonal: sea_orm_sync.executor.query uses a module listed above it, which is the healthy direction.
sea_orm_sync.executor.query uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.executor.query, while a change to sea_orm_sync.executor.query can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.executor.query uses a module listed above it, which is the healthy direction.
sea_orm_sync.executor.query uses sea_orm_sync.executor.select, so a change to sea_orm_sync.executor.select can break sea_orm_sync.executor.query, while a change to sea_orm_sync.executor.query can't break sea_orm_sync.executor.select.
Position
Below the diagonal: sea_orm_sync.executor.query uses a module listed above it, which is the healthy direction.
18→23 sea_orm_sync.executor.query uses sea_orm_sync.database.proxypart of a loop✕
Connections
1 pair of types, where a type in sea_orm_sync.executor.query uses a type in sea_orm_sync.database.proxy.
sea_orm_sync.executor.query uses sea_orm_sync.database.proxy, so a change to sea_orm_sync.database.proxy can break sea_orm_sync.executor.query, while a change to sea_orm_sync.executor.query can't break sea_orm_sync.database.proxy.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.database.executor uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.database.executor, while a change to sea_orm.database.executor can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.database.executor uses a module listed above it, which is the healthy direction.
sea_orm.database.executor uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.executor, while a change to sea_orm.database.executor can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.executor uses a module listed above it, which is the healthy direction.
sea_orm.database.executor uses sea_orm.database.connection, so a change to sea_orm.database.connection can break sea_orm.database.executor, while a change to sea_orm.database.executor can't break sea_orm.database.connection.
Position
Below the diagonal: sea_orm.database.executor uses a module listed above it, which is the healthy direction.
sea_orm.database.executor uses sea_orm.database.transaction, so a change to sea_orm.database.transaction can break sea_orm.database.executor, while a change to sea_orm.database.executor can't break sea_orm.database.transaction.
Position
Below the diagonal: sea_orm.database.executor uses a module listed above it, which is the healthy direction.
19→26 sea_orm.database.executor uses sea_orm.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm.database.executor uses a type in sea_orm.database.db_connection.
sea_orm.database.executor uses sea_orm.database.db_connection, so a change to sea_orm.database.db_connection can break sea_orm.database.executor, while a change to sea_orm.database.executor can't break sea_orm.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.database.restricted_connection uses sea_orm.error, so a change to sea_orm.error can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.error.
Position
Below the diagonal: sea_orm.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.restricted_connection uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.restricted_connection uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.restricted_connection uses sea_orm.database.connection, so a change to sea_orm.database.connection can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.database.connection.
Position
Below the diagonal: sea_orm.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.restricted_connection uses sea_orm.database.transaction, so a change to sea_orm.database.transaction can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.database.transaction.
Position
Below the diagonal: sea_orm.database.restricted_connection uses a module listed above it, which is the healthy direction.
20→26 sea_orm.database.restricted_connection uses sea_orm.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm.database.restricted_connection uses a type in sea_orm.database.db_connection.
sea_orm.database.restricted_connection uses sea_orm.database.db_connection, so a change to sea_orm.database.db_connection can break sea_orm.database.restricted_connection, while a change to sea_orm.database.restricted_connection can't break sea_orm.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.executor.query uses sea_orm.error, so a change to sea_orm.error can break sea_orm.executor.query, while a change to sea_orm.executor.query can't break sea_orm.error.
Position
Below the diagonal: sea_orm.executor.query uses a module listed above it, which is the healthy direction.
sea_orm.executor.query uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.executor.query, while a change to sea_orm.executor.query can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.executor.query uses a module listed above it, which is the healthy direction.
sea_orm.executor.query uses sea_orm.executor.select, so a change to sea_orm.executor.select can break sea_orm.executor.query, while a change to sea_orm.executor.query can't break sea_orm.executor.select.
Position
Below the diagonal: sea_orm.executor.query uses a module listed above it, which is the healthy direction.
sea_orm.executor.query uses sea_orm.driver.rusqlite, so a change to sea_orm.driver.rusqlite can break sea_orm.executor.query, while a change to sea_orm.executor.query can't break sea_orm.driver.rusqlite.
Position
Below the diagonal: sea_orm.executor.query uses a module listed above it, which is the healthy direction.
21→27 sea_orm.executor.query uses sea_orm.database.proxypart of a loop✕
Connections
1 pair of types, where a type in sea_orm.executor.query uses a type in sea_orm.database.proxy.
sea_orm.executor.query uses sea_orm.database.proxy, so a change to sea_orm.database.proxy can break sea_orm.executor.query, while a change to sea_orm.executor.query can't break sea_orm.database.proxy.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.database.executor uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.database.executor, while a change to sea_orm_sync.database.executor can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.database.executor uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.executor uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.executor, while a change to sea_orm_sync.database.executor can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.executor uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.executor uses sea_orm_sync.database.connection, so a change to sea_orm_sync.database.connection can break sea_orm_sync.database.executor, while a change to sea_orm_sync.database.executor can't break sea_orm_sync.database.connection.
Position
Below the diagonal: sea_orm_sync.database.executor uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.executor uses sea_orm_sync.database.transaction, so a change to sea_orm_sync.database.transaction can break sea_orm_sync.database.executor, while a change to sea_orm_sync.database.executor can't break sea_orm_sync.database.transaction.
Position
Below the diagonal: sea_orm_sync.database.executor uses a module listed above it, which is the healthy direction.
22→29 sea_orm_sync.database.executor uses sea_orm_sync.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm_sync.database.executor uses a type in sea_orm_sync.database.db_connection.
sea_orm_sync.database.executor uses sea_orm_sync.database.db_connection, so a change to sea_orm_sync.database.db_connection can break sea_orm_sync.database.executor, while a change to sea_orm_sync.database.executor can't break sea_orm_sync.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.database.proxy uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.proxy, while a change to sea_orm_sync.database.proxy can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.proxy uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.proxy uses sea_orm_sync.executor.query, so a change to sea_orm_sync.executor.query can break sea_orm_sync.database.proxy, while a change to sea_orm_sync.database.proxy can't break sea_orm_sync.executor.query.
Position
Below the diagonal: sea_orm_sync.database.proxy uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.error, so a change to sea_orm_sync.error can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.error.
Position
Below the diagonal: sea_orm_sync.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.database.connection, so a change to sea_orm_sync.database.connection can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.database.connection.
Position
Below the diagonal: sea_orm_sync.database.restricted_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.database.transaction, so a change to sea_orm_sync.database.transaction can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.database.transaction.
Position
Below the diagonal: sea_orm_sync.database.restricted_connection uses a module listed above it, which is the healthy direction.
24→29 sea_orm_sync.database.restricted_connection uses sea_orm_sync.database.db_connectionpart of a loop✕
Connections
1 pair of types, where a type in sea_orm_sync.database.restricted_connection uses a type in sea_orm_sync.database.db_connection.
sea_orm_sync.database.restricted_connection uses sea_orm_sync.database.db_connection, so a change to sea_orm_sync.database.db_connection can break sea_orm_sync.database.restricted_connection, while a change to sea_orm_sync.database.restricted_connection can't break sea_orm_sync.database.db_connection.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.dynamic.model uses sea_orm_sync.executor.query, so a change to sea_orm_sync.executor.query can break sea_orm_sync.dynamic.model, while a change to sea_orm_sync.dynamic.model can't break sea_orm_sync.executor.query.
Position
Below the diagonal: sea_orm_sync.dynamic.model uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.database.connection, so a change to sea_orm.database.connection can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.database.connection.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.driver.rusqlite, so a change to sea_orm.driver.rusqlite can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.driver.rusqlite.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.database.executor, so a change to sea_orm.database.executor can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.database.executor.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.db_connection uses sea_orm.database.restricted_connection, so a change to sea_orm.database.restricted_connection can break sea_orm.database.db_connection, while a change to sea_orm.database.db_connection can't break sea_orm.database.restricted_connection.
Position
Below the diagonal: sea_orm.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm.database.proxy uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.database.proxy, while a change to sea_orm.database.proxy can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.database.proxy uses a module listed above it, which is the healthy direction.
sea_orm.database.proxy uses sea_orm.executor.query, so a change to sea_orm.executor.query can break sea_orm.database.proxy, while a change to sea_orm.database.proxy can't break sea_orm.executor.query.
Position
Below the diagonal: sea_orm.database.proxy uses a module listed above it, which is the healthy direction.
sea_orm.dynamic.model uses sea_orm.executor.query, so a change to sea_orm.executor.query can break sea_orm.dynamic.model, while a change to sea_orm.dynamic.model can't break sea_orm.executor.query.
Position
Below the diagonal: sea_orm.dynamic.model uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.db_connection uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.database.db_connection, while a change to sea_orm_sync.database.db_connection can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.db_connection uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.database.db_connection, while a change to sea_orm_sync.database.db_connection can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.db_connection uses sea_orm_sync.database.connection, so a change to sea_orm_sync.database.connection can break sea_orm_sync.database.db_connection, while a change to sea_orm_sync.database.db_connection can't break sea_orm_sync.database.connection.
Position
Below the diagonal: sea_orm_sync.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.db_connection uses sea_orm_sync.database.executor, so a change to sea_orm_sync.database.executor can break sea_orm_sync.database.db_connection, while a change to sea_orm_sync.database.db_connection can't break sea_orm_sync.database.executor.
Position
Below the diagonal: sea_orm_sync.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.database.db_connection uses sea_orm_sync.database.restricted_connection, so a change to sea_orm_sync.database.restricted_connection can break sea_orm_sync.database.db_connection, while a change to sea_orm_sync.database.db_connection can't break sea_orm_sync.database.restricted_connection.
Position
Below the diagonal: sea_orm_sync.database.db_connection uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.loader uses sea_orm_sync.error, so a change to sea_orm_sync.error can break sea_orm_sync.query.loader, while a change to sea_orm_sync.query.loader can't break sea_orm_sync.error.
Position
Below the diagonal: sea_orm_sync.query.loader uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.loader uses sea_orm_sync.unused_async_trait_impl, so a change to sea_orm_sync.unused_async_trait_impl can break sea_orm_sync.query.loader, while a change to sea_orm_sync.query.loader can't break sea_orm_sync.unused_async_trait_impl.
Position
Below the diagonal: sea_orm_sync.query.loader uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.loader uses sea_orm_sync.dynamic.model, so a change to sea_orm_sync.dynamic.model can break sea_orm_sync.query.loader, while a change to sea_orm_sync.query.loader can't break sea_orm_sync.dynamic.model.
Position
Below the diagonal: sea_orm_sync.query.loader uses a module listed above it, which is the healthy direction.
30→32 sea_orm_sync.query.loader uses sea_orm_sync.query.selectpart of a loop✕
Connections
2 pairs of types, where a type in sea_orm_sync.query.loader uses a type in sea_orm_sync.query.select.
sea_orm_sync.query.loader uses sea_orm_sync.query.select, so a change to sea_orm_sync.query.select can break sea_orm_sync.query.loader, while a change to sea_orm_sync.query.loader can't break sea_orm_sync.query.select.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→34 sea_orm_sync.query.loader uses sea_orm_sync.entity.relationpart of a loop✕
Connections
3 pairs of types, where a type in sea_orm_sync.query.loader uses a type in sea_orm_sync.entity.relation.
sea_orm_sync.query.loader uses sea_orm_sync.entity.relation, so a change to sea_orm_sync.entity.relation can break sea_orm_sync.query.loader, while a change to sea_orm_sync.query.loader can't break sea_orm_sync.entity.relation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm.query.loader uses sea_orm.error, so a change to sea_orm.error can break sea_orm.query.loader, while a change to sea_orm.query.loader can't break sea_orm.error.
Position
Below the diagonal: sea_orm.query.loader uses a module listed above it, which is the healthy direction.
sea_orm.query.loader uses sea_orm.unused_async_trait_impl, so a change to sea_orm.unused_async_trait_impl can break sea_orm.query.loader, while a change to sea_orm.query.loader can't break sea_orm.unused_async_trait_impl.
Position
Below the diagonal: sea_orm.query.loader uses a module listed above it, which is the healthy direction.
sea_orm.query.loader uses sea_orm.dynamic.model, so a change to sea_orm.dynamic.model can break sea_orm.query.loader, while a change to sea_orm.query.loader can't break sea_orm.dynamic.model.
Position
Below the diagonal: sea_orm.query.loader uses a module listed above it, which is the healthy direction.
31→33 sea_orm.query.loader uses sea_orm.query.selectpart of a loop✕
Connections
2 pairs of types, where a type in sea_orm.query.loader uses a type in sea_orm.query.select.
sea_orm.query.loader uses sea_orm.query.select, so a change to sea_orm.query.select can break sea_orm.query.loader, while a change to sea_orm.query.loader can't break sea_orm.query.select.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→35 sea_orm.query.loader uses sea_orm.entity.relationpart of a loop✕
Connections
3 pairs of types, where a type in sea_orm.query.loader uses a type in sea_orm.entity.relation.
sea_orm.query.loader uses sea_orm.entity.relation, so a change to sea_orm.entity.relation can break sea_orm.query.loader, while a change to sea_orm.query.loader can't break sea_orm.entity.relation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
sea_orm_sync.query.select uses sea_orm_sync.database.statement, so a change to sea_orm_sync.database.statement can break sea_orm_sync.query.select, while a change to sea_orm_sync.query.select can't break sea_orm_sync.database.statement.
Position
Below the diagonal: sea_orm_sync.query.select uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.select uses sea_orm_sync.executor.select, so a change to sea_orm_sync.executor.select can break sea_orm_sync.query.select, while a change to sea_orm_sync.query.select can't break sea_orm_sync.executor.select.
Position
Below the diagonal: sea_orm_sync.query.select uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.select uses sea_orm_sync.dynamic.model, so a change to sea_orm_sync.dynamic.model can break sea_orm_sync.query.select, while a change to sea_orm_sync.query.select can't break sea_orm_sync.dynamic.model.
Position
Below the diagonal: sea_orm_sync.query.select uses a module listed above it, which is the healthy direction.
sea_orm_sync.query.select uses sea_orm_sync.query.loader, so a change to sea_orm_sync.query.loader can break sea_orm_sync.query.select, while a change to sea_orm_sync.query.select can't break sea_orm_sync.query.loader.
Position
Below the diagonal: sea_orm_sync.query.select uses a module listed above it, which is the healthy direction.
sea_orm.query.select uses sea_orm.database.statement, so a change to sea_orm.database.statement can break sea_orm.query.select, while a change to sea_orm.query.select can't break sea_orm.database.statement.
Position
Below the diagonal: sea_orm.query.select uses a module listed above it, which is the healthy direction.
sea_orm.query.select uses sea_orm.query.helper, so a change to sea_orm.query.helper can break sea_orm.query.select, while a change to sea_orm.query.select can't break sea_orm.query.helper.
Position
Below the diagonal: sea_orm.query.select uses a module listed above it, which is the healthy direction.
sea_orm.query.select uses sea_orm.executor.select, so a change to sea_orm.executor.select can break sea_orm.query.select, while a change to sea_orm.query.select can't break sea_orm.executor.select.
Position
Below the diagonal: sea_orm.query.select uses a module listed above it, which is the healthy direction.
sea_orm.query.select uses sea_orm.dynamic.model, so a change to sea_orm.dynamic.model can break sea_orm.query.select, while a change to sea_orm.query.select can't break sea_orm.dynamic.model.
Position
Below the diagonal: sea_orm.query.select uses a module listed above it, which is the healthy direction.
sea_orm.query.select uses sea_orm.query.loader, so a change to sea_orm.query.loader can break sea_orm.query.select, while a change to sea_orm.query.select can't break sea_orm.query.loader.
Position
Below the diagonal: sea_orm.query.select uses a module listed above it, which is the healthy direction.
sea_orm_sync.entity.relation uses sea_orm_sync.query.select, so a change to sea_orm_sync.query.select can break sea_orm_sync.entity.relation, while a change to sea_orm_sync.entity.relation can't break sea_orm_sync.query.select.
Position
Below the diagonal: sea_orm_sync.entity.relation uses a module listed above it, which is the healthy direction.
sea_orm.entity.relation uses sea_orm.query.select, so a change to sea_orm.query.select can break sea_orm.entity.relation, while a change to sea_orm.entity.relation can't break sea_orm.query.select.
Position
Below the diagonal: sea_orm.entity.relation uses a module listed above it, which is the healthy direction.
sea_orm_sync.dynamic.entity uses sea_orm_sync.dynamic.model, so a change to sea_orm_sync.dynamic.model can break sea_orm_sync.dynamic.entity, while a change to sea_orm_sync.dynamic.entity can't break sea_orm_sync.dynamic.model.
Position
Below the diagonal: sea_orm_sync.dynamic.entity uses a module listed above it, which is the healthy direction.
sea_orm_sync.dynamic.entity uses sea_orm_sync.entity.relation, so a change to sea_orm_sync.entity.relation can break sea_orm_sync.dynamic.entity, while a change to sea_orm_sync.dynamic.entity can't break sea_orm_sync.entity.relation.
Position
Below the diagonal: sea_orm_sync.dynamic.entity uses a module listed above it, which is the healthy direction.
sea_orm_sync.entity.base_entity uses sea_orm_sync.query.select, so a change to sea_orm_sync.query.select can break sea_orm_sync.entity.base_entity, while a change to sea_orm_sync.entity.base_entity can't break sea_orm_sync.query.select.
Position
Below the diagonal: sea_orm_sync.entity.base_entity uses a module listed above it, which is the healthy direction.
sea_orm_sync.entity.base_entity uses sea_orm_sync.entity.relation, so a change to sea_orm_sync.entity.relation can break sea_orm_sync.entity.base_entity, while a change to sea_orm_sync.entity.base_entity can't break sea_orm_sync.entity.relation.
Position
Below the diagonal: sea_orm_sync.entity.base_entity uses a module listed above it, which is the healthy direction.
sea_orm.dynamic.entity uses sea_orm.entity.column_def, so a change to sea_orm.entity.column_def can break sea_orm.dynamic.entity, while a change to sea_orm.dynamic.entity can't break sea_orm.entity.column_def.
Position
Below the diagonal: sea_orm.dynamic.entity uses a module listed above it, which is the healthy direction.
sea_orm.dynamic.entity uses sea_orm.dynamic.model, so a change to sea_orm.dynamic.model can break sea_orm.dynamic.entity, while a change to sea_orm.dynamic.entity can't break sea_orm.dynamic.model.
Position
Below the diagonal: sea_orm.dynamic.entity uses a module listed above it, which is the healthy direction.
sea_orm.dynamic.entity uses sea_orm.entity.relation, so a change to sea_orm.entity.relation can break sea_orm.dynamic.entity, while a change to sea_orm.dynamic.entity can't break sea_orm.entity.relation.
Position
Below the diagonal: sea_orm.dynamic.entity uses a module listed above it, which is the healthy direction.
sea_orm.entity.base_entity uses sea_orm.query.select, so a change to sea_orm.query.select can break sea_orm.entity.base_entity, while a change to sea_orm.entity.base_entity can't break sea_orm.query.select.
Position
Below the diagonal: sea_orm.entity.base_entity uses a module listed above it, which is the healthy direction.
sea_orm.entity.base_entity uses sea_orm.entity.relation, so a change to sea_orm.entity.relation can break sea_orm.entity.base_entity, while a change to sea_orm.entity.base_entity can't break sea_orm.entity.relation.
Position
Below the diagonal: sea_orm.entity.base_entity uses a module listed above it, which is the healthy direction.
sea_orm.entity.active_model uses sea_orm.dynamic.model, so a change to sea_orm.dynamic.model can break sea_orm.entity.active_model, while a change to sea_orm.entity.active_model can't break sea_orm.dynamic.model.
Position
Below the diagonal: sea_orm.entity.active_model uses a module listed above it, which is the healthy direction.
sea_orm.entity.active_model uses sea_orm.query.select, so a change to sea_orm.query.select can break sea_orm.entity.active_model, while a change to sea_orm.entity.active_model can't break sea_orm.query.select.
Position
Below the diagonal: sea_orm.entity.active_model uses a module listed above it, which is the healthy direction.
sea_orm.entity.active_model uses sea_orm.entity.relation, so a change to sea_orm.entity.relation can break sea_orm.entity.active_model, while a change to sea_orm.entity.active_model can't break sea_orm.entity.relation.
Position
Below the diagonal: sea_orm.entity.active_model uses a module listed above it, which is the healthy direction.
sea_orm.entity.active_model uses sea_orm.dynamic.entity, so a change to sea_orm.dynamic.entity can break sea_orm.entity.active_model, while a change to sea_orm.entity.active_model can't break sea_orm.dynamic.entity.
Position
Below the diagonal: sea_orm.entity.active_model uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 60% · Adequate · gated by D4, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
85
High / Critical
A05:2025 — Injection
76
High / Critical
A02:2025 — Security Misconfiguration
5
Medium
Roadmap
Top priorities: Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only; Interpolated log message defeats structured logging; Resolve the 94 Low coverage finding(s) in Code Coverage — start with users.rs (3), model.rs (3), lib.rs (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 94 Low coverage finding(s) in Code Coverage — start with users.rs (3), model.rs (3), lib.rs (2).
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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 — 125
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 — 1020
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 — 90
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
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 50 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 — 50 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, 1199 of 1235 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.
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 (.rs) and this repository declares a Cargo test suite (repository root, 274 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.12 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — 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. Not scored — this repository declares Cargo manifests but commits no Cargo.lock, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of bae satisfies `0.2`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D19 Documentation Quality — 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 ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — 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. 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 — 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. 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — 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. 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.
GD1 Unfinished & placeholder code — 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 C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — 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 C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — 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.
P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
X12 Unreachable branch — 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 C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — 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 C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — 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 C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — 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 C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — 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 C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — 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 C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — 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 C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — 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 C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — 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 C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — 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 C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — 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 C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
X5 Nullable reference types — 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 C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: 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.
32 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was sea_orm_macros::derives::entity_model::expand_derive_entity_model at 79. A further 11 function(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 sea_orm_sync::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row at 53 — they are counted neither in the figure above nor in this dimension's score. 9 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: sea-orm-sync/src/driver/sqlx_postgres.rs (sea_orm_sync::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row at 53), src/driver/sqlx_postgres.rs (sea_orm::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row at 53), sea-orm-codegen/src/entity/writer/mermaid.rs (sea_orm_codegen::entity::writer::mermaid::col_type_name at 36), sea-orm-sync/src/dynamic/model.rs (sea_orm_sync::dynamic::model::try_get at 32), src/dynamic/model.rs (sea_orm::dynamic::model::try_get at 32), and 4 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.
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with sea_orm_macros::derives::entity_model::expand_derive_entity_model (cyclomatic 79). — Refactoring it lifts Cyclomatic Complexity from 6.3 to about 6.5/10.
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.
52 function(s) exceeded the cognitive complexity threshold of 15; the worst was sea_orm_macros::derives::entity_model::expand_derive_entity_model at 241.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with sea_orm_macros::derives::entity_model::expand_derive_entity_model (cognitive 241), EntityTransformer::transform (cognitive 140), EntitySchemaInfo::sync (cognitive 131). — 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 6 together lifts Cognitive Complexity from 5.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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.5 / 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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 FileTooLong finding(s) in God Classes — start with query.rs (2), loader.rs (2), transaction.rs (2). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 11 FunctionTooLong finding(s) in God Classes — start with lib.rs (3), sqlx_postgres.rs (2), sqlx_mysql.rs (2). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 MethodTooLong finding(s) in God Classes — start with builder.rs (4), transformer.rs, relation.rs. — One of this dimension's main actionable groups (10 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.
556 duplicated block group(s) detected. 19.4 % of the production lines (21,611 of 111,166) are in a reported copy. A further 157 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 9 of the 713 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.
+ 179 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 56 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with query.rs (6), helper.rs (5), active_value.rs (4). — One of this dimension's main actionable groups (56 warning-level).
Resolve the 48 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with active_value.rs (7), consolidate.rs (7), active_model_ex.rs (4). — One of this dimension's main actionable groups (48 warning-level).
Resolve the 39 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with transaction.rs (5), rusqlite.rs (3), column.rs (3). — One of this dimension's main actionable groups (39 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.4 / 10Stronggated by 2 serious findings✓ 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.
29 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 21 of the 29 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: entity (issues/1599/entity) · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage7.1 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 35.3% — 94 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 155 production file(s), 73 test binaries and 1 doc-test binaries).
Resolve the 94 Low coverage finding(s) in Code Coverage — start with users.rs (3), model.rs (3), lib.rs (2). — One of this dimension's main actionable groups (94 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 outdated, 0 yanked direct Cargo dependencies. 50 of 101 direct crates were graded against crates.io (0 not published there, 51 not resolved by a committed Cargo.lock). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
Outdated: uuid
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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: 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 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with entity_model.rs, generate.rs. — One of this dimension's main actionable groups (2 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 Factor9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is sea-orm-sync/src/executor/consolidate.rs. Counted over 229 of the 451 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
✓ On the Gold path — maintain.
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.
18 deducted task-comment markers across 111166 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 14 TodoComment finding(s) in Explicit Debt — start with downloader.rs (3), nested_alias.rs (2), builder.rs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with json_struct_tests.rs (4). — One of this dimension's main actionable groups (4 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.
1 of 1 documentation facets pass in full. 12 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 28 build units (Cargo) 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: Secret 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.
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).
76 finding(s): 0 critical, 73 high, 3 medium, 0 low. 70 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 1 file(s) — `src/database/mock.rs` (line 468, line 510, line 541, …) — 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 2 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
What to do
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 70 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (70 issue-level, 0 of them charged here).
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 48 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17), REDACTED (16), REDACTED (14). — One of this dimension's main actionable groups (48 issue-level).
Resolve the 4 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 20 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (20 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 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.
9 of 229 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/entity/primary_key.rs. Counted over 229 of the 451 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×9src/entity/primary_key.rs:1
Orphaned files with no living knowledge
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Domain Modelling — Whether an aggregate references another aggregate by identity rather than embedding it by object reference.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
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.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
Do you agree with this assessment?
P2 · Observability7.2 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 10/24 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `issues/1143`, `issues/1278`, `issues/1357`, `issues/1473`, `issues/249/app` and 9 more.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route on your axum/actix router) 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.
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:12
What to do
Enable Dependabot/Renovate or a dependency-review gate.
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 · 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.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
What to do
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
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 a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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 `REDACTED` 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.
`warn!` at line 466 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/schema/builder.rs:466
`debug!` at line 47 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/entity/registry.rs:47, sea-orm-sync/src/entity/registry.rs:47
`debug!` at line 51 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/entity/registry.rs:51, sea-orm-sync/src/entity/registry.rs:51
`debug!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/entity/registry.rs:53, sea-orm-sync/src/entity/registry.rs:53
`debug!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:329, sea-orm-sync/src/driver/rusqlite.rs:329
`debug!` at line 349 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:349, sea-orm-sync/src/driver/rusqlite.rs:349
`debug!` at line 366 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:366, sea-orm-sync/src/driver/rusqlite.rs:366
`debug!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:391, sea-orm-sync/src/driver/rusqlite.rs:391
`debug!` at line 417 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:417, sea-orm-sync/src/driver/rusqlite.rs:417
`debug!` at line 502 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:502, sea-orm-sync/src/driver/rusqlite.rs:502
`debug!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:520, sea-orm-sync/src/driver/rusqlite.rs:520
`debug!` at line 539 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:539, sea-orm-sync/src/driver/rusqlite.rs:539
`debug!` at line 566 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:566, sea-orm-sync/src/driver/rusqlite.rs:566
`debug!` at line 589 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. (×2) — src/driver/rusqlite.rs:589, sea-orm-sync/src/driver/rusqlite.rs:589
`warn!` at line 460 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-sync/src/schema/builder.rs:460
`info!` at line 196 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator.rs:196
`info!` at line 159 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:159
`info!` at line 167 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:167
`info!` at line 177 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:177
`info!` at line 183 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:183
`info!` at line 193 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:193
`info!` at line 197 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:197
`info!` at line 270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:270
`info!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:287
`info!` at line 293 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:293
`info!` at line 299 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:299
`info!` at line 316 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — sea-orm-migration/src/migrator/exec.rs:316
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 — 4 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.
AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXI1 Runtime container hardening — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 21 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 — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~58339 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its sibling role token rows: 4 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (sea-orm-sync), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — SeaORM, sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — coverage data present for 155 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X19 Unrestored process-global state — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — 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
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — 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.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 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.
Duplicated block (7 lines × 2) sea-orm-macros/src/derives/entity_loader.rs:309— sea-orm-macros/src/derives/entity_loader.rs:309-315 | sea-orm-macros/src/derives/entity_loader.rs:365-371 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/entity_loader.rs:309` 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) sea-orm-macros/src/derives/entity_loader.rs:330— sea-orm-macros/src/derives/entity_loader.rs:330-336 | sea-orm-macros/src/derives/entity_loader.rs:394-400 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/entity_loader.rs:330` 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) sea-orm-sync/src/database/db_connection.rs:519— sea-orm-sync/src/database/db_connection.rs:519-525 | src/database/db_connection.rs:558-564 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:519` 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) sea-orm-sync/src/database/db_connection.rs:565— sea-orm-sync/src/database/db_connection.rs:565-571 | src/database/db_connection.rs:613-619 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:565` 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) sea-orm-sync/src/database/transaction.rs:467— sea-orm-sync/src/database/transaction.rs:467-473 | src/database/transaction.rs:498-504 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:467` 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) sea-orm-sync/src/database/transaction.rs:474— sea-orm-sync/src/database/transaction.rs:474-480 | src/database/transaction.rs:506-512 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:474` 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) sea-orm-sync/src/entity/relation.rs:567— sea-orm-sync/src/entity/relation.rs:567-573 | src/entity/relation.rs:567-573 — before extracting anything, compare `sea-orm-sync/src/entity/relation.rs` and `src/entity/relation.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 lines × 2) sea-orm-sync/src/executor/update.rs:148— sea-orm-sync/src/executor/update.rs:148-154 | src/executor/update.rs:153-159 — before extracting anything, compare `sea-orm-sync/src/executor/update.rs` and `src/executor/update.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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 `sea-orm-sync/src/executor/update.rs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) sea-orm-sync/src/rbac/schema.rs:49— sea-orm-sync/src/rbac/schema.rs:49-55 | src/rbac/schema.rs:53-59 — 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) sea-orm-sync/src/entity/active_value.rs:622— sea-orm-sync/src/entity/active_value.rs:622-628 | src/entity/active_value.rs:622-628 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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. 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 lines × 2) sea-orm-sync/src/query/helper.rs:901— sea-orm-sync/src/query/helper.rs:901-907 | src/query/helper.rs:901-907 — before extracting anything, compare `sea-orm-sync/src/query/helper.rs` and `src/query/helper.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 77 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. 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 lines × 2) sea-orm-sync/src/query/helper.rs:916— sea-orm-sync/src/query/helper.rs:916-922 | src/query/helper.rs:916-922 — before extracting anything, compare `sea-orm-sync/src/query/helper.rs` and `src/query/helper.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 77 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. 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 lines × 2) sea-orm-sync/src/entity/column.rs:442— sea-orm-sync/src/entity/column.rs:442-448 | src/entity/column.rs:442-448 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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 `sea-orm-sync/src/entity/column.rs:442` 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) sea-orm-sync/src/entity/column.rs:479— sea-orm-sync/src/entity/column.rs:479-485 | src/entity/column.rs:479-485 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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 `sea-orm-sync/src/entity/column.rs:479` 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) sea-orm-sync/src/executor/update.rs:214— sea-orm-sync/src/executor/update.rs:214-220 | src/executor/update.rs:221-227 — before extracting anything, compare `sea-orm-sync/src/executor/update.rs` and `src/executor/update.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/executor.rs:44— sea-orm-sync/src/database/executor.rs:44-50 | src/database/executor.rs:45-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/mock.rs:103— sea-orm-sync/src/database/mock.rs:103-109 | src/database/mock.rs:103-109 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/mock.rs:391— sea-orm-sync/src/database/mock.rs:391-397 | src/database/mock.rs:391-397 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/restricted_connection.rs:531— sea-orm-sync/src/database/restricted_connection.rs:531-537 | src/database/restricted_connection.rs:578-584 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/restricted_connection.rs:539— sea-orm-sync/src/database/restricted_connection.rs:539-545 | src/database/restricted_connection.rs:586-592 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/database/restricted_connection.rs:562— sea-orm-sync/src/database/restricted_connection.rs:562-568 | src/database/restricted_connection.rs:609-615 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 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 `sea-orm-sync/src/database/restricted_connection.rs:562` 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) sea-orm-sync/src/driver/mock.rs:121— sea-orm-sync/src/driver/mock.rs:121-127 | src/driver/mock.rs:122-128 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:708— sea-orm-sync/src/driver/rusqlite.rs:708-714 | src/driver/rusqlite.rs:708-714 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/driver/sqlx_common.rs:45— sea-orm-sync/src/driver/sqlx_common.rs:45-51 | src/driver/sqlx_common.rs:47-53 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_common.rs` and `src/driver/sqlx_common.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) sea-orm-sync/src/entity/active_model_ex.rs:310— sea-orm-sync/src/entity/active_model_ex.rs:310-316 | src/entity/active_model_ex.rs:310-316 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-arrow/src/lib.rs:1295— sea-orm-arrow/src/lib.rs:1295-1300 | sea-orm-arrow/src/lib.rs:1332-1337 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:1295` 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) sea-orm-sync/src/database/mod.rs:214— sea-orm-sync/src/database/mod.rs:214-219 | src/database/mod.rs:230-235 — before extracting anything, compare `sea-orm-sync/src/database/mod.rs` and `src/database/mod.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/database/mod.rs:214` 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) sea-orm-sync/src/value/text_uuid.rs:49— sea-orm-sync/src/value/text_uuid.rs:49-54 | src/value/text_uuid.rs:49-54 — before extracting anything, compare `sea-orm-sync/src/value/text_uuid.rs` and `src/value/text_uuid.rs` as WHOLE FILES: 100% 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 3 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. 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. 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 (6 lines × 2) sea-orm-sync/src/schema/entity.rs:114— sea-orm-sync/src/schema/entity.rs:114-119 | src/schema/entity.rs:114-119 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (6 lines × 2) sea-orm-sync/src/database/connection.rs:237— sea-orm-sync/src/database/connection.rs:237-242 | src/database/connection.rs:252-257 — before extracting anything, compare `sea-orm-sync/src/database/connection.rs` and `src/database/connection.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) sea-orm-sync/src/database/mock.rs:179— sea-orm-sync/src/database/mock.rs:179-184 | src/database/mock.rs:179-184 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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) sea-orm-sync/src/database/mock.rs:347— sea-orm-sync/src/database/mock.rs:347-352 | src/database/mock.rs:347-352 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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) sea-orm-sync/src/database/transaction.rs:865— sea-orm-sync/src/database/transaction.rs:865-870 | src/database/transaction.rs:920-925 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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) sea-orm-sync/src/dynamic/entity.rs:34— sea-orm-sync/src/dynamic/entity.rs:34-39 | src/dynamic/entity.rs:34-39 — before extracting anything, compare `sea-orm-sync/src/dynamic/entity.rs` and `src/dynamic/entity.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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) sea-orm-sync/src/dynamic/execute.rs:40— sea-orm-sync/src/dynamic/execute.rs:40-45 | src/dynamic/execute.rs:40-45 — before extracting anything, compare `sea-orm-sync/src/dynamic/execute.rs` and `src/dynamic/execute.rs` as WHOLE FILES: 91% 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 2 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. 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) sea-orm-sync/src/entity/active_model_ex.rs:148— sea-orm-sync/src/entity/active_model_ex.rs:148-153 | src/entity/active_model_ex.rs:148-153 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/entity/active_model_ex.rs:283— sea-orm-sync/src/entity/active_model_ex.rs:283-288 | src/entity/active_model_ex.rs:283-288 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/entity/active_model_ex.rs:302— sea-orm-sync/src/entity/active_model_ex.rs:302-307 | src/entity/active_model_ex.rs:302-307 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/entity/active_model_ex.rs:454— sea-orm-sync/src/entity/active_model_ex.rs:454-459 | src/entity/active_model_ex.rs:454-459 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/entity/active_value.rs:276— sea-orm-sync/src/entity/active_value.rs:276-281 | src/entity/active_value.rs:276-281 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:288— sea-orm-sync/src/entity/active_value.rs:288-293 | src/entity/active_value.rs:288-293 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:296— sea-orm-sync/src/entity/active_value.rs:296-301 | src/entity/active_value.rs:296-301 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:314— sea-orm-sync/src/entity/active_value.rs:314-319 | src/entity/active_value.rs:314-319 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:351— sea-orm-sync/src/entity/active_value.rs:351-356 | src/entity/active_value.rs:351-356 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:536— sea-orm-sync/src/entity/active_value.rs:536-541 | src/entity/active_value.rs:536-541 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/active_value.rs:609— sea-orm-sync/src/entity/active_value.rs:609-614 | src/entity/active_value.rs:609-614 — before extracting anything, compare `sea-orm-sync/src/entity/active_value.rs` and `src/entity/active_value.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 70 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) sea-orm-sync/src/entity/base_entity.rs:39— sea-orm-sync/src/entity/base_entity.rs:39-44 | src/entity/base_entity.rs:39-44 — before extracting anything, compare `sea-orm-sync/src/entity/base_entity.rs` and `src/entity/base_entity.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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) sea-orm-sync/src/entity/compound.rs:176— sea-orm-sync/src/entity/compound.rs:176-181 | sea-orm-sync/src/executor/paginator.rs:172-177 — 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) sea-orm-sync/src/entity/identity.rs:86— sea-orm-sync/src/entity/identity.rs:86-91 | src/entity/identity.rs:86-91 — before extracting anything, compare `sea-orm-sync/src/entity/identity.rs` and `src/entity/identity.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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) sea-orm-sync/src/executor/consolidate.rs:108— sea-orm-sync/src/executor/consolidate.rs:108-113 | src/executor/consolidate.rs:108-113 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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) issues/1357/src/main.rs:20— issues/1357/src/main.rs:20-27 | issues/1357/src/main.rs:32-39 — both copies are in the same file, so extract the 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 `issues/1357/src/main.rs:20` 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) sea-orm-arrow/src/lib.rs:818— sea-orm-arrow/src/lib.rs:818-825 | sea-orm-arrow/src/lib.rs:1100-1107 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:818` 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 lines × 2) sea-orm-macros/src/derives/entity_loader.rs:319— sea-orm-macros/src/derives/entity_loader.rs:319-326 | sea-orm-macros/src/derives/entity_loader.rs:379-386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-macros/src/derives/entity_loader.rs:319` 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) sea-orm-macros/src/derives/model_ex.rs:824— sea-orm-macros/src/derives/model_ex.rs:824-831 | sea-orm-macros/src/derives/model_ex.rs:995-1002 — both copies are in the same file, so extract the 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) sea-orm-macros/src/derives/partial_model.rs:76— sea-orm-macros/src/derives/partial_model.rs:76-83 | sea-orm-macros/src/derives/partial_model.rs:121-129 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/partial_model.rs:76` 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 (8 lines × 2) sea-orm-sync/src/database/tracing_spans.rs:68— sea-orm-sync/src/database/tracing_spans.rs:68-75 | src/database/tracing_spans.rs:68-75 — before extracting anything, compare `sea-orm-sync/src/database/tracing_spans.rs` and `src/database/tracing_spans.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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. 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 (8 lines × 2) sea-orm-sync/src/database/transaction.rs:430— sea-orm-sync/src/database/transaction.rs:430-437 | src/database/transaction.rs:460-467 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:430` 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) sea-orm-sync/src/database/transaction.rs:459— sea-orm-sync/src/database/transaction.rs:459-466 | src/database/transaction.rs:489-496 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:459` 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) sea-orm-sync/src/database/transaction.rs:549— sea-orm-sync/src/database/transaction.rs:549-556 | src/database/transaction.rs:582-589 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:549` 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) sea-orm-sync/src/driver/rusqlite.rs:472— sea-orm-sync/src/driver/rusqlite.rs:472-479 | src/driver/rusqlite.rs:472-479 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (8 lines × 2) sea-orm-sync/src/entity/column.rs:139— sea-orm-sync/src/entity/column.rs:139-146 | src/entity/column.rs:139-146 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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. 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 (8 lines × 2) sea-orm-sync/src/entity/column.rs:171— sea-orm-sync/src/entity/column.rs:171-178 | src/entity/column.rs:171-178 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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. 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 (8 lines × 2) sea-orm-sync/src/executor/paginator.rs:296— sea-orm-sync/src/executor/paginator.rs:296-303 | src/executor/paginator.rs:305-312 — before extracting anything, compare `sea-orm-sync/src/executor/paginator.rs` and `src/executor/paginator.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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) sea-orm-sync/src/schema/builder.rs:254— sea-orm-sync/src/schema/builder.rs:254-261 | src/schema/builder.rs:258-265 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:254` 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) sea-orm-sync/src/schema/builder.rs:670— sea-orm-sync/src/schema/builder.rs:670-677 | src/schema/builder.rs:679-686 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (8 lines × 2) sea-orm-sync/src/value/text_uuid.rs:60— sea-orm-sync/src/value/text_uuid.rs:60-67 | src/value/text_uuid.rs:60-67 — before extracting anything, compare `sea-orm-sync/src/value/text_uuid.rs` and `src/value/text_uuid.rs` as WHOLE FILES: 100% 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 3 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. 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. 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 (8 lines × 2) sea-orm-sync/src/database/transaction.rs:412— sea-orm-sync/src/database/transaction.rs:412-419 | src/database/transaction.rs:442-449 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:412` 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) sea-orm-sync/src/database/transaction.rs:421— sea-orm-sync/src/database/transaction.rs:421-428 | src/database/transaction.rs:451-458 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:421` 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) sea-orm-sync/src/driver/mock.rs:190— sea-orm-sync/src/driver/mock.rs:190-197 | src/driver/mock.rs:191-198 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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 `sea-orm-sync/src/driver/mock.rs:190` 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) sea-orm-macros/src/derives/column.rs:18— sea-orm-macros/src/derives/column.rs:18-25 | sea-orm-macros/src/derives/primary_key.rs:22-29 — 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 `sea-orm-macros/src/derives/column.rs:18` 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) sea-orm-sync/src/database/connection.rs:217— sea-orm-sync/src/database/connection.rs:217-224 | src/database/connection.rs:232-239 — before extracting anything, compare `sea-orm-sync/src/database/connection.rs` and `src/database/connection.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) sea-orm-sync/src/database/db_connection.rs:605— sea-orm-sync/src/database/db_connection.rs:605-612 | src/database/db_connection.rs:655-662 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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) sea-orm-sync/src/driver/mock.rs:147— sea-orm-sync/src/driver/mock.rs:147-154 | src/driver/mock.rs:148-155 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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) sea-orm-sync/src/driver/mock.rs:171— sea-orm-sync/src/driver/mock.rs:171-178 | src/driver/mock.rs:172-179 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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) sea-orm-sync/src/driver/rusqlite.rs:181— sea-orm-sync/src/driver/rusqlite.rs:181-188 | src/driver/rusqlite.rs:181-188 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) sea-orm-arrow/src/lib.rs:934— sea-orm-arrow/src/lib.rs:934-944 | sea-orm-arrow/src/lib.rs:1226-1236 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:934` 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) sea-orm-arrow/src/lib.rs:946— sea-orm-arrow/src/lib.rs:946-956 | sea-orm-arrow/src/lib.rs:1238-1248 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:946` 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) sea-orm-macros/src/derives/model_ex.rs:771— sea-orm-macros/src/derives/model_ex.rs:771-781 | sea-orm-macros/src/derives/model_ex.rs:965-975 — both copies are in the same file, so extract the 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) sea-orm-sync/src/database/mock.rs:188— sea-orm-sync/src/database/mock.rs:188-198 | src/database/mock.rs:188-198 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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. 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 (11 lines × 2) sea-orm-sync/src/database/mock.rs:202— sea-orm-sync/src/database/mock.rs:202-212 | src/database/mock.rs:202-212 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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. 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 (11 lines × 2) sea-orm-sync/src/database/mod.rs:193— sea-orm-sync/src/database/mod.rs:193-203 | src/database/mod.rs:209-219 — before extracting anything, compare `sea-orm-sync/src/database/mod.rs` and `src/database/mod.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/database/mod.rs:193` 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) sea-orm-sync/src/database/stream/metric.rs:80— sea-orm-sync/src/database/stream/metric.rs:80-90 | src/database/stream/metric.rs:82-92 — before extracting anything, compare `sea-orm-sync/src/database/stream/metric.rs` and `src/database/stream/metric.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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. 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 (11 lines × 2) sea-orm-sync/src/database/transaction.rs:132— sea-orm-sync/src/database/transaction.rs:132-142 | src/database/transaction.rs:144-154 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) sea-orm-sync/src/database/transaction.rs:143— sea-orm-sync/src/database/transaction.rs:143-153 | src/database/transaction.rs:156-166 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:143` 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) sea-orm-sync/src/database/transaction.rs:246— sea-orm-sync/src/database/transaction.rs:246-256 | src/database/transaction.rs:271-281 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:246` 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) sea-orm-sync/src/database/transaction.rs:300— sea-orm-sync/src/database/transaction.rs:300-310 | src/database/transaction.rs:328-338 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:300` 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) sea-orm-sync/src/database/transaction.rs:589— sea-orm-sync/src/database/transaction.rs:589-599 | src/database/transaction.rs:623-633 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:589` 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) sea-orm-sync/src/database/transaction.rs:600— sea-orm-sync/src/database/transaction.rs:600-610 | src/database/transaction.rs:635-645 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:600` 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) sea-orm-sync/src/driver/rusqlite.rs:349— sea-orm-sync/src/driver/rusqlite.rs:349-359 | src/driver/rusqlite.rs:349-359 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:349` 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) sea-orm-sync/src/driver/rusqlite.rs:502— sea-orm-sync/src/driver/rusqlite.rs:502-512 | src/driver/rusqlite.rs:502-512 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:502` 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) sea-orm-sync/src/entity/compound.rs:27— sea-orm-sync/src/entity/compound.rs:27-37 | src/entity/compound.rs:28-38 — before extracting anything, compare `sea-orm-sync/src/entity/compound.rs` and `src/entity/compound.rs` as WHOLE FILES: 88% 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 2 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. 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. 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 (11 lines × 2) sea-orm-sync/src/executor/insert.rs:443— sea-orm-sync/src/executor/insert.rs:443-453 | src/executor/insert.rs:451-461 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:443` 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 (11 lines × 2) sea-orm-sync/src/query/loader.rs:1050— sea-orm-sync/src/query/loader.rs:1050-1060 | src/query/loader.rs:1134-1144 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (11 lines × 2) sea-orm-sync/src/query/loader.rs:1391— sea-orm-sync/src/query/loader.rs:1391-1401 | src/query/loader.rs:1479-1489 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (11 lines × 2) sea-orm-sync/src/query/update.rs:217— sea-orm-sync/src/query/update.rs:217-227 | src/query/update.rs:217-227 — before extracting anything, compare `sea-orm-sync/src/query/update.rs` and `src/query/update.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 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. 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 (11 lines × 2) sea-orm-sync/src/schema/builder.rs:26— sea-orm-sync/src/schema/builder.rs:26-36 | src/schema/builder.rs:26-36 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (11 lines × 2) sea-orm-sync/src/schema/builder.rs:657— sea-orm-sync/src/schema/builder.rs:657-667 | src/schema/builder.rs:666-676 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (11 lines × 2) sea-orm-sync/src/schema/builder.rs:114— sea-orm-sync/src/schema/builder.rs:114-124 | sea-orm-sync/src/schema/builder.rs:153-163 — both copies are in the same file, so extract the 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 `sea-orm-sync/src/schema/builder.rs:114` 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) src/schema/builder.rs:116— src/schema/builder.rs:116-126 | src/schema/builder.rs:156-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/schema/builder.rs:116` 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) sea-orm-sync/src/database/db_connection.rs:710— sea-orm-sync/src/database/db_connection.rs:710-720 | src/database/db_connection.rs:763-773 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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) sea-orm-arrow/src/lib.rs:828— sea-orm-arrow/src/lib.rs:828-836 | sea-orm-arrow/src/lib.rs:1110-1118 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:828` 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 × 2) sea-orm-arrow/src/lib.rs:838— sea-orm-arrow/src/lib.rs:838-846 | sea-orm-arrow/src/lib.rs:1120-1128 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:838` 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 × 2) sea-orm-arrow/src/lib.rs:848— sea-orm-arrow/src/lib.rs:848-856 | sea-orm-arrow/src/lib.rs:1130-1138 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:848` 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 × 2) sea-orm-cli/src/commands/generate.rs:461— sea-orm-cli/src/commands/generate.rs:461-469 | src/driver/sqlx_postgres.rs:131-139 — 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 `sea-orm-cli/src/commands/generate.rs:461` 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) sea-orm-sync/src/database/transaction.rs:611— sea-orm-sync/src/database/transaction.rs:611-619 | src/database/transaction.rs:647-655 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:611` 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) sea-orm-sync/src/driver/mock.rs:159— sea-orm-sync/src/driver/mock.rs:159-167 | src/driver/mock.rs:160-168 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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. 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 (9 lines × 2) sea-orm-sync/src/dynamic/model.rs:48— sea-orm-sync/src/dynamic/model.rs:48-56 | src/dynamic/model.rs:48-56 — before extracting anything, compare `sea-orm-sync/src/dynamic/model.rs` and `src/dynamic/model.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 100 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. 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 (9 lines × 2) sea-orm-sync/src/rbac/engine/snapshot.rs:73— sea-orm-sync/src/rbac/engine/snapshot.rs:73-81 | src/rbac/engine/snapshot.rs:73-81 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/snapshot.rs` and `src/rbac/engine/snapshot.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 54 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. 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 (9 lines × 2) sea-orm-sync/src/schema/builder.rs:339— sea-orm-sync/src/schema/builder.rs:339-347 | src/schema/builder.rs:343-351 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (9 lines × 2) sea-orm-codegen/src/util.rs:5— sea-orm-codegen/src/util.rs:5-13 | sea-orm-macros/src/derives/util.rs:318-326 — before extracting anything, compare `sea-orm-codegen/src/util.rs` and `sea-orm-macros/src/derives/util.rs` as WHOLE FILES: 100% 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. 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. 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 (9 lines × 2) sea-orm-macros/src/derives/entity_loader.rs:816— sea-orm-macros/src/derives/entity_loader.rs:816-824 | sea-orm-macros/src/derives/entity_loader.rs:832-840 — both copies are in the same file, so extract the 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 (9 lines × 2) sea-orm-sync/src/query/combine.rs:201— sea-orm-sync/src/query/combine.rs:201-209 | src/query/combine.rs:201-209 — before extracting anything, compare `sea-orm-sync/src/query/combine.rs` and `src/query/combine.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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. 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 (9 lines × 2) sea-orm-sync/src/query/select.rs:358— sea-orm-sync/src/query/select.rs:358-366 | src/query/select.rs:358-366 — before extracting anything, compare `sea-orm-sync/src/query/select.rs` and `src/query/select.rs` as WHOLE FILES: 100% 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 2 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. 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. 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 (9 lines × 2) sea-orm-sync/src/database/mock.rs:72— sea-orm-sync/src/database/mock.rs:72-80 | src/database/mock.rs:72-80 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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) sea-orm-sync/src/database/restricted_connection.rs:447— sea-orm-sync/src/database/restricted_connection.rs:447-455 | sea-orm-sync/src/database/transaction.rs:174-182 — 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) sea-orm-sync/src/driver/rusqlite.rs:416— sea-orm-sync/src/driver/rusqlite.rs:416-424 | src/driver/rusqlite.rs:416-424 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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) sea-orm-sync/src/driver/rusqlite.rs:644— sea-orm-sync/src/driver/rusqlite.rs:644-652 | src/driver/rusqlite.rs:644-652 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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) sea-orm-sync/src/driver/sqlx_sqlite.rs:360— sea-orm-sync/src/driver/sqlx_sqlite.rs:360-368 | src/driver/sqlx_sqlite.rs:367-375 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_sqlite.rs` and `src/driver/sqlx_sqlite.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 198 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 `sea-orm-sync/src/driver/sqlx_sqlite.rs:360` 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) sea-orm-sync/src/entity/active_model.rs:799— sea-orm-sync/src/entity/active_model.rs:799-807 | src/entity/active_model.rs:807-815 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:799` 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) sea-orm-sync/src/entity/active_model.rs:834— sea-orm-sync/src/entity/active_model.rs:834-842 | src/entity/active_model.rs:842-850 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:834` 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) sea-orm-sync/src/entity/active_model_ex.rs:291— sea-orm-sync/src/entity/active_model_ex.rs:291-299 | src/entity/active_model_ex.rs:291-299 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/entity/compound.rs:149— sea-orm-sync/src/entity/compound.rs:149-157 | sea-orm-sync/src/executor/paginator.rs:110-118 — 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) sea-orm-sync/src/executor/cursor.rs:234— sea-orm-sync/src/executor/cursor.rs:234-242 | src/executor/cursor.rs:234-242 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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 (9 lines × 2) sea-orm-sync/src/executor/select_ext.rs:24— sea-orm-sync/src/executor/select_ext.rs:24-32 | src/executor/select_ext.rs:25-33 — before extracting anything, compare `sea-orm-sync/src/executor/select_ext.rs` and `src/executor/select_ext.rs` as WHOLE FILES: 98% 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 2 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. 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) sea-orm-sync/src/query/loader.rs:1403— sea-orm-sync/src/query/loader.rs:1403-1411 | src/query/loader.rs:1491-1499 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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) sea-orm-arrow/src/lib.rs:540— sea-orm-arrow/src/lib.rs:540-549 | sea-orm-arrow/src/lib.rs:554-563 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:540` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) sea-orm-arrow/src/lib.rs:1429— sea-orm-arrow/src/lib.rs:1429-1438 | sea-orm-arrow/src/lib.rs:1506-1515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-arrow/src/lib.rs:1429` 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) sea-orm-macros/src/derives/active_model.rs:27— sea-orm-macros/src/derives/active_model.rs:27-36 | sea-orm-macros/src/derives/model.rs:51-60 — 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 `sea-orm-macros/src/derives/active_model.rs:27` 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) sea-orm-macros/src/derives/entity_loader.rs:296— sea-orm-macros/src/derives/entity_loader.rs:296-305 | sea-orm-macros/src/derives/entity_loader.rs:348-357 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/entity_loader.rs: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-macros/src/derives/entity_loader.rs:346` calls `value`, `span` and `sea-orm-macros/src/derives/entity_loader.rs:294` 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) sea-orm-macros/src/derives/entity_loader.rs:292— sea-orm-macros/src/derives/entity_loader.rs:292-301 | sea-orm-macros/src/derives/entity_loader.rs:403-412 — both copies are in the same file, so extract the 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) sea-orm-macros/src/derives/entity_loader.rs:407— sea-orm-macros/src/derives/entity_loader.rs:407-416 | sea-orm-macros/src/derives/entity_loader.rs:459-468 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/entity_loader.rs:407` 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, `sea-orm-macros/src/derives/entity_loader.rs:457` calls `value`, `span` and `sea-orm-macros/src/derives/entity_loader.rs:405` 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) sea-orm-macros/src/derives/model_ex.rs:1006— sea-orm-macros/src/derives/model_ex.rs:1006-1015 | sea-orm-macros/src/derives/model_ex.rs:1212-1221 — both copies are in the same file, so extract the 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, `sea-orm-macros/src/derives/model_ex.rs:1223` calls `is_self_ref` and `sea-orm-macros/src/derives/model_ex.rs:1017` 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 × 2) sea-orm-sync/src/database/restricted_connection.rs:486— sea-orm-sync/src/database/restricted_connection.rs:486-495 | src/database/restricted_connection.rs:533-542 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 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. 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 (10 lines × 2) sea-orm-sync/src/database/transaction.rs:663— sea-orm-sync/src/database/transaction.rs:663-672 | src/database/transaction.rs:699-708 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:663` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:520— sea-orm-sync/src/driver/rusqlite.rs:520-529 | src/driver/rusqlite.rs:520-529 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:520` 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) sea-orm-sync/src/driver/sqlx_common.rs:102— sea-orm-sync/src/driver/sqlx_common.rs:102-111 | src/driver/sqlx_common.rs:104-113 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_common.rs` and `src/driver/sqlx_common.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 `sea-orm-sync/src/driver/sqlx_common.rs:102` 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) sea-orm-sync/src/entity/active_model.rs:784— sea-orm-sync/src/entity/active_model.rs:784-793 | src/entity/active_model.rs:792-801 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:784` 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 × 2) sea-orm-sync/src/entity/active_model.rs:818— sea-orm-sync/src/entity/active_model.rs:818-827 | src/entity/active_model.rs:826-835 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:818` 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 × 2) sea-orm-sync/src/entity/active_model_ex.rs:403— sea-orm-sync/src/entity/active_model_ex.rs:403-412 | src/entity/active_model_ex.rs:403-412 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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. 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 (10 lines × 2) sea-orm-sync/src/query/loader.rs:1463— sea-orm-sync/src/query/loader.rs:1463-1472 | src/query/loader.rs:1551-1560 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (10 lines × 2) sea-orm-sync/src/schema/builder.rs:56— sea-orm-sync/src/schema/builder.rs:56-65 | src/schema/builder.rs:56-65 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (10 lines × 2) sea-orm-sync/src/schema/entity.rs:193— sea-orm-sync/src/schema/entity.rs:193-202 | src/schema/entity.rs:193-202 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (10 lines × 2) src/database/restricted_connection.rs:493— src/database/restricted_connection.rs:493-502 | src/database/transaction.rs:192-201 — 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. 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 (10 lines × 2) sea-orm-sync/src/rbac/context.rs:264— sea-orm-sync/src/rbac/context.rs:264-273 | src/rbac/context.rs:276-285 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 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 `sea-orm-sync/src/rbac/context.rs:264` 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) sea-orm-macros/src/derives/column.rs:141— sea-orm-macros/src/derives/column.rs:141-150 | sea-orm-macros/src/derives/primary_key.rs:53-62 — 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) sea-orm-sync/src/database/db_connection.rs:655— sea-orm-sync/src/database/db_connection.rs:655-664 | src/database/db_connection.rs:705-714 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:655` 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) sea-orm-sync/src/driver/rusqlite.rs:123— sea-orm-sync/src/driver/rusqlite.rs:123-132 | src/driver/rusqlite.rs:123-132 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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) sea-orm-sync/src/entity/active_model_ex.rs:438— sea-orm-sync/src/entity/active_model_ex.rs:438-447 | src/entity/active_model_ex.rs:438-447 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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) sea-orm-sync/src/executor/cursor.rs:223— sea-orm-sync/src/executor/cursor.rs:223-232 | src/executor/cursor.rs:223-232 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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) sea-orm-sync/src/executor/paginator.rs:319— sea-orm-sync/src/executor/paginator.rs:319-328 | src/executor/paginator.rs:328-337 — before extracting anything, compare `sea-orm-sync/src/executor/paginator.rs` and `src/executor/paginator.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-cli/src/commands/generate.rs:226— sea-orm-cli/src/commands/generate.rs:226-237 | sea-orm-cli/src/commands/generate.rs:306-317 — both copies are in the same file, so extract the 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 `sea-orm-cli/src/commands/generate.rs:226` 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) sea-orm-macros/src/derives/case_style.rs:42— sea-orm-macros/src/derives/case_style.rs:42-53 | sea-orm-macros/src/strum/helpers/case_style.rs:40-51 — before extracting anything, compare `sea-orm-macros/src/derives/case_style.rs` and `sea-orm-macros/src/strum/helpers/case_style.rs` as WHOLE FILES: 100% 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 2 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. 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. 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 (12 lines × 2) sea-orm-sync/src/database/stream/query.rs:101— sea-orm-sync/src/database/stream/query.rs:101-112 | src/database/stream/query.rs:103-114 — before extracting anything, compare `sea-orm-sync/src/database/stream/query.rs` and `src/database/stream/query.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 `sea-orm-sync/src/database/stream/query.rs:101` 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) sea-orm-sync/src/database/stream/transaction.rs:94— sea-orm-sync/src/database/stream/transaction.rs:94-105 | src/database/stream/transaction.rs:95-106 — before extracting anything, compare `sea-orm-sync/src/database/stream/transaction.rs` and `src/database/stream/transaction.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 `sea-orm-sync/src/database/stream/transaction.rs:94` 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) sea-orm-sync/src/database/transaction.rs:676— sea-orm-sync/src/database/transaction.rs:676-687 | src/database/transaction.rs:712-723 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:676` 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 (12 lines × 2) sea-orm-sync/src/database/transaction.rs:691— sea-orm-sync/src/database/transaction.rs:691-702 | src/database/transaction.rs:727-738 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:691` 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 (12 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:329— sea-orm-sync/src/driver/rusqlite.rs:329-340 | src/driver/rusqlite.rs:329-340 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:329` 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) sea-orm-sync/src/driver/sqlx_postgres.rs:376— sea-orm-sync/src/driver/sqlx_postgres.rs:376-387 | src/driver/sqlx_postgres.rs:387-398 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_postgres.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 701 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 `sea-orm-sync/src/driver/sqlx_postgres.rs:376` 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) sea-orm-sync/src/entity/active_model.rs:717— sea-orm-sync/src/entity/active_model.rs:717-728 | src/entity/active_model.rs:725-736 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (12 lines × 2) sea-orm-sync/src/entity/active_model.rs:762— sea-orm-sync/src/entity/active_model.rs:762-773 | src/entity/active_model.rs:770-781 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (12 lines × 2) sea-orm-sync/src/entity/active_model.rs:880— sea-orm-sync/src/entity/active_model.rs:880-891 | src/entity/active_model.rs:888-899 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (12 lines × 2) sea-orm-sync/src/entity/base_entity.rs:322— sea-orm-sync/src/entity/base_entity.rs:322-333 | src/entity/base_entity.rs:325-336 — before extracting anything, compare `sea-orm-sync/src/entity/base_entity.rs` and `src/entity/base_entity.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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. 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 (12 lines × 2) sea-orm-sync/src/entity/base_entity.rs:1053— sea-orm-sync/src/entity/base_entity.rs:1053-1064 | src/entity/base_entity.rs:1075-1086 — before extracting anything, compare `sea-orm-sync/src/entity/base_entity.rs` and `src/entity/base_entity.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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. 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 (12 lines × 2) sea-orm-sync/src/executor/insert.rs:567— sea-orm-sync/src/executor/insert.rs:567-578 | src/executor/insert.rs:581-592 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:567` 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) sea-orm-sync/src/executor/paginator.rs:83— sea-orm-sync/src/executor/paginator.rs:83-94 | src/executor/paginator.rs:87-98 — before extracting anything, compare `sea-orm-sync/src/executor/paginator.rs` and `src/executor/paginator.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-sync/src/executor/select_ext.rs:48— sea-orm-sync/src/executor/select_ext.rs:48-59 | src/executor/select_ext.rs:50-61 — before extracting anything, compare `sea-orm-sync/src/executor/select_ext.rs` and `src/executor/select_ext.rs` as WHOLE FILES: 98% 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 2 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. 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. 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 (12 lines × 2) sea-orm-sync/src/executor/update.rs:178— sea-orm-sync/src/executor/update.rs:178-189 | src/executor/update.rs:184-195 — before extracting anything, compare `sea-orm-sync/src/executor/update.rs` and `src/executor/update.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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 `sea-orm-sync/src/executor/update.rs:178` 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) sea-orm-sync/src/rbac/schema.rs:31— sea-orm-sync/src/rbac/schema.rs:31-42 | src/rbac/schema.rs:31-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. 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 (12 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:433— sea-orm-sync/src/driver/rusqlite.rs:433-444 | src/driver/rusqlite.rs:433-444 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:433` 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) sea-orm-sync/src/driver/rusqlite.rs:630— sea-orm-sync/src/driver/rusqlite.rs:630-641 | src/driver/rusqlite.rs:630-641 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-sync/src/dynamic/entity.rs:66— sea-orm-sync/src/dynamic/entity.rs:66-77 | src/dynamic/entity.rs:66-77 — before extracting anything, compare `sea-orm-sync/src/dynamic/entity.rs` and `src/dynamic/entity.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-sync/src/entity/active_model_ex.rs:346— sea-orm-sync/src/entity/active_model_ex.rs:346-357 | src/entity/active_model_ex.rs:346-357 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-sync/src/executor/query.rs:1624— sea-orm-sync/src/executor/query.rs:1624-1635 | src/executor/query.rs:1626-1637 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) sea-orm-sync/src/query/delete.rs:221— sea-orm-sync/src/query/delete.rs:221-232 | src/query/delete.rs:221-232 — before extracting anything, compare `sea-orm-sync/src/query/delete.rs` and `src/query/delete.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) src/driver/sqlx_mysql.rs:394— src/driver/sqlx_mysql.rs:394-405 | src/driver/sqlx_postgres.rs:435-446 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/driver/sqlx_mysql.rs:394` 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.
+ 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×20
FileTooLong: executor/query.rs sea-orm-sync/src/executor/query.rs— FileTooLong — 1289 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 789 over it, 2.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: executor/query.rs src/executor/query.rs— FileTooLong — 1289 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 789 over it, 2.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: query/loader.rs src/query/loader.rs— FileTooLong — 1164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 664 over it, 2.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs sea-orm-arrow/src/lib.rs— FileTooLong — 1129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 44 free functions. The bar is 500 significant lines; this is 629 over it, 2.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: derives/model_ex.rs sea-orm-macros/src/derives/model_ex.rs— FileTooLong — 1089 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 589 over it, 2.18× 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/loader.rs sea-orm-sync/src/query/loader.rs— FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 582 over it, 2.16× 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: derives/active_model_ex.rs sea-orm-macros/src/derives/active_model_ex.rs— FileTooLong — 1011 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 511 over it, 2.02× 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: database/transaction.rs src/database/transaction.rs— FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: DatabaseTransaction (8 blocks, 37-903). The bar is 500 significant lines; this is 192 over it, 1.38× 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: driver/sqlx_postgres.rs src/driver/sqlx_postgres.rs— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: entity/writer.rs sea-orm-codegen/src/entity/writer.rs— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: EntityWriter (2 blocks, 26-962). The bar is 500 significant lines; this is 180 over it, 1.36× 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: derives/entity_loader.rs sea-orm-macros/src/derives/entity_loader.rs— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 180 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: driver/sqlx_postgres.rs sea-orm-sync/src/driver/sqlx_postgres.rs— FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 169 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: database/db_connection.rs src/database/db_connection.rs— FileTooLong — 654 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: DatabaseConnection (11 blocks, 35-946). The bar is 500 significant lines; this is 154 over it, 1.31× 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: database/transaction.rs sea-orm-sync/src/database/transaction.rs— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: DatabaseTransaction (8 blocks, 37-848). The bar is 500 significant lines; this is 131 over it, 1.26× 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: database/db_connection.rs sea-orm-sync/src/database/db_connection.rs— FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: DatabaseConnection (11 blocks, 35-893). The bar is 500 significant lines; this is 108 over it, 1.22× 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: derives/active_enum.rs sea-orm-macros/src/derives/active_enum.rs— FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: ActiveEnum (2 blocks, 8-888). The bar is 500 significant lines; this is 98 over it, 1.20× 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: entity/active_model.rs src/entity/active_model.rs— FileTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: ActiveModelTrait (31-1046). The bar is 500 significant lines; this is 95 over it, 1.19× 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: entity/active_model.rs sea-orm-sync/src/entity/active_model.rs— FileTooLong — 584 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: ActiveModelTrait (30-1036). The bar is 500 significant lines; this is 84 over it, 1.17× 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.
TodoComment tests/partial_model_nested/nested_alias.rs:52— // TODO: init utils — 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 sea-orm-sync/tests/partial_model_nested/nested_alias.rs:50— // TODO: init utils — 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 src/schema/builder.rs:410— // TODO add enum variants — 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 sea-orm-sync/src/schema/builder.rs:406— // TODO add enum variants — 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 src/query/loader.rs:10— // TODO: Replace DynIden::inner with a better API that without clone — 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 sea-orm-sync/src/query/loader.rs:10— // TODO: Replace DynIden::inner with a better API that without clone — 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 src/driver/rusqlite.rs:209— // TODO handle disable_statement_logging — 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 sea-orm-sync/src/driver/rusqlite.rs:209— // TODO handle disable_statement_logging — 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 sea-orm-macros/src/derives/active_enum.rs:823— // TODO: Use DynIden constructor — 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 sea-orm-macros/src/derives/active_model_ex.rs:1306— // TODO: Batch save? — 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 examples/react_admin/backend/src/workers/downloader.rs:25— // TODO: Some actual work goes here... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment examples/loco_starter/src/workers/downloader.rs:25— // TODO: Some actual work goes here... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment examples/loco_seaography/src/workers/downloader.rs:25— // TODO: Some actual work goes here... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment examples/loco_example/tests/requests/notes.rs:8— // TODO: see how to dedup / extract this to app-local test utils — 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.
Duplicated block (15 lines × 2) sea-orm-sync/src/database/db_connection.rs:523— sea-orm-sync/src/database/db_connection.rs:523-537 | sea-orm-sync/src/database/db_connection.rs:569-583 — both copies are in the same file, so extract the 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 `sea-orm-sync/src/database/db_connection.rs:523` 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 (15 lines × 2) sea-orm-sync/src/database/db_connection.rs:837— sea-orm-sync/src/database/db_connection.rs:837-851 | src/database/db_connection.rs:890-904 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:837` 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 (15 lines × 2) sea-orm-sync/src/database/mod.rs:169— sea-orm-sync/src/database/mod.rs:169-183 | src/database/mod.rs:185-199 — before extracting anything, compare `sea-orm-sync/src/database/mod.rs` and `src/database/mod.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 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. 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 (15 lines × 2) sea-orm-sync/src/driver/sqlx_mysql.rs:341— sea-orm-sync/src/driver/sqlx_mysql.rs:341-355 | src/driver/sqlx_mysql.rs:348-362 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `src/driver/sqlx_mysql.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 306 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 `sea-orm-sync/src/driver/sqlx_mysql.rs:341` 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) sea-orm-sync/src/entity/relation.rs:210— sea-orm-sync/src/entity/relation.rs:210-224 | src/entity/relation.rs:210-224 — before extracting anything, compare `sea-orm-sync/src/entity/relation.rs` and `src/entity/relation.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 (15 lines × 2) sea-orm-sync/src/entity/relation.rs:468— sea-orm-sync/src/entity/relation.rs:468-482 | src/entity/relation.rs:468-482 — before extracting anything, compare `sea-orm-sync/src/entity/relation.rs` and `src/entity/relation.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 (15 lines × 2) sea-orm-sync/src/executor/cursor.rs:440— sea-orm-sync/src/executor/cursor.rs:440-454 | src/executor/cursor.rs:442-456 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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 `sea-orm-sync/src/executor/cursor.rs:440` 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) sea-orm-sync/src/query/loader.rs:1237— sea-orm-sync/src/query/loader.rs:1237-1251 | src/query/loader.rs:1325-1339 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (15 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:339— sea-orm-sync/src/rbac/engine/mod.rs:339-353 | src/rbac/engine/mod.rs:339-353 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (15 lines × 2) sea-orm-sync/src/schema/builder.rs:396— sea-orm-sync/src/schema/builder.rs:396-410 | src/schema/builder.rs:400-414 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs: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 (15 lines × 2) src/driver/sqlx_mysql.rs:97— src/driver/sqlx_mysql.rs:97-111 | src/driver/sqlx_sqlite.rs:107-123 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_sqlite.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 145 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/driver/sqlx_mysql.rs:97` 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) sea-orm-sync/src/value/with_chrono.rs:36— sea-orm-sync/src/value/with_chrono.rs:36-50 | src/value/with_chrono.rs:36-50 — before extracting anything, compare `sea-orm-sync/src/value/with_chrono.rs` and `src/value/with_chrono.rs` as WHOLE FILES: 100% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) sea-orm-sync/src/executor/cursor.rs:51— sea-orm-sync/src/executor/cursor.rs:51-65 | src/executor/cursor.rs:51-65 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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 (15 lines × 2) sea-orm-sync/src/tests_cfg/cake_filling.rs:35— sea-orm-sync/src/tests_cfg/cake_filling.rs:35-49 | src/tests_cfg/cake_filling.rs:35-49 — before extracting anything, compare `sea-orm-sync/src/tests_cfg/cake_filling.rs` and `src/tests_cfg/cake_filling.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/tests_cfg/cake_filling.rs:35` 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 (5 lines × 2) sea-orm-sync/src/database/db_connection.rs:177— sea-orm-sync/src/database/db_connection.rs:177-181 | src/database/db_connection.rs:184-188 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/database/db_connection.rs:251— sea-orm-sync/src/database/db_connection.rs:251-255 | src/database/db_connection.rs:264-268 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/database/db_connection.rs:281— sea-orm-sync/src/database/db_connection.rs:281-285 | src/database/db_connection.rs:300-304 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/database/db_connection.rs:812— sea-orm-sync/src/database/db_connection.rs:812-816 | src/database/db_connection.rs:865-869 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/entity/active_model_ex.rs:200— sea-orm-sync/src/entity/active_model_ex.rs:200-204 | src/entity/active_model_ex.rs:200-204 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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 `sea-orm-sync/src/entity/active_model_ex.rs:200` 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 (5 lines × 2) sea-orm-sync/src/entity/active_model_ex.rs:266— sea-orm-sync/src/entity/active_model_ex.rs:266-270 | src/entity/active_model_ex.rs:266-270 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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 `sea-orm-sync/src/entity/active_model_ex.rs:266` 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 (5 lines × 2) sea-orm-sync/src/executor/update.rs:140— sea-orm-sync/src/executor/update.rs:140-144 | src/executor/update.rs:145-149 — before extracting anything, compare `sea-orm-sync/src/executor/update.rs` and `src/executor/update.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 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 `sea-orm-sync/src/executor/update.rs:140` 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) sea-orm-sync/src/database/restricted_connection.rs:547— sea-orm-sync/src/database/restricted_connection.rs:547-551 | src/database/restricted_connection.rs:594-598 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/database/restricted_connection.rs:553— sea-orm-sync/src/database/restricted_connection.rs:553-557 | src/database/restricted_connection.rs:600-604 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:457— sea-orm-sync/src/driver/rusqlite.rs:457-461 | src/driver/rusqlite.rs:457-461 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/query/loader.rs:1443— sea-orm-sync/src/query/loader.rs:1443-1447 | src/query/loader.rs:1531-1535 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-sync/src/rbac/context.rs:149— sea-orm-sync/src/rbac/context.rs:149-153 | src/rbac/context.rs:157-161 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) sea-orm-arrow/src/lib.rs:430— sea-orm-arrow/src/lib.rs:430-434 | sea-orm-arrow/src/lib.rs:438-442 — both copies are in the same file, so extract the 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) sea-orm-arrow/src/lib.rs:595— sea-orm-arrow/src/lib.rs:595-599 | sea-orm-arrow/src/lib.rs:601-605 — both copies are in the same file, so extract the 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 (4 members, 50+ identical tokens) · ×13
Members sharing a duplicated core (4 members, 50+ identical tokens) sea-orm-macros/src/derives/active_model_ex.rs:1116— sea-orm-macros/src/derives/active_model_ex.rs:1116-1170 | sea-orm-macros/src/derives/active_model_ex.rs:1172-1189 | sea-orm-macros/src/derives/active_model_ex.rs:1349-1386 | sea-orm-macros/src/derives/active_model_ex.rs:1388-1404 — 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) sea-orm-sync/src/database/mock.rs:232— sea-orm-sync/src/database/mock.rs:232-251 | sea-orm-sync/src/database/proxy.rs:195-214 | src/database/mock.rs:232-251 | src/database/proxy.rs:196-215 — 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) sea-orm-sync/src/driver/rusqlite.rs:328— sea-orm-sync/src/driver/rusqlite.rs:328-344 | sea-orm-sync/src/driver/rusqlite.rs:501-516 | src/driver/rusqlite.rs:328-344 | src/driver/rusqlite.rs:501-516 — 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) sea-orm-sync/src/driver/rusqlite.rs:348— sea-orm-sync/src/driver/rusqlite.rs:348-361 | sea-orm-sync/src/driver/rusqlite.rs:519-531 | src/driver/rusqlite.rs:348-361 | src/driver/rusqlite.rs:519-531 — 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) sea-orm-sync/src/driver/sqlx_mysql.rs:338— sea-orm-sync/src/driver/sqlx_mysql.rs:338-359 | sea-orm-sync/src/driver/sqlx_postgres.rs:373-391 | src/driver/sqlx_mysql.rs:345-366 | src/driver/sqlx_postgres.rs:384-403 — 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) sea-orm-sync/src/entity/column.rs:437— sea-orm-sync/src/entity/column.rs:437-448 | sea-orm-sync/src/entity/column.rs:474-485 | src/entity/column.rs:437-448 | src/entity/column.rs:474-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) sea-orm-sync/src/entity/link.rs:38— sea-orm-sync/src/entity/link.rs:38-66 | sea-orm-sync/src/query/join.rs:122-165 | src/entity/link.rs:38-66 | src/query/join.rs:122-165 — 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) sea-orm-sync/src/executor/cursor.rs:313— sea-orm-sync/src/executor/cursor.rs:313-327 | sea-orm-sync/src/executor/cursor.rs:340-354 | src/executor/cursor.rs:315-329 | src/executor/cursor.rs:342-356 — 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) sea-orm-sync/src/executor/cursor.rs:438— sea-orm-sync/src/executor/cursor.rs:438-454 | sea-orm-sync/src/executor/cursor.rs:493-522 | src/executor/cursor.rs:440-456 | src/executor/cursor.rs:495-524 — 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) sea-orm-sync/src/executor/delete.rs:151— sea-orm-sync/src/executor/delete.rs:151-166 | sea-orm-sync/src/executor/delete.rs:175-190 | src/executor/delete.rs:151-168 | src/executor/delete.rs:177-194 — 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) sea-orm-sync/src/executor/insert.rs:498— sea-orm-sync/src/executor/insert.rs:498-523 | sea-orm-sync/src/executor/insert.rs:566-585 | src/executor/insert.rs:509-537 | src/executor/insert.rs:580-600 — 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) sea-orm-sync/src/executor/select.rs:909— sea-orm-sync/src/executor/select.rs:909-924 | sea-orm-sync/src/executor/select.rs:1202-1217 | src/executor/select.rs:924-939 | src/executor/select.rs:1228-1243 — 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) sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:9— sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:9-29 | sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:36-61 | src/rbac/engine/role_hierarchy_impl.rs:9-29 | src/rbac/engine/role_hierarchy_impl.rs:36-61 — 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 (7 corresponding lines) · ×13
Edited copy of a member (7 corresponding lines) sea-orm-sync/src/executor/consolidate.rs:67— sea-orm-sync/src/executor/consolidate.rs:67-73 | src/executor/consolidate.rs:67-73 — 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) sea-orm-sync/src/executor/consolidate.rs:78— sea-orm-sync/src/executor/consolidate.rs:78-84 | src/executor/consolidate.rs:78-84 — 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) sea-orm-sync/src/schema/entity.rs:113— sea-orm-sync/src/schema/entity.rs:113-119 | src/schema/entity.rs:113-119 — 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) sea-orm-sync/src/value/text_uuid.rs:48— sea-orm-sync/src/value/text_uuid.rs:48-54 | src/value/text_uuid.rs:48-54 — 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) src/entity/active_model.rs:452— src/entity/active_model.rs:452-458 | sea-orm-sync/src/entity/active_model.rs:444-450 — 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) sea-orm-sync/src/database/restricted_connection.rs:308— sea-orm-sync/src/database/restricted_connection.rs:308-314 | src/database/restricted_connection.rs:323-332 — 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) sea-orm-sync/src/database/restricted_connection.rs:320— sea-orm-sync/src/database/restricted_connection.rs:320-326 | src/database/restricted_connection.rs:338-344 — 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) sea-orm-sync/src/database/restricted_connection.rs:377— sea-orm-sync/src/database/restricted_connection.rs:377-383 | src/database/restricted_connection.rs:405-414 — 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) sea-orm-sync/src/database/restricted_connection.rs:295— sea-orm-sync/src/database/restricted_connection.rs:295-301 | src/database/restricted_connection.rs:310-316 — 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) sea-orm-sync/src/database/restricted_connection.rs:389— sea-orm-sync/src/database/restricted_connection.rs:389-395 | src/database/restricted_connection.rs:420-426 — 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) sea-orm-sync/src/database/restricted_connection.rs:364— sea-orm-sync/src/database/restricted_connection.rs:364-370 | src/database/restricted_connection.rs:392-398 — 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) sea-orm-migration/src/migrator.rs:155— sea-orm-migration/src/migrator.rs:155-161 | sea-orm-migration/src/migrator/with_self.rs:113-120 — 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) sea-orm-migration/src/migrator.rs:170— sea-orm-migration/src/migrator.rs:170-176 | sea-orm-migration/src/migrator/with_self.rs:129-136 — 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.
Duplicated block (13 lines × 2) sea-orm-arrow/src/lib.rs:958— sea-orm-arrow/src/lib.rs:958-970 | sea-orm-arrow/src/lib.rs:1250-1262 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:958` 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) sea-orm-sync/src/database/tracing_spans.rs:51— sea-orm-sync/src/database/tracing_spans.rs:51-63 | src/database/tracing_spans.rs:51-63 — before extracting anything, compare `sea-orm-sync/src/database/tracing_spans.rs` and `src/database/tracing_spans.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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. 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 (13 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:615— sea-orm-sync/src/driver/rusqlite.rs:615-627 | src/driver/rusqlite.rs:615-627 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (13 lines × 2) sea-orm-sync/src/executor/query.rs:1703— sea-orm-sync/src/executor/query.rs:1703-1715 | src/executor/query.rs:1705-1717 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (13 lines × 2) sea-orm-sync/src/query/loader.rs:1217— sea-orm-sync/src/query/loader.rs:1217-1229 | src/query/loader.rs:1305-1317 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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 `sea-orm-sync/src/query/loader.rs:1217` 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 (13 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:135— sea-orm-sync/src/rbac/engine/mod.rs:135-147 | src/rbac/engine/mod.rs:135-147 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (13 lines × 2) sea-orm-sync/src/entity/identity.rs:72— sea-orm-sync/src/entity/identity.rs:72-84 | src/entity/identity.rs:72-84 — before extracting anything, compare `sea-orm-sync/src/entity/identity.rs` and `src/entity/identity.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 (13 lines × 2) sea-orm-sync/src/database/mock.rs:399— sea-orm-sync/src/database/mock.rs:399-411 | src/database/mock.rs:399-411 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) sea-orm-sync/src/database/mock.rs:413— sea-orm-sync/src/database/mock.rs:413-425 | src/database/mock.rs:413-425 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) sea-orm-sync/src/entity/active_model.rs:739— sea-orm-sync/src/entity/active_model.rs:739-751 | src/entity/active_model.rs:747-759 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) sea-orm-sync/src/entity/active_model_ex.rs:384— sea-orm-sync/src/entity/active_model_ex.rs:384-396 | src/entity/active_model_ex.rs:384-396 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) sea-orm-sync/src/driver/mock.rs:267— sea-orm-sync/src/driver/mock.rs:267-279 | sea-orm-sync/src/driver/proxy.rs:146-158 — 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 `sea-orm-sync/src/driver/mock.rs:267` 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) sea-orm-sync/src/tests_cfg/entity_linked.rs:46— sea-orm-sync/src/tests_cfg/entity_linked.rs:46-58 | src/tests_cfg/entity_linked.rs:46-58 — before extracting anything, compare `sea-orm-sync/src/tests_cfg/entity_linked.rs` and `src/tests_cfg/entity_linked.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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.
AXH1 · Runtime security headers· Runtime security header not set · ×11
Runtime security header not set: content-security-policy — The live app's responses did not include content-security-policy (restricts the sources a page may load — mitigates XSS/injection). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-embedder-policy — The live app's responses did not include cross-origin-embedder-policy (recommended by the OWASP Secure Headers Project (value: require-corp)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-opener-policy — The live app's responses did not include cross-origin-opener-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: cross-origin-resource-policy — The live app's responses did not include cross-origin-resource-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: permissions-policy — The live app's responses did not include permissions-policy (restricts powerful browser features (camera, geolocation, …)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: referrer-policy — The live app's responses did not include referrer-policy (limits referrer leakage to third parties). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: strict-transport-security — The live app's responses did not include strict-transport-security (forces HTTPS on subsequent requests — mitigates downgrade/MITM). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-content-type-options — The live app's responses did not include x-content-type-options (stops MIME-sniffing (expects 'nosniff')). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-dns-prefetch-control — The live app's responses did not include x-dns-prefetch-control (recommended by the OWASP Secure Headers Project (value: off)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-frame-options — The live app's responses did not include x-frame-options (blocks clickjacking via framing (or use CSP frame-ancestors)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
Runtime security header not set: x-permitted-cross-domain-policies — The live app's responses did not include x-permitted-cross-domain-policies (recommended by the OWASP Secure Headers Project (value: none)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
FunctionTooLong: sea_orm_sync::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row sea-orm-sync/src/driver/sqlx_postgres.rs:437— FunctionTooLong — sea_orm_sync::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row runs 381 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 281 over it, 3.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row src/driver/sqlx_postgres.rs:450— FunctionTooLong — sea_orm::driver::sqlx_postgres::from_sqlx_postgres_row_to_proxy_row runs 381 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 281 over it, 3.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_macros::derives::entity_model::expand_derive_entity_model sea-orm-macros/src/derives/entity_model.rs:16— FunctionTooLong — sea_orm_macros::derives::entity_model::expand_derive_entity_model runs 375 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 275 over it, 3.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_cli::commands::generate::run_generate_command sea-orm-cli/src/commands/generate.rs:116— FunctionTooLong — sea_orm_cli::commands::generate::run_generate_command runs 238 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 138 over it, 2.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.
FunctionTooLong: sea_orm_arrow::option_values_to_arrow_array sea-orm-arrow/src/lib.rs:977— FunctionTooLong — sea_orm_arrow::option_values_to_arrow_array runs 226 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_arrow::values_to_arrow_array sea-orm-arrow/src/lib.rs:695— FunctionTooLong — sea_orm_arrow::values_to_arrow_array runs 217 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_macros::derives::entity_loader::expand_entity_loader sea-orm-macros/src/derives/entity_loader.rs:715— FunctionTooLong — sea_orm_macros::derives::entity_loader::expand_entity_loader runs 208 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_sync::driver::sqlx_mysql::from_sqlx_mysql_row_to_proxy_row sea-orm-sync/src/driver/sqlx_mysql.rs:401— FunctionTooLong — sea_orm_sync::driver::sqlx_mysql::from_sqlx_mysql_row_to_proxy_row runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm::driver::sqlx_mysql::from_sqlx_mysql_row_to_proxy_row src/driver/sqlx_mysql.rs:409— FunctionTooLong — sea_orm::driver::sqlx_mysql::from_sqlx_mysql_row_to_proxy_row runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_arrow::arrow_array_to_value sea-orm-arrow/src/lib.rs:49— FunctionTooLong — sea_orm_arrow::arrow_array_to_value runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: sea_orm_macros::derives::model_ex::expand_sea_orm_model sea-orm-macros/src/derives/model_ex.rs:21— FunctionTooLong — sea_orm_macros::derives::model_ex::expand_sea_orm_model runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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· Edited copy of a member (8 corresponding lines) · ×11
Edited copy of a member (8 corresponding lines) sea-orm-sync/src/entity/relation.rs:577— sea-orm-sync/src/entity/relation.rs:577-584 | src/entity/relation.rs:577-584 — 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) sea-orm-sync/src/executor/consolidate.rs:15— sea-orm-sync/src/executor/consolidate.rs:15-22 | src/executor/consolidate.rs:15-22 — 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) sea-orm-sync/src/query/helper.rs:900— sea-orm-sync/src/query/helper.rs:900-907 | src/query/helper.rs:900-907 — 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) sea-orm-sync/src/query/helper.rs:915— sea-orm-sync/src/query/helper.rs:915-922 | src/query/helper.rs:915-922 — 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) sea-orm-sync/src/entity/active_value.rs:621— sea-orm-sync/src/entity/active_value.rs:621-628 | src/entity/active_value.rs:621-628 — 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) sea-orm-sync/src/entity/relation.rs:566— sea-orm-sync/src/entity/relation.rs:566-573 | src/entity/relation.rs:566-573 — 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) sea-orm-sync/src/executor/insert.rs:205— sea-orm-sync/src/executor/insert.rs:205-212 | src/executor/insert.rs:205-212 — 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) sea-orm-sync/src/database/connection.rs:125— sea-orm-sync/src/database/connection.rs:125-132 | src/database/connection.rs: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) sea-orm-migration/src/migrator.rs:109— sea-orm-migration/src/migrator.rs:109-116 | sea-orm-migration/src/migrator/with_self.rs:65-73 — 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) sea-orm-migration/src/migrator.rs:122— sea-orm-migration/src/migrator.rs:122-129 | sea-orm-migration/src/migrator/with_self.rs:79-87 — 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) sea-orm-sync/src/tests_cfg/entity_linked.rs:69— sea-orm-sync/src/tests_cfg/entity_linked.rs:69-76 | src/tests_cfg/entity_linked.rs:69-76 — 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.
Duplicated block (20 lines × 2) sea-orm-macros/src/derives/model_ex.rs:681— sea-orm-macros/src/derives/model_ex.rs:681-700 | sea-orm-macros/src/derives/model_ex.rs:1054-1073 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/model_ex.rs:681` 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 lines × 2) sea-orm-sync/src/database/db_connection.rs:134— sea-orm-sync/src/database/db_connection.rs:134-153 | src/database/db_connection.rs:134-153 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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. 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 (20 lines × 2) sea-orm-sync/src/database/db_connection.rs:782— sea-orm-sync/src/database/db_connection.rs:782-801 | src/database/db_connection.rs:835-854 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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. 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 (20 lines × 2) sea-orm-sync/src/entity/active_model.rs:850— sea-orm-sync/src/entity/active_model.rs:850-869 | src/entity/active_model.rs:858-877 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (20 lines × 2) sea-orm-sync/src/query/join.rs:205— sea-orm-sync/src/query/join.rs:205-224 | src/query/join.rs:205-224 — before extracting anything, compare `sea-orm-sync/src/query/join.rs` and `src/query/join.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 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. 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 (20 lines × 2) sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:10— sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:10-29 | src/rbac/engine/role_hierarchy_impl.rs:10-29 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs` and `src/rbac/engine/role_hierarchy_impl.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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. 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 (20 lines × 2) sea-orm-sync/src/rbac/engine/snapshot.rs:19— sea-orm-sync/src/rbac/engine/snapshot.rs:19-38 | src/rbac/engine/snapshot.rs:19-38 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/snapshot.rs` and `src/rbac/engine/snapshot.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 54 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. 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 (20 lines × 2) sea-orm-sync/src/schema/builder.rs:621— sea-orm-sync/src/schema/builder.rs:621-640 | src/schema/builder.rs:630-649 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (20 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:589— sea-orm-sync/src/driver/rusqlite.rs:589-608 | src/driver/rusqlite.rs:589-608 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (20 lines × 2) sea-orm-sync/src/executor/query.rs:76— sea-orm-sync/src/executor/query.rs:76-95 | src/executor/query.rs:76-95 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (20 lines × 2) sea-orm-sync/src/database/stream/metric.rs:53— sea-orm-sync/src/database/stream/metric.rs:53-72 | src/database/stream/metric.rs:55-74 — before extracting anything, compare `sea-orm-sync/src/database/stream/metric.rs` and `src/database/stream/metric.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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. 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 (17 lines × 2) sea-orm-codegen/src/entity/base_entity.rs:135— sea-orm-codegen/src/entity/base_entity.rs:135-151 | sea-orm-codegen/src/entity/base_entity.rs:193-209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-codegen/src/entity/base_entity.rs:135` 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) sea-orm-macros/src/derives/derive_iden.rs:57— sea-orm-macros/src/derives/derive_iden.rs:57-73 | sea-orm-macros/src/derives/derive_iden.rs:112-128 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/derive_iden.rs: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 (17 lines × 2) sea-orm-sync/src/database/transaction.rs:706— sea-orm-sync/src/database/transaction.rs:706-722 | src/database/transaction.rs:742-758 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:706` 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 lines × 2) sea-orm-sync/src/dynamic/entity.rs:48— sea-orm-sync/src/dynamic/entity.rs:48-64 | src/dynamic/entity.rs:48-64 — before extracting anything, compare `sea-orm-sync/src/dynamic/entity.rs` and `src/dynamic/entity.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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. 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 (17 lines × 2) sea-orm-sync/src/entity/column.rs:634— sea-orm-sync/src/entity/column.rs:634-650 | src/entity/column.rs:634-650 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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. 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 (17 lines × 2) sea-orm-sync/src/executor/query.rs:385— sea-orm-sync/src/executor/query.rs:385-401 | src/executor/query.rs:385-401 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (17 lines × 2) sea-orm-sync/src/query/loader.rs:1063— sea-orm-sync/src/query/loader.rs:1063-1079 | src/query/loader.rs:1147-1163 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (17 lines × 2) sea-orm-sync/src/query/util.rs:96— sea-orm-sync/src/query/util.rs:96-112 | src/query/util.rs:96-112 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (17 lines × 2) src/database/db_connection.rs:562— src/database/db_connection.rs:562-578 | src/database/db_connection.rs:617-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/database/db_connection.rs:562` 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 (17 lines × 2) sea-orm-sync/src/executor/paginator.rs:338— sea-orm-sync/src/executor/paginator.rs:338-354 | src/executor/paginator.rs:347-363 — before extracting anything, compare `sea-orm-sync/src/executor/paginator.rs` and `src/executor/paginator.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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. 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 (17 lines × 2) sea-orm-sync/src/query/insert.rs:534— sea-orm-sync/src/query/insert.rs:534-550 | src/query/insert.rs:534-550 — before extracting anything, compare `sea-orm-sync/src/query/insert.rs` and `src/query/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 163 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) sea-orm-codegen/src/entity/writer/dense.rs:194— sea-orm-codegen/src/entity/writer/dense.rs:194-209 | sea-orm-codegen/src/entity/writer/frontend.rs:87-102 — 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 `sea-orm-codegen/src/entity/writer/dense.rs:194` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-codegen/src/entity/writer/dense.rs:193` calls `as_str` and `sea-orm-codegen/src/entity/writer/frontend.rs:86` 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 (16 lines × 2) sea-orm-macros/src/derives/case_style.rs:60— sea-orm-macros/src/derives/case_style.rs:60-75 | sea-orm-macros/src/strum/helpers/case_style.rs:58-73 — before extracting anything, compare `sea-orm-macros/src/derives/case_style.rs` and `sea-orm-macros/src/strum/helpers/case_style.rs` as WHOLE FILES: 100% 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 2 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. 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. 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 (16 lines × 2) sea-orm-macros/src/derives/column.rs:32— sea-orm-macros/src/derives/column.rs:32-47 | sea-orm-macros/src/derives/column.rs:104-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) sea-orm-sync/src/database/db_connection.rs:724— sea-orm-sync/src/database/db_connection.rs:724-739 | src/database/db_connection.rs:777-792 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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. 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 (16 lines × 2) sea-orm-sync/src/database/db_connection.rs:747— sea-orm-sync/src/database/db_connection.rs:747-762 | src/database/db_connection.rs:800-815 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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. 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 (16 lines × 2) sea-orm-sync/src/entity/relation.rs:362— sea-orm-sync/src/entity/relation.rs:362-377 | src/entity/relation.rs:362-377 — before extracting anything, compare `sea-orm-sync/src/entity/relation.rs` and `src/entity/relation.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 (16 lines × 2) sea-orm-sync/src/entity/relation.rs:380— sea-orm-sync/src/entity/relation.rs:380-395 | src/entity/relation.rs:380-395 — before extracting anything, compare `sea-orm-sync/src/entity/relation.rs` and `src/entity/relation.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. 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 (16 lines × 2) sea-orm-sync/src/executor/cursor.rs:461— sea-orm-sync/src/executor/cursor.rs:461-476 | src/executor/cursor.rs:463-478 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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 (16 lines × 2) sea-orm-sync/src/schema/builder.rs:489— sea-orm-sync/src/schema/builder.rs:489-504 | src/schema/builder.rs:495-510 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:489` 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 (16 lines × 2) sea-orm-sync/src/schema/entity.rs:126— sea-orm-sync/src/schema/entity.rs:126-141 | src/schema/entity.rs:126-141 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (16 lines × 2) sea-orm-sync/src/query/insert.rs:467— sea-orm-sync/src/query/insert.rs:467-482 | src/query/insert.rs:467-482 — before extracting anything, compare `sea-orm-sync/src/query/insert.rs` and `src/query/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 163 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) sea-orm-sync/src/database/stream/metric.rs:95— sea-orm-sync/src/database/stream/metric.rs:95-108 | src/database/stream/metric.rs:97-110 — before extracting anything, compare `sea-orm-sync/src/database/stream/metric.rs` and `src/database/stream/metric.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 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. 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 (14 lines × 2) sea-orm-sync/src/dynamic/execute.rs:57— sea-orm-sync/src/dynamic/execute.rs:57-70 | src/dynamic/execute.rs:57-70 — before extracting anything, compare `sea-orm-sync/src/dynamic/execute.rs` and `src/dynamic/execute.rs` as WHOLE FILES: 91% 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 2 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. 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. 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 (14 lines × 2) sea-orm-sync/src/entity/active_model.rs:692— sea-orm-sync/src/entity/active_model.rs:692-705 | src/entity/active_model.rs:700-713 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:692` 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 × 2) sea-orm-sync/src/entity/active_model.rs:979— sea-orm-sync/src/entity/active_model.rs:979-992 | src/entity/active_model.rs:987-1000 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) sea-orm-sync/src/query/delete.rs:202— sea-orm-sync/src/query/delete.rs:202-215 | src/query/delete.rs:202-215 — before extracting anything, compare `sea-orm-sync/src/query/delete.rs` and `src/query/delete.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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. 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 (14 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:150— sea-orm-sync/src/rbac/engine/mod.rs:150-163 | src/rbac/engine/mod.rs:150-163 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (14 lines × 2) sea-orm-sync/src/database/db_connection.rs:383— sea-orm-sync/src/database/db_connection.rs:383-396 | src/database/db_connection.rs:412-425 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:383` 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 × 2) sea-orm-sync/src/query/util.rs:42— sea-orm-sync/src/query/util.rs:42-55 | src/query/util.rs:42-55 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (14 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:205— sea-orm-sync/src/rbac/engine/mod.rs:205-218 | src/rbac/engine/mod.rs:205-218 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) src/driver/mock.rs:268— src/driver/mock.rs:268-281 | src/driver/proxy.rs:146-159 — 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 `src/driver/mock.rs:268` 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) sea-orm-migration/src/manager.rs:150— sea-orm-migration/src/manager.rs:150-163 | sea-orm-migration/src/manager.rs:181-194 — both copies are in the same file, so extract the 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 `sea-orm-migration/src/manager.rs:150` 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.
MethodTooLong: EntityTransformer.transform sea-orm-codegen/src/entity/transformer.rs:12— MethodTooLong — transform runs 219 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: EntitySchemaInfo.sync sea-orm-sync/src/schema/builder.rs:390— MethodTooLong — sync runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: EntitySchemaInfo.sync src/schema/builder.rs:394— MethodTooLong — sync runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: DeriveRelation.impl_relation_trait sea-orm-macros/src/derives/relation.rs:44— MethodTooLong — impl_relation_trait runs 146 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ActiveEnum.new sea-orm-macros/src/derives/active_enum.rs:129— MethodTooLong — new runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DeriveActiveModel.impl_from_json sea-orm-macros/src/derives/active_model.rs:311— MethodTooLong — impl_from_json runs 128 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RelationAttr.from_attr sea-orm-macros/src/derives/active_model_ex.rs:34— MethodTooLong — from_attr runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DerivePartialModel.new sea-orm-macros/src/derives/partial_model.rs:58— MethodTooLong — new runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SchemaBuilder.sync src/schema/builder.rs:90— MethodTooLong — sync runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SchemaBuilder.sync sea-orm-sync/src/schema/builder.rs:90— MethodTooLong — sync runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
sea_orm_macros::derives::entity_model::expand_derive_entity_model (cognitive 241) sea-orm-macros/src/derives/entity_model.rs:16— sea_orm_macros::derives::entity_model::expand_derive_entity_model has cognitive complexity 241 (threshold 15). Drivers by points: if/else 87 (217 pts), loops 3 (14 pts), match/switch 2 (6 pts), boolean chains 4 (nesting depth added 145). 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.
sea_orm_macros::derives::arrow_schema::column_type_to_arrow_datatype (cognitive 66) sea-orm-macros/src/derives/arrow_schema.rs:174— sea_orm_macros::derives::arrow_schema::column_type_to_arrow_datatype has cognitive complexity 66 (threshold 15). Drivers by points: if/else 43 (62 pts), boolean chains 4 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_macros::derives::typed_column::expand_typed_column (cognitive 49) sea-orm-macros/src/derives/typed_column.rs:10— sea_orm_macros::derives::typed_column::expand_typed_column has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (42 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_macros::derives::value_type_match::column_type_wrapper (cognitive 49) sea-orm-macros/src/derives/value_type_match.rs:23— sea_orm_macros::derives::value_type_match::column_type_wrapper has cognitive complexity 49 (threshold 15). Drivers by points: if/else 32 (43 pts), boolean chains 4, match/switch 1 (2 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.
sea_orm_macros::derives::model_ex::expand_sea_orm_model (cognitive 48) sea-orm-macros/src/derives/model_ex.rs:21— sea_orm_macros::derives::model_ex::expand_sea_orm_model has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (32 pts), match/switch 2 (7 pts), loops 4 (6 pts), boolean chains 3 (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.
sea_orm_macros::derives::arrow_schema::expand_derive_arrow_schema (cognitive 46) sea-orm-macros/src/derives/arrow_schema.rs:6— sea_orm_macros::derives::arrow_schema::expand_derive_arrow_schema has cognitive complexity 46 (threshold 15). Drivers by points: if/else 18 (37 pts), loops 2 (8 pts), boolean chains 1 (nesting depth added 25). 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.
sea_orm_macros::derives::into_active_model::parse_field (cognitive 22) sea-orm-macros/src/derives/into_active_model.rs:204— sea_orm_macros::derives::into_active_model::parse_field has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_macros::derives::model_ex::entity_loader_field (cognitive 19) sea-orm-macros/src/derives/model_ex.rs:477— sea_orm_macros::derives::model_ex::entity_loader_field has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 3 (5 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.
sea_orm_macros::derives::model_ex::expand_belongs_to_into (cognitive 17) sea-orm-macros/src/derives/model_ex.rs:816— sea_orm_macros::derives::model_ex::expand_belongs_to_into 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.
ClassTooLong: DatabaseTransaction src/database/transaction.rs:37— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 8 blocks, lines 37-903. The bar is 400 significant lines; this is 227 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DatabaseTransaction sea-orm-sync/src/database/transaction.rs:37— ClassTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 8 blocks, lines 37-848. The bar is 400 significant lines; this is 176 over it, 1.44× 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: DatabaseConnection src/database/db_connection.rs:35— ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 11 blocks, lines 35-946. The bar is 400 significant lines; this is 145 over it, 1.36× 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: ActiveEnum sea-orm-macros/src/derives/active_enum.rs:8— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 12 methods, 2 blocks, lines 8-888. The bar is 400 significant lines; this is 119 over it, 1.30× 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: DatabaseConnection sea-orm-sync/src/database/db_connection.rs:35— ClassTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 21 methods, 11 blocks, lines 35-893. The bar is 400 significant lines; this is 102 over it, 1.26× 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: EntityWriter sea-orm-codegen/src/entity/writer.rs:26— ClassTooLong — 485 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 41 methods, 2 blocks, lines 26-962. The bar is 400 significant lines; this is 85 over it, 1.21× 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: ActiveModelTrait src/entity/active_model.rs:31— ClassTooLong — 451 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods. The bar is 400 significant lines; this is 51 over it, 1.13× 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: ActiveModelTrait sea-orm-sync/src/entity/active_model.rs:30— ClassTooLong — 447 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods. The bar is 400 significant lines; this is 47 over it, 1.12× 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 (11 corresponding lines) · ×8
Edited copy of a member (11 corresponding lines) src/database/transaction.rs:55— src/database/transaction.rs:55-71 | sea-orm-sync/src/database/transaction.rs:54-64 — 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) sea-orm-sync/src/driver/proxy.rs:81— sea-orm-sync/src/driver/proxy.rs:81-91 | src/driver/proxy.rs:81-91 — 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) sea-orm-migration/src/migrator.rs:190— sea-orm-migration/src/migrator.rs:190-200 | sea-orm-migration/src/migrator/with_self.rs:150-160 — 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) sea-orm-sync/src/database/transaction.rs:804— sea-orm-sync/src/database/transaction.rs:804-814 | src/database/transaction.rs:849-860 — 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) sea-orm-sync/src/driver/sqlx_sqlite.rs:266— sea-orm-sync/src/driver/sqlx_sqlite.rs:266-276 | src/driver/sqlx_sqlite.rs:267-278 — 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) sea-orm-sync/src/driver/sqlx_sqlite.rs:413— sea-orm-sync/src/driver/sqlx_sqlite.rs:413-423 | src/driver/sqlx_sqlite.rs:421-432 — 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) sea-orm-sync/src/database/transaction.rs:771— sea-orm-sync/src/database/transaction.rs:771-781 | src/database/transaction.rs:814-825 — 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) sea-orm-sync/src/database/transaction.rs:788— sea-orm-sync/src/database/transaction.rs:788-798 | src/database/transaction.rs:832-843 — 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.
sea_orm_macros::derives::entity_model::expand_derive_entity_model (cyclomatic 79) sea-orm-macros/src/derives/entity_model.rs:16— sea_orm_macros::derives::entity_model::expand_derive_entity_model has cyclomatic complexity 79 (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.
sea_orm_macros::derives::arrow_schema::column_type_to_arrow_datatype (cyclomatic 40) sea-orm-macros/src/derives/arrow_schema.rs:174— sea_orm_macros::derives::arrow_schema::column_type_to_arrow_datatype 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.
sea_orm_macros::derives::value_type_match::column_type_wrapper (cyclomatic 38) sea-orm-macros/src/derives/value_type_match.rs:23— sea_orm_macros::derives::value_type_match::column_type_wrapper 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.
sea_orm_macros::derives::arrow_schema::rust_type_to_arrow_datatype (cyclomatic 27) sea-orm-macros/src/derives/arrow_schema.rs:289— sea_orm_macros::derives::arrow_schema::rust_type_to_arrow_datatype 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.
sea_orm_macros::derives::model_ex::expand_sea_orm_model (cyclomatic 25) sea-orm-macros/src/derives/model_ex.rs:21— sea_orm_macros::derives::model_ex::expand_sea_orm_model 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.
sea_orm_macros::derives::arrow_schema::expand_derive_arrow_schema (cyclomatic 21) sea-orm-macros/src/derives/arrow_schema.rs:6— sea_orm_macros::derives::arrow_schema::expand_derive_arrow_schema 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.
sea_orm_macros::derives::typed_column::expand_typed_column (cyclomatic 17) sea-orm-macros/src/derives/typed_column.rs:10— sea_orm_macros::derives::typed_column::expand_typed_column 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.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×7
Edited copy of a member (9 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs:471— sea-orm-sync/src/driver/rusqlite.rs:471-479 | src/driver/rusqlite.rs:471-479 — 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) sea-orm-sync/src/schema/builder.rs:669— sea-orm-sync/src/schema/builder.rs:669-677 | src/schema/builder.rs:678-686 — 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) sea-orm-sync/src/database/tracing_spans.rs:67— sea-orm-sync/src/database/tracing_spans.rs:67-75 | src/database/tracing_spans.rs:67-75 — 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) sea-orm-sync/src/value/text_uuid.rs:59— sea-orm-sync/src/value/text_uuid.rs:59-67 | src/value/text_uuid.rs:59-67 — 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) sea-orm-codegen/src/entity/writer.rs:145— sea-orm-codegen/src/entity/writer.rs:145-153 | sea-orm-codegen/src/entity/writer.rs:160-171 — 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) sea-orm-sync/src/query/loader.rs:1113— sea-orm-sync/src/query/loader.rs:1113-1121 | src/query/loader.rs:1198-1207 — 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) sea-orm-migration/src/migrator.rs:73— sea-orm-migration/src/migrator.rs:73-81 | sea-orm-migration/src/migrator/with_self.rs:29-37 — 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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×7
Edited copy of a member (4 corresponding lines) sea-orm-sync/src/executor/select.rs:201— sea-orm-sync/src/executor/select.rs:201-204 | src/executor/select.rs:203-206 — 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) sea-orm-sync/src/entity/active_model.rs:677— sea-orm-sync/src/entity/active_model.rs:677-680 | src/entity/active_model.rs:685-688 — 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) sea-orm-sync/src/entity/base_entity.rs:228— sea-orm-sync/src/entity/base_entity.rs:228-231 | src/entity/base_entity.rs:229-232 — 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) sea-orm-sync/src/entity/model.rs:57— sea-orm-sync/src/entity/model.rs:57-60 | src/entity/model.rs:58-61 — 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) sea-orm-sync/src/executor/query.rs:190— sea-orm-sync/src/executor/query.rs:190-193 | src/executor/query.rs:190-193 — 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) issues/324/src/model.rs:48— issues/324/src/model.rs:48-83 | issues/400/src/model.rs:49-52 — 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) sea-orm-sync/src/driver/rusqlite.rs:664— sea-orm-sync/src/driver/rusqlite.rs:664-667 | src/driver/rusqlite.rs:664-667 — 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.
Duplicated block (32 lines × 2) sea-orm-sync/src/database/proxy.rs:67— sea-orm-sync/src/database/proxy.rs:67-98 | src/database/proxy.rs:68-99 — before extracting anything, compare `sea-orm-sync/src/database/proxy.rs` and `src/database/proxy.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 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. 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 (32 lines × 2) sea-orm-sync/src/database/transaction.rs:630— sea-orm-sync/src/database/transaction.rs:630-661 | src/database/transaction.rs:666-697 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:630` 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 (32 lines × 2) sea-orm-sync/src/entity/active_model.rs:85— sea-orm-sync/src/entity/active_model.rs:85-116 | src/entity/active_model.rs:86-117 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (32 lines × 2) sea-orm-sync/src/entity/model.rs:86— sea-orm-sync/src/entity/model.rs:86-117 | src/entity/model.rs:87-118 — before extracting anything, compare `sea-orm-sync/src/entity/model.rs` and `src/entity/model.rs` as WHOLE FILES: 97% 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. 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. 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 (32 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:228— sea-orm-sync/src/rbac/engine/mod.rs:228-259 | src/rbac/engine/mod.rs:228-259 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (32 lines × 2) sea-orm-sync/src/entity/with_arrow.rs:8— sea-orm-sync/src/entity/with_arrow.rs:8-39 | src/entity/with_arrow.rs:8-39 — before extracting anything, compare `sea-orm-sync/src/entity/with_arrow.rs` and `src/entity/with_arrow.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/with_arrow.rs:8` 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 (32 lines × 2) sea-orm-sync/src/query/traits.rs:25— sea-orm-sync/src/query/traits.rs:25-56 | src/query/traits.rs:25-56 — before extracting anything, compare `sea-orm-sync/src/query/traits.rs` and `src/query/traits.rs` as WHOLE FILES: 100% 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. 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) sea-orm-macros/src/derives/model_ex.rs:910— sea-orm-macros/src/derives/model_ex.rs:910-931 | sea-orm-macros/src/derives/model_ex.rs:1058-1079 — both copies are in the same file, so extract the 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 `sea-orm-macros/src/derives/model_ex.rs:910` 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 lines × 2) sea-orm-sync/src/database/connection.rs:147— sea-orm-sync/src/database/connection.rs:147-168 | src/database/connection.rs:156-177 — before extracting anything, compare `sea-orm-sync/src/database/connection.rs` and `src/database/connection.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (22 lines × 2) sea-orm-sync/src/database/mock.rs:155— sea-orm-sync/src/database/mock.rs:155-176 | src/database/mock.rs:155-176 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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. 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 (22 lines × 2) sea-orm-sync/src/driver/sqlx_common.rs:59— sea-orm-sync/src/driver/sqlx_common.rs:59-80 | src/driver/sqlx_common.rs:61-82 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_common.rs` and `src/driver/sqlx_common.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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. 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 (22 lines × 2) sea-orm-sync/src/entity/active_model.rs:1004— sea-orm-sync/src/entity/active_model.rs:1004-1025 | src/entity/active_model.rs:1013-1034 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:1004` 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 (22 lines × 2) sea-orm-sync/src/executor/query.rs:205— sea-orm-sync/src/executor/query.rs:205-226 | src/executor/query.rs:205-226 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (22 lines × 2) sea-orm-sync/src/query/delete.rs:108— sea-orm-sync/src/query/delete.rs:108-129 | src/query/delete.rs:108-129 — before extracting anything, compare `sea-orm-sync/src/query/delete.rs` and `src/query/delete.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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. 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 (6 lines × 4) sea-orm-sync/src/database/transaction.rs:229— sea-orm-sync/src/database/transaction.rs:229-234 | sea-orm-sync/src/database/transaction.rs:283-288 | src/database/transaction.rs:251-256 | src/database/transaction.rs:308-313 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:229` 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 × 4) sea-orm-sync/src/database/transaction.rs:530— sea-orm-sync/src/database/transaction.rs:530-535 | sea-orm-sync/src/database/transaction.rs:591-596 | src/database/transaction.rs:563-568 | src/database/transaction.rs:625-630 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:530` 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) sea-orm-sync/src/database/transaction.rs:540— sea-orm-sync/src/database/transaction.rs:540-545 | sea-orm-sync/src/database/transaction.rs:602-607 | src/database/transaction.rs:573-578 | src/database/transaction.rs:637-642 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:540` 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) sea-orm-sync/src/entity/active_model_ex.rs:187— sea-orm-sync/src/entity/active_model_ex.rs:187-192 | sea-orm-sync/src/entity/active_model_ex.rs:253-258 | src/entity/active_model_ex.rs:187-192 | src/entity/active_model_ex.rs:253-258 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 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 × 4) sea-orm-sync/src/executor/select.rs:644— sea-orm-sync/src/executor/select.rs:644-649 | sea-orm-sync/src/executor/select.rs:780-785 | src/executor/select.rs:655-660 | src/executor/select.rs:791-796 — before extracting anything, compare `sea-orm-sync/src/executor/select.rs` and `src/executor/select.rs` as WHOLE FILES: 82% 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 4 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. 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 × 4) sea-orm-sync/src/query/loader.rs:1454— sea-orm-sync/src/query/loader.rs:1454-1459 | sea-orm-sync/src/query/util.rs:247-252 | src/query/loader.rs:1542-1547 | src/query/util.rs:247-252 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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 × 4) sea-orm-macros/src/derives/active_enum.rs:138— sea-orm-macros/src/derives/active_enum.rs:138-144 | sea-orm-macros/src/derives/active_model.rs:30-36 | sea-orm-macros/src/derives/derive_iden.rs:57-62 | sea-orm-macros/src/derives/derive_iden.rs:112-118 — 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 `sea-orm-macros/src/derives/active_enum.rs:138` 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 first that the copies are not typed on the same thing: the declarations holding them bind `input` to `syn::DeriveInput` in one and `DeriveInput` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×6
Edited copy of a member (5 corresponding lines) src/entity/active_model.rs:352— src/entity/active_model.rs:352-356 | sea-orm-sync/src/entity/active_model.rs:345-349 — 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) sea-orm-sync/src/entity/active_model.rs:227— sea-orm-sync/src/entity/active_model.rs:227-231 | src/entity/active_model.rs:230-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) sea-orm-migration/src/migrator.rs:245— sea-orm-migration/src/migrator.rs:245-249 | sea-orm-migration/src/migrator/with_self.rs:201-205 — 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) sea-orm-migration/src/migrator.rs:255— sea-orm-migration/src/migrator.rs:255-259 | sea-orm-migration/src/migrator/with_self.rs:211-215 — 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) sea-orm-migration/src/migrator.rs:265— sea-orm-migration/src/migrator.rs:265-269 | sea-orm-migration/src/migrator/with_self.rs:221-225 — 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) sea-orm-migration/src/migrator.rs:206— sea-orm-migration/src/migrator.rs:206-210 | sea-orm-migration/src/migrator/with_self.rs:166-170 — 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.
Duplicated block (35 lines × 2) sea-orm-sync/src/database/transaction.rs:330— sea-orm-sync/src/database/transaction.rs:330-364 | src/database/transaction.rs:358-392 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:330` 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 (35 lines × 2) sea-orm-sync/src/entity/active_model.rs:640— sea-orm-sync/src/entity/active_model.rs:640-674 | src/entity/active_model.rs:648-682 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (35 lines × 2) sea-orm-sync/src/executor/cursor.rs:245— sea-orm-sync/src/executor/cursor.rs:245-279 | src/executor/cursor.rs:245-279 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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 (35 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:169— sea-orm-sync/src/rbac/engine/mod.rs:169-203 | src/rbac/engine/mod.rs:169-203 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (35 lines × 2) sea-orm-sync/src/database/proxy.rs:154— sea-orm-sync/src/database/proxy.rs:154-188 | src/database/proxy.rs:155-189 — before extracting anything, compare `sea-orm-sync/src/database/proxy.rs` and `src/database/proxy.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 83 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. 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 (35 lines × 2) sea-orm-sync/src/entity/active_enum.rs:132— sea-orm-sync/src/entity/active_enum.rs:132-166 | src/entity/active_enum.rs:132-166 — before extracting anything, compare `sea-orm-sync/src/entity/active_enum.rs` and `src/entity/active_enum.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/active_enum.rs:132` 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 (28 lines × 2) sea-orm-sync/src/database/restricted_connection.rs:502— sea-orm-sync/src/database/restricted_connection.rs:502-529 | src/database/restricted_connection.rs:549-576 — before extracting anything, compare `sea-orm-sync/src/database/restricted_connection.rs` and `src/database/restricted_connection.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 69 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. 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 (28 lines × 2) sea-orm-sync/src/database/sea_schema_shim.rs:67— sea-orm-sync/src/database/sea_schema_shim.rs:67-94 | src/database/sea_schema_shim.rs:76-103 — 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. 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 (28 lines × 2) sea-orm-sync/src/driver/sqlite.rs:5— sea-orm-sync/src/driver/sqlite.rs:5-32 | src/driver/sqlite.rs:5-32 — before extracting anything, compare `sea-orm-sync/src/driver/sqlite.rs` and `src/driver/sqlite.rs` as WHOLE FILES: 100% 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. 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. 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 (28 lines × 2) sea-orm-sync/src/entity/link.rs:39— sea-orm-sync/src/entity/link.rs:39-66 | src/entity/link.rs:39-66 — before extracting anything, compare `sea-orm-sync/src/entity/link.rs` and `src/entity/link.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 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. 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 (28 lines × 2) sea-orm-sync/src/query/loader.rs:1264— sea-orm-sync/src/query/loader.rs:1264-1291 | src/query/loader.rs:1352-1379 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (28 lines × 2) sea-orm-sync/src/database/db_connection.rs:314— sea-orm-sync/src/database/db_connection.rs:314-341 | src/database/db_connection.rs:335-362 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:314` 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 (18 lines × 2) sea-orm-sync/src/database/statement.rs:78— sea-orm-sync/src/database/statement.rs:78-95 | src/database/statement.rs:78-95 — before extracting anything, compare `sea-orm-sync/src/database/statement.rs` and `src/database/statement.rs` as WHOLE FILES: 99% 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. 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. 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 (18 lines × 2) sea-orm-sync/src/driver/mock.rs:63— sea-orm-sync/src/driver/mock.rs:63-80 | src/driver/mock.rs:64-81 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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. 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 (18 lines × 2) sea-orm-sync/src/executor/insert.rs:462— sea-orm-sync/src/executor/insert.rs:462-479 | src/executor/insert.rs:470-487 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:462` 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 (18 lines × 2) sea-orm-sync/src/executor/insert.rs:539— sea-orm-sync/src/executor/insert.rs:539-556 | src/executor/insert.rs:553-570 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:539` 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 (18 lines × 2) sea-orm-sync/src/schema/json.rs:44— sea-orm-sync/src/schema/json.rs:44-61 | src/schema/json.rs:44-61 — before extracting anything, compare `sea-orm-sync/src/schema/json.rs` and `src/schema/json.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 85 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. 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 (18 lines × 2) sea-orm-sync/src/query/loader.rs:1295— sea-orm-sync/src/query/loader.rs:1295-1312 | src/query/loader.rs:1383-1400 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (11 lines × 3) sea-orm-sync/src/database/db_connection.rs:413— sea-orm-sync/src/database/db_connection.rs:413-423 | sea-orm-sync/src/database/db_connection.rs:448-458 | sea-orm-sync/src/database/db_connection.rs:486-496 — 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 `sea-orm-sync/src/database/db_connection.rs:413` 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 (11 lines × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:144— sea-orm-sync/src/driver/sqlx_mysql.rs:144-154 | sea-orm-sync/src/driver/sqlx_postgres.rs:179-189 | sea-orm-sync/src/driver/sqlx_sqlite.rs:163-173 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. 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 (11 lines × 3) src/database/db_connection.rs:447— src/database/db_connection.rs:447-457 | src/database/db_connection.rs:482-492 | src/database/db_connection.rs:521-531 — 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 `src/database/db_connection.rs:447` 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 (11 lines × 3) src/driver/sqlx_mysql.rs:145— src/driver/sqlx_mysql.rs:145-155 | src/driver/sqlx_postgres.rs:184-194 | src/driver/sqlx_sqlite.rs:164-174 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. 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 (11 lines × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:189— sea-orm-sync/src/driver/sqlx_mysql.rs:189-199 | sea-orm-sync/src/driver/sqlx_postgres.rs:224-234 | sea-orm-sync/src/driver/sqlx_sqlite.rs:208-218 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. 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 (11 lines × 3) src/driver/sqlx_mysql.rs:190— src/driver/sqlx_mysql.rs:190-200 | src/driver/sqlx_postgres.rs:229-239 | src/driver/sqlx_sqlite.rs:209-219 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. 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 lines × 3) sea-orm-arrow/src/lib.rs:543— sea-orm-arrow/src/lib.rs:543-549 | sea-orm-arrow/src/lib.rs:557-563 | sea-orm-arrow/src/lib.rs:571-577 — 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 `sea-orm-arrow/src/lib.rs: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 (7 lines × 3) sea-orm-macros/src/derives/entity_loader.rs:420— sea-orm-macros/src/derives/entity_loader.rs:420-426 | sea-orm-macros/src/derives/entity_loader.rs:476-482 | sea-orm-macros/src/derives/entity_loader.rs:584-590 — 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 `sea-orm-macros/src/derives/entity_loader.rs:420` 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 × 3) sea-orm-sync/src/database/transaction.rs:586— sea-orm-sync/src/database/transaction.rs:586-592 | sea-orm-sync/src/database/transaction.rs:597-603 | sea-orm-sync/src/database/transaction.rs:608-614 — 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 `sea-orm-sync/src/database/transaction.rs:586` 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 × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:289— sea-orm-sync/src/driver/sqlx_mysql.rs:289-295 | sea-orm-sync/src/driver/sqlx_postgres.rs:324-330 | sea-orm-sync/src/driver/sqlx_sqlite.rs:311-317 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) src/database/restricted_connection.rs:378— src/database/restricted_connection.rs:378-384 | src/database/restricted_connection.rs:460-466 | src/database/transaction.rs:896-902 — 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 (7 lines × 3) src/driver/sqlx_mysql.rs:296— src/driver/sqlx_mysql.rs:296-302 | src/driver/sqlx_postgres.rs:335-341 | src/driver/sqlx_sqlite.rs:318-324 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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.
TooManyMethods: ConnectOptions sea-orm-sync/src/database/mod.rs:81— TooManyMethods — 45 methods, declared across 2 files: database/mod.rs (43), driver/sqlx_common.rs (2). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ConnectOptions src/database/mod.rs:95— TooManyMethods — 45 methods, declared across 2 files: database/mod.rs (43), driver/sqlx_common.rs (2). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EntityWriter sea-orm-codegen/src/entity/writer.rs:26— TooManyMethods — 41 methods, declared across 6 files: entity/writer.rs (29), writer/compact.rs (3), writer/dense.rs (3), writer/frontend.rs (3), +2 more file(s). The bar is 30 methods; this is 11 over it, 1.37× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Select sea-orm-sync/src/query/select.rs:15— TooManyMethods — 39 methods, declared across 6 files: query/join.rs (13), executor/select.rs (11), query/select.rs (8), query/combine.rs (5), +2 more file(s). The bar is 30 methods; this is 9 over it, 1.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Select src/query/select.rs:15— TooManyMethods — 39 methods, declared across 6 files: query/join.rs (13), executor/select.rs (11), query/select.rs (8), query/combine.rs (5), +2 more file(s). The bar is 30 methods; this is 9 over it, 1.30× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) sea-orm-sync/src/rbac/context.rs:261— sea-orm-sync/src/rbac/context.rs:261-278 | src/rbac/context.rs:273-291 — 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) sea-orm-sync/src/database/transaction.rs:752— sea-orm-sync/src/database/transaction.rs:752-764 | src/database/transaction.rs:794-806 — 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) sea-orm-macros/src/derives/value_type_match.rs:9— sea-orm-macros/src/derives/value_type_match.rs:9-21 | sea-orm-macros/src/derives/value_type_match.rs:194-206 — 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) sea-orm-sync/src/database/executor.rs:164— sea-orm-sync/src/database/executor.rs:164-176 | src/database/executor.rs:177-194 — 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) src/database/executor.rs:123— src/database/executor.rs:123-135 | sea-orm-sync/src/database/executor.rs:118-130 — 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 (21 corresponding lines) · ×5
Edited copy of a member (21 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs:565— sea-orm-sync/src/driver/rusqlite.rs:565-585 | src/driver/rusqlite.rs:565-585 — 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) sea-orm-sync/src/driver/rusqlite.rs:538— sea-orm-sync/src/driver/rusqlite.rs:538-558 | src/driver/rusqlite.rs:538-558 — 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) sea-orm-macros/src/derives/entity_loader.rs:517— sea-orm-macros/src/derives/entity_loader.rs:517-537 | sea-orm-macros/src/derives/entity_loader.rs:543-563 — 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) sea-orm-sync/src/rbac/context.rs:287— sea-orm-sync/src/rbac/context.rs:287-307 | src/rbac/context.rs:300-321 — 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) sea-orm-codegen/src/entity/writer/dense.rs:157— sea-orm-codegen/src/entity/writer/dense.rs:157-179 | sea-orm-codegen/src/entity/writer/frontend.rs:53-73 — 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.
Duplicated block (26 lines × 2) sea-orm-sync/src/database/sea_schema_rusqlite.rs:36— sea-orm-sync/src/database/sea_schema_rusqlite.rs:36-61 | src/database/sea_schema_rusqlite.rs:36-61 — before extracting anything, compare `sea-orm-sync/src/database/sea_schema_rusqlite.rs` and `src/database/sea_schema_rusqlite.rs` as WHOLE FILES: 100% 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. 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. 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 (26 lines × 2) sea-orm-sync/src/entity/registry.rs:32— sea-orm-sync/src/entity/registry.rs:32-57 | src/entity/registry.rs:32-57 — before extracting anything, compare `sea-orm-sync/src/entity/registry.rs` and `src/entity/registry.rs` as WHOLE FILES: 100% 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. 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. 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 (26 lines × 2) sea-orm-sync/src/executor/consolidate.rs:426— sea-orm-sync/src/executor/consolidate.rs:426-451 | src/executor/consolidate.rs:426-451 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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. 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 (26 lines × 2) sea-orm-sync/src/rbac/context.rs:224— sea-orm-sync/src/rbac/context.rs:224-249 | src/rbac/context.rs:235-260 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 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 `sea-orm-sync/src/rbac/context.rs:224` 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) sea-orm-sync/src/value.rs:104— sea-orm-sync/src/value.rs:104-129 | src/value.rs:104-129 — before extracting anything, compare `sea-orm-sync/src/value.rs` and `src/value.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/value.rs:104` 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 (19 lines × 2) sea-orm-sync/src/database/mock.rs:133— sea-orm-sync/src/database/mock.rs:133-151 | src/database/mock.rs:133-151 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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. 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 (19 lines × 2) sea-orm-sync/src/query/util.rs:13— sea-orm-sync/src/query/util.rs:13-31 | src/query/util.rs:13-31 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (19 lines × 2) sea-orm-sync/src/schema/builder.rs:160— sea-orm-sync/src/schema/builder.rs:160-178 | src/schema/builder.rs:163-181 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:160` 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 (19 lines × 2) sea-orm-sync/src/query/debug.rs:22— sea-orm-sync/src/query/debug.rs:22-40 | src/query/debug.rs:22-40 — before extracting anything, compare `sea-orm-sync/src/query/debug.rs` and `src/query/debug.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/query/debug.rs:22` 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 (19 lines × 2) sea-orm-sync/src/value/with_time.rs:36— sea-orm-sync/src/value/with_time.rs:36-54 | src/value/with_time.rs:36-54 — before extracting anything, compare `sea-orm-sync/src/value/with_time.rs` and `src/value/with_time.rs` as WHOLE FILES: 100% 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. 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 × 3) sea-orm-macros/src/derives/entity_loader.rs:440— sea-orm-macros/src/derives/entity_loader.rs:440-447 | sea-orm-macros/src/derives/entity_loader.rs:504-511 | sea-orm-macros/src/derives/entity_loader.rs:604-611 — 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 `sea-orm-macros/src/derives/entity_loader.rs:440` 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 × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:159— sea-orm-sync/src/driver/sqlx_mysql.rs:159-166 | sea-orm-sync/src/driver/sqlx_postgres.rs:194-201 | sea-orm-sync/src/driver/sqlx_sqlite.rs:178-185 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. 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 (8 lines × 3) src/database/transaction.rs:619— src/database/transaction.rs:619-626 | src/database/transaction.rs:631-638 | src/database/transaction.rs:643-650 — 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 `src/database/transaction.rs:619` 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 × 3) src/driver/sqlx_mysql.rs:160— src/driver/sqlx_mysql.rs:160-167 | src/driver/sqlx_postgres.rs:199-206 | src/driver/sqlx_sqlite.rs:179-186 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. 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 (8 lines × 3) sea-orm-macros/src/derives/model_ex.rs:825— sea-orm-macros/src/derives/model_ex.rs:825-832 | sea-orm-macros/src/derives/model_ex.rs:996-1003 | sea-orm-macros/src/derives/model_ex.rs:1202-1209 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
AXI1 · Runtime container hardening· Container process runs as root · ×4
Container process runs as root: devcontainer-app-1 — 'devcontainer-app-1' (devcontainer-app) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a Dockerfile reader. Advisory evidence for CRA Annex I (2)(b).
Container process runs as root: devcontainer-db-1 — 'devcontainer-db-1' (postgres:15.3-alpine) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a Dockerfile reader. Advisory evidence for CRA Annex I (2)(b).
Container process runs as root: devcontainer-mailer-1 — 'devcontainer-mailer-1' (mailtutan/mailtutan:latest) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a Dockerfile reader. Advisory evidence for CRA Annex I (2)(b).
Container process runs as root: devcontainer-redis-1 — 'devcontainer-redis-1' (redis:latest) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a Dockerfile reader. Advisory evidence for CRA Annex I (2)(b).
FixmeComment tests/json_struct_tests.rs:179— // FIXME how can we abstract this? — 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.
FixmeComment tests/json_struct_tests.rs:213— // FIXME how can we abstract this? — 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.
FixmeComment sea-orm-sync/tests/json_struct_tests.rs:172— // FIXME how can we abstract this? — 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.
FixmeComment sea-orm-sync/tests/json_struct_tests.rs:204— // FIXME how can we abstract this? — 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 copies of one member (4 members, 4+ corresponding lines) · ×4
Edited copies of one member (4 members, 4+ corresponding lines) sea-orm-sync/src/dynamic/entity.rs:142— sea-orm-sync/src/dynamic/entity.rs:142-145 | sea-orm-sync/src/entity/column.rs:318-321 | src/dynamic/entity.rs:142-145 | src/entity/column.rs:318-321 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) sea-orm-sync/src/dynamic/entity.rs:150— sea-orm-sync/src/dynamic/entity.rs:150-153 | sea-orm-sync/src/entity/column.rs:342-345 | src/dynamic/entity.rs:150-153 | src/entity/column.rs:342-345 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) sea-orm-sync/src/dynamic/entity.rs:158— sea-orm-sync/src/dynamic/entity.rs:158-161 | sea-orm-sync/src/entity/column.rs:366-369 | src/dynamic/entity.rs:158-161 | src/entity/column.rs:366-369 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) sea-orm-sync/src/database/stream/query.rs:124— sea-orm-sync/src/database/stream/query.rs:124-127 | sea-orm-sync/src/database/stream/transaction.rs:117-120 | src/database/stream/query.rs:126-129 | src/database/stream/transaction.rs:118-121 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Duplicated block (34 lines × 2) sea-orm-sync/src/query/combine.rs:47— sea-orm-sync/src/query/combine.rs:47-80 | src/query/combine.rs:47-80 — before extracting anything, compare `sea-orm-sync/src/query/combine.rs` and `src/query/combine.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 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. 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 (34 lines × 2) sea-orm-sync/src/schema/builder.rs:448— sea-orm-sync/src/schema/builder.rs:448-481 | src/schema/builder.rs:454-487 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs: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 (34 lines × 2) sea-orm-sync/src/schema/entity.rs:150— sea-orm-sync/src/schema/entity.rs:150-183 | src/schema/entity.rs:150-183 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (34 lines × 2) sea-orm-sync/src/executor/query.rs:296— sea-orm-sync/src/executor/query.rs:296-329 | src/executor/query.rs:296-329 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (30 lines × 2) sea-orm-sync/src/entity/column.rs:656— sea-orm-sync/src/entity/column.rs:656-685 | src/entity/column.rs:656-685 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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. 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 (30 lines × 2) sea-orm-sync/src/query/loader.rs:1347— sea-orm-sync/src/query/loader.rs:1347-1376 | src/query/loader.rs:1435-1464 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (30 lines × 2) sea-orm-sync/src/query/util.rs:122— sea-orm-sync/src/query/util.rs:122-151 | src/query/util.rs:122-151 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (30 lines × 2) sea-orm-sync/src/executor/cursor.rs:86— sea-orm-sync/src/executor/cursor.rs:86-115 | src/executor/cursor.rs:86-115 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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 (29 lines × 2) sea-orm-macros/src/derives/model_ex.rs:702— sea-orm-macros/src/derives/model_ex.rs:702-730 | sea-orm-macros/src/derives/model_ex.rs:927-955 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-macros/src/derives/model_ex.rs:702` 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 (29 lines × 2) sea-orm-sync/src/executor/cursor.rs:494— sea-orm-sync/src/executor/cursor.rs:494-522 | src/executor/cursor.rs:496-524 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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 (29 lines × 2) sea-orm-sync/src/schema/entity.rs:208— sea-orm-sync/src/schema/entity.rs:208-236 | src/schema/entity.rs:208-236 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (29 lines × 2) sea-orm-sync/src/executor/consolidate.rs:156— sea-orm-sync/src/executor/consolidate.rs:156-184 | src/executor/consolidate.rs:156-184 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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. 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 (21 lines × 2) sea-orm-sync/src/database/mod.rs:236— sea-orm-sync/src/database/mod.rs:236-256 | src/database/mod.rs:252-272 — before extracting anything, compare `sea-orm-sync/src/database/mod.rs` and `src/database/mod.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 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. 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 (21 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:292— sea-orm-sync/src/driver/rusqlite.rs:292-312 | src/driver/rusqlite.rs:292-312 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (21 lines × 2) sea-orm-sync/src/entity/active_model.rs:463— sea-orm-sync/src/entity/active_model.rs:463-483 | src/entity/active_model.rs:471-491 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (21 lines × 2) sea-orm-sync/src/schema/json.rs:18— sea-orm-sync/src/schema/json.rs:18-38 | src/schema/json.rs:18-38 — before extracting anything, compare `sea-orm-sync/src/schema/json.rs` and `src/schema/json.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 85 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. 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 (13 lines × 4) sea-orm-sync/src/database/stream/query.rs:87— sea-orm-sync/src/database/stream/query.rs:87-99 | sea-orm-sync/src/database/stream/transaction.rs:80-92 | src/database/stream/query.rs:89-101 | src/database/stream/transaction.rs:81-93 — before extracting anything, compare `sea-orm-sync/src/database/stream/query.rs` and `sea-orm-sync/src/database/stream/transaction.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/database/stream/query.rs:87` 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 (13 lines × 4) sea-orm-sync/src/driver/sqlx_mysql.rs:73— sea-orm-sync/src/driver/sqlx_mysql.rs:73-85 | sea-orm-sync/src/driver/sqlx_postgres.rs:73-85 | src/driver/sqlx_mysql.rs:73-85 | src/driver/sqlx_postgres.rs:73-85 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:73` 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 × 4) sea-orm-sync/src/entity/link.rs:49— sea-orm-sync/src/entity/link.rs:49-61 | sea-orm-sync/src/query/join.rs:134-146 | src/entity/link.rs:49-61 | src/query/join.rs:134-146 — before extracting anything, compare `sea-orm-sync/src/entity/link.rs` and `src/entity/link.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) sea-orm-sync/src/executor/consolidate.rs:256— sea-orm-sync/src/executor/consolidate.rs:256-268 | sea-orm-sync/src/executor/consolidate.rs:385-397 | src/executor/consolidate.rs:256-268 | src/executor/consolidate.rs:385-397 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 `sea-orm-sync/src/executor/consolidate.rs:256` 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 (12 lines × 4) sea-orm-sync/src/driver/sqlx_mysql.rs:476— sea-orm-sync/src/driver/sqlx_mysql.rs:476-487 | sea-orm-sync/src/driver/sqlx_postgres.rs:768-779 | src/driver/sqlx_mysql.rs:484-495 | src/driver/sqlx_postgres.rs:781-792 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:476` 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 × 4) sea-orm-sync/src/driver/sqlx_mysql.rs:487— sea-orm-sync/src/driver/sqlx_mysql.rs:487-498 | sea-orm-sync/src/driver/sqlx_postgres.rs:810-821 | src/driver/sqlx_mysql.rs:495-506 | src/driver/sqlx_postgres.rs:823-834 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) sea-orm-sync/src/driver/rusqlite.rs:375— sea-orm-sync/src/driver/rusqlite.rs:375-386 | sea-orm-sync/src/driver/rusqlite.rs:547-558 | src/driver/rusqlite.rs:375-386 | src/driver/rusqlite.rs:547-558 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:375` 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 × 4) sea-orm-sync/src/driver/rusqlite.rs:400— sea-orm-sync/src/driver/rusqlite.rs:400-411 | sea-orm-sync/src/driver/rusqlite.rs:574-585 | src/driver/rusqlite.rs:400-411 | src/driver/rusqlite.rs:574-585 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:400` 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 (11 lines × 4) sea-orm-sync/src/database/stream/query.rs:104— sea-orm-sync/src/database/stream/query.rs:104-114 | sea-orm-sync/src/database/stream/transaction.rs:97-107 | src/database/stream/query.rs:106-116 | src/database/stream/transaction.rs:98-108 — before extracting anything, compare `sea-orm-sync/src/database/stream/query.rs` and `sea-orm-sync/src/database/stream/transaction.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/database/stream/query.rs:104` 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 × 4) sea-orm-sync/src/driver/sqlx_mysql.rs:339— sea-orm-sync/src/driver/sqlx_mysql.rs:339-349 | sea-orm-sync/src/driver/sqlx_postgres.rs:374-384 | src/driver/sqlx_mysql.rs:346-356 | src/driver/sqlx_postgres.rs:385-395 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:339` 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 × 4) sea-orm-sync/src/schema/builder.rs:104— sea-orm-sync/src/schema/builder.rs:104-114 | sea-orm-sync/src/schema/builder.rs:142-152 | src/schema/builder.rs:106-116 | src/schema/builder.rs:145-155 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:104` 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 × 4) sea-orm-sync/src/driver/rusqlite.rs:366— sea-orm-sync/src/driver/rusqlite.rs:366-376 | sea-orm-sync/src/driver/rusqlite.rs:391-401 | src/driver/rusqlite.rs:366-376 | src/driver/rusqlite.rs:391-401 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:366` 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 × 3) sea-orm-sync/src/database/transaction.rs:669— sea-orm-sync/src/database/transaction.rs:669-678 | sea-orm-sync/src/database/transaction.rs:684-693 | sea-orm-sync/src/database/transaction.rs:699-708 — 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 `sea-orm-sync/src/database/transaction.rs:669` 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 × 3) src/database/transaction.rs:705— src/database/transaction.rs:705-714 | src/database/transaction.rs:720-729 | src/database/transaction.rs:735-744 — 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 `src/database/transaction.rs:705` 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 × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:229— sea-orm-sync/src/driver/sqlx_mysql.rs:229-238 | sea-orm-sync/src/driver/sqlx_postgres.rs:264-273 | sea-orm-sync/src/driver/sqlx_sqlite.rs:248-257 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) src/driver/sqlx_mysql.rs:230— src/driver/sqlx_mysql.rs:230-239 | src/driver/sqlx_postgres.rs:269-278 | src/driver/sqlx_sqlite.rs:249-258 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) sea-orm-sync/src/driver/sqlx_mysql.rs:470— sea-orm-sync/src/driver/sqlx_mysql.rs:470-476 | sea-orm-sync/src/driver/sqlx_postgres.rs:731-737 | src/driver/sqlx_mysql.rs:478-484 | src/driver/sqlx_postgres.rs:744-750 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:470` 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 × 4) sea-orm-sync/src/executor/delete.rs:152— sea-orm-sync/src/executor/delete.rs:152-158 | sea-orm-sync/src/executor/delete.rs:176-182 | src/executor/delete.rs:152-158 | src/executor/delete.rs:178-184 — there are 4 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 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 `sea-orm-sync/src/executor/delete.rs:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) sea-orm-sync/src/entity/active_model_ex.rs:178— sea-orm-sync/src/entity/active_model_ex.rs:178-184 | sea-orm-sync/src/entity/active_model_ex.rs:244-250 | src/entity/active_model_ex.rs:178-184 | src/entity/active_model_ex.rs:244-250 — before extracting anything, compare `sea-orm-sync/src/entity/active_model_ex.rs` and `src/entity/active_model_ex.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 134 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) sea-orm-sync/src/executor/query.rs:65— sea-orm-sync/src/executor/query.rs:65-71 | sea-orm-sync/src/executor/query.rs:1650-1656 | src/executor/query.rs:65-71 | src/executor/query.rs:1652-1658 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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 `sea-orm-sync/src/executor/query.rs:65` 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.
sea_orm_sync::entity::active_model::establish_links (cognitive 55) sea-orm-sync/src/entity/active_model.rs:1220— sea_orm_sync::entity::active_model::establish_links has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 9 (25 pts), boolean chains 2 (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.
sea_orm_sync::schema::entity::column_def_from_entity_column (cognitive 18) sea-orm-sync/src/schema/entity.rs:238— sea_orm_sync::schema::entity::column_def_from_entity_column has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (4 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_sync::executor::consolidate::consolidate_query_result_of_ordered_rows (cognitive 16) sea-orm-sync/src/executor/consolidate.rs:419— sea_orm_sync::executor::consolidate::consolidate_query_result_of_ordered_rows has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (4 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.
sea_orm::entity::active_model::establish_links (cognitive 55) src/entity/active_model.rs:1231— sea_orm::entity::active_model::establish_links has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 9 (25 pts), boolean chains 2 (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.
sea_orm::schema::entity::column_def_from_entity_column (cognitive 18) src/schema/entity.rs:238— sea_orm::schema::entity::column_def_from_entity_column has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (4 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm::executor::consolidate::consolidate_query_result_of_ordered_rows (cognitive 16) src/executor/consolidate.rs:419— sea_orm::executor::consolidate::consolidate_query_result_of_ordered_rows has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (4 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.
sea_orm_codegen::merge::merge_derives (cognitive 28) sea-orm-codegen/src/merge/mod.rs:265— sea_orm_codegen::merge::merge_derives has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (9 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.
sea_orm_codegen::merge::render_file_with_spacing (cognitive 27) sea-orm-codegen/src/merge/mod.rs:443— sea_orm_codegen::merge::render_file_with_spacing has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 3, loops 1 (nesting depth added 8). Of this number, 22 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_codegen::merge::merge_item_attributes (cognitive 19) sea-orm-codegen/src/merge/mod.rs:223— sea_orm_codegen::merge::merge_item_attributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 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.
EntityWriter::gen_dense_model_struct (cognitive 21) sea-orm-codegen/src/entity/writer/dense.rs:182— EntityWriter::gen_dense_model_struct has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 3 (4 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.
EntityWriter::gen_import_active_enum (cognitive 19) sea-orm-codegen/src/entity/writer.rs:615— EntityWriter::gen_import_active_enum has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 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.
EntityWriter::gen_compact_model_struct (cognitive 16) sea-orm-codegen/src/entity/writer/compact.rs:48— EntityWriter::gen_compact_model_struct has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (2 pts), 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) sea-orm-sync/src/driver/mock.rs:182— sea-orm-sync/src/driver/mock.rs:182-197 | src/driver/mock.rs:183-198 — 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) sea-orm-sync/src/rbac/schema.rs:48— sea-orm-sync/src/rbac/schema.rs:48-63 | src/rbac/schema.rs:52-67 — 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) sea-orm-sync/src/entity/active_model.rs:978— sea-orm-sync/src/entity/active_model.rs:978-993 | src/entity/active_model.rs:986-1002 — 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 (17 corresponding lines) · ×3
Edited copy of a member (17 corresponding lines) sea-orm-sync/src/executor/update.rs:213— sea-orm-sync/src/executor/update.rs:213-229 | src/executor/update.rs:220-236 — 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) sea-orm-arrow/src/lib.rs:270— sea-orm-arrow/src/lib.rs:270-286 | sea-orm-arrow/src/lib.rs:309-325 — 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) sea-orm-macros/src/lib.rs:190— sea-orm-macros/src/lib.rs:190-206 | sea-orm-macros/src/lib.rs:211-227 — 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) sea-orm-migration/src/migrator/queries.rs:11— sea-orm-migration/src/migrator/queries.rs:11-28 | sea-orm-migration/src/migrator/queries.rs:34-48 — 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) sea-orm-sync/src/schema/builder.rs:253— sea-orm-sync/src/schema/builder.rs:253-267 | src/schema/builder.rs:257-271 — 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) sea-orm-sync/src/executor/paginator.rs:243— sea-orm-sync/src/executor/paginator.rs:243-257 | src/executor/paginator.rs:251-265 — 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.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×3
Edited copies of one member (4 members, 7+ corresponding lines) sea-orm-sync/src/executor/consolidate.rs:31— sea-orm-sync/src/executor/consolidate.rs:31-37 | sea-orm-sync/src/executor/consolidate.rs:46-52 | src/executor/consolidate.rs:31-37 | src/executor/consolidate.rs:46-52 — 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) sea-orm-sync/src/entity/active_model_ex.rs:198— sea-orm-sync/src/entity/active_model_ex.rs:198-204 | sea-orm-sync/src/entity/active_model_ex.rs:264-270 | src/entity/active_model_ex.rs:198-204 | src/entity/active_model_ex.rs:264-270 — 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) sea-orm-sync/src/executor/returning.rs:31— sea-orm-sync/src/executor/returning.rs:31-37 | sea-orm-sync/src/executor/select.rs:1124-1130 | src/executor/returning.rs:31-37 | src/executor/select.rs:1144-1150 — 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 copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) sea-orm-migration/src/migrator.rs:216— sea-orm-migration/src/migrator.rs:216-221 | sea-orm-migration/src/migrator/with_self.rs:176-181 — 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) sea-orm-sync/src/dynamic/execute.rs:99— sea-orm-sync/src/dynamic/execute.rs:99-104 | src/dynamic/execute.rs:99-105 — 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) sea-orm-sync/src/executor/returning.rs:42— sea-orm-sync/src/executor/returning.rs:42-47 | src/executor/returning.rs:42-48 — 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.
Duplicated block (36 lines × 2) sea-orm-sync/src/entity/base_entity.rs:337— sea-orm-sync/src/entity/base_entity.rs:337-372 | src/entity/base_entity.rs:340-375 — before extracting anything, compare `sea-orm-sync/src/entity/base_entity.rs` and `src/entity/base_entity.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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. 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 (36 lines × 2) sea-orm-sync/src/query/insert.rs:92— sea-orm-sync/src/query/insert.rs:92-127 | src/query/insert.rs:92-127 — before extracting anything, compare `sea-orm-sync/src/query/insert.rs` and `src/query/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 163 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. 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 (36 lines × 2) sea-orm-sync/src/query/loader.rs:1178— sea-orm-sync/src/query/loader.rs:1178-1213 | src/query/loader.rs:1266-1301 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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 `sea-orm-sync/src/query/loader.rs:1178` 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 (11–12 lines × 2) sea-orm-sync/src/database/transaction.rs:99— sea-orm-sync/src/database/transaction.rs:99-109 | src/database/transaction.rs:106-117 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:99` 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–12 lines × 2) sea-orm-sync/src/executor/insert.rs:499— sea-orm-sync/src/executor/insert.rs:499-509 | src/executor/insert.rs:510-521 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:499` 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–12 lines × 2) sea-orm-sync/src/rbac/context.rs:103— sea-orm-sync/src/rbac/context.rs:103-113 | src/rbac/context.rs:109-120 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 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 `sea-orm-sync/src/rbac/context.rs:103` 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 (10 lines × 4) sea-orm-sync/src/driver/rusqlite.rs:335— sea-orm-sync/src/driver/rusqlite.rs:335-344 | sea-orm-sync/src/driver/rusqlite.rs:507-516 | src/driver/rusqlite.rs:335-344 | src/driver/rusqlite.rs:507-516 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:335` 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) sea-orm-sync/src/executor/select.rs:915— sea-orm-sync/src/executor/select.rs:915-924 | sea-orm-sync/src/executor/select.rs:1208-1217 | src/executor/select.rs:930-939 | src/executor/select.rs:1234-1243 — before extracting anything, compare `sea-orm-sync/src/executor/select.rs` and `src/executor/select.rs` as WHOLE FILES: 82% 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 4 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. 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 `sea-orm-sync/src/executor/select.rs:915` 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) sea-orm-sync/src/driver/rusqlite.rs:539— sea-orm-sync/src/driver/rusqlite.rs:539-548 | sea-orm-sync/src/driver/rusqlite.rs:566-575 | src/driver/rusqlite.rs:539-548 | src/driver/rusqlite.rs:566-575 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:539` 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 × 4) sea-orm-macros/src/derives/active_model_ex.rs:1123— sea-orm-macros/src/derives/active_model_ex.rs:1123-1130 | sea-orm-macros/src/derives/active_model_ex.rs:1175-1182 | sea-orm-macros/src/derives/active_model_ex.rs:1359-1366 | sea-orm-macros/src/derives/active_model_ex.rs:1391-1398 — 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 `sea-orm-macros/src/derives/active_model_ex.rs:1123` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-macros/src/derives/active_model_ex.rs:1357` calls `clone_with_mixed_site_span` and `sea-orm-macros/src/derives/active_model_ex.rs:1122` 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 lines × 4) sea-orm-macros/src/derives/entity_loader.rs:295— sea-orm-macros/src/derives/entity_loader.rs:295-302 | sea-orm-macros/src/derives/entity_loader.rs:347-354 | sea-orm-macros/src/derives/entity_loader.rs:406-413 | sea-orm-macros/src/derives/entity_loader.rs:458-465 — 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 before the matched lines, `sea-orm-macros/src/derives/entity_loader.rs:346` calls `value`, `span` and `sea-orm-macros/src/derives/entity_loader.rs:294` 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 × 4) sea-orm-sync/src/executor/cursor.rs:439— sea-orm-sync/src/executor/cursor.rs:439-446 | sea-orm-sync/src/executor/cursor.rs:500-507 | src/executor/cursor.rs:441-448 | src/executor/cursor.rs:502-509 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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.
sea_orm_arrow::values_to_arrow_array (cyclomatic 52) sea-orm-arrow/src/lib.rs:695— sea_orm_arrow::values_to_arrow_array has cyclomatic complexity 52 (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 shape REPEATS in the file: one other method here (sea_orm_arrow::option_values_to_arrow_array) 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.
sea_orm_arrow::option_values_to_arrow_array (cyclomatic 52) sea-orm-arrow/src/lib.rs:977— sea_orm_arrow::option_values_to_arrow_array has cyclomatic complexity 52 (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 shape REPEATS in the file: one other method here (sea_orm_arrow::values_to_arrow_array) 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.
Column::get_def_inner::write_col_def (cyclomatic 49) sea-orm-codegen/src/entity/column.rs:134— Column::get_def_inner::write_col_def has cyclomatic complexity 49 (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.
Column::get_rs_type::write_rs_type (cyclomatic 36) sea-orm-codegen/src/entity/column.rs:38— Column::get_rs_type::write_rs_type 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.
EntitySchemaInfo::sync (cyclomatic 44) sea-orm-sync/src/schema/builder.rs:390— EntitySchemaInfo::sync has cyclomatic complexity 44 (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.
EntitySchemaInfo::sync (cyclomatic 44) src/schema/builder.rs:394— EntitySchemaInfo::sync has cyclomatic complexity 44 (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.
sea_orm_cli::commands::generate::run_generate_command (cyclomatic 21) sea-orm-cli/src/commands/generate.rs:116— sea_orm_cli::commands::generate::run_generate_command 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.
sea_orm_cli::commands::migrate::run_migrate_command (cyclomatic 16) sea-orm-cli/src/commands/migrate.rs:16— sea_orm_cli::commands::migrate::run_migrate_command 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.
RbacEngine::user_can (cyclomatic 21) sea-orm-sync/src/rbac/engine/mod.rs:274— RbacEngine::user_can 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.
RbacEngine::user_can (cyclomatic 21) src/rbac/engine/mod.rs:274— RbacEngine::user_can 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.
EntityWriter::gen_import_frontend::collect (cyclomatic 19) sea-orm-codegen/src/entity/writer/frontend.rs:126— EntityWriter::gen_import_frontend::collect 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.
EntityWriter::gen_dense_model_struct (cyclomatic 16) sea-orm-codegen/src/entity/writer/dense.rs:182— EntityWriter::gen_dense_model_struct 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.
DbErr::sql_err (cyclomatic 16) sea-orm-sync/src/error.rs:252— DbErr::sql_err 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.
DbErr::sql_err (cyclomatic 16) src/error.rs:252— DbErr::sql_err 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.
Hotspot: sea-orm-macros/src/derives/entity_model.rs sea-orm-macros/src/derives/entity_model.rs:16— sea-orm-macros/src/derives/entity_model.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in sea_orm_macros::derives::entity_model::expand_derive_entity_model at line 16. 1 of those changes was a fix/bug commit, and the other 1 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 13:24:28 +00:00' --until='2026-11-10 13:24:28 +00:00' --full-history --no-merges -- sea-orm-macros/src/derives/entity_model.rs`: 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: sea-orm-cli/src/commands/generate.rs sea-orm-cli/src/commands/generate.rs:116— sea-orm-cli/src/commands/generate.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in sea_orm_cli::commands::generate::run_generate_command at line 116. 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-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 13:24:28 +00:00' --until='2026-11-10 13:24:28 +00:00' --full-history --no-merges -- sea-orm-cli/src/commands/generate.rs`: 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.
EntitySchemaInfo::sync (cognitive 131) sea-orm-sync/src/schema/builder.rs:390— EntitySchemaInfo::sync has cognitive complexity 131 (threshold 15). Drivers by points: if/else 30 (96 pts), loops 11 (30 pts), boolean chains 5 (nesting depth added 85). 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.
EntitySchemaInfo::sync (cognitive 131) src/schema/builder.rs:394— EntitySchemaInfo::sync has cognitive complexity 131 (threshold 15). Drivers by points: if/else 30 (96 pts), loops 11 (30 pts), boolean chains 5 (nesting depth added 85). 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.
ActiveEnum::new (cognitive 55) sea-orm-macros/src/derives/active_enum.rs:129— ActiveEnum::new has cognitive complexity 55 (threshold 15). Drivers by points: if/else 24 (45 pts), match/switch 2 (4 pts), boolean chains 3, loops 2 (3 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.
ActiveEnum::impl_active_enum (cognitive 20) sea-orm-codegen/src/entity/active_enum.rs:15— ActiveEnum::impl_active_enum has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3, loops 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.
RbacEngine::user_can (cognitive 51) sea-orm-sync/src/rbac/engine/mod.rs:274— RbacEngine::user_can has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (40 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RbacEngine::user_can (cognitive 51) src/rbac/engine/mod.rs:274— RbacEngine::user_can has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (40 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sea_orm_arrow::values_to_arrow_array (cognitive 50) sea-orm-arrow/src/lib.rs:695— sea_orm_arrow::values_to_arrow_array has cognitive complexity 50 (threshold 15). Drivers by points: match/switch 20 (36 pts), if/else 4 (12 pts), loops 1 (2 pts) (nesting depth added 25). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own 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 (sea_orm_arrow::option_values_to_arrow_array) 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.
sea_orm_arrow::option_values_to_arrow_array (cognitive 50) sea-orm-arrow/src/lib.rs:977— sea_orm_arrow::option_values_to_arrow_array has cognitive complexity 50 (threshold 15). Drivers by points: match/switch 20 (36 pts), if/else 4 (12 pts), loops 1 (2 pts) (nesting depth added 25). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own 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 (sea_orm_arrow::values_to_arrow_array) 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.
SqlxPostgresConnector::connect (cognitive 23) sea-orm-sync/src/driver/sqlx_postgres.rs:68— SqlxPostgresConnector::connect has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 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.
SqlxPostgresConnector::connect (cognitive 23) src/driver/sqlx_postgres.rs:68— SqlxPostgresConnector::connect has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 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.
DbErr::sql_err (cognitive 23) sea-orm-sync/src/error.rs:252— DbErr::sql_err has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 6 (10 pts), 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.
DbErr::sql_err (cognitive 23) src/error.rs:252— DbErr::sql_err has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 6 (10 pts), 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.
InsertMany::many (cognitive 18) sea-orm-sync/src/query/insert.rs:311— InsertMany::many has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (4 pts), 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.
InsertMany::many (cognitive 18) src/query/insert.rs:311— InsertMany::many has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (4 pts), 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.
ActiveModelTrait::from_arrow (cognitive 17) sea-orm-sync/src/entity/active_model.rs:571— ActiveModelTrait::from_arrow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 1 (4 pts), loops 2 (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.
ActiveModelTrait::from_arrow (cognitive 17) src/entity/active_model.rs:579— ActiveModelTrait::from_arrow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 1 (4 pts), loops 2 (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.
SchemaBuilder::sync (cognitive 16) sea-orm-sync/src/schema/builder.rs:90— SchemaBuilder::sync has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (9 pts), match/switch 3 (5 pts), if/else 1 (2 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.
SchemaBuilder::sync (cognitive 16) src/schema/builder.rs:90— SchemaBuilder::sync has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (9 pts), match/switch 3 (5 pts), if/else 1 (2 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.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×2
Edited copy of a member (33 corresponding lines) sea-orm-sync/src/entity/active_model.rs:1002— sea-orm-sync/src/entity/active_model.rs:1002-1035 | src/entity/active_model.rs:1011-1045 — 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) sea-orm-sync/src/executor/update.rs:139— sea-orm-sync/src/executor/update.rs:139-171 | src/executor/update.rs:144-177 — 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) sea-orm-sync/src/driver/sqlx_mysql.rs:401— sea-orm-sync/src/driver/sqlx_mysql.rs:401-555 | sea-orm-sync/src/driver/sqlx_postgres.rs:437-965 | sea-orm-sync/src/driver/sqlx_sqlite.rs:427-523 | src/driver/sqlx_mysql.rs:409-563 | src/driver/sqlx_postgres.rs:450-978 | src/driver/sqlx_sqlite.rs:436-532 — 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) sea-orm-sync/src/entity/active_model.rs:689— sea-orm-sync/src/entity/active_model.rs:689-705 | sea-orm-sync/src/entity/active_model.rs:781-793 | sea-orm-sync/src/entity/active_model.rs:815-827 | src/entity/active_model.rs:697-713 | src/entity/active_model.rs:789-801 | src/entity/active_model.rs:823-835 — 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· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) sea-orm-sync/src/driver/rusqlite.rs:390— sea-orm-sync/src/driver/rusqlite.rs:390-411 | src/driver/rusqlite.rs:390-411 — 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) sea-orm-sync/src/driver/rusqlite.rs:365— sea-orm-sync/src/driver/rusqlite.rs:365-386 | src/driver/rusqlite.rs:365-386 — 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.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×2
Edited copies of one member (3 members, 17+ corresponding lines) src/database/db_connection.rs:403— src/database/db_connection.rs:403-425 | src/database/db_connection.rs:857-873 | src/database/db_connection.rs:882-904 — 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.
Edited copies of one member (3 members, 17+ corresponding lines) sea-orm-sync/src/database/db_connection.rs:374— sea-orm-sync/src/database/db_connection.rs:374-396 | sea-orm-sync/src/database/db_connection.rs:804-820 | sea-orm-sync/src/database/db_connection.rs:829-851 — 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 copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) sea-orm-sync/src/schema/builder.rs:373— sea-orm-sync/src/schema/builder.rs:373-386 | src/schema/builder.rs:377-390 — 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) sea-orm-sync/src/executor/insert.rs:276— sea-orm-sync/src/executor/insert.rs:276-289 | src/executor/insert.rs:284-297 — 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 (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) sea-orm-sync/src/driver/proxy.rs:66— sea-orm-sync/src/driver/proxy.rs:66-77 | src/driver/proxy.rs:66-77 — 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) sea-orm-sync/src/executor/update.rs:118— sea-orm-sync/src/executor/update.rs:118-129 | src/executor/update.rs:123-134 — 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.
D4 · Code Duplication· Edited copies of one member (5 members, 11+ corresponding lines) · ×2
Edited copies of one member (5 members, 11+ corresponding lines) src/executor/insert.rs:104— src/executor/insert.rs:104-114 | src/executor/insert.rs:121-131 | src/executor/insert.rs:141-151 | src/executor/insert.rs:161-172 | src/executor/insert.rs:182-193 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 11+ corresponding lines) sea-orm-sync/src/executor/insert.rs:104— sea-orm-sync/src/executor/insert.rs:104-114 | sea-orm-sync/src/executor/insert.rs:121-131 | sea-orm-sync/src/executor/insert.rs:141-151 | sea-orm-sync/src/executor/insert.rs:161-172 | sea-orm-sync/src/executor/insert.rs:182-193 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×2
Edited copy of a member (3 corresponding lines) sea-orm-sync/src/entity/relation.rs:74— sea-orm-sync/src/entity/relation.rs:74-76 | src/entity/relation.rs:74-76 — 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) sea-orm-sync/src/entity/relation.rs:56— sea-orm-sync/src/entity/relation.rs:56-58 | src/entity/relation.rs:56-58 — 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.
Duplicated block (73 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:207— sea-orm-sync/src/driver/rusqlite.rs:207-279 | src/driver/rusqlite.rs:207-279 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (73 lines × 2) sea-orm-sync/src/query/util.rs:161— sea-orm-sync/src/query/util.rs:161-233 | src/query/util.rs:161-233 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (51 lines × 2) sea-orm-sync/src/driver/sqlx_sqlite.rs:70— sea-orm-sync/src/driver/sqlx_sqlite.rs:70-120 | src/driver/sqlx_sqlite.rs:70-120 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_sqlite.rs` and `src/driver/sqlx_sqlite.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 198 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 `sea-orm-sync/src/driver/sqlx_sqlite.rs:70` 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 (51 lines × 2) sea-orm-sync/src/entity/active_model.rs:504— sea-orm-sync/src/entity/active_model.rs:504-554 | src/entity/active_model.rs:512-562 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (48 lines × 2) sea-orm-sync/src/schema/entity.rs:242— sea-orm-sync/src/schema/entity.rs:242-289 | src/schema/entity.rs:242-289 — before extracting anything, compare `sea-orm-sync/src/schema/entity.rs` and `src/schema/entity.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 158 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. 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 (48 lines × 2) sea-orm-sync/src/executor/consolidate.rs:299— sea-orm-sync/src/executor/consolidate.rs:299-346 | src/executor/consolidate.rs:299-346 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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. 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 (42 lines × 2) sea-orm-sync/src/entity/active_model.rs:1262— sea-orm-sync/src/entity/active_model.rs:1262-1303 | src/entity/active_model.rs:1274-1315 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:1262` 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 (42 lines × 2) sea-orm-sync/src/executor/consolidate.rs:360— sea-orm-sync/src/executor/consolidate.rs:360-401 | src/executor/consolidate.rs:360-401 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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. 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 (40 lines × 2) sea-orm-sync/src/driver/sqlx_mysql.rs:69— sea-orm-sync/src/driver/sqlx_mysql.rs:69-108 | src/driver/sqlx_mysql.rs:69-108 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `src/driver/sqlx_mysql.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 306 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 `sea-orm-sync/src/driver/sqlx_mysql.rs:69` 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 (40 lines × 2) sea-orm-sync/src/rbac/engine/resource_request.rs:16— sea-orm-sync/src/rbac/engine/resource_request.rs:16-55 | src/rbac/engine/resource_request.rs:16-55 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/resource_request.rs` and `src/rbac/engine/resource_request.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/rbac/engine/resource_request.rs:16` 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 (35–36 lines × 2) sea-orm-arrow/src/lib.rs:898— sea-orm-arrow/src/lib.rs:898-932 | sea-orm-arrow/src/lib.rs:1189-1224 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:898` 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 (35–36 lines × 2) sea-orm-sync/src/query/loader.rs:1141— sea-orm-sync/src/query/loader.rs:1141-1175 | src/query/loader.rs:1228-1263 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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. 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 (33 lines × 2) sea-orm-sync/src/query/update.rs:89— sea-orm-sync/src/query/update.rs:89-121 | src/query/update.rs:89-121 — before extracting anything, compare `sea-orm-sync/src/query/update.rs` and `src/query/update.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 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. 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 (33 lines × 2) sea-orm-sync/src/schema/builder.rs:281— sea-orm-sync/src/schema/builder.rs:281-313 | src/schema/builder.rs:285-317 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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. 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 (31 lines × 2) sea-orm-sync/src/entity/link.rs:75— sea-orm-sync/src/entity/link.rs:75-105 | src/entity/link.rs:75-105 — before extracting anything, compare `sea-orm-sync/src/entity/link.rs` and `src/entity/link.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 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. 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 (31 lines × 2) sea-orm-sync/src/driver/rusqlite.rs:135— sea-orm-sync/src/driver/rusqlite.rs:135-165 | src/driver/rusqlite.rs:135-165 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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 (24 lines × 2) sea-orm-sync/src/entity/identity.rs:117— sea-orm-sync/src/entity/identity.rs:117-140 | src/entity/identity.rs:117-140 — before extracting anything, compare `sea-orm-sync/src/entity/identity.rs` and `src/entity/identity.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 (24 lines × 2) sea-orm-sync/src/entity/identity.rs:147— sea-orm-sync/src/entity/identity.rs:147-170 | src/entity/identity.rs:147-170 — before extracting anything, compare `sea-orm-sync/src/entity/identity.rs` and `src/entity/identity.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 75 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. 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 (22 lines × 3) sea-orm-sync/src/driver/sqlx_mysql.rs:203— sea-orm-sync/src/driver/sqlx_mysql.rs:203-224 | sea-orm-sync/src/driver/sqlx_postgres.rs:238-259 | sea-orm-sync/src/driver/sqlx_sqlite.rs:222-243 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:203` 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 (22 lines × 3) src/driver/sqlx_mysql.rs:204— src/driver/sqlx_mysql.rs:204-225 | src/driver/sqlx_postgres.rs:243-264 | src/driver/sqlx_sqlite.rs:223-244 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/driver/sqlx_mysql.rs:204` 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 (20–21 lines × 2) sea-orm-sync/src/rbac/context.rs:187— sea-orm-sync/src/rbac/context.rs:187-206 | src/rbac/context.rs:197-217 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 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 `sea-orm-sync/src/rbac/context.rs:187` 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 (20–21 lines × 2) sea-orm-sync/src/schema/builder.rs:121— sea-orm-sync/src/schema/builder.rs:121-140 | src/schema/builder.rs:123-143 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:121` 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. 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 (23 lines × 2) sea-orm-sync/src/query/util.rs:64— sea-orm-sync/src/query/util.rs:64-86 | src/query/util.rs:64-86 — before extracting anything, compare `sea-orm-sync/src/query/util.rs` and `src/query/util.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 182 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. 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 (23 lines × 2) sea-orm-sync/src/tests_cfg/filling.rs:34— sea-orm-sync/src/tests_cfg/filling.rs:34-56 | src/tests_cfg/filling.rs:34-56 — before extracting anything, compare `sea-orm-sync/src/tests_cfg/filling.rs` and `src/tests_cfg/filling.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/tests_cfg/filling.rs:34` 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 (14–15 lines × 2) sea-orm-macros/src/derives/active_model_ex.rs:1434— sea-orm-macros/src/derives/active_model_ex.rs:1434-1448 | sea-orm-macros/src/derives/model_ex.rs:1242-1255 — 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–15 lines × 2) sea-orm-sync/src/database/db_connection.rs:211— sea-orm-sync/src/database/db_connection.rs:211-225 | src/database/db_connection.rs:220-233 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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 `sea-orm-sync/src/database/db_connection.rs:211` 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 (14 lines × 4) sea-orm-sync/src/executor/cursor.rs:314— sea-orm-sync/src/executor/cursor.rs:314-327 | sea-orm-sync/src/executor/cursor.rs:341-354 | src/executor/cursor.rs:316-329 | src/executor/cursor.rs:343-356 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-sync/src/executor/cursor.rs:335` calls `select_cols`, `select_only`, `into_json` and `sea-orm-sync/src/executor/cursor.rs:313` 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 (14 lines × 4) sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:10— sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:10-23 | sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:38-51 | src/rbac/engine/role_hierarchy_impl.rs:10-23 | src/rbac/engine/role_hierarchy_impl.rs:38-51 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs` and `src/rbac/engine/role_hierarchy_impl.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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 `sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:10` 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–14 lines × 2) sea-orm-arrow/src/lib.rs:884— sea-orm-arrow/src/lib.rs:884-896 | sea-orm-arrow/src/lib.rs:1174-1187 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:884` 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. 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–14 lines × 2) sea-orm-sync/src/rbac/context.rs:290— sea-orm-sync/src/rbac/context.rs:290-302 | src/rbac/context.rs:303-316 — before extracting anything, compare `sea-orm-sync/src/rbac/context.rs` and `src/rbac/context.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 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 `sea-orm-sync/src/rbac/context.rs:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 6) sea-orm-sync/src/database/db_connection.rs:309— sea-orm-sync/src/database/db_connection.rs:309-320 | sea-orm-sync/src/database/db_connection.rs:323-334 | sea-orm-sync/src/database/db_connection.rs:337-348 | src/database/db_connection.rs:330-341 | src/database/db_connection.rs:344-355 | src/database/db_connection.rs:358-369 — before extracting anything, compare `sea-orm-sync/src/database/db_connection.rs` and `src/database/db_connection.rs` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 219 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. 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 (12 lines × 6) sea-orm-sync/src/driver/sqlx_mysql.rs:74— sea-orm-sync/src/driver/sqlx_mysql.rs:74-85 | sea-orm-sync/src/driver/sqlx_postgres.rs:74-85 | sea-orm-sync/src/driver/sqlx_sqlite.rs:79-90 | src/driver/sqlx_mysql.rs:74-85 | src/driver/sqlx_postgres.rs:74-85 | src/driver/sqlx_sqlite.rs:79-90 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-sync/src/driver/sqlx_sqlite.rs:76` calls `Some`, `pragma`, `clone` and `sea-orm-sync/src/driver/sqlx_postgres.rs:73` 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 × 3) sea-orm-sync/src/database/transaction.rs:396— sea-orm-sync/src/database/transaction.rs:396-407 | sea-orm-sync/src/database/transaction.rs:512-523 | sea-orm-sync/src/database/transaction.rs:572-583 — 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 `sea-orm-sync/src/database/transaction.rs: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 (12 lines × 3) src/database/transaction.rs:426— src/database/transaction.rs:426-437 | src/database/transaction.rs:545-556 | src/database/transaction.rs:605-616 — 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 `src/database/transaction.rs:426` 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 × 6) sea-orm-sync/src/entity/active_model.rs:690— sea-orm-sync/src/entity/active_model.rs:690-698 | sea-orm-sync/src/entity/active_model.rs:782-790 | sea-orm-sync/src/entity/active_model.rs:816-824 | src/entity/active_model.rs:698-706 | src/entity/active_model.rs:790-798 | src/entity/active_model.rs:824-832 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 6) sea-orm-sync/src/database/transaction.rs:402— sea-orm-sync/src/database/transaction.rs:402-410 | sea-orm-sync/src/database/transaction.rs:518-526 | sea-orm-sync/src/database/transaction.rs:578-586 | src/database/transaction.rs:432-440 | src/database/transaction.rs:551-559 | src/database/transaction.rs:611-619 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:402` 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 × 4) sea-orm-macros/src/derives/entity_loader.rs:343— sea-orm-macros/src/derives/entity_loader.rs:343-351 | sea-orm-macros/src/derives/entity_loader.rs:454-462 | sea-orm-macros/src/derives/entity_loader.rs:518-526 | sea-orm-macros/src/derives/entity_loader.rs:544-552 — 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, `sea-orm-macros/src/derives/entity_loader.rs:352` calls `clone`, `pop`, `push` and `sea-orm-macros/src/derives/entity_loader.rs:528` 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 × 4) sea-orm-sync/src/driver/rusqlite.rs:353— sea-orm-sync/src/driver/rusqlite.rs:353-361 | sea-orm-sync/src/driver/rusqlite.rs:523-531 | src/driver/rusqlite.rs:353-361 | src/driver/rusqlite.rs:523-531 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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 `sea-orm-sync/src/driver/rusqlite.rs:353` 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) sea-orm-sync/src/driver/sqlx_mysql.rs:171— sea-orm-sync/src/driver/sqlx_mysql.rs:171-184 | sea-orm-sync/src/driver/sqlx_postgres.rs:206-219 | sea-orm-sync/src/driver/sqlx_sqlite.rs:190-203 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. 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 (14 lines × 3) src/driver/sqlx_mysql.rs:172— src/driver/sqlx_mysql.rs:172-185 | src/driver/sqlx_postgres.rs:211-224 | src/driver/sqlx_sqlite.rs:191-204 — before extracting anything, compare `src/driver/sqlx_mysql.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 206 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. 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 lines × 6) sea-orm-sync/src/database/transaction.rs:668— sea-orm-sync/src/database/transaction.rs:668-674 | sea-orm-sync/src/database/transaction.rs:683-689 | sea-orm-sync/src/database/transaction.rs:698-704 | src/database/transaction.rs:704-710 | src/database/transaction.rs:719-725 | src/database/transaction.rs:734-740 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 6) sea-orm-sync/src/driver/sqlx_mysql.rs:326— sea-orm-sync/src/driver/sqlx_mysql.rs:326-332 | sea-orm-sync/src/driver/sqlx_postgres.rs:361-367 | sea-orm-sync/src/driver/sqlx_sqlite.rs:348-354 | src/driver/sqlx_mysql.rs:333-339 | src/driver/sqlx_postgres.rs:372-378 | src/driver/sqlx_sqlite.rs:355-361 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) sea-orm-sync/src/database/transaction.rs:228— sea-orm-sync/src/database/transaction.rs:228-233 | sea-orm-sync/src/database/transaction.rs:282-287 | sea-orm-sync/src/database/transaction.rs:401-406 | sea-orm-sync/src/database/transaction.rs:458-463 | sea-orm-sync/src/database/transaction.rs:517-522 | sea-orm-sync/src/database/transaction.rs:577-582 — 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 `sea-orm-sync/src/database/transaction.rs:228` 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 × 6) sea-orm-macros/src/derives/entity_model.rs:201— sea-orm-macros/src/derives/entity_model.rs:201-208 | sea-orm-macros/src/derives/entity_model.rs:220-227 | sea-orm-macros/src/derives/entity_model.rs:229-234 | sea-orm-macros/src/derives/entity_model.rs:247-254 | sea-orm-macros/src/derives/entity_model.rs:256-263 | sea-orm-macros/src/derives/typed_column.rs:37-42 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. 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.
Off the main sequence: entity (issues/1599/entity) — entity (issues/1599/entity): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: sea-orm-codegen — sea-orm-codegen: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Low cohesion: ConnectOptions (LCOM4 20) sea-orm-sync/src/database/mod.rs:81— ConnectOptions's methods fall into 20 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 20 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: ConnectOptions (LCOM4 20) src/database/mod.rs:95— ConnectOptions's methods fall into 20 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 20 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.
AXR1 · Runtime accessibility (rendered)· WCAG 1.4.3 reproducibly failed in a rendered surface · ×1
WCAG 1.4.3 reproducibly failed in a rendered surface — axe-core rule(s) color-contrast failed on: a, h1. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
AXR1 · Runtime accessibility (rendered)· WCAG 3.1.1 reproducibly failed in a rendered surface · ×1
WCAG 3.1.1 reproducibly failed in a rendered surface — axe-core rule(s) html-has-lang failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
EntityTransformer::transform (cyclomatic 51) sea-orm-codegen/src/entity/transformer.rs:12— EntityTransformer::transform has cyclomatic complexity 51 (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.
DerivePartialModel::new (cyclomatic 35) sea-orm-macros/src/derives/partial_model.rs:58— DerivePartialModel::new 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.
ActiveEnum::new (cyclomatic 28) sea-orm-macros/src/derives/active_enum.rs:129— ActiveEnum::new 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.
sea_orm_sync::entity::active_model::establish_links (cyclomatic 25) sea-orm-sync/src/entity/active_model.rs:1220— sea_orm_sync::entity::active_model::establish_links 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.
sea_orm::entity::active_model::establish_links (cyclomatic 25) src/entity/active_model.rs:1231— sea_orm::entity::active_model::establish_links 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.
RelationAttr::from_attr (cyclomatic 21) sea-orm-macros/src/derives/active_model_ex.rs:34— RelationAttr::from_attr 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.
DeriveRelation::impl_relation_trait (cyclomatic 21) sea-orm-macros/src/derives/relation.rs:44— DeriveRelation::impl_relation_trait has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
BelongsToAttr::from_attr (cyclomatic 19) sea-orm-macros/src/derives/model_ex.rs:678— BelongsToAttr::from_attr 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.
sea_orm_codegen::merge::render_file_with_spacing (cyclomatic 18) sea-orm-codegen/src/merge/mod.rs:443— sea_orm_codegen::merge::render_file_with_spacing has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
DeriveActiveModel::impl_from_json (cyclomatic 16) sea-orm-macros/src/derives/active_model.rs:311— DeriveActiveModel::impl_from_json 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.
HasManyAttr::from_attr (cyclomatic 16) sea-orm-macros/src/derives/model_ex.rs:1048— HasManyAttr::from_attr 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.
EntityTransformer::transform (cognitive 140) sea-orm-codegen/src/entity/transformer.rs:12— EntityTransformer::transform has cognitive complexity 140 (threshold 15). Drivers by points: if/else 30 (90 pts), loops 15 (38 pts), match/switch 3 (7 pts), boolean chains 5 (nesting depth added 87). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DerivePartialModel::new (cognitive 78) sea-orm-macros/src/derives/partial_model.rs:58— DerivePartialModel::new has cognitive complexity 78 (threshold 15). Drivers by points: if/else 22 (47 pts), loops 6 (17 pts), match/switch 4 (14 pts) (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.
sea_orm_cli::commands::generate::run_generate_command (cognitive 49) sea-orm-cli/src/commands/generate.rs:116— sea_orm_cli::commands::generate::run_generate_command has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (31 pts), loops 3 (9 pts), match/switch 3 (7 pts), boolean chains 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.
DeriveFromQueryResult::new (cognitive 40) sea-orm-macros/src/derives/from_query_result.rs:115— DeriveFromQueryResult::new has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (13 pts), match/switch 3 (11 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DenseRelationField::field_tokens (cognitive 27) sea-orm-codegen/src/entity/writer/dense.rs:43— DenseRelationField::field_tokens has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (21 pts), match/switch 3 (5 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.
DeriveRelation::impl_relation_trait (cognitive 26) sea-orm-macros/src/derives/relation.rs:44— DeriveRelation::impl_relation_trait has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (19 pts), match/switch 4 (7 pts) (nesting depth added 4). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
DeriveActiveModel::impl_from_json (cognitive 25) sea-orm-macros/src/derives/active_model.rs:311— DeriveActiveModel::impl_from_json has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BelongsToAttr::from_attr (cognitive 23) sea-orm-macros/src/derives/model_ex.rs:678— BelongsToAttr::from_attr has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, boolean chains 5, match/switch 4 (5 pts) (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.
DeriveIntoActiveModel::new (cognitive 22) sea-orm-macros/src/derives/into_active_model.rs:32— DeriveIntoActiveModel::new has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 4 (8 pts), match/switch 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.
CompoundType::from_type (cognitive 22) sea-orm-macros/src/derives/util.rs:141— CompoundType::from_type has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 2 (3 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.
RelationAttr::from_attr (cognitive 19) sea-orm-macros/src/derives/active_model_ex.rs:34— RelationAttr::from_attr has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, 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.
HasManyAttr::from_attr (cognitive 18) sea-orm-macros/src/derives/model_ex.rs:1048— HasManyAttr::from_attr has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, match/switch 2 (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.
Field::from_field (cognitive 16) sea-orm-macros/src/derives/active_model_ex.rs:258— Field::from_field has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 1 (2 pts), boolean chains 1, 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.
TooManyFunctions: sea_orm_migration::schema sea-orm-migration/src/schema.rs:55— TooManyFunctions — 125 free functions. The bar is 30 free functions; this is 95 over it, 4.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.
Change coupling: query.rs ↔ transaction.rs src/database/stream/query.rs:1— `src/database/stream/query.rs` and `src/database/stream/transaction.rs` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `76e7d998` Add error variant BackendNotSupported (#2626); `85fc3d04` feat: Add support for async proxy connection. (#2278); `80d35a9d` cargo fmt — run `git show` on any of them.
D4 · Code Duplication· Near-duplicate member family (6 members, 16 shared lines) · ×1
Near-duplicate member family (6 members, 16 shared lines) sea-orm-sync/src/driver/sqlx_mysql.rs:201— sea-orm-sync/src/driver/sqlx_mysql.rs:201-224 | sea-orm-sync/src/driver/sqlx_postgres.rs:236-259 | sea-orm-sync/src/driver/sqlx_sqlite.rs:220-243 | src/driver/sqlx_mysql.rs:202-225 | src/driver/sqlx_postgres.rs:241-264 | src/driver/sqlx_sqlite.rs:221-244 — These 6 members are variants of one another: a block of 16 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 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· Near-duplicate member family (4 members, 54 shared lines) · ×1
Near-duplicate member family (4 members, 54 shared lines) sea-orm-sync/src/database/stream/query.rs:40— sea-orm-sync/src/database/stream/query.rs:40-114 | sea-orm-sync/src/database/stream/transaction.rs:44-107 | src/database/stream/query.rs:42-116 | src/database/stream/transaction.rs:45-108 — These 4 members are variants of one another: a block of 54 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 17 shared lines) · ×1
Near-duplicate member family (4 members, 17 shared lines) sea-orm-sync/src/executor/consolidate.rs:196— sea-orm-sync/src/executor/consolidate.rs:196-280 | sea-orm-sync/src/executor/consolidate.rs:358-401 | src/executor/consolidate.rs:196-280 | src/executor/consolidate.rs:358-401 — These 4 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 24 shared lines) · ×1
Near-duplicate member family (3 members, 24 shared lines) sea-orm-macros/src/derives/entity_loader.rs:402— sea-orm-macros/src/derives/entity_loader.rs:402-447 | sea-orm-macros/src/derives/entity_loader.rs:453-511 | sea-orm-macros/src/derives/entity_loader.rs:570-611 — These 3 members are variants of one another: a block of 24 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (172 shared lines) sea-orm-sync/src/schema/builder.rs:395— sea-orm-sync/src/schema/builder.rs:395-614 | src/schema/builder.rs:399-623 — These two members are variants of one another: 172 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 (133 shared lines) sea-orm-sync/src/schema/builder.rs:93— sea-orm-sync/src/schema/builder.rs:93-248 | src/schema/builder.rs:93-252 — These two members are variants of one another: 133 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 (130 shared lines) sea-orm-arrow/src/lib.rs:698— sea-orm-arrow/src/lib.rs:698-970 | sea-orm-arrow/src/lib.rs:980-1262 — These two members are variants of one another: 130 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 (89 shared lines) sea-orm-sync/src/database/transaction.rs:629— sea-orm-sync/src/database/transaction.rs:629-735 | src/database/transaction.rs:665-771 — These two members are variants of one another: 89 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 (84 shared lines) sea-orm-sync/src/query/loader.rs:1139— sea-orm-sync/src/query/loader.rs:1139-1229 | src/query/loader.rs:1226-1317 — These two members are variants of one another: 84 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 (59 shared lines) sea-orm-macros/src/derives/model_ex.rs:678— sea-orm-macros/src/derives/model_ex.rs:678-813 | sea-orm-macros/src/derives/model_ex.rs:905-984 — These two members are variants of one another: 59 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 (33 shared lines) sea-orm-macros/src/derives/entity_loader.rs:291— sea-orm-macros/src/derives/entity_loader.rs:291-336 | sea-orm-macros/src/derives/entity_loader.rs:342-400 — These two members are variants of one another: 33 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· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) sea-orm-sync/src/database/transaction.rs:220— sea-orm-sync/src/database/transaction.rs:220-269 | sea-orm-sync/src/database/transaction.rs:274-323 | sea-orm-sync/src/database/transaction.rs:391-444 | sea-orm-sync/src/database/transaction.rs:448-503 | sea-orm-sync/src/database/transaction.rs:507-563 | sea-orm-sync/src/database/transaction.rs:567-626 | src/database/transaction.rs:242-294 | src/database/transaction.rs:299-351 | src/database/transaction.rs:421-474 | src/database/transaction.rs:478-536 | src/database/transaction.rs:540-596 | src/database/transaction.rs:600-662 — 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.
D4 · Code Duplication· Edited copy of a member (127 corresponding lines) · ×1
Edited copy of a member (127 corresponding lines) sea-orm-sync/src/entity/active_model.rs:1235— sea-orm-sync/src/entity/active_model.rs:1235-1361 | src/entity/active_model.rs:1246-1377 — These two members are one piece of code written twice and then edited apart: 127 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (93 corresponding lines) · ×1
Edited copy of a member (93 corresponding lines) sea-orm-sync/src/driver/sqlx_postgres.rs:68— sea-orm-sync/src/driver/sqlx_postgres.rs:68-160 | src/driver/sqlx_postgres.rs:68-165 — These two members are one piece of code written twice and then edited apart: 93 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (84 corresponding lines) · ×1
Edited copy of a member (84 corresponding lines) sea-orm-sync/src/database/transaction.rs:82— sea-orm-sync/src/database/transaction.rs:82-165 | src/database/transaction.rs:89-178 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) sea-orm-sync/src/database/db_connection.rs:305— sea-orm-sync/src/database/db_connection.rs:305-356 | src/database/db_connection.rs:326-377 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) sea-orm-arrow/src/lib.rs:419— sea-orm-arrow/src/lib.rs:419-455 | sea-orm-arrow/src/lib.rs:527-584 — 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 (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) sea-orm-sync/src/executor/insert.rs:435— sea-orm-sync/src/executor/insert.rs:435-479 | src/executor/insert.rs:443-487 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 58+ corresponding lines) · ×1
Edited copies of one member (4 members, 58+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs:68— sea-orm-sync/src/driver/sqlx_mysql.rs:68-125 | sea-orm-sync/src/driver/sqlx_sqlite.rs:69-144 | src/driver/sqlx_mysql.rs:68-126 | src/driver/sqlx_sqlite.rs:69-145 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 58 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 copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) sea-orm-migration/src/migrator/exec.rs:266— sea-orm-migration/src/migrator/exec.rs:266-305 | sea-orm-migration/src/migrator/exec.rs:312-351 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) sea-orm-sync/src/database/mod.rs:192— sea-orm-sync/src/database/mod.rs:192-227 | src/database/mod.rs:208-243 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) sea-orm-macros/src/derives/entity_loader.rs:157— sea-orm-macros/src/derives/entity_loader.rs:157-213 | sea-orm-macros/src/derives/entity_loader.rs:219-267 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 33+ corresponding lines) · ×1
Edited copies of one member (4 members, 33+ corresponding lines) sea-orm-sync/src/database/db_connection.rs:505— sea-orm-sync/src/database/db_connection.rs:505-537 | sea-orm-sync/src/database/db_connection.rs:551-583 | src/database/db_connection.rs:544-578 | src/database/db_connection.rs:596-633 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 33 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 copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) sea-orm-sync/src/rbac/context.rs:184— sea-orm-sync/src/rbac/context.rs:184-215 | src/rbac/context.rs:194-226 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) sea-orm-sync/src/rbac/context.rs:221— sea-orm-sync/src/rbac/context.rs:221-255 | src/rbac/context.rs:232-267 — 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· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) sea-orm-arrow/src/lib.rs:1294— sea-orm-arrow/src/lib.rs:1294-1325 | sea-orm-arrow/src/lib.rs:1331-1358 — 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 (6 members, 21+ corresponding lines) · ×1
Edited copies of one member (6 members, 21+ corresponding lines) sea-orm-sync/src/database/db_connection.rs:403— sea-orm-sync/src/database/db_connection.rs:403-423 | sea-orm-sync/src/database/db_connection.rs:430-458 | sea-orm-sync/src/database/db_connection.rs:468-496 | src/database/db_connection.rs:433-457 | src/database/db_connection.rs:464-492 | src/database/db_connection.rs:502-531 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 21 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 (8 members, 25+ corresponding lines) · ×1
Edited copies of one member (8 members, 25+ corresponding lines) sea-orm-sync/src/database/db_connection.rs:163— sea-orm-sync/src/database/db_connection.rs:163-187 | sea-orm-sync/src/database/db_connection.rs:191-231 | sea-orm-sync/src/database/db_connection.rs:235-261 | sea-orm-sync/src/database/db_connection.rs:265-291 | src/database/db_connection.rs:164-196 | src/database/db_connection.rs:200-240 | src/database/db_connection.rs:244-276 | src/database/db_connection.rs:280-312 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 25 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 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) sea-orm-arrow/src/lib.rs:397— sea-orm-arrow/src/lib.rs:397-416 | sea-orm-arrow/src/lib.rs:505-524 — 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) sea-orm-sync/src/rbac/context.rs:43— sea-orm-sync/src/rbac/context.rs:43-73 | src/rbac/context.rs:43-78 — 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, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) sea-orm-migration/src/manager.rs:142— sea-orm-migration/src/manager.rs:142-167 | sea-orm-migration/src/manager.rs:173-198 | sea-orm-migration/src/manager.rs:205-229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) sea-orm-sync/src/executor/insert.rs:533— sea-orm-sync/src/executor/insert.rs:533-556 | src/executor/insert.rs:547-570 — 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) sea-orm-sync/src/executor/update.rs:177— sea-orm-sync/src/executor/update.rs:177-199 | src/executor/update.rs:183-206 — 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) · ×1
Edited copy of a member (19 corresponding lines) sea-orm-arrow/src/lib.rs:1428— sea-orm-arrow/src/lib.rs:1428-1447 | sea-orm-arrow/src/lib.rs:1465-1483 — 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 copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) sea-orm-sync/src/driver/sqlx_common.rs:101— sea-orm-sync/src/driver/sqlx_common.rs:101-127 | src/driver/sqlx_common.rs:103-129 — 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 copies of one member (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) sea-orm-sync/src/executor/cursor.rs:285— sea-orm-sync/src/executor/cursor.rs:285-307 | sea-orm-sync/src/executor/paginator.rs:52-74 | src/executor/cursor.rs:285-309 | src/executor/paginator.rs:54-78 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 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, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) sea-orm-sync/src/executor/paginator.rs:82— sea-orm-sync/src/executor/paginator.rs:82-100 | sea-orm-sync/src/executor/paginator.rs:295-309 | src/executor/paginator.rs:86-104 | src/executor/paginator.rs:304-318 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 18+ corresponding lines) · ×1
Edited copies of one member (5 members, 18+ corresponding lines) sea-orm-sync/src/rbac/context.rs:80— sea-orm-sync/src/rbac/context.rs:80-97 | sea-orm-sync/src/rbac/context.rs:100-123 | sea-orm-sync/src/rbac/context.rs:130-147 | src/rbac/context.rs:85-103 | src/rbac/context.rs:137-155 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) sea-orm-sync/src/database/sea_schema_shim.rs:37— sea-orm-sync/src/database/sea_schema_shim.rs:37-49 | sea-orm-sync/src/database/sea_schema_shim.rs:51-63 | src/database/sea_schema_shim.rs:46-58 | src/database/sea_schema_shim.rs:60-72 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 9+ corresponding lines) · ×1
Edited copies of one member (6 members, 9+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs:158— sea-orm-sync/src/driver/sqlx_mysql.rs:158-166 | sea-orm-sync/src/driver/sqlx_postgres.rs:193-201 | sea-orm-sync/src/driver/sqlx_sqlite.rs:177-185 | src/driver/sqlx_mysql.rs:159-167 | src/driver/sqlx_postgres.rs:198-206 | src/driver/sqlx_sqlite.rs:178-186 — 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.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) sea-orm-sync/src/executor/select.rs:888— sea-orm-sync/src/executor/select.rs:888-901 | sea-orm-sync/src/executor/select.rs:1181-1194 | src/executor/select.rs:899-915 | src/executor/select.rs:1203-1219 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) sea-orm-macros/src/derives/active_enum_display.rs:98— sea-orm-macros/src/derives/active_enum_display.rs:98-108 | sea-orm-macros/src/derives/into_active_model.rs:278-288 | sea-orm-macros/src/derives/related_entity.rs:146-159 | sea-orm-macros/src/derives/relation.rs:238-248 — 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) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) sea-orm-sync/src/entity/column.rs:138— sea-orm-sync/src/entity/column.rs:138-146 | sea-orm-sync/src/entity/column.rs:170-178 | src/entity/column.rs:138-146 | src/entity/column.rs:170-178 — 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 (6 members, 12+ corresponding lines) · ×1
Edited copies of one member (6 members, 12+ corresponding lines) sea-orm-sync/src/driver/sqlx_mysql.rs:268— sea-orm-sync/src/driver/sqlx_mysql.rs:268-279 | sea-orm-sync/src/driver/sqlx_postgres.rs:303-314 | sea-orm-sync/src/driver/sqlx_sqlite.rs:289-301 | src/driver/sqlx_mysql.rs:274-286 | src/driver/sqlx_postgres.rs:313-325 | src/driver/sqlx_sqlite.rs:295-308 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) sea-orm-sync/src/dynamic/execute.rs:86— sea-orm-sync/src/dynamic/execute.rs:86-93 | sea-orm-sync/src/executor/select.rs:862-869 | src/dynamic/execute.rs:86-93 | src/executor/select.rs:873-880 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 6+ corresponding lines) · ×1
Edited copies of one member (6 members, 6+ corresponding lines) sea-orm-sync/src/entity/active_model.rs:919— sea-orm-sync/src/entity/active_model.rs:919-924 | sea-orm-sync/src/entity/active_model.rs:942-947 | sea-orm-sync/src/entity/active_model.rs:965-970 | src/entity/active_model.rs:927-932 | src/entity/active_model.rs:950-955 | src/entity/active_model.rs:973-978 — These 6 members are one piece of code written 6 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) issues/262/src/main.rs:5— issues/262/src/main.rs:5-14 | issues/319/src/main.rs:5-14 — 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 (525 lines × 2) sea-orm-sync/src/driver/sqlx_postgres.rs:441— sea-orm-sync/src/driver/sqlx_postgres.rs:441-965 | src/driver/sqlx_postgres.rs:454-978 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_postgres.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 701 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 `sea-orm-sync/src/driver/sqlx_postgres.rs:441` 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 (96 lines × 2) sea-orm-sync/src/error.rs:253— sea-orm-sync/src/error.rs:253-348 | src/error.rs:253-348 — before extracting anything, compare `sea-orm-sync/src/error.rs` and `src/error.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/error.rs:253` 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 (93 lines × 2) sea-orm-sync/src/driver/sqlx_sqlite.rs:431— sea-orm-sync/src/driver/sqlx_sqlite.rs:431-523 | src/driver/sqlx_sqlite.rs:440-532 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_sqlite.rs` and `src/driver/sqlx_sqlite.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 198 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 `sea-orm-sync/src/driver/sqlx_sqlite.rs:431` 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 (151 lines × 2) sea-orm-sync/src/driver/sqlx_mysql.rs:405— sea-orm-sync/src/driver/sqlx_mysql.rs:405-555 | src/driver/sqlx_mysql.rs:413-563 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `src/driver/sqlx_mysql.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 306 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 `sea-orm-sync/src/driver/sqlx_mysql.rs:405` 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 (3–65 lines × 4) sea-orm-sync/src/executor/consolidate.rs:216— sea-orm-sync/src/executor/consolidate.rs:216-280 | sea-orm-sync/src/executor/consolidate.rs:362-364 | src/executor/consolidate.rs:216-280 | src/executor/consolidate.rs:362-364 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 `sea-orm-sync/src/executor/consolidate.rs:216` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `sea-orm-sync/src/executor/consolidate.rs:215` calls `match`, `take`, `Some` and `sea-orm-sync/src/executor/consolidate.rs:362` 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 (64 lines × 2) sea-orm-sync/src/driver/sqlx_postgres.rs:69— sea-orm-sync/src/driver/sqlx_postgres.rs:69-132 | src/driver/sqlx_postgres.rs:69-132 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_postgres.rs` and `src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 701 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 `sea-orm-sync/src/driver/sqlx_postgres.rs:69` 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 (67 lines × 2) sea-orm-sync/src/query/insert.rs:316— sea-orm-sync/src/query/insert.rs:316-382 | src/query/insert.rs:316-382 — before extracting anything, compare `sea-orm-sync/src/query/insert.rs` and `src/query/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 163 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. 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 (58 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:279— sea-orm-sync/src/rbac/engine/mod.rs:279-336 | src/rbac/engine/mod.rs:279-336 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (83 lines × 2) sea-orm-sync/src/dynamic/model.rs:72— sea-orm-sync/src/dynamic/model.rs:72-154 | src/dynamic/model.rs:72-154 — before extracting anything, compare `sea-orm-sync/src/dynamic/model.rs` and `src/dynamic/model.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 100 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. 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 (50 lines × 2) sea-orm-sync/src/entity/active_model.rs:572— sea-orm-sync/src/entity/active_model.rs:572-621 | src/entity/active_model.rs:580-629 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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. 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 (48–49 lines × 2) sea-orm-sync/src/schema/builder.rs:547— sea-orm-sync/src/schema/builder.rs:547-594 | src/schema/builder.rs:554-602 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:547` 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 (41 lines × 2) sea-orm-sync/src/database/mod.rs:274— sea-orm-sync/src/database/mod.rs:274-314 | src/database/mod.rs:290-330 — before extracting anything, compare `sea-orm-sync/src/database/mod.rs` and `src/database/mod.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 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. 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 (62 lines × 2) sea-orm-sync/src/rbac/engine/mod.rs:70— sea-orm-sync/src/rbac/engine/mod.rs:70-131 | src/rbac/engine/mod.rs:70-131 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/mod.rs` and `src/rbac/engine/mod.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 252 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. 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 (52 lines × 2) sea-orm-sync/src/executor/query.rs:131— sea-orm-sync/src/executor/query.rs:131-182 | src/executor/query.rs:131-182 — before extracting anything, compare `sea-orm-sync/src/executor/query.rs` and `src/executor/query.rs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 227 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. 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 (34–35 lines × 2) sea-orm-sync/src/schema/builder.rs:508— sea-orm-sync/src/schema/builder.rs:508-541 | src/schema/builder.rs:514-548 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:508` 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 (30 lines × 4) sea-orm-sync/src/database/stream/query.rs:46— sea-orm-sync/src/database/stream/query.rs:46-75 | sea-orm-sync/src/database/stream/transaction.rs:50-79 | src/database/stream/query.rs:48-77 | src/database/stream/transaction.rs:51-80 — before extracting anything, compare `sea-orm-sync/src/database/stream/query.rs` and `sea-orm-sync/src/database/stream/transaction.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/database/stream/query.rs:46` 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 (43 lines × 2) sea-orm-sync/src/query/join.rs:123— sea-orm-sync/src/query/join.rs:123-165 | src/query/join.rs:123-165 — before extracting anything, compare `sea-orm-sync/src/query/join.rs` and `src/query/join.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 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. 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 (75 lines × 2) sea-orm-sync/src/executor/cursor.rs:121— sea-orm-sync/src/executor/cursor.rs:121-195 | src/executor/cursor.rs:121-195 — before extracting anything, compare `sea-orm-sync/src/executor/cursor.rs` and `src/executor/cursor.rs` as WHOLE FILES: this scan already matched 11 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. 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 (63 lines × 2) sea-orm-sync/src/schema/builder.rs:180— sea-orm-sync/src/schema/builder.rs:180-242 | src/schema/builder.rs:184-246 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:180` 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 (27 lines × 2) sea-orm-sync/src/driver/mock.rs:86— sea-orm-sync/src/driver/mock.rs:86-112 | src/driver/mock.rs:87-113 — before extracting anything, compare `sea-orm-sync/src/driver/mock.rs` and `src/driver/mock.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 85 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. 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 (25–26 lines × 2) sea-orm-sync/src/schema/builder.rs:412— sea-orm-sync/src/schema/builder.rs:412-436 | src/schema/builder.rs:416-441 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:412` 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 (24–25 lines × 2) sea-orm-sync/src/entity/active_model.rs:1236— sea-orm-sync/src/entity/active_model.rs:1236-1259 | src/entity/active_model.rs:1247-1271 — before extracting anything, compare `sea-orm-sync/src/entity/active_model.rs` and `src/entity/active_model.rs` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 433 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 `sea-orm-sync/src/entity/active_model.rs:1236` 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 (25 lines × 2) sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:37— sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs:37-61 | src/rbac/engine/role_hierarchy_impl.rs:37-61 — before extracting anything, compare `sea-orm-sync/src/rbac/engine/role_hierarchy_impl.rs` and `src/rbac/engine/role_hierarchy_impl.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 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. 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 (19 lines × 3) sea-orm-macros/src/derives/model_ex.rs:682— sea-orm-macros/src/derives/model_ex.rs:682-700 | sea-orm-macros/src/derives/model_ex.rs:907-925 | sea-orm-macros/src/derives/model_ex.rs:1055-1073 — 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 `sea-orm-macros/src/derives/model_ex.rs:682` 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 (46 lines × 2) sea-orm-sync/src/schema/json.rs:64— sea-orm-sync/src/schema/json.rs:64-109 | src/schema/json.rs:64-109 — before extracting anything, compare `sea-orm-sync/src/schema/json.rs` and `src/schema/json.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 85 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. 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 (3–17 lines × 4) sea-orm-sync/src/executor/consolidate.rs:197— sea-orm-sync/src/executor/consolidate.rs:197-213 | sea-orm-sync/src/executor/consolidate.rs:361-363 | src/executor/consolidate.rs:197-213 | src/executor/consolidate.rs:361-363 — before extracting anything, compare `sea-orm-sync/src/executor/consolidate.rs` and `src/executor/consolidate.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 303 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 `sea-orm-sync/src/executor/consolidate.rs:197` 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, `sea-orm-sync/src/executor/consolidate.rs:213` calls `iter_mut`, `fold`, `get` and `sea-orm-sync/src/executor/consolidate.rs:363` 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 (16 lines × 4) sea-orm-sync/src/database/mock.rs:233— sea-orm-sync/src/database/mock.rs:233-248 | sea-orm-sync/src/database/proxy.rs:196-211 | src/database/mock.rs:233-248 | src/database/proxy.rs:197-212 — before extracting anything, compare `sea-orm-sync/src/database/mock.rs` and `src/database/mock.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 140 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 `sea-orm-sync/src/database/mock.rs:233` 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–16 lines × 2) sea-orm-sync/src/database/transaction.rs:481— sea-orm-sync/src/database/transaction.rs:481-496 | src/database/transaction.rs:514-528 — before extracting anything, compare `sea-orm-sync/src/database/transaction.rs` and `src/database/transaction.rs` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 315 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 `sea-orm-sync/src/database/transaction.rs:481` 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 (15 lines × 4) sea-orm-sync/src/query/loader.rs:1141— sea-orm-sync/src/query/loader.rs:1141-1155 | sea-orm-sync/src/query/loader.rs:1197-1211 | src/query/loader.rs:1228-1242 | src/query/loader.rs:1285-1299 — before extracting anything, compare `sea-orm-sync/src/query/loader.rs` and `src/query/loader.rs` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 276 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–14 lines × 2) sea-orm-arrow/src/lib.rs:871— sea-orm-arrow/src/lib.rs:871-882 | sea-orm-arrow/src/lib.rs:1158-1171 — both copies are in the same file, so extract the 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 `sea-orm-arrow/src/lib.rs:871` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 3) sea-orm-sync/src/driver/rusqlite.rs:725— sea-orm-sync/src/driver/rusqlite.rs:725-737 | sea-orm-sync/src/driver/sqlx_sqlite.rs:372-384 | src/driver/rusqlite.rs:725-737 — before extracting anything, compare `sea-orm-sync/src/driver/rusqlite.rs` and `src/driver/rusqlite.rs` as WHOLE FILES: this scan already matched 27 separate duplicated blocks between them, totalling at least 378 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `conn` to `&RusqliteSharedConnection` in one and `&SqlxSqlitePoolConnection` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 6) sea-orm-sync/src/driver/sqlx_mysql.rs:208— sea-orm-sync/src/driver/sqlx_mysql.rs:208-218 | sea-orm-sync/src/driver/sqlx_postgres.rs:243-253 | sea-orm-sync/src/driver/sqlx_sqlite.rs:227-237 | src/driver/sqlx_mysql.rs:209-219 | src/driver/sqlx_postgres.rs:248-258 | src/driver/sqlx_sqlite.rs:228-238 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 3) sea-orm-macros/src/derives/active_model_ex.rs:1174— sea-orm-macros/src/derives/active_model_ex.rs:1174-1184 | sea-orm-macros/src/derives/active_model_ex.rs:1358-1367 | sea-orm-macros/src/derives/active_model_ex.rs:1390-1399 — 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 `sea-orm-macros/src/derives/active_model_ex.rs:1174` 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–11 lines × 2) sea-orm-sync/src/schema/builder.rs:94— sea-orm-sync/src/schema/builder.rs:94-102 | src/schema/builder.rs:94-104 — before extracting anything, compare `sea-orm-sync/src/schema/builder.rs` and `src/schema/builder.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 432 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 `sea-orm-sync/src/schema/builder.rs:94` 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 (10 lines × 6) sea-orm-sync/src/driver/sqlx_mysql.rs:404— sea-orm-sync/src/driver/sqlx_mysql.rs:404-413 | sea-orm-sync/src/driver/sqlx_postgres.rs:440-449 | sea-orm-sync/src/driver/sqlx_sqlite.rs:430-439 | src/driver/sqlx_mysql.rs:412-421 | src/driver/sqlx_postgres.rs:453-462 | src/driver/sqlx_sqlite.rs:439-448 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs:404` 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–10 lines × 4) sea-orm-sync/src/executor/insert.rs:501— sea-orm-sync/src/executor/insert.rs:501-509 | sea-orm-sync/src/executor/insert.rs:568-577 | src/executor/insert.rs:512-520 | src/executor/insert.rs:582-591 — before extracting anything, compare `sea-orm-sync/src/executor/insert.rs` and `src/executor/insert.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 94 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 `sea-orm-sync/src/executor/insert.rs:501` 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–10 lines × 2) sea-orm-macros/src/derives/entity_model.rs:166— sea-orm-macros/src/derives/entity_model.rs:166-174 | sea-orm-macros/src/derives/entity_model.rs:190-199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) sea-orm-macros/src/derives/entity_loader.rs:429— sea-orm-macros/src/derives/entity_loader.rs:429-437 | sea-orm-macros/src/derives/entity_loader.rs:489-497 | sea-orm-macros/src/derives/entity_loader.rs:593-601 — 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 `sea-orm-macros/src/derives/entity_loader.rs:429` 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–9 lines × 2) sea-orm-codegen/src/entity/writer/dense.rs:100— sea-orm-codegen/src/entity/writer/dense.rs:100-106 | sea-orm-codegen/src/entity/writer/dense.rs:115-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. 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–9 lines × 2) sea-orm-macros/src/derives/from_query_result.rs:142— sea-orm-macros/src/derives/from_query_result.rs:142-149 | sea-orm-macros/src/derives/partial_model.rs:123-131 — 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 `sea-orm-macros/src/derives/from_query_result.rs:142` 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–8 lines × 2) sea-orm-macros/src/derives/arrow_schema.rs:203— sea-orm-macros/src/derives/arrow_schema.rs:203-209 | sea-orm-macros/src/derives/arrow_schema.rs:321-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 `sea-orm-macros/src/derives/arrow_schema.rs:203` 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 × 6) src/database/transaction.rs:248— src/database/transaction.rs:248-255 | src/database/transaction.rs:305-312 | src/database/transaction.rs:429-436 | src/database/transaction.rs:486-493 | src/database/transaction.rs:548-555 | src/database/transaction.rs:608-615 — 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 `src/database/transaction.rs:248` 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 × 6) sea-orm-sync/src/driver/sqlx_mysql.rs:202— sea-orm-sync/src/driver/sqlx_mysql.rs:202-206 | sea-orm-sync/src/driver/sqlx_postgres.rs:237-241 | sea-orm-sync/src/driver/sqlx_sqlite.rs:221-225 | src/driver/sqlx_mysql.rs:203-207 | src/driver/sqlx_postgres.rs:242-246 | src/driver/sqlx_sqlite.rs:222-226 — before extracting anything, compare `sea-orm-sync/src/driver/sqlx_mysql.rs` and `sea-orm-sync/src/driver/sqlx_postgres.rs` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `sea-orm-sync/src/driver/sqlx_mysql.rs: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.
Duplicated block (5 lines × 4) sea-orm-sync/src/entity/column.rs:438— sea-orm-sync/src/entity/column.rs:438-442 | sea-orm-sync/src/entity/column.rs:475-479 | src/entity/column.rs:438-442 | src/entity/column.rs:475-479 — before extracting anything, compare `sea-orm-sync/src/entity/column.rs` and `src/entity/column.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 96 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 `sea-orm-sync/src/entity/column.rs:438` 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 × 5) issues/1599/entity/src/cake.rs:30— issues/1599/entity/src/cake.rs:30-42 | sea-orm-sync/src/tests_cfg/cake_compact.rs:35-47 | sea-orm-sync/src/tests_cfg/cake_seaography.rs:31-43 | src/tests_cfg/cake_compact.rs:35-47 | src/tests_cfg/cake_seaography.rs:31-43 — before extracting anything, compare `issues/1599/entity/src/cake.rs` and `sea-orm-sync/src/tests_cfg/cake_seaography.rs` as WHOLE FILES: 95% 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. 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 `issues/1599/entity/src/cake.rs:30` 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 (268 lines × 2) sea-orm-sync/src/entity/column/types.rs:95— sea-orm-sync/src/entity/column/types.rs:95-362 | src/entity/column/types.rs:95-362 — before extracting anything, compare `sea-orm-sync/src/entity/column/types.rs` and `src/entity/column/types.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/column/types.rs:95` 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 (94 lines × 2) sea-orm-sync/src/entity/column_def.rs:40— sea-orm-sync/src/entity/column_def.rs:40-133 | src/entity/column_def.rs:40-133 — before extracting anything, compare `sea-orm-sync/src/entity/column_def.rs` and `src/entity/column_def.rs` as WHOLE FILES: 100% 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. 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 (214 lines × 2) sea-orm-sync/src/entity/compound/belongs_to.rs:88— sea-orm-sync/src/entity/compound/belongs_to.rs:88-301 | src/entity/compound/belongs_to.rs:88-301 — before extracting anything, compare `sea-orm-sync/src/entity/compound/belongs_to.rs` and `src/entity/compound/belongs_to.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/compound/belongs_to.rs:88` 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 (275 lines × 2) sea-orm-sync/src/entity/compound/has_many.rs:20— sea-orm-sync/src/entity/compound/has_many.rs:20-294 | src/entity/compound/has_many.rs:20-294 — before extracting anything, compare `sea-orm-sync/src/entity/compound/has_many.rs` and `src/entity/compound/has_many.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/compound/has_many.rs:20` 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 (126 lines × 2) sea-orm-sync/src/entity/compound/has_one.rs:18— sea-orm-sync/src/entity/compound/has_one.rs:18-143 | src/entity/compound/has_one.rs:18-143 — before extracting anything, compare `sea-orm-sync/src/entity/compound/has_one.rs` and `src/entity/compound/has_one.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/entity/compound/has_one.rs:18` 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 × 5) src/database/db_connection.rs:746— src/database/db_connection.rs:746-752 | src/database/executor.rs:260-266 | src/database/restricted_connection.rs:192-198 | src/database/restricted_connection.rs:281-287 | src/database/transaction.rs:231-237 — there are 5 copies across 4 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 (6 lines × 7) sea-orm-macros/src/derives/entity_model.rs:201— sea-orm-macros/src/derives/entity_model.rs:201-208 | sea-orm-macros/src/derives/entity_model.rs:220-227 | sea-orm-macros/src/derives/entity_model.rs:229-234 | sea-orm-macros/src/derives/entity_model.rs:247-254 | sea-orm-macros/src/derives/entity_model.rs:256-263 | sea-orm-macros/src/derives/entity_model.rs:265-270 | sea-orm-macros/src/derives/typed_column.rs:37-42 — there are 7 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 7 sites; resolving a subset leaves the remainder to drift apart. 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 (68 lines × 2) sea-orm-sync/src/tests_cfg/cake_expanded.rs:8— sea-orm-sync/src/tests_cfg/cake_expanded.rs:8-75 | src/tests_cfg/cake_expanded.rs:8-75 — before extracting anything, compare `sea-orm-sync/src/tests_cfg/cake_expanded.rs` and `src/tests_cfg/cake_expanded.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/tests_cfg/cake_expanded.rs:8` 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 (53 lines × 2) sea-orm-sync/src/tests_cfg/lunch_set_expanded.rs:9— sea-orm-sync/src/tests_cfg/lunch_set_expanded.rs:9-61 | src/tests_cfg/lunch_set_expanded.rs:9-61 — before extracting anything, compare `sea-orm-sync/src/tests_cfg/lunch_set_expanded.rs` and `src/tests_cfg/lunch_set_expanded.rs` as WHOLE FILES: 100% 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. 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 `sea-orm-sync/src/tests_cfg/lunch_set_expanded.rs:9` 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.
Interpolated log message defeats structured logging src/schema/builder.rs:466— `warn!` at line 466 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/entity/registry.rs:47— `debug!` at line 47 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/entity/registry.rs:51— `debug!` at line 51 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/entity/registry.rs:53— `debug!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:329— `debug!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:349— `debug!` at line 349 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:366— `debug!` at line 366 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:391— `debug!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:417— `debug!` at line 417 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:502— `debug!` at line 502 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:520— `debug!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:539— `debug!` at line 539 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:566— `debug!` at line 566 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging src/driver/rusqlite.rs:589— `debug!` at line 589 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/schema/builder.rs:460— `warn!` at line 460 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/entity/registry.rs:47— `debug!` at line 47 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/entity/registry.rs:51— `debug!` at line 51 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/entity/registry.rs:53— `debug!` at line 53 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:329— `debug!` at line 329 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:349— `debug!` at line 349 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:366— `debug!` at line 366 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:391— `debug!` at line 391 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:417— `debug!` at line 417 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:502— `debug!` at line 502 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging sea-orm-sync/src/driver/rusqlite.rs:520— `debug!` at line 520 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:347— `(resource.schema.is_none() || resource.schema.as_ref().unwrap() == WILDCARD) && resource.table == WILDCARD` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/executor/cursor.rs:227— `(self.sort_asc && !should_reverse_order) || (!self.sort_asc && should_reverse_order)` appears character-identically in 2 files — sea-orm-sync/src/executor/cursor.rs, src/executor/cursor.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/schema/builder.rs:673— `a.get_name() == b.get_name() || (a.get_ref_table() == b.get_ref_table() && a.get_columns() == b.get_columns() && a.get_ref_columns() == b.ge…` appears character-identically in 2 files — sea-orm-sync/src/schema/builder.rs, src/schema/builder.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/database/db_connection.rs:906— `base_url_parsed.scheme() == "postgres" || base_url_parsed.scheme() == "postgresql"` appears character-identically in 2 files — sea-orm-sync/src/database/db_connection.rs, src/database/db_connection.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/query/util.rs:181— `cfg!(feature = "sqlite-no-row-value-before-3_15") && matches!(backend, DbBackend::Sqlite)` appears character-identically in 2 files — sea-orm-sync/src/query/util.rs, src/query/util.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/schema/builder.rs:569— `column_def.get_column_name() == index_cols[0] && column_def.get_column_spec().unique` appears character-identically in 2 files — sea-orm-sync/src/schema/builder.rs, src/schema/builder.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/schema/entity.rs:156— `column_def.indexed && !column_def.unique` appears character-identically in 2 files — sea-orm-sync/src/schema/entity.rs, src/schema/entity.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/executor/insert.rs:471— `db_backend == DbBackend::MySql && last_insert_id == 0` appears character-identically in 2 files — sea-orm-sync/src/executor/insert.rs, src/executor/insert.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/query/loader.rs:1352— `from_cols.is_empty() || to_cols.is_empty()` appears character-identically in 2 files — sea-orm-sync/src/query/loader.rs, src/query/loader.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:320— `is_wildcard_permission && is_wildcard_resource` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/entity/active_model_ex.rs:388— `item.get_primary_key_value() && pk_item == pk` appears character-identically in 2 files — sea-orm-sync/src/entity/active_model_ex.rs, src/entity/active_model_ex.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/driver/sqlite.rs:24— `major > 3 || (major == 3 && minor >= 35)` appears character-identically in 2 files — sea-orm-sync/src/driver/sqlite.rs, src/driver/sqlite.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/driver/sqlx_common.rs:104— `ping_after_idle.is_none() && user_cb.is_none()` appears character-identically in 2 files — sea-orm-sync/src/driver/sqlx_common.rs, src/driver/sqlx_common.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:73— `resource.schema.as_deref() == Some(WILDCARD) || resource.table == WILDCARD` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:341— `resource.schema.is_none() || resource.schema.as_ref().unwrap() == WILDCARD || resource.schema == target.schema` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:344— `resource.table == WILDCARD || resource.table == target.table` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/executor/update.rs:123— `self.check_record_exists && result.rows_affected() == 0` appears character-identically in 2 files — sea-orm-sync/src/executor/update.rs, src/executor/update.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/driver/sqlx_mysql.rs:63— `string.starts_with("mysql://") && string.parse::<MySqlConnectOptions>().is_ok()` appears character-identically in 2 files — sea-orm-sync/src/driver/sqlx_mysql.rs, src/driver/sqlx_mysql.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/driver/sqlx_postgres.rs:63— `string.starts_with("postgres://") && string.parse::<PgConnectOptions>().is_ok()` appears character-identically in 2 files — sea-orm-sync/src/driver/sqlx_postgres.rs, src/driver/sqlx_postgres.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/driver/sqlx_sqlite.rs:64— `string.starts_with("sqlite:") && string.parse::<SqliteConnectOptions>().is_ok()` appears character-identically in 2 files — sea-orm-sync/src/driver/sqlx_sqlite.rs, src/driver/sqlx_sqlite.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate sea-orm-sync/src/rbac/engine/mod.rs:290— `user_override.permission_id == permission.id && user_override.resource_id == resource.id` appears character-identically in 2 files — sea-orm-sync/src/rbac/engine/mod.rs, src/rbac/engine/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file src/entity/primary_key.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/strum/helpers/metadata.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/strum/enum_iter.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/derives/derive_iden.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/strum/helpers/type_props.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/strum/helpers/case_style.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/strum/helpers/variant_props.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file sea-orm-macros/src/derives/active_enum_display.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file issues/324/src/model.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 18 significant file(s) lose their only recent owner: sea-orm-sync/src/executor/consolidate.rs, src/rbac/engine/mod.rs, src/entity/active_model_ex.rs, sea-orm-sync/src/entity/active_model_ex.rs, sea-orm-sync/src/query/json.rs, src/error.rs, sea-orm-sync/src/error.rs, src/rbac/context.rs (+10 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: src/executor/select_ext.rs, src/tests_cfg/serde_rename.rs, sea-orm-sync/src/docs.rs. Pair on, review, or document these before any departure.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
No ADRs found sea-orm-cli/Cargo.toml:34— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `sea-orm-cli/Cargo.toml` makes this repository a deployable product (line 34).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 28 project(s) overshoot their size bounds, lowering Project Cohesion to 8.6/10. The most over is `(repository root)` (42336 LoC, 346 module-visible types across 16 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.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 9 of 229 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 229 of the 451 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/entity/primary_key.rs, sea-orm-macros/src/strum/helpers/metadata.rs, sea-orm-macros/src/strum/enum_iter.rs, sea-orm-macros/src/derives/derive_iden.rs, sea-orm-macros/src/strum/helpers/type_props.rs, sea-orm-macros/src/strum/helpers/case_style.rs, sea-orm-macros/src/strum/helpers/variant_props.rs, sea-orm-macros/src/derives/active_enum_display.rs (and 1 more). 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 ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 10/24 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `issues/1143`, `issues/1278`, `issues/1357`, `issues/1473`, `issues/249/app` and 9 more.
No dependency-update automation REDACTED:12— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No app-layer HTTPS enforcement detected — This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
No inbound request validation detected — No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `Server::new(TcpListener` (issues/1599/graphql/src/main.rs:60).
Outdated: uuid — `uuid` is locked at 1.26.1 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated Cargo.lock.
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.
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 01a1daea-3209-755f-8ca3-3567960d3f93 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 125 · Warnings: 1020 · Recommendations: 89 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 16:35 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.