Public report of apache/opendal, 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 report Measured 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, 19:04 UTC · Survey ID cd_5dc54a50353e4b6db419f58ea1d15733

apache/opendal

Measured 14 November 2026, 19:03 UTC, at code version 68de94d

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 57out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 1 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: 207,315 lines of product code in 141 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Code Health, 47

Findings by how serious they are

397 critical 1289 serious 71 minor

15 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 19:03 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

60of 60 dimensions measured by tools.
1736of 1757 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
60dimensions across 7 lenses, read from 207,315 lines of product code in 141 projects.
Chapters

Executive summary

apache/opendal falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 57 out of 100 and is rated Adequate, and 391 of its 397 critical findings are security problems.

Code Health, at 47, is the weakest lens and counts most in the score. The best first step is handling the discarded errors, worth about 6 points. Removing the copied code would lift Code Health itself, also worth about 6. Raising Code Health to 67 would lift the score to about 64.

287 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Forty-four secrets can leak from the build pipeline, and thirty known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. The 14 pipeline steps that run downloads without checking them need each download checked against a known checksum first. The four pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The two errors that are caught and ignored need handling or logging instead of being ignored.

The product code is 207,315 lines, about €200,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 for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 47 · counts for 46%Production Readiness 56 · counts for 25%Security and Compliance 61 · counts for 14%Performance 85 · counts for 8%Domain Modelling 88 · counts for 4%Maturity 93 · counts for 2%Architecture 99 · counts for 1%

If Code Health rose from 47 to 67, the lowest score rated Strong, the score would rise from 57 to about 64.

Code composition: what the lines of code are
Business logic 2%Supporting code 8%Tests 90%
New since the last survey: 640 findings

These 640 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · SmbLister::query (cyclomatic 17) core/services/smb/src/lister.rs
  • Cognitive Complexity · SmbLister::query (cognitive 31) core/services/smb/src/lister.rs
  • Cognitive Complexity · local-images.localImages.rehype.<returned closure> (cognitive 30) website/plugins/local-images.js
  • Cognitive Complexity · AzblobBuilder::build (cognitive 16) core/services/azblob/src/backend.rs
  • God Classes · FunctionTooLong: odev::generate::dotnet::options_class dev/src/generate/dotnet.rs
  • God Classes · FileTooLong: generate/dotnet.rs dev/src/generate/dotnet.rs
  • God Classes · ClassTooLong: GitCore core/services/git/src/core.rs
  • God Classes · FunctionTooLong: odev::generate::dotnet::metadata_field dev/src/generate/dotnet.rs
  • God Classes · TooManyMethods: GcsCore core/services/gcs/src/core.rs
  • Code Duplication · Near-duplicate member family (4 members, 16 shared lines) core/core/src/raw/ops.rs
  • Code Duplication · Near-duplicate member pair (86 shared lines) core/core/src/layers/simulate.rs
  • Code Duplication · Near-duplicate member pair (44 shared lines) core/services/azdls/src/core.rs
  • Code Duplication · Near-duplicate member pair (25 shared lines) core/services/oss/src/core.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) core/services/mini_moka/src/backend.rs
  • Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/azblob/src/config.rs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) bindings/c/src/presign.rs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) core/services/compfs/src/config.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/alluxio/src/core.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/cos/src/core.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/foundationdb/src/backend.rs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) core/services/dropbox/src/core.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/c/src/operator.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/cloudflare-kv/src/core.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/etcd/src/core.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/github/src/core.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/dotnet/src/operator.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/dotnet/src/operator.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/aliyun-drive/src/config.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/cos/src/core.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/persy/src/backend.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED
  • Code Duplication · Edited copy of a member (89 corresponding lines) core/services/ghac/src/core.rs
  • Code Duplication · Edited copy of a member (76 corresponding lines) core/layers/fastmetrics/src/lib.rs
  • Code Duplication · Edited copy of a member (91 corresponding lines) core/services/s3/src/core.rs
  • Code Duplication · Edited copy of a member (80 corresponding lines) core/services/cos/src/backend.rs
  • Code Duplication · Edited copy of a member (70 corresponding lines) core/services/s3/src/copier.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) core/services/redis/src/reader.rs
  • Code Duplication · Edited copy of a member (55 corresponding lines) bindings/go/reader.go
  • Code Duplication · Edited copies of one member (4 members, 55+ corresponding lines) core/services/gcs/src/core.rs
  • Code Duplication · Edited copy of a member (86 corresponding lines) core/services/gdrive/src/backend.rs
  • Code Duplication · Edited copy of a member (50 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs
  • Code Duplication · Edited copies of one member (4 members, 59+ corresponding lines) core/services/koofr/src/backend.rs
  • Code Duplication · Edited copy of a member (53 corresponding lines) bindings/c/src/operator_info.rs
  • Code Duplication · Edited copy of a member (34 corresponding lines) core/services/b2/src/core.rs
  • Code Duplication · Edited copy of a member (42 corresponding lines) core/services/cos/src/backend.rs
  • Code Duplication · Edited copy of a member (51 corresponding lines) core/services/mongodb/src/backend.rs
  • Code Duplication · Edited copy of a member (52 corresponding lines) core/services/s3/src/copier.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) core/services/gcs/src/core.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) core/services/koofr/src/lister.rs
  • Code Duplication · Edited copy of a member (54 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs
  • Code Duplication · Edited copy of a member (47 corresponding lines) bindings/python/src/operator.rs
  • Code Duplication · Edited copy of a member (44 corresponding lines) core/services/s3/src/core.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) core/services/s3/src/deleter.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) core/services/gdrive/src/core.rs
  • Code Duplication · Edited copy of a member (42 corresponding lines) core/services/swift/src/core.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) bindings/python/src/operator.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) core/services/git/src/core.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) core/services/gridfs/src/config.rs
  • Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) core/services/mysql/src/backend.rs
  • Code Duplication · Edited copies of one member (3 members, 33+ corresponding lines) core/services/http/src/core.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) core/services/tos/src/copier.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) core/services/s3/src/core.rs
  • Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) core/services/azdls/src/config.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) core/services/s3/src/copier.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) core/core/src/raw/ops.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) core/services/gcs/src/reader.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) core/services/webdav/src/core.rs
  • Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) core/core/src/layers/correctness_check.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) core/core/src/types/copy.rs
  • Code Duplication · Edited copy of a member (31 corresponding lines) core/services/s3/src/core.rs
  • Code Duplication · Edited copies of one member (6 members, 27+ corresponding lines) core/services/cos/src/reader.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) core/services/azblob/src/core.rs
  • Code Duplication · Edited copies of one member (5 members, 35+ corresponding lines) core/services/azdls/src/core.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) core/services/persy/src/core.rs
  • Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) core/services/mysql/src/config.rs
  • Code Duplication · Edited copies of one member (4 members, 34+ corresponding lines) core/services/oss/src/core.rs
  • Code Duplication · Edited copies of one member (3 members, 33+ corresponding lines) core/core/src/types/operator/operator.rs
  • Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) core/services/azdls/src/reader.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) core/services/koofr/src/core.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs
  • Code Duplication · Edited copy of a member (36 corresponding lines) core/core/src/raw/oio/write/block_write.rs
  • Code Duplication · Edited copies of one member (5 members, 24+ corresponding lines) core/services/aliyun-drive/src/reader.rs
  • Code Duplication · Edited copy of a member (23 corresponding lines) core/services/ghac/src/reader.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) core/core/src/layers/correctness_check.rs
  • Code Duplication · Edited copy of a member (37 corresponding lines) core/services/s3/src/core.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) core/layers/retry/src/lib.rs
  • Code Duplication · Edited copy of a member (37 corresponding lines) core/services/dropbox/src/backend.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) core/services/github/src/core.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) core/services/http/src/reader.rs
  • Code Duplication · Edited copies of one member (3 members, 33+ corresponding lines) core/services/dashmap/src/writer.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) core/services/pcloud/src/backend.rs
  • Code Duplication · Edited copies of one member (4 members, 33+ corresponding lines) core/services/cos/src/core.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) core/services/ipmfs/src/reader.rs
  • Code Duplication · Edited copies of one member (7 members, 24+ corresponding lines) core/services/azblob/src/backend.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) core/services/tos/src/core.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) dev/src/generate/dotnet.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) core/layers/metrics/src/lib.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) core/services/lakefs/src/core.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) core/services/upyun/src/core.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: 282 findings

These 282 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one. The first 100 are listed here.

  • Cyclomatic Complexity · label.selected_labels (cyclomatic 19) scripts/label.py
  • Cyclomatic Complexity · sign_source_release.validate (cyclomatic 18) scripts/sign_source_release.py
  • Cyclomatic Complexity · verify_source_reproducibility.main (cyclomatic 18) scripts/verify_source_reproducibility.py
  • Cognitive Complexity · verify_source_reproducibility.main (cognitive 33) scripts/verify_source_reproducibility.py
  • Cognitive Complexity · local-images.localImages.rehype (cognitive 30) website/plugins/local-images.js
  • Cognitive Complexity · label.selected_labels (cognitive 23) scripts/label.py
  • Cognitive Complexity · sign_source_release.validate (cognitive 21) scripts/sign_source_release.py
  • Cognitive Complexity · merge_local_staging.copy_and_append_index (cognitive 19) scripts/merge_local_staging.py
  • Cognitive Complexity · release_impact.breaking_declaration (cognitive 17) scripts/release_impact.py
  • Cognitive Complexity · release_impact.render_plan (cognitive 17) scripts/release_impact.py
  • Cognitive Complexity · release_lifecycle.publish (cognitive 17) scripts/release_lifecycle.py
  • Cognitive Complexity · label.label_event (cognitive 16) scripts/label.py
  • God Classes · FileTooLong: go/reader.go bindings/go/reader.go
  • Code Duplication · Near-duplicate member family (4 members, 17 shared lines) core/services/gcs/src/core.rs
  • Code Duplication · Near-duplicate member family (4 members, 16 shared lines) core/core/src/raw/ops.rs
  • Code Duplication · Near-duplicate member family (3 members, 30 shared lines) core/services/gridfs/src/config.rs
  • Code Duplication · Near-duplicate member pair (71 shared lines) core/core/src/layers/simulate.rs
  • Code Duplication · Near-duplicate member pair (43 shared lines) core/services/azdls/src/core.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) core/services/azdls/src/core.rs
  • Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) bindings/go/copier.go
  • Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/b2/src/config.rs
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) core/services/compfs/src/config.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/alluxio/src/core.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/cos/src/core.rs
  • Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/foundationdb/src/backend.rs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) bindings/go/copy.go
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/c/src/operator.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/cloudflare-kv/src/core.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/etcd/src/core.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/github/src/core.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/c/src/presign.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/dotnet/src/operator.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/layers/retry/src/lib.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/aliyun-drive/src/config.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/cos/src/core.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/dropbox/src/core.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/obs/src/backend.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/persy/src/backend.rs
  • Code Duplication · Duplicated block (31–38 lines × 2) core/services/gcs-grpc/src/backend.rs
  • Code Duplication · Duplicated block (33–34 lines × 2) core/core/src/layers/simulate.rs
  • Code Duplication · Duplicated block (28 lines × 2) core/services/azdls/src/core.rs
  • Code Duplication · Duplicated block (21–22 lines × 2) core/services/gdrive/src/core.rs
  • Code Duplication · Duplicated block (21 lines × 2) bindings/haskell/src/lib.rs
  • Code Duplication · Duplicated block (21 lines × 2) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (21 lines × 2) core/services/s3/src/core.rs
  • Code Duplication · Duplicated block (20 lines × 2) bindings/c/src/operator.rs
  • Code Duplication · Duplicated block (18–19 lines × 4) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (18–19 lines × 4) core/services/cos/src/writer.rs
  • Code Duplication · Duplicated block (19 lines × 2) core/services/azdls/src/config.rs
  • Code Duplication · Duplicated block (19 lines × 2) core/services/s3/src/lister.rs
  • Code Duplication · Duplicated block (19 lines × 2) core/services/yandex-disk/src/core.rs
  • Code Duplication · Duplicated block (19 lines × 2) integrations/object_store/src/service/core.rs
  • Code Duplication · Duplicated block (16–18 lines × 4) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (18 lines × 2) core/core/src/types/copy.rs
  • Code Duplication · Duplicated block (17–18 lines × 2) core/services/gcs-grpc/src/backend.rs
  • Code Duplication · Duplicated block (18 lines × 2) core/services/gridfs/src/config.rs
  • Code Duplication · Duplicated block (18 lines × 2) core/services/rocksdb/src/backend.rs
  • Code Duplication · Duplicated block (16–17 lines × 3) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (15–17 lines × 2) bindings/dotnet/src/operator.rs
  • Code Duplication · Duplicated block (13–17 lines × 2) bindings/dotnet/src/operator.rs
  • Code Duplication · Duplicated block (16–17 lines × 2) core/services/azblob/src/backend.rs
  • Code Duplication · Duplicated block (17 lines × 2) core/services/cos/src/core.rs
  • Code Duplication · Duplicated block (16 lines × 3) core/layers/retry/src/lib.rs
  • Code Duplication · Duplicated block (15–16 lines × 3) core/services/cos/src/writer.rs
  • Code Duplication · Duplicated block (16 lines × 2) core/services/azblob/src/writer.rs
  • Code Duplication · Duplicated block (16 lines × 2) core/services/oss/src/lister.rs
  • Code Duplication · Duplicated block (16 lines × 2) core/services/persy/src/backend.rs
  • Code Duplication · Duplicated block (15 lines × 2) core/core/src/raw/oio/copy/block_copy.rs
  • Code Duplication · Duplicated block (15 lines × 2) core/services/tos/src/core.rs
  • Code Duplication · Duplicated block (10–14 lines × 5) core/services/b2/src/core.rs
  • Code Duplication · Duplicated block (14 lines × 4) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (14 lines × 4) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (13–14 lines × 3) core/services/tos/src/core.rs
  • Code Duplication · Duplicated block (14 lines × 2) bindings/c/src/operator.rs
  • Code Duplication · Duplicated block (14 lines × 2) bindings/haskell/src/lib.rs
  • Code Duplication · Duplicated block (14 lines × 2) core/services/azdls/src/core.rs
  • Code Duplication · Duplicated block (13–14 lines × 2) core/services/cos/src/core.rs
  • Code Duplication · Duplicated block (13–14 lines × 2) core/services/cos/src/writer.rs
  • Code Duplication · Duplicated block (14 lines × 2) core/services/mini_moka/src/writer.rs
  • Code Duplication · Duplicated block (14 lines × 2) core/services/surrealdb/src/core.rs
  • Code Duplication · Duplicated block (13 lines × 11) bindings/haskell/src/lib.rs
  • Code Duplication · Duplicated block (12–13 lines × 6) core/services/cos/src/lister.rs
  • Code Duplication · Duplicated block (11–13 lines × 3) core/services/azblob/src/core.rs
  • Code Duplication · Duplicated block (13 lines × 3) core/services/cos/src/core.rs
  • Code Duplication · Duplicated block (13 lines × 3) core/services/oss/src/lister.rs
  • Code Duplication · Duplicated block (11–13 lines × 2) bindings/c/src/types.rs
  • Code Duplication · Duplicated block (12–13 lines × 2) core/services/alluxio/src/core.rs
  • Code Duplication · Duplicated block (12–13 lines × 2) core/services/cos/src/writer.rs
  • Code Duplication · Duplicated block (13 lines × 2) core/services/oss/src/core.rs
  • Code Duplication · Duplicated block (9–13 lines × 2) core/services/s3/src/deleter.rs
  • Code Duplication · Duplicated block (12 lines × 6) core/services/aliyun-drive/src/reader.rs
  • Code Duplication · Duplicated block (12 lines × 4) core/core/src/raw/ops.rs
  • Code Duplication · Duplicated block (12 lines × 4) core/services/azdls/src/core.rs
  • Code Duplication · Duplicated block (11–12 lines × 2) bindings/haskell/src/types.rs
  • Code Duplication · Duplicated block (12 lines × 2) bindings/nodejs/src/options.rs
  • Code Duplication · Duplicated block (11–12 lines × 2) bindings/python/src/operator.rs
  • Code Duplication · Duplicated block (11–12 lines × 2) core/core/src/layers/simulate.rs
  • Code Duplication · Duplicated block (12 lines × 2) core/services/b2/src/writer.rs
  • Code Duplication · Duplicated block (11–12 lines × 2) core/services/gdrive/src/backend.rs
  • Code Duplication · Duplicated block (12 lines × 2) core/services/github/src/core.rs
Rebuild cost: about €200,000 · Estimate
Cost to rebuild€67,000 to €340,000, for 1,121 to 3,556 hours of work, about 1.4 person-years for 1 to 3 engineers
Difficulty of the problemLow, 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.8 at a score of 57. 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.
SizeLarge: 207,315 lines of product code
Comment linesThe estimate prices 205,250 lines. Comment lines count towards the size of 207,315 lines but aren't priced as work.
What it is notNot 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.

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 2 EmptyCatchBlock finding(s) in Explicit Debt — start with OperatorOutputStream.cs (2).
Raises the score by about 6 points · Low effort · Explicit Debt
2
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).
Raises the score by about 5 points · Low effort · REDACTED Scanning
3
Act on each finding's own remediation rather than one rule: the move depends on what recurs.
Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
Raises the score by about 6 points · Medium effort · Code Duplication

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Code Health, at 47 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 2 Explicit Debt 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 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 104,399 lines over the last 90 days, which is about 423,396 lines a year. At that pace, the extra work comes to an estimated 24.2 to 145.1 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.

arch opendal (Cargo) opendal (Cargo) opendal-core opendal-core opendal (Cargo)->opendal-core opendal-http-transport-reqwest opendal-http-transport-reqwest opendal (Cargo)->opendal-http-transport-reqwest opendal-layer-async-backtrace opendal-layer-async-backtrace opendal (Cargo)->opendal-layer-async-backtrace opendal-layer-await-tree opendal-layer-await-tree opendal (Cargo)->opendal-layer-await-tree opendal-layer-fastmetrics opendal-layer-fastmetrics opendal (Cargo)->opendal-layer-fastmetrics opendal-layer-logging opendal-layer-logging opendal (Cargo)->opendal-layer-logging opendal-layer-metrics opendal-layer-metrics opendal (Cargo)->opendal-layer-metrics opendal-layer-observe-metrics-common opendal-layer-observe-metrics-common opendal (Cargo)->opendal-layer-observe-metrics-common opendal-layer-otelmetrics opendal-layer-otelmetrics opendal (Cargo)->opendal-layer-otelmetrics opendal-layer-prometheus opendal-layer-prometheus opendal (Cargo)->opendal-layer-prometheus opendal-layer-prometheus-client opendal-layer-prometheus-client opendal (Cargo)->opendal-layer-prometheus-client opendal-layer-retry opendal-layer-retry opendal (Cargo)->opendal-layer-retry opendal-layer-timeout opendal-layer-timeout opendal (Cargo)->opendal-layer-timeout opendal-service-azblob opendal-service-azblob opendal (Cargo)->opendal-service-azblob opendal-service-azdls opendal-service-azdls opendal (Cargo)->opendal-service-azdls opendal-service-azfile opendal-service-azfile opendal (Cargo)->opendal-service-azfile opendal-service-ghac opendal-service-ghac opendal (Cargo)->opendal-service-ghac opendal-testkit opendal-testkit opendal (Cargo)->opendal-testkit opendal-http-transport-reqwest->opendal-core opendal-layer-async-backtrace->opendal-core opendal-layer-await-tree->opendal-core opendal-layer-fastmetrics->opendal-core opendal-layer-fastmetrics->opendal-layer-observe-metrics-common opendal-layer-logging->opendal-core opendal-layer-metrics->opendal-core opendal-layer-metrics->opendal-layer-observe-metrics-common opendal-layer-observe-metrics-common->opendal-core opendal-layer-otelmetrics->opendal-core opendal-layer-otelmetrics->opendal-layer-observe-metrics-common opendal-layer-prometheus->opendal-core opendal-layer-prometheus->opendal-layer-observe-metrics-common opendal-layer-prometheus-client->opendal-core opendal-layer-prometheus-client->opendal-layer-observe-metrics-common opendal-layer-retry->opendal-core opendal-layer-timeout->opendal-core opendal-service-azblob->opendal-core opendal-service-azure-common opendal-service-azure-common opendal-service-azblob->opendal-service-azure-common opendal-service-azdls->opendal-core opendal-service-azdls->opendal-service-azure-common opendal-service-azfile->opendal-core opendal-service-azfile->opendal-service-azure-common opendal-service-azure-common->opendal-core opendal-service-ghac->opendal-core opendal-service-ghac->opendal-service-azblob opendal-testkit->opendal-core opendal-testkit->opendal-layer-logging opendal-testkit->opendal-layer-retry opendal-testkit->opendal-layer-timeout __more__ +121 more projects

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.

855 modules, with 2760 dependencies between them. 7 loops run through 19 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 opendal_core.blocking.operator2 opendal_core.raw.oio.list.api3 opendal_core.raw.operation4 opendal_core.types.bytes_range5 opendal_core.types.capability6 opendal_core.types.context.operation7 opendal_core.types.error8 opendal_core.types.metadata9 opendal_core.types.operator.uri10 opendal_core.raw.layer11 opendal_core.raw.oio.copy.api12 opendal_core.raw.oio.entry13 opendal_core.raw.oio.list.page_list14 opendal_core.raw.oio.read.api15 opendal_core.raw.ops16 opendal_core.types.builder17 opendal_core.types.operator.registry18 opendal_core.raw.oio.delete.api19 opendal_core.raw.oio.read.stream_read20 opendal_core.raw.service21 opendal_core.types.buffer22 opendal_core.raw.oio.buf.queue_buf23 opendal_core.raw.oio.delete.one_shot_delete24 opendal_core.raw.oio.write.api25 opendal_service_azblob.core26 opendal_service_b2.core27 opendal_service_gcs.core28 opendal_service_gdrive.core29 opendal_service_hf.core30 opendal_service_s3.core31 opendal_service_tos.core32 opendal_core.layers.complete33 opendal_core.layers.error_context34 opendal_core.raw.oio.write.multipart_write35 opendal_core.raw.oio.write.one_shot_write36 opendal_layer_concurrent_limit37 opendal_layer_logging38 opendal_layer_observe_metrics_common39 opendal_layer_retry40 opendal_layer_timeout
1 opendal_core.blocking.operator
2 opendal_core.raw.oio.list.api
3 opendal_core.raw.operation
4 opendal_core.types.bytes_range
5 opendal_core.types.capability
6 opendal_core.types.context.operation
7 opendal_core.types.error
8 opendal_core.types.metadata
9 opendal_core.types.operator.uri
10 opendal_core.raw.layer1
11 opendal_core.raw.oio.copy.api1
12 opendal_core.raw.oio.entry1
13 opendal_core.raw.oio.list.page_list1
14 opendal_core.raw.oio.read.api2
15 opendal_core.raw.ops52
16 opendal_core.types.builder1
17 opendal_core.types.operator.registry1
18 opendal_core.raw.oio.delete.api2
19 opendal_core.raw.oio.read.stream_read21
20 opendal_core.raw.service2220
21 opendal_core.types.buffer3
22 opendal_core.raw.oio.buf.queue_buf1
23 opendal_core.raw.oio.delete.one_shot_delete21
24 opendal_core.raw.oio.write.api222
25 opendal_service_azblob.core111115111
26 opendal_service_b2.core211111211
27 opendal_service_gcs.core111112711
28 opendal_service_gdrive.core11131211
29 opendal_service_hf.core311111
30 opendal_service_s3.core221125112
31 opendal_service_tos.core121115111
32 opendal_core.layers.complete12121111211211
33 opendal_core.layers.error_context11111112121211
34 opendal_core.raw.oio.write.multipart_write2221
35 opendal_core.raw.oio.write.one_shot_write21
36 opendal_layer_concurrent_limit1212113121211
37 opendal_layer_logging132113112121911
38 opendal_layer_observe_metrics_common12122112121411
39 opendal_layer_retry113111113121211
40 opendal_layer_timeout11112112121211
Uses a module listed above itPart of a loopThe module itself
1 opendal_core.blocking.operator2 opendal_core.raw.oio.list.api3 opendal_core.raw.operation4 opendal_core.types.bytes_range5 opendal_core.types.capability6 opendal_core.types.context.operation7 opendal_core.types.error8 opendal_core.types.metadata9 opendal_core.types.operator.uri10 opendal_core.raw.layer11 opendal_core.raw.oio.copy.api12 opendal_core.raw.oio.entry13 opendal_core.raw.oio.list.page_list14 opendal_core.raw.oio.read.api15 opendal_core.raw.ops16 opendal_core.types.builder17 opendal_core.types.operator.registry18 opendal_core.raw.oio.delete.api19 opendal_core.raw.oio.read.stream_read20 opendal_core.raw.service21 opendal_core.types.buffer22 opendal_core.raw.oio.buf.queue_buf23 opendal_core.raw.oio.delete.one_shot_delete24 opendal_core.raw.oio.write.api25 opendal_service_azblob.core26 opendal_service_b2.core27 opendal_service_gcs.core28 opendal_service_gdrive.core29 opendal_service_hf.core30 opendal_service_s3.core31 opendal_service_tos.core32 opendal_core.layers.complete33 opendal_core.layers.error_context34 opendal_core.raw.oio.write.multipart_write35 opendal_core.raw.oio.write.one_shot_write36 opendal_layer_concurrent_limit37 opendal_layer_logging38 opendal_layer_observe_metrics_common39 opendal_layer_retry40 opendal_layer_timeoutopendal_core.blocking.operator1opendal_core.raw.oio.list.api2opendal_core.raw.operation3opendal_core.types.bytes_range4opendal_core.types.capability5opendal_core.types.context.operation6opendal_core.types.error7opendal_core.types.metadata8opendal_core.types.operator.uri9opendal_core.raw.layer10opendal_core.raw.oio.copy.api11opendal_core.raw.oio.entry12opendal_core.raw.oio.list.page_list13opendal_core.raw.oio.read.api14opendal_core.raw.ops15opendal_core.types.builder16opendal_core.types.operator.registry17opendal_core.raw.oio.delete.api18opendal_core.raw.oio.read.stream_read19opendal_core.raw.service20opendal_core.types.buffer21opendal_core.raw.oio.buf.queue_buf22opendal_core.raw.oio.delete.one_shot_delete23opendal_core.raw.oio.write.api24opendal_service_azblob.core25opendal_service_b2.core26opendal_service_gcs.core27opendal_service_gdrive.core28opendal_service_hf.core29opendal_service_s3.core30opendal_service_tos.core31opendal_core.layers.complete32opendal_core.layers.error_context33opendal_core.raw.oio.write.multipart_write34opendal_core.raw.oio.write.one_shot_write35opendal_layer_concurrent_limit36opendal_layer_logging37opendal_layer_observe_metrics_common38opendal_layer_retry39opendal_layer_timeout401111252112212220312122211111511121111121111111271111131211311111221125112121115111121211112112111111111212121122212112121131212111321131121219111212211212141111311111312121111112112121211+815 more modules (most-connected shown)

At a glance — Code Health · 47% · Weak · gated by R1, R10 ·

At a glance — Architecture · 99% · Exemplary ·

At a glance — Maturity · 93% · Exemplary ·

At a glance — Readiness · 56% · Adequate · gated by D13, R4 ·

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

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

At a glance — Performance · 85% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection373High / Critical
A03:2025 — Software Supply Chain Failures135High / Critical
A07:2025 — Authentication Failures5High / Critical

Roadmap

Top priorities: Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with OperatorOutputStream.cs (2); Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract; Resolve the 1 finding(s) in Type Safety.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with OperatorOutputStream.cs (2).+6.2 ptsLowExplicit Debt
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).+5.3 ptsLowREDACTED Scanning
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.+6.1 ptsMediumCode Duplication
Resolve the 1 finding(s) in Type Safety.+5.9 ptsMediumType Safety
Add tests that import the unreached modules (directly or through their public entry).+2.2 ptsMediumTest Coverage
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+1.6 ptsMediumDR & Backup
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json.+0.7 ptsLowPlatform End-of-Life
Resolve the 4 No assertions finding(s) in Test Quality — start with DeleteBehaviorTest.cs (2), ListBehaviorTest.cs (2).+0.6 ptsLowTest Quality

File quality

Per-file score 0–10 — a quality signature. Of 438 files carrying findings, judged against the Preview bar: 6% slop · 15% mixed · 79% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: High CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.6SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopREDACTED Scanning: Leaked secret: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 397

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 — 1289

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 — 71

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

Could not be resolved — 15

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

Methodology & how to trust this report

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 60 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 — 60 dimensions across the health lenses
D1D2D3D4D5D6D7D10D11D13D14D15D16D17D19D20D24D26D28D29D30D31D34D35D36D37D43D44AX10AX2AX3AX4AX5AX8AX9DM4DM5GD1M1M2M3M4P1P10P3P4P5P6PF3R1R10R2R3R4R6R7R8R9X20X5

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
  1. 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, 1736 of 1757 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1db71-a066-71cb-b7e4-eec5718402d7.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .cs, .tsx, .rs, and our analyzer cannot run the .rs test suite(s) — so no coverage was collected for the repository as a whole. The .NET half did build and run, and its own line coverage came back at 5.2% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test 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. The 125 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 169 test source file(s) (.py, .rs, .java, .go, .js, .mjs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — 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. Test reliability for the vitest suite in bindings/nodejs/ was NOT MEASURED: the dependency install for bindings/nodejs/ could not reach github.com, which the analyzer sandbox's egress allowlist does not carry (Error: Error when performing the request to https://registry.npmjs.org/pnpm/-/pnpm-8.11.0.tgz; for troubleshooting help, see https://github.com/nodejs/corepack#…), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D14 License Compliance — 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. This repository declares a Cargo manifest, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Cargo dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D17 Explicit Debt — 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. The 2 deducted marker(s) and the 0.1/KLoC density on this row were taken over this repository's .NET projects ALONE: .rs (179,803 lines, 89% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 35 task marker(s) (TODO/FIXME/HACK/XXX) across 30 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • 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.
  • 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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.
  • D23 Boundary Type-Coupling — 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. Large codebase (195,720 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `bindings/dotnet/OpenDAL/Options/NativeOptionsWriter.cs`, `bindings/nodejs/generated.d.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX6 Interface segregation — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • AXR1 Runtime accessibility — 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. User interface: 10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" .
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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.
  • X1 Async 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

Repo exclusion declarations: 16 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
  • 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".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity7.2 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was S3Builder::build at 40. A further 10 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FastmetricsInterceptor::observe at 18 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: core/layers/fastmetrics/src/lib.rs (FastmetricsInterceptor::observe at 18), core/layers/metrics/src/lib.rs (MetricsInterceptor::observe at 18), core/layers/otelmetrics/src/lib.rs (OtelMetricsInterceptor::observe at 18), core/layers/prometheus-client/src/lib.rs (PrometheusClientInterceptor::observe at 18), core/layers/prometheus/src/lib.rs (PrometheusInterceptor::observe at 18), and 3 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.

S3Builder::build (cyclomatic 40)core/services/s3/src/backend.rs:931
Storage.init (cyclomatic 32)bindings/dart/lib/opendal.dart:32
opendal_service_webdav::core::parse_user_metadata_from_xml (cyclomatic 29)core/services/webdav/src/core.rs:610
GdriveFlatLister::initialize (cyclomatic 24)core/services/gdrive/src/lister.rs:400
CorrectnessService::compose (cyclomatic 22)core/core/src/layers/correctness_check.rs:339

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

What to do

  1. Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with S3Builder::build (cyclomatic 40), Storage.init (cyclomatic 32). — 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 2 together lifts Cyclomatic Complexity from 7.2 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

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

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

69 method(s) exceeded the cognitive complexity threshold of 15; the worst was opendal_service_webdav::core::parse_user_metadata_from_xml at 54.

odev::generate::python::format_text (cognitive 28) · ×6dev/src/generate/python.rs:115
opendal_service_webdav::core::parse_user_metadata_from_xml (cognitive 54) · ×2core/services/webdav/src/core.rs:610
S3Builder::build (cognitive 50) · ×2core/services/s3/src/backend.rs:931
GdriveFlatLister::initialize (cognitive 47) · ×2core/services/gdrive/src/lister.rs:400
GdriveBackend::rename (cognitive 33) · ×2core/services/gdrive/src/backend.rs:499

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

What to do

  1. Bring the 10 bodies over 30 down to 30 or less in Cognitive Complexity — start with opendal_service_webdav::core::parse_user_metadata_from_xml (cognitive 54), S3Builder::build (cognitive 50), GdriveFlatLister::initialize (cognitive 47). — 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 10 together lifts Cognitive Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D3 · God Classes8.7 / 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.

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

72 god class(es) detected.

FileTooLong: src/operator.rs · ×30bindings/dotnet/src/operator.rs
ClassTooLong: S3Core · ×12core/services/s3/src/core.rs:97
TooManyMethods: Operator · ×10core/core/src/types/operator/operator.rs:196
MethodTooLong: S3Builder.build · ×9core/services/s3/src/backend.rs:931
TooManyFields: Capability · ×6core/core/src/types/capability.rs:65

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

What to do

  1. Resolve the 30 FileTooLong finding(s) in God Classes — start with core.rs (13), lib.rs (6), operator.rs (4). — One of this dimension's main actionable groups (30 warning-level).
  2. Resolve the 12 ClassTooLong finding(s) in God Classes — start with core.rs (8), operator.rs (2), backend.rs. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 10 TooManyMethods finding(s) in God Classes — start with operator.rs (2), core.rs (2), Operator.cs. — 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.

D4 · Code Duplication4.5 / 10Weak✓ Tool-verified

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.

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

539 duplicated block group(s) detected. 13.8 % of the production lines (26,927 of 195,720) are in a reported copy. A further 415 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 954 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (10 lines × 2) · ×32bindings/c/src/operator.rs:441
Duplicated block (9 lines × 2) · ×31bindings/python/src/options.rs:178
Duplicated block (8 lines × 2) · ×31bindings/dotnet/src/operator.rs:602
Duplicated block (7 lines × 2) · ×25bindings/c/src/reader.rs:70
Duplicated block (12 lines × 2) · ×23bindings/c/src/operator.rs:554

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

What to do

  1. Resolve the 32 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with core.rs (9), operator.rs (6), backend.rs (4). — One of this dimension's main actionable groups (32 warning-level).
  2. Resolve the 31 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with core.rs (11), backend.rs (8), deleter.rs (2). — One of this dimension's main actionable groups (31 warning-level).
  3. Resolve the 31 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with core.rs (14), backend.rs (4), lib.rs (3). — One of this dimension's main actionable groups (31 warning-level).

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

D5 · Coupling9.8 / 10Stronggated by 3 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.

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

141 production modules (Maven+Cargo+npm+Go+SwiftPM+RubyGems+pub+CMake), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 120 of the 141 (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: OpenDAL (SwiftPM) · ×2
Unstable project opendal (Cargo)
Off the main sequence: opendal-service-azure-common · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Unstable project opendal (Cargo) finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 560 classes have LCOM4 above 3.

Low cohesion: OpendalStore (LCOM4 4)integrations/object_store/src/store.rs:182

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with store.rs. — One of this dimension's main actionable groups (1 warning-level).

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

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

All 1 mechanizable ADR(s) are enforced: 1 by analyzers, 0 by tests. Cycles found: 0.

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

D10 · Test Quality9.5 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 125 tests. Measured on the C# suite only — at least 169 test source file(s) (.py, .rs, .java, .go, .js, .mjs) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: DeleteBehavior_DeletingMissingPath_IsAllowed · ×4bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:68

What to do

  1. Resolve the 4 No assertions finding(s) in Test Quality — start with DeleteBehaviorTest.cs (2), ListBehaviorTest.cs (2). — One of this dimension's main actionable groups (4 warning-level).

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 3 measured tier(s). unit: measured (0 flaky); JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in bindings/nodejs/; node:test via `pnpm install --frozen-lockfile --ignore-scripts` in website/ (3 tests)): measured (0 flaky); Rust (integrations/parquet, 242 test files): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

2 secret(s) detected. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

REDACTED

What to do

  1. Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

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

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

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 118 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 4 direct `PackageReference`(s), and 114 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Cargo manifest and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 15 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: core/services/s3/src/backend.rs (15×40=600); core/services/gcs/src/core.rs (11×17=187); core/services/hf/src/core.rs (10×18=180) Repeated repair below the complexity floor: core/services/hf/src/reader.rs (6 of 8 changes were fixes); scripts/release_lifecycle.py (6 of 6 changes were fixes); bindings/java/src/executor.rs (4 of 4 changes were fixes)

Hotspot: core/services/s3/src/backend.rs · ×10core/services/s3/src/backend.rs:931
Repeated repair: core/services/hf/src/reader.rs · ×5core/services/hf/src/reader.rs:145

What to do

  1. Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with lister.rs (6), backend.rs (2), core.rs (2). — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 5 Repeated repair finding(s) in Churn × Complexity Hotspots — start with reader.rs, release_lifecycle.py, executor.rs. — One of this dimension's main actionable groups (5 warning-level).

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

D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

45 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is bindings/dotnet/OpenDAL/Operator.cs. Counted over 613 of the 965 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 · ×3
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.7 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

2 deducted debt markers + 0 dead symbols across 11821 LoC in the .NET projects (0.1/KLoC) → score 9.7. Measured on the .NET source only: .rs (89% of production source) was not read, and carries at least 35 uncounted task marker(s) in 30 file(s).

EmptyCatchBlock · ×2bindings/dotnet/OpenDAL/OperatorOutputStream.cs:319

What to do

  1. Resolve the 2 EmptyCatchBlock finding(s) in Explicit Debt — start with OperatorOutputStream.cs (2). — One of this dimension's main actionable groups (2 issue-level).

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

D19 · Documentation Quality6.4 / 10Adequate✓ Tool-verified

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

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

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

1 of 2 documentation facets pass in full; short on: F2 example. 231 document(s) read across 12 unit(s).

Documentation: no build, run or usage example · ×8bindings/nodejs/npm/darwin-arm64/README.md:1

What to do

  1. Resolve the 8 Documentation finding(s) in Documentation Quality — start with README.md (8). — One of this dimension's main actionable groups (8 recommendation-level).

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

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

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.

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

0 of 89 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D24 · Comment Value10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

0 of 63 judged comments only repeat the code they sit on (0.0 %).

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 3 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

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

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

373 finding(s): 0 critical, 357 high, 13 medium, 3 low. 275 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 8 file(s) — `bindings/dotnet/OpenDAL.Tests/ConstructorTest.cs` (lines 118–120, line 144), `bindings/dotnet/OpenDAL/Options/NativeOptionsWriter.cs` (line 56, line 177), `bindings/java/mvnw` (lines 204–205, line 257), `bindings/nodejs/generated.d.ts` (line 25), `core/services/gdrive/src/path_index.rs` (line 290), … (+3 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `bindings/dotnet/OpenDAL.Tests/ConstructorTest.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. Separately, one or more rules could not re-parse an embedded snippet in 40 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 20 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (20 issue-level).
  2. Resolve the 12 REDACTED finding(s) charged to Static Analysis (SAST) — the other 275 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (287 issue-level, 12 of them charged here).
  3. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

101 finding(s): 4 critical, 26 high, 68 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (7), REDACTED (5). — One of this dimension's main actionable groups (26 issue-level).
  2. Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

D34 · Knowledge Freshness9.6 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

26 of 613 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/services/azure-common/src/lib.rs. Counted over 613 of the 965 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledgecore/services/azure-common/src/lib.rs:1
Orphaned file · ×25bindings/nodejs/src/layer.rs:1
Further orphaned files (smaller)

What to do

  1. Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with lib.rs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 25 Orphaned file finding(s) in Knowledge Freshness — start with lister.rs (5), writer.rs (4), layer.rs (2). — One of this dimension's main actionable groups (25 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.2 / 10Stronggated by 34 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: error_context.rs↔lib.rs 89%; operator_info.rs↔REDACTED 82%; lister.rs↔lister.rs 67%

Change coupling: operator_info.rs ↔ REDACTED · ×27bindings/c/src/operator_info.rs:1
Change-coupling hub: error_context.rs → lib.rs, lib.rs, lib.rs, lib.rs, lib.rs, lib.rs · ×7core/core/src/layers/error_context.rs

What to do

  1. Resolve the 27 Change coupling finding(s) in Change Coupling — start with backend.rs (11), lib.rs (4), lister.rs (3). — One of this dimension's main actionable groups (27 warning-level).
  2. Resolve the 7 Change-coupling hub finding(s) in Change Coupling — start with backend.rs (3), lib.rs (2), error_context.rs. — One of this dimension's main actionable groups (7 warning-level).

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

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

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 15 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 12 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

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

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

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

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

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

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

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 18 platform declaration(s) and 15 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.

End-of-life runtime: Node.js 10bindings/nodejs/package.json:82

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces OpenDAL ↔ OpenDAL.Interop.Buffers ↔ OpenDAL.Interop.Result ↔ OpenDAL.Interop.Result.Abstractions ↔ OpenDAL.Layer.Abstractions depend on each other. The lightest dependency in the cycle is OpenDAL → OpenDAL.Layer.Abstractions (OpenDAL.Operator → OpenDAL.Layer.Abstractions.ILayer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — bindings/dotnet/OpenDAL/Operator.cs:27

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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

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

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

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

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

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

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

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

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

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

DM4 · Rich vs anemic domain model8.0 / 10Strong✓ 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.

  • `Capability` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — bindings/python/src/capability.rs:29

What to do

  • Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

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

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

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

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

M1 · Documentation (README)8.3 / 10Exemplary✓ Tool-verified

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.

M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

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

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.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

P10 · Library API & versioning9.8 / 10Exemplary✓ Tool-verified

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.

  • `OpenDAL.Interop.Result.OpenDALResult` (bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net8.0)`, `OpenDAL.Tests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25
  • `OpenDAL.Interop.Result.OpenDALResult` (bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net10.0)`, `OpenDAL.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25
  • `OpenDAL.Utilities` (bindings/dotnet/OpenDAL/Utilities.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net8.0)`, `OpenDAL.Tests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — bindings/dotnet/OpenDAL/Utilities.cs:28
  • `OpenDAL.Utilities` (bindings/dotnet/OpenDAL/Utilities.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net10.0)`, `OpenDAL.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — bindings/dotnet/OpenDAL/Utilities.cs:28

What to do

  • Make `OpenDAL.Interop.Result.OpenDALResult` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `OpenDAL.Interop.Result.OpenDALResult` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `OpenDAL.Utilities` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `OpenDAL.Utilities` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling9.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `maven`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:19

What to do

  • Dependabot is configured but does not watch `nuget`, `maven` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene8.5 / 10Exemplary✓ Tool-verified

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from 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.

  • `fs.readFileSync` in `includeSpecifications` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — website/plugins/specifications-docs-plugin.js:79

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety0.4 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 1 typed · 22 plain JS — the untyped files are bindings/nodejs/index.cjs, bindings/nodejs/index.mjs, bindings/nodejs/scripts/header.mjs, bindings/nodejs/tests/service.test.mjs, bindings/nodejs/tests/suites/async.suite.mjs, bindings/nodejs/tests/suites/asyncDeleteOptions.suite.mjs (+16 more).
R10 · Code Duplication0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • bindings/nodejs/index.cjs:24 · bindings/nodejs/index.mjs:24 — these 2 files are line-for-line copies of one another — 68 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — bindings/nodejs/index.cjs:24

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R4 · Test Coverage2.5 / 10Weak✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — bindings/nodejs/index.cjs:1, bindings/nodejs/scripts/header.mjs:1, bindings/nodejs/theme/index.tsx:1

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

R8 · Dependency Hygiene7.0 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. — bindings/nodejs/theme/index.tsx:20
  • Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types9.8 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • ~0.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 31112 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health47%Weak — gated by R1, R10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture99%ExemplaryStrongest area.
Maturity93%ExemplarySolid.
Readiness56%Adequate — gated by D13, R4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security61%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling88%ExemplarySolid.
Performance85%ExemplarySolid.
Unscored — 3 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 75 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AX1 Captive dependencies — no DI registrations detected
  • AX6 Interface segregation — AX6 reached only 6% of this repository's production lines — rust (179,803 lines), go (4,441 lines), c (2,946 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), swift (207 lines), lua (177 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5432: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5432/ Call log: - navigating to "http://127.0.0.1:5432/", waiting until "load" . This repository also has a user interface (10 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .cpp, .dart, .go, .hs, .java, .lua, .ml, .php, .py, .rb, .rs, .swift, .tsx, .zig, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby, Rust, Swift surface was not measured.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
  • DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
  • DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
  • 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
  • DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • 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 this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • 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
  • IC1 Incompleteness & stubs — IC1 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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'.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — sqlx is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
  • P9 Domain vs controller coverage — coverage data present for 108 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 by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — X1 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — X16 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — X18 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — X2 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — X3 reached only 2% of this repository's production lines — rust (179,803 lines), go (4,441 lines), javascript (4,251 lines), c (2,946 lines), java (2,889 lines), python (2,767 lines), cpp (1,902 lines), haskell (902 lines), ocaml (849 lines), zig (568 lines), dart (249 lines), ruby (237 lines), swift (207 lines), lua (177 lines), typescript (40 lines), php (36 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 397 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 262 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×26
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 1 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D17 · Explicit Debt · EmptyCatchBlock · ×2
  • EmptyCatchBlock bindings/dotnet/OpenDAL/OperatorOutputStream.cs:319 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock bindings/dotnet/OpenDAL/OperatorOutputStream.cs:344 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle bindings/dotnet/OpenDAL/Operator.cs:27 — The namespaces OpenDAL ↔ OpenDAL.Interop.Buffers ↔ OpenDAL.Interop.Result ↔ OpenDAL.Interop.Result.Abstractions ↔ OpenDAL.Layer.Abstractions depend on each other. The lightest dependency in the cycle is OpenDAL → OpenDAL.Layer.Abstractions (OpenDAL.Operator → OpenDAL.Layer.Abstractions.ILayer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×1
  • Orphaned knowledge core/services/azure-common/src/lib.rs:1 — No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
DM4 · Rich vs anemic domain model · Anemic domain model · ×1
  • Anemic domain model: Capability bindings/python/src/capability.rs:29 — `Capability` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside.
R8 · Dependency Hygiene · Unlisted import 'react' · ×1
  • Unlisted import 'react' bindings/nodejs/theme/index.tsx:20 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Serious — 1289 finding(s)
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×32
  • Duplicated block (10 lines × 2) bindings/c/src/operator.rs:441 — bindings/c/src/operator.rs:441-450 | bindings/c/src/operator.rs:499-508 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/operator.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 (10 lines × 2) bindings/c/src/operator.rs:987 — bindings/c/src/operator.rs:987-996 | bindings/c/src/operator.rs:1039-1048 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/operator.rs:987` 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) bindings/c/src/operator.rs:1111 — bindings/c/src/operator.rs:1111-1120 | bindings/c/src/operator.rs:1181-1190 — both copies are in the same file, so extract the 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 `bindings/c/src/operator.rs:1111` 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) bindings/c/src/operator.rs:1492 — bindings/c/src/operator.rs:1492-1501 | bindings/c/src/operator.rs:1539-1548 — both copies are in the same file, so extract the 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 `bindings/c/src/operator.rs:1492` 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) bindings/dotnet/src/operator.rs:708 — bindings/dotnet/src/operator.rs:708-717 | bindings/dotnet/src/operator.rs:812-821 — both copies are in the same file, so extract the 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 `bindings/dotnet/src/operator.rs:708` 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) bindings/java/src/async_operator.rs:499 — bindings/java/src/async_operator.rs:499-508 | bindings/java/src/operator.rs:335-344 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (10 lines × 2) bindings/python/src/operator.rs:415 — bindings/python/src/operator.rs:415-424 | bindings/python/src/operator.rs:1225-1234 — both copies are in the same file, so extract the 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 `bindings/python/src/operator.rs:415` 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) core/core/src/raw/oio/copy/block_copy.rs:128 — core/core/src/raw/oio/copy/block_copy.rs:128-137 | core/core/src/raw/oio/copy/multipart_copy.rs:154-166 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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 `core/core/src/raw/oio/copy/block_copy.rs:128` 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 × 2) core/core/src/types/write/buffer_sink.rs:91 — core/core/src/types/write/buffer_sink.rs:91-100 | core/core/src/types/write/buffer_sink.rs:138-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) core/services/cos/src/deleter.rs:43 — core/services/cos/src/deleter.rs:43-52 | core/services/obs/src/deleter.rs:42-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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/deleter.rs:43` 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) core/services/d1/src/core.rs:151 — core/services/d1/src/core.rs:151-160 | core/services/d1/src/core.rs:170-179 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/d1/src/core.rs:151` 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) core/services/gcs/src/deleter.rs:43 — core/services/gcs/src/deleter.rs:43-52 | core/services/gcs/src/deleter.rs:91-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gcs/src/deleter.rs:43` 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) core/services/lakefs/src/core.rs:64 — core/services/lakefs/src/core.rs:64-73 | core/services/lakefs/src/core.rs:96-105 — both copies are in the same file, so extract the 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 `core/services/lakefs/src/core.rs:64` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/lakefs/src/core.rs:107` calls `is_full`, `header`, `to_header` and `core/services/lakefs/src/core.rs:75` 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) core/services/lakefs/src/core.rs:176 — core/services/lakefs/src/core.rs:176-185 | core/services/lakefs/src/core.rs:241-250 — both copies are in the same file, so extract the 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 `core/services/lakefs/src/core.rs:176` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/lakefs/src/core.rs:251` calls `header`, `insert` and `core/services/lakefs/src/core.rs:187` 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) core/services/mysql/src/backend.rs:131 — core/services/mysql/src/backend.rs:131-140 | core/services/postgresql/src/backend.rs:125-134 — before extracting anything, compare `core/services/mysql/src/backend.rs` and `core/services/postgresql/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/mysql/src/backend.rs:131` 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) core/services/oss/src/core.rs:338 — core/services/oss/src/core.rs:338-348 | core/services/s3/src/core.rs:577-586 — before extracting anything, compare `core/services/oss/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/oss/src/core.rs:338` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) core/services/redis/src/reader.rs:60 — core/services/redis/src/reader.rs:60-69 | core/services/sqlite/src/reader.rs:58-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/redis/src/reader.rs:60` 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) core/services/smb/src/copier.rs:81 — core/services/smb/src/copier.rs:81-91 | core/services/smb/src/writer.rs:85-94 — 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 `core/services/smb/src/copier.rs:81` 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 (10 lines × 2) core/services/upyun/src/core.rs:192 — core/services/upyun/src/core.rs:192-201 | core/services/upyun/src/core.rs:354-363 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) core/core/src/raw/oio/copy/block_copy.rs:172 — core/core/src/raw/oio/copy/block_copy.rs:172-181 | core/core/src/raw/oio/copy/multipart_copy.rs:197-206 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) core/services/cos/src/lister.rs:49 — core/services/cos/src/lister.rs:49-58 | core/services/obs/src/lister.rs:45-55 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) core/services/s3/src/core.rs:913 — core/services/s3/src/core.rs:913-922 | core/services/s3/src/core.rs:962-974 — both copies are in the same file, so extract the 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 `core/services/s3/src/core.rs:962` 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) core/services/koofr/src/core.rs:86 — core/services/koofr/src/core.rs:86-95 | core/services/vercel-blob/src/core.rs:258-269 — 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 `core/services/vercel-blob/src/core.rs:258` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) core/services/alluxio/src/core.rs:60 — core/services/alluxio/src/core.rs:60-70 | core/services/alluxio/src/core.rs:98-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) core/services/github/src/config.rs:80 — core/services/github/src/config.rs:80-89 | core/services/lakefs/src/config.rs:111-120 — 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 `core/services/github/src/config.rs:80` 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.
  • + 7 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×31
  • Duplicated block (9 lines × 2) bindings/python/src/options.rs:178 — bindings/python/src/options.rs:178-186 | bindings/python/src/options.rs:198-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bindings/python/src/options.rs:177` calls `make_range` and `bindings/python/src/options.rs:197` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) core/core/src/raw/http_util/multipart.rs:225 — core/core/src/raw/http_util/multipart.rs:225-233 | core/core/src/raw/http_util/multipart.rs:391-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/raw/http_util/multipart.rs:225` 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) core/core/src/types/copy.rs:145 — core/core/src/types/copy.rs:145-153 | core/core/src/types/list.rs:73-81 — 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 `core/core/src/types/copy.rs:145` 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) core/core/src/types/delete/futures_delete_sink.rs:98 — core/core/src/types/delete/futures_delete_sink.rs:98-106 | core/core/src/types/delete/futures_delete_sink.rs:131-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/types/delete/futures_delete_sink.rs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/services/azblob/src/core.rs:670 — core/services/azblob/src/core.rs:670-678 | core/services/azblob/src/core.rs:800-808 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/azfile/src/backend.rs:167 — core/services/azfile/src/backend.rs:167-175 | core/services/dbfs/src/backend.rs:85-93 — 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 `core/services/azfile/src/backend.rs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/services/b2/src/backend.rs:114 — core/services/b2/src/backend.rs:114-122 | core/services/upyun/src/backend.rs:106-114 — before extracting anything, compare `core/services/b2/src/backend.rs` and `core/services/upyun/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/b2/src/backend.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) core/services/cos/src/backend.rs:171 — core/services/cos/src/backend.rs:171-179 | core/services/obs/src/backend.rs:138-146 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/obs/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/backend.rs:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/services/onedrive/src/writer.rs:82 — core/services/onedrive/src/writer.rs:82-90 | core/services/onedrive/src/writer.rs:141-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/s3/src/backend.rs:1567 — core/services/s3/src/backend.rs:1567-1577 | core/services/tos/src/backend.rs:443-451 — before extracting anything, compare `core/services/s3/src/backend.rs` and `core/services/tos/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/s3/src/backend.rs:1567` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/services/tos/src/core.rs:694 — core/services/tos/src/core.rs:694-702 | core/services/tos/src/core.rs:740-748 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/webhdfs/src/core.rs:183 — core/services/webhdfs/src/core.rs:183-191 | core/services/webhdfs/src/core.rs:342-350 — both copies are in the same file, so extract the 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 `core/services/webhdfs/src/core.rs:183` 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) dev/src/generate/metadata.rs:76 — dev/src/generate/metadata.rs:76-84 | dev/src/generate/metadata.rs:123-131 — both copies are in the same file, so extract the 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 `dev/src/generate/metadata.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) integrations/object_store/src/store.rs:472 — integrations/object_store/src/store.rs:472-480 | integrations/object_store/src/store.rs:822-830 — both copies are in the same file, so extract the 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 `integrations/object_store/src/store.rs:472` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/core/src/raw/std_io_util.rs:57 — core/core/src/raw/std_io_util.rs:57-65 | core/core/src/types/error.rs:519-527 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) core/services/ftp/src/backend.rs:70 — core/services/ftp/src/backend.rs:70-78 | core/services/sftp/src/backend.rs:77-85 — before extracting anything, compare `core/services/ftp/src/backend.rs` and `core/services/sftp/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) core/services/pcloud/src/backend.rs:81 — core/services/pcloud/src/backend.rs:81-89 | core/services/seafile/src/backend.rs:82-90 — before extracting anything, compare `core/services/pcloud/src/backend.rs` and `core/services/seafile/src/backend.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) core/services/rocksdb/src/backend.rs:175 — core/services/rocksdb/src/backend.rs:175-183 | core/services/sled/src/backend.rs:199-207 — before extracting anything, compare `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` as WHOLE FILES: this scan already matched 6 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 (9 lines × 2) core/core/src/layers/simulate.rs:506 — core/core/src/layers/simulate.rs:506-514 | core/core/src/raw/oio/list/flat_list.rs:98-109 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/core/src/layers/simulate.rs:506` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) core/services/cloudflare-kv/src/deleter.rs:83 — core/services/cloudflare-kv/src/deleter.rs:83-92 | core/services/s3/src/deleter.rs:71-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) core/services/cos/src/core.rs:221 — core/services/cos/src/core.rs:221-229 | core/services/cos/src/core.rs:466-474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/b2/src/core.rs:596 — core/services/b2/src/core.rs:596-604 | core/services/b2/src/core.rs:627-635 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/azdls/src/core.rs:474 — core/services/azdls/src/core.rs:474-482 | core/services/azdls/src/core.rs:520-528 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (9 lines × 2) core/services/azdls/src/lister.rs:67 — core/services/azdls/src/lister.rs:67-75 | core/services/azfile/src/lister.rs:67-75 — 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 `core/services/azdls/src/lister.rs:67` 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, `core/services/azdls/src/lister.rs:66` calls `status` and `core/services/azfile/src/lister.rs:66` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) core/services/gdrive/src/deleter.rs:69 — core/services/gdrive/src/deleter.rs:69-77 | core/services/gdrive/src/deleter.rs:101-109 — both copies are in the same file, so extract the 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.
  • + 6 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×31
  • Duplicated block (8 lines × 2) bindings/dotnet/src/operator.rs:602 — bindings/dotnet/src/operator.rs:602-609 | bindings/dotnet/src/operator.rs:2043-2050 — both copies are in the same file, so extract the 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 `bindings/dotnet/src/operator.rs:602` 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) core/layers/dtrace/src/lib.rs:342 — core/layers/dtrace/src/lib.rs:342-349 | core/layers/dtrace/src/lib.rs:381-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) core/layers/fastmetrics/src/lib.rs:173 — core/layers/fastmetrics/src/lib.rs:173-180 | core/layers/prometheus-client/src/lib.rs:117-124 — 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 `core/layers/fastmetrics/src/lib.rs:173` 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) core/services/azblob/src/core.rs:668 — core/services/azblob/src/core.rs:668-675 | core/services/s3/src/core.rs:813-821 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) core/services/azblob/src/core.rs:803 — core/services/azblob/src/core.rs:803-810 | core/services/gcs/src/core.rs:553-560 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) core/services/cos/src/core.rs:534 — core/services/cos/src/core.rs:534-544 | core/services/s3/src/core.rs:1321-1328 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:534` 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, `core/services/s3/src/core.rs:1319` calls `insert_sse_headers` and `core/services/cos/src/core.rs:532` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) core/services/dropbox/src/core.rs:251 — core/services/dropbox/src/core.rs:251-258 | core/services/dropbox/src/core.rs:276-283 — both copies are in the same file, so extract the 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 `core/services/dropbox/src/core.rs:251` 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) core/services/dropbox/src/core.rs:301 — core/services/dropbox/src/core.rs:301-308 | core/services/dropbox/src/core.rs:328-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/dropbox/src/core.rs:301` 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) core/services/gcs/src/core.rs:410 — core/services/gcs/src/core.rs:410-417 | core/services/gcs/src/core.rs:856-863 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) core/services/http/src/core.rs:171 — core/services/http/src/core.rs:171-178 | core/services/obs/src/core.rs:708-715 — before extracting anything, compare `core/services/http/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 5 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 `core/services/http/src/core.rs:171` 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) core/services/ipfs/src/core.rs:60 — core/services/ipfs/src/core.rs:60-67 | core/services/webdav/src/core.rs:214-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/ipfs/src/core.rs:60` 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) core/services/onedrive/src/core.rs:194 — core/services/onedrive/src/core.rs:194-201 | core/services/onedrive/src/core.rs:251-258 — both copies are in the same file, so extract the 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 `core/services/onedrive/src/core.rs:194` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) core/services/pcloud/src/core.rs:145 — core/services/pcloud/src/core.rs:145-152 | core/services/pcloud/src/writer.rs:49-56 — 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 `core/services/pcloud/src/core.rs:145` 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 after the matched lines, `core/services/pcloud/src/core.rs:154` calls `Err` and `core/services/pcloud/src/writer.rs:58` 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 × 2) core/services/pcloud/src/deleter.rs:48 — core/services/pcloud/src/deleter.rs:48-55 | core/services/pcloud/src/writer.rs:49-56 — 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 `core/services/pcloud/src/deleter.rs:48` 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) core/services/redis/src/reader.rs:39 — core/services/redis/src/reader.rs:39-46 | core/services/sqlite/src/reader.rs:40-47 — 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 `core/services/redis/src/reader.rs:39` 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) dev/src/release/package.rs:326 — dev/src/release/package.rs:326-333 | dev/src/release/package.rs:460-470 — both copies are in the same file, so extract the 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 `dev/src/release/package.rs:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) bindings/nodejs/src/lib.rs:966 — bindings/nodejs/src/lib.rs:966-973 | bindings/python/src/metadata.rs:157-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) core/services/dbfs/src/backend.rs:62 — core/services/dbfs/src/backend.rs:62-69 | core/services/swift/src/backend.rs:55-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) core/services/hdfs/src/backend.rs:99 — core/services/hdfs/src/backend.rs:99-106 | core/services/webhdfs/src/backend.rs:125-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) core/services/rocksdb/src/lister.rs:32 — core/services/rocksdb/src/lister.rs:32-39 | core/services/sled/src/lister.rs:32-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `core` to `Arc<RocksdbCore>` in one and `Arc<SledCore>` 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 (8 lines × 2) bindings/c/src/entry.rs:92 — bindings/c/src/entry.rs:92-99 | bindings/c/src/metadata.rs:106-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) bindings/c/src/lister.rs:88 — bindings/c/src/lister.rs:88-95 | bindings/c/src/writer.rs:136-143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) core/services/dashmap/src/backend.rs:172 — core/services/dashmap/src/backend.rs:172-179 | core/services/moka/src/backend.rs:318-325 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 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.
  • Duplicated block (8 lines × 2) core/services/fs/src/writer.rs:105 — core/services/fs/src/writer.rs:105-112 | core/services/sftp/src/writer.rs:42-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) core/services/rocksdb/src/backend.rs:185 — core/services/rocksdb/src/backend.rs:185-192 | core/services/sled/src/backend.rs:209-216 — before extracting anything, compare `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` as WHOLE FILES: this scan already matched 6 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.
  • + 6 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×30
  • FileTooLong: src/operator.rs bindings/dotnet/src/operator.rs — FileTooLong — 1323 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 96 free functions. The bar is 500 significant lines; this is 823 over it, 2.65× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/core.rs core/services/s3/src/core.rs — FileTooLong — 1142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: S3Core (4 blocks, 97-1502). The bar is 500 significant lines; this is 642 over it, 2.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/operator.rs bindings/python/src/operator.rs — FileTooLong — 1087 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 587 over it, 2.17× 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/core.rs core/services/gcs/src/core.rs — FileTooLong — 1035 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: GcsCore (4 blocks, 67-1107). The bar is 500 significant lines; this is 535 over it, 2.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/core.rs core/services/hf/src/core.rs — FileTooLong — 876 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 376 over it, 1.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/types.rs bindings/c/src/types.rs — FileTooLong — 841 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 341 over it, 1.68× 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: operator/operator.rs core/core/src/types/operator/operator.rs — FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: Operator (5 blocks, 196-2828). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs core/layers/observe-metrics-common/src/lib.rs — FileTooLong — 835 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 335 over it, 1.67× 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: raw/ops.rs core/core/src/raw/ops.rs — FileTooLong — 834 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 334 over it, 1.67× 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/core.rs core/services/tos/src/core.rs — FileTooLong — 833 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: TosCore (3 blocks, 61-917). The bar is 500 significant lines; this is 333 over it, 1.67× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/backend.rs core/services/s3/src/backend.rs — FileTooLong — 832 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: S3Builder (4 blocks, 84-1305). The bar is 500 significant lines; this is 332 over it, 1.66× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/core.rs core/services/azblob/src/core.rs — FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: AzblobCore (4 blocks, 75-884). The bar is 500 significant lines; this is 274 over it, 1.55× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/core.rs core/services/gdrive/src/core.rs — FileTooLong — 674 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 174 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/core.rs core/services/oss/src/core.rs — FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 168 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/lib.rs core/layers/retry/src/lib.rs — FileTooLong — 660 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 160 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: generate/dotnet.rs dev/src/generate/dotnet.rs — FileTooLong — 638 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 138 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/core.rs core/services/aliyun-drive/src/core.rs — FileTooLong — 625 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: AliyunDriveCore (3 blocks, 61-615). The bar is 500 significant lines; this is 125 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs core/layers/logging/src/lib.rs — FileTooLong — 603 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 103 over it, 1.21× 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: OpenDAL/Operator.cs bindings/dotnet/OpenDAL/Operator.cs — FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 96 over it, 1.19× 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/operator.rs bindings/c/src/operator.rs — FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 31 free functions. The bar is 500 significant lines; this is 90 over it, 1.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: src/core.rs core/services/b2/src/core.rs — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: B2Core (4 blocks, 46-654). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/core.rs core/services/webdav/src/core.rs — FileTooLong — 569 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 69 over it, 1.14× 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/core.rs core/services/azdls/src/core.rs — FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: AzdlsCore (4 blocks, 51-621). The bar is 500 significant lines; this is 56 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/store.rs integrations/object_store/src/store.rs — FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: OpendalStore (6 blocks, 182-755). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs core/layers/tail-cut/src/lib.rs — FileTooLong — 547 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 47 over it, 1.09× 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.
  • + 5 more in this group — see findings.md.
D35 · Change Coupling · Change coupling · ×27
  • Change coupling: operator_info.rs ↔ REDACTED bindings/c/src/operator_info.rs:1 — `bindings/c/src/operator_info.rs` and `REDACTED` change together 82% of the time (9 of the 11 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `62d8866f` feat(copy.go): add copy options (#7707); `6d0e75db` feat(lister.go): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
  • Change coupling: types.rs ↔ operator_info.go bindings/c/src/types.rs:1 — `bindings/c/src/types.rs` and `bindings/go/operator_info.go` change together 64% of the time (7 of the 11 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `62d8866f` feat(copy.go): add copy options (#7707); `6d0e75db` feat(lister.go): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/azdls/src/backend.rs:1 — `core/services/azdls/src/backend.rs` and `core/services/azfile/src/backend.rs` change together 64% of the time (7 of the 11 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d5dd6dfa` fix: repair azfile, b2, and conditional read behavior (#8175); `15fd535c` test: Add suffix read behavior tests (#7739); `0f45d6af` refactor(core): route reqsign send via accessor http client (#7234) — run `git show` on any of them.
  • Change coupling: operator_info.rs ↔ types.rs bindings/c/src/operator_info.rs:1 — `bindings/c/src/operator_info.rs` and `bindings/c/src/types.rs` change together 64% of the time (7 of the 11 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 7 shared commits counted here, the most recent 3 are `62d8866f` feat(copy.go): add copy options (#7707); `6d0e75db` feat(lister.go): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
  • Change coupling: lib.rs ↔ lib.rs core/layers/await-tree/src/lib.rs:1 — `core/layers/await-tree/src/lib.rs` and `core/layers/fastrace/src/lib.rs` change together 64% of the time (7 of the 11 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4196c1fe` fix(layers): wrap copier with all layers (#7596); `ebcdfb4c` refactor!: Refactor oio::Delete to make it's API simple (#6823) (at that commit the files were still `core/src/layers/await_tree.rs` and `core/src/layers/fastrace.rs`); `13c3214d` refactor(core)!: Merge operations to build more clean metrics (#5892) (at that commit the files were still `core/src/layers/await_tree.rs` and `core/src/layers/fastrace.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/mysql/src/backend.rs:1 — `core/services/mysql/src/backend.rs` and `core/services/postgresql/src/backend.rs` change together 64% of the time (7 of the 11 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/postgresql/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/postgresql/backend.rs`) — run `git show` on any of them.
  • Change coupling: lister.rs ↔ lister.rs core/services/gcs/src/lister.rs:1 — `core/services/gcs/src/lister.rs` and `core/services/obs/src/lister.rs` change together 62% of the time (10 of the 16 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/gcs/lister.rs` and `core/src/services/obs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/gcs/dir_stream.rs` and `src/services/obs/dir_stream.rs`); `c2147124` feat: Implement object page stream for services like s3 (#787) (at that commit the files were still `src/services/gcs/dir_stream.rs` and `src/services/obs/dir_stream.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ lister.rs core/services/fs/src/backend.rs:1 — `core/services/fs/src/backend.rs` and `core/services/fs/src/lister.rs` change together 61% of the time (11 of the 18 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 11 shared commits counted here, the most recent 3 are `cd2fc9ff` refactor: Remove metakey concept (#5319) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/fs/lister.rs`); `87e98ef7` feat(fs): expose the metadata for fs services (#5005) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/fs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/fs/backend.rs` and `src/services/fs/dir_stream.rs`) — run `git show` on any of them.
  • Change coupling: lib.rs ↔ lib.rs core/layers/metrics/src/lib.rs:1 — `core/layers/metrics/src/lib.rs` and `core/layers/tracing/src/lib.rs` change together 61% of the time (28 of the 46 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 28 shared commits counted here, the most recent 3 are `0805ddd1` chore(layers): check the examples when running tests (#5104) (at that commit the files were still `core/src/layers/metrics.rs` and `core/src/layers/tracing.rs`); `1ec735ec` feat: add Writer::abort method (#1937) (at that commit the files were still `core/src/layers/metrics.rs` and `core/src/layers/tracing.rs`); `8b9c4c28` refactor: Change presign to async for future refactor (#1900) (at that commit the files were still `core/src/layers/metrics.rs` and `core/src/layers/tracing.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/rocksdb/src/backend.rs:1 — `core/services/rocksdb/src/backend.rs` and `core/services/sled/src/backend.rs` change together 59% of the time (10 of the 17 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `15d6d484` Set shared capability of Mini Moka and OPFS (#7856); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/rocksdb/backend.rs` and `core/src/services/sled/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/rocksdb/backend.rs` and `core/src/services/sled/backend.rs`) — run `git show` on any of them.
  • Change coupling: lister.rs ↔ lister.rs core/services/azblob/src/lister.rs:1 — `core/services/azblob/src/lister.rs` and `core/services/gcs/src/lister.rs` change together 57% of the time (12 of the 21 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/azblob/lister.rs` and `core/src/services/gcs/lister.rs`); `42ad2dd7` refactor: Use chrono instead of time to work well with ecosystem (#1912) (at that commit the files were still `core/src/services/azblob/pager.rs` and `core/src/services/gcs/pager.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/gcs/dir_stream.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/fs/src/backend.rs:1 — `core/services/fs/src/backend.rs` and `core/services/hdfs/src/backend.rs` change together 57% of the time (41 of the 72 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 41 shared commits counted here, the most recent 3 are `b94d02e0` refactor(core): lazy open positioned read handles (#7796); `577912df` refactor: remove uuid dependency when creating a temp path (#6324) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/hdfs/backend.rs`); `c00f0fdd` refactor(raw/oio): Reorganize to allow adding more features (#2698) (at that commit the files were still `core/src/services/fs/backend.rs` and `core/src/services/hdfs/backend.rs`) — run `git show` on any of them.
  • Change coupling: lister.rs ↔ lister.rs core/services/azblob/src/lister.rs:1 — `core/services/azblob/src/lister.rs` and `core/services/obs/src/lister.rs` change together 56% of the time (9 of the 16 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, 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 `09b0672f` fix(core): List root should not return itself (#3824) (at that commit the files were still `core/src/services/azblob/lister.rs` and `core/src/services/obs/lister.rs`); `168c7994` feat: Add object page size support (#1318) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/obs/dir_stream.rs`); `9fdd2d6e` feat: Implement cached metadata for ObjectEntry (#761) (at that commit the files were still `src/services/azblob/dir_stream.rs` and `src/services/obs/dir_stream.rs`) — run `git show` on any of them.
  • Change coupling: operator.rs ↔ REDACTED bindings/c/src/operator.rs:1 — `bindings/c/src/operator.rs` and `REDACTED` change together 55% of the time (11 of the 20 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `2f395484` feat(binding/go): Add Copier (#7732); `dc006976` feat(binding/go): add write with metadata (#7827); `57307918` feat(binding/go): add reader with options (#7817) — run `git show` on any of them.
  • Change coupling: operator.rs ↔ operator_info.go bindings/c/src/operator.rs:1 — `bindings/c/src/operator.rs` and `bindings/go/operator_info.go` change together 55% of the time (6 of the 11 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `62d8866f` feat(copy.go): add copy options (#7707); `6d0e75db` feat(lister.go): Add opendal_list_options_set_versions and opendal_li…; `70016be9` feat(binding/go): expose all stats options (#7670) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/mysql/src/backend.rs:1 — `core/services/mysql/src/backend.rs` and `core/services/sqlite/src/backend.rs` change together 55% of the time (6 of the 11 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/sqlite/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/mysql/backend.rs` and `core/src/services/sqlite/backend.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/cloudflare-kv/src/backend.rs:1 — `core/services/cloudflare-kv/src/backend.rs` and `core/services/redis/src/backend.rs` change together 54% of the time (7 of the 13 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dcbf53ea` Reapply "fix(core): deserialize duration config values from strings" …; `399cfbf3` Revert "fix(core): deserialize duration config values from strings" (…; `188f0c07` fix(core): deserialize duration config values from strings (#7983) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/cloudflare-kv/src/backend.rs:1 — `core/services/cloudflare-kv/src/backend.rs` and `core/services/memcached/src/backend.rs` change together 54% of the time (7 of the 13 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dcbf53ea` Reapply "fix(core): deserialize duration config values from strings" …; `399cfbf3` Revert "fix(core): deserialize duration config values from strings" (…; `188f0c07` fix(core): deserialize duration config values from strings (#7983) — run `git show` on any of them.
  • Change coupling: async_operator.rs ↔ operator.rs bindings/java/src/async_operator.rs:1 — `bindings/java/src/async_operator.rs` and `bindings/java/src/operator.rs` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 8 shared commits counted here, the most recent 3 are `06235da7` refactor: Deprecate remove_all API in favor of RFC-3911: Deleter API …; `a612f32a` feat(bindings/java): Add StatOptions support for new options API (#6255); `7c6e970f` feat(bindings/java): Add ListOptions support for new options API (#6246) — run `git show` on any of them.
  • Change coupling: lib.rs ↔ Operator.java bindings/java/src/lib.rs:1 — `bindings/java/src/lib.rs` and `bindings/java/src/main/java/org/apache/opendal/Operator.java` change together 53% of the time (17 of the 32 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `27c7afe4` feat(bindings/java): add OperatorReader and ReaderOptions (#8259); `a76040c6` feat: Binding Java's createInputStream and createOutputStream to supp…; `a612f32a` feat(bindings/java): Add StatOptions support for new options API (#6255) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/gcs/src/backend.rs:1 — `core/services/gcs/src/backend.rs` and `core/services/obs/src/backend.rs` change together 53% of the time (43 of the 81 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 43 shared commits counted here, the most recent 3 are `0f45d6af` refactor(core): route reqsign send via accessor http client (#7234); `bb145e66` feat: Add from_uri support for more object storage services (#6665) (at that commit the files were still `core/src/services/gcs/backend.rs` and `core/src/services/obs/backend.rs`); `96c041c1` feat(core): Add presign delete support (#5647) (at that commit the files were still `core/src/services/gcs/backend.rs` and `core/src/services/obs/backend.rs`) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/redis/src/backend.rs:1 — `core/services/redis/src/backend.rs` and `core/services/sled/src/backend.rs` change together 53% of the time (9 of the 17 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, 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 `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`); `52998792` refactor: kv::adapter should use Buffer (write part) (#4496) (at that commit the files were still `core/src/services/redis/backend.rs` and `core/src/services/sled/backend.rs`) — run `git show` on any of them.
  • Change coupling: lib.rs ↔ lib.rs core/layers/retry/src/lib.rs:1 — `core/layers/retry/src/lib.rs` and `core/layers/tracing/src/lib.rs` change together 52% of the time (24 of the 46 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 24 shared commits counted here, the most recent 3 are `ebcdfb4c` refactor!: Refactor oio::Delete to make it's API simple (#6823) (at that commit the files were still `core/src/layers/retry.rs` and `core/src/layers/tracing.rs`); `e5076ac4` chore(core/layers): adjust await point to simplify combinator code (#… (at that commit the files were still `core/src/layers/retry.rs` and `core/src/layers/tracing.rs`); `0805ddd1` chore(layers): check the examples when running tests (#5104) (at that commit the files were still `core/src/layers/retry.rs` and `core/src/layers/tracing.rs`) — run `git show` on any of them.
  • Change coupling: config.rs ↔ core.rs core/services/s3/src/config.rs:1 — `core/services/s3/src/config.rs` and `core/services/s3/src/core.rs` change together 52% of the time (12 of the 23 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 12 shared commits counted here, the most recent 3 are `30f1616b` feat(services/s3): add region fallback and Bucket Key controls (#6531); `b25d98f3` feat(services/s3): Rename allow_anonymous to skip_signature (#7544); `77e74d05` feat(services/s3): Add a way to specify a default object ACL (#7186) — run `git show` on any of them.
  • Change coupling: backend.rs ↔ backend.rs core/services/postgresql/src/backend.rs:1 — `core/services/postgresql/src/backend.rs` and `core/services/sqlite/src/backend.rs` change together 50% of the time (6 of the 12 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 — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `311f324c` fix(services): improve stat implementation (#7857); `f93c6194` chore(core/raw): align `info` method of `kv::Adapter` and `typed_kv::… (at that commit the files were still `core/src/services/postgresql/backend.rs` and `core/src/services/sqlite/backend.rs`); `6cec7b48` feat(adapter/kv): support async iterating on scan results (#5208) (at that commit the files were still `core/src/services/postgresql/backend.rs` and `core/src/services/sqlite/backend.rs`) — run `git show` on any of them.
  • + 2 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×25
  • Duplicated block (7 lines × 2) bindings/c/src/reader.rs:70 — bindings/c/src/reader.rs:70-76 | bindings/c/src/reader.rs:109-115 — both copies are in the same file, so extract the 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 `bindings/c/src/reader.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 (7 lines × 2) bindings/java/src/async_operator.rs:368 — bindings/java/src/async_operator.rs:368-374 | bindings/java/src/async_operator.rs:408-414 — both copies are in the same file, so extract the 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 `bindings/java/src/async_operator.rs:368` 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) bindings/python/src/options.rs:106 — bindings/python/src/options.rs:106-112 | bindings/python/src/options.rs:308-314 — both copies are in the same file, so extract the 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 `bindings/python/src/options.rs:106` 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) core/core/src/raw/ops.rs:534 — core/core/src/raw/ops.rs:534-540 | core/core/src/raw/ops.rs:748-754 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) core/layers/foyer/src/lib.rs:137 — core/layers/foyer/src/lib.rs:137-143 | core/services/foyer/src/lib.rs:104-110 — 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 (7 lines × 2) core/services/cos/src/backend.rs:181 — core/services/cos/src/backend.rs:181-187 | core/services/obs/src/backend.rs:148-154 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/obs/src/backend.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/backend.rs:181` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/cos/src/backend.rs:189` calls `with_context` and `core/services/obs/src/backend.rs:156` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) core/services/d1/src/core.rs:97 — core/services/d1/src/core.rs:97-103 | core/services/d1/src/core.rs:121-127 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/d1/src/core.rs:97` 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) core/services/fs/src/backend.rs:85 — core/services/fs/src/backend.rs:85-91 | core/services/monoiofs/src/backend.rs:65-71 — 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 (7 lines × 2) core/services/gcs/src/core.rs:644 — core/services/gcs/src/core.rs:644-650 | core/services/tos/src/core.rs:393-399 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/tos/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gcs/src/core.rs:644` 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 `args` to `&OpStat` in one and `OpStat` 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 (7 lines × 2) core/services/gcs/src/reader.rs:55 — core/services/gcs/src/reader.rs:55-61 | core/services/s3/src/reader.rs:52-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) core/services/gdrive/src/core.rs:277 — core/services/gdrive/src/core.rs:277-283 | core/services/gdrive/src/core.rs:561-567 — both copies are in the same file, so extract the 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 `core/services/gdrive/src/core.rs:277` 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) core/services/git/src/config.rs:86 — core/services/git/src/config.rs:86-92 | core/services/git/src/core.rs:87-93 — 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 `core/services/git/src/config.rs:86` 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) core/services/tos/src/copier.rs:228 — core/services/tos/src/copier.rs:228-234 | core/services/tos/src/writer.rs:179-185 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `core/services/tos/src/copier.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 (7 lines × 2) core/services/upyun/src/backend.rs:252 — core/services/upyun/src/backend.rs:252-258 | core/services/vercel-blob/src/backend.rs:202-208 — before extracting anything, compare `core/services/upyun/src/backend.rs` and `core/services/vercel-blob/src/backend.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/upyun/src/backend.rs:252` 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) dev/src/generate/core_options.rs:85 — dev/src/generate/core_options.rs:85-91 | dev/src/generate/options.rs:69-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `dev/src/generate/core_options.rs:85` 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) core/services/aliyun-drive/src/core.rs:324 — core/services/aliyun-drive/src/core.rs:324-334 | core/services/aliyun-drive/src/core.rs:460-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) core/services/b2/src/core.rs:217 — core/services/b2/src/core.rs:217-226 | core/services/b2/src/core.rs:320-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) core/services/b2/src/core.rs:162 — core/services/b2/src/core.rs:162-169 | core/services/lakefs/src/core.rs:111-117 — 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 `core/services/b2/src/core.rs:162` 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) core/services/gdrive/src/core.rs:760 — core/services/gdrive/src/core.rs:760-766 | core/services/onedrive/src/core.rs:785-791 — 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 `core/services/gdrive/src/core.rs:760` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) core/services/lakefs/src/core.rs:75 — core/services/lakefs/src/core.rs:75-81 | core/services/lakefs/src/core.rs:155-161 — both copies are in the same file, so extract the 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 `core/services/lakefs/src/core.rs:75` 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) core/services/azdls/src/config.rs:106 — core/services/azdls/src/config.rs:106-112 | core/services/azfile/src/config.rs:81-87 — 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 `core/services/azdls/src/config.rs:106` 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) core/core/src/raw/http_util/bytes_content_range.rs:168 — core/core/src/raw/http_util/bytes_content_range.rs:168-174 | core/core/src/types/bytes_range.rs:350-356 — 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 `core/core/src/raw/http_util/bytes_content_range.rs:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) core/services/s3/src/core.rs:907 — core/services/s3/src/core.rs:907-913 | core/services/swift/src/core.rs:214-220 — 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 `core/services/s3/src/core.rs:907` 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) core/services/ghac/src/config.rs:69 — core/services/ghac/src/config.rs:69-75 | core/services/swift/src/config.rs:85-91 — 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 `core/services/ghac/src/config.rs:69` 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) integrations/spring/opendal-spring/src/main/java/org/apache/opendal/spring/core/OpenDALTemplate.java:40 — integrations/spring/opendal-spring/src/main/java/org/apache/opendal/spring/core/OpenDALTemplate.java:40-46 | integrations/spring/opendal-spring/src/main/java/org/apache/opendal/spring/core/ReactiveOpenDALTemplate.java:40-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×23
  • Duplicated block (12 lines × 2) bindings/c/src/operator.rs:554 — bindings/c/src/operator.rs:554-565 | bindings/c/src/operator.rs:610-621 — both copies are in the same file, so extract the 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 `bindings/c/src/operator.rs:554` 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) bindings/c/src/operator.rs:1424 — bindings/c/src/operator.rs:1424-1435 | bindings/c/src/operator.rs:1526-1537 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) bindings/nodejs/src/options.rs:218 — bindings/nodejs/src/options.rs:218-229 | bindings/nodejs/src/options.rs:334-345 — both copies are in the same file, so extract the 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 `bindings/nodejs/src/options.rs:218` 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 `value` to `ReadOptions` in one and `ReaderOptions` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bindings/nodejs/src/options.rs:217` calls `make_range` and `bindings/nodejs/src/options.rs:333` 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 (12 lines × 2) bindings/python/src/operator.rs:393 — bindings/python/src/operator.rs:393-404 | bindings/python/src/operator.rs:1199-1210 — both copies are in the same file, so extract the 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, `bindings/python/src/operator.rs:1212` calls `future_into_py` and `bindings/python/src/operator.rs:406` 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 (12 lines × 2) core/core/src/raw/futures_util.rs:265 — core/core/src/raw/futures_util.rs:265-276 | core/core/src/raw/futures_util.rs:308-319 — both copies are in the same file, so extract the 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 `core/core/src/raw/futures_util.rs:265` 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) core/layers/tail-cut/src/lib.rs:327 — core/layers/tail-cut/src/lib.rs:327-338 | core/layers/tail-cut/src/lib.rs:511-522 — both copies are in the same file, so extract the 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 (12 lines × 2) core/services/b2/src/writer.rs:134 — core/services/b2/src/writer.rs:134-145 | core/services/vercel-blob/src/writer.rs:110-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/b2/src/writer.rs:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) core/services/cos/src/core.rs:169 — core/services/cos/src/core.rs:169-180 | core/services/oss/src/core.rs:366-377 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:169` 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) core/services/cos/src/core.rs:189 — core/services/cos/src/core.rs:189-200 | core/services/obs/src/core.rs:173-184 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/cos/src/core.rs:201` calls `Some`, `content_disposition`, `header` and `core/services/obs/src/core.rs:186` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (12 lines × 2) core/services/cos/src/core.rs:271 — core/services/cos/src/core.rs:271-282 | core/services/oss/src/core.rs:437-448 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:271` 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 first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `&OpDelete` 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 (12 lines × 2) core/services/etcd/src/reader.rs:48 — core/services/etcd/src/reader.rs:48-59 | core/services/mini_moka/src/reader.rs:50-61 — 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 `core/services/etcd/src/reader.rs:48` 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) core/services/gcs/src/core.rs:199 — core/services/gcs/src/core.rs:199-210 | core/services/gcs/src/core.rs:271-282 — both copies are in the same file, so extract the 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 `core/services/gcs/src/core.rs:199` 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) core/services/github/src/core.rs:299 — core/services/github/src/core.rs:299-310 | core/services/github/src/core.rs:338-349 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/github/src/core.rs:299` 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) core/services/http/src/backend.rs:117 — core/services/http/src/backend.rs:117-128 | core/services/webdav/src/backend.rs:192-203 — before extracting anything, compare `core/services/http/src/backend.rs` and `core/services/webdav/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) core/services/http/src/reader.rs:62 — core/services/http/src/reader.rs:62-73 | core/services/ipfs/src/reader.rs:55-66 — 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 `core/services/http/src/reader.rs:62` 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) core/services/koofr/src/core.rs:523 — core/services/koofr/src/core.rs:523-534 | core/services/upyun/src/core.rs:619-630 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) core/services/persy/src/core.rs:79 — core/services/persy/src/core.rs:79-90 | core/services/persy/src/core.rs:115-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) core/services/smb/src/deleter.rs:46 — core/services/smb/src/deleter.rs:46-57 | core/services/smb/src/lister.rs:61-72 — 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 `core/services/smb/src/deleter.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 (12 lines × 2) core/services/swift/src/writer.rs:46 — core/services/swift/src/writer.rs:46-57 | core/services/webdav/src/writer.rs:46-57 — 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) core/services/upyun/src/core.rs:240 — core/services/upyun/src/core.rs:240-251 | core/services/upyun/src/core.rs:275-286 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) core/services/koofr/src/deleter.rs:42 — core/services/koofr/src/deleter.rs:42-53 | core/services/upyun/src/deleter.rs:42-53 — 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 `core/services/koofr/src/deleter.rs:42` 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) core/services/seafile/src/core.rs:422 — core/services/seafile/src/core.rs:422-433 | core/services/vercel-blob/src/core.rs:306-317 — before extracting anything, compare `core/services/seafile/src/core.rs` and `core/services/vercel-blob/src/core.rs` as WHOLE FILES: this scan already matched 3 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 `core/services/seafile/src/core.rs:422` 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) bindings/go/delete.go:134 — bindings/go/delete.go:134-145 | bindings/go/writer.go:440-451 — 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 `bindings/go/delete.go:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×22
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×21
  • Duplicated block (11 lines × 2) core/layers/retry/src/lib.rs:841 — core/layers/retry/src/lib.rs:841-851 | core/layers/retry/src/lib.rs:1069-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 `core/layers/retry/src/lib.rs:841` 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) core/layers/retry/src/lib.rs:905 — core/layers/retry/src/lib.rs:905-915 | core/layers/retry/src/lib.rs:1007-1017 — both copies are in the same file, so extract the 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 `core/layers/retry/src/lib.rs:905` 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) core/services/azblob/src/core.rs:156 — core/services/azblob/src/core.rs:156-166 | core/services/oss/src/core.rs:105-115 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:156` 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) core/services/cos/src/core.rs:145 — core/services/cos/src/core.rs:145-155 | core/services/gcs/src/core.rs:246-256 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 8 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/core.rs:145` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/cos/src/core.rs:157` calls `is_full`, `header`, `to_header` and `core/services/gcs/src/core.rs:257` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) core/services/cos/src/core.rs:931 — core/services/cos/src/core.rs:931-941 | core/services/obs/src/core.rs:714-724 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:931` 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 × 2) core/services/dbfs/src/core.rs:56 — core/services/dbfs/src/core.rs:56-66 | core/services/dbfs/src/core.rs:85-95 — both copies are in the same file, so extract the 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 `core/services/dbfs/src/core.rs:56` 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) core/services/fs/src/writer.rs:118 — core/services/fs/src/writer.rs:118-128 | core/services/fs/src/writer.rs:192-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) core/services/github/src/lister.rs:65 — core/services/github/src/lister.rs:65-75 | core/services/github/src/lister.rs:105-115 — both copies are in the same file, so extract the 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 `core/services/github/src/lister.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.
  • Duplicated block (11 lines × 2) core/services/obs/src/backend.rs:423 — core/services/obs/src/backend.rs:423-433 | core/services/oss/src/backend.rs:799-809 — before extracting anything, compare `core/services/obs/src/backend.rs` and `core/services/oss/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/obs/src/backend.rs:423` 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 × 2) core/services/pcloud/src/backend.rs:312 — core/services/pcloud/src/backend.rs:312-322 | core/services/pcloud/src/backend.rs:357-367 — both copies are in the same file, so extract the 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 `core/services/pcloud/src/backend.rs:312` 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) core/services/s3/src/core.rs:580 — core/services/s3/src/core.rs:580-590 | core/services/tos/src/core.rs:273-283 — 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 `core/services/s3/src/core.rs:580` 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) core/services/s3/src/writer.rs:83 — core/services/s3/src/writer.rs:83-93 | core/services/s3/src/writer.rs:372-382 — both copies are in the same file, so extract the 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 `core/services/s3/src/writer.rs:83` 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) core/services/webhdfs/src/core.rs:66 — core/services/webhdfs/src/core.rs:66-76 | core/services/webhdfs/src/core.rs:100-110 — both copies are in the same file, so extract the 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 `core/services/webhdfs/src/core.rs:66` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) core/services/webhdfs/src/core.rs:297 — core/services/webhdfs/src/core.rs:297-307 | core/services/webhdfs/src/core.rs:326-336 — both copies are in the same file, so extract the 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 `core/services/webhdfs/src/core.rs:297` 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 × 2) core/services/dbfs/src/core.rs:144 — core/services/dbfs/src/core.rs:144-154 | core/services/dbfs/src/core.rs:195-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/dbfs/src/core.rs:144` 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) core/services/oss/src/deleter.rs:66 — core/services/oss/src/deleter.rs:66-77 | core/services/s3/src/deleter.rs:71-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (11 lines × 2) core/services/swift/src/backend.rs:131 — core/services/swift/src/backend.rs:131-141 | core/services/webhdfs/src/backend.rs:148-159 — before extracting anything, compare `core/services/swift/src/backend.rs` and `core/services/webhdfs/src/backend.rs` as WHOLE FILES: this scan already matched 3 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/swift/src/backend.rs:131` 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) core/services/yandex-disk/src/core.rs:232 — core/services/yandex-disk/src/core.rs:232-242 | core/services/yandex-disk/src/core.rs:261-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) core/services/swift/src/writer.rs:69 — core/services/swift/src/writer.rs:69-79 | core/services/swift/src/writer.rs:152-162 — both copies are in the same file, so extract the 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 `core/services/swift/src/writer.rs:69` 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 × 2) core/services/tos/src/core.rs:713 — core/services/tos/src/core.rs:713-723 | core/services/tos/src/core.rs:756-766 — both copies are in the same file, so extract the 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 `core/services/tos/src/core.rs:713` 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) bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:45 — bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:45-55 | bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:86-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
D30 · Dependency Vulnerabilities · Medium CVE · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×18
  • Duplicated block (6 lines × 2) bindings/nodejs/src/lib.rs:335 — bindings/nodejs/src/lib.rs:335-340 | bindings/nodejs/src/lib.rs:402-407 — both copies are in the same file, so extract the 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 first that the copies are not typed on the same thing: the declarations holding them bind `options` to `Option<options::ReaderOptions>` in one and `Option<options::WriteOptions>` 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 (6 lines × 2) core/layers/prometheus-client/src/lib.rs:220 — core/layers/prometheus-client/src/lib.rs:220-225 | core/layers/prometheus-client/src/lib.rs:252-257 — both copies are in the same file, so extract the 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 `core/layers/prometheus-client/src/lib.rs:220` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) core/services/aliyun-drive/src/backend.rs:339 — core/services/aliyun-drive/src/backend.rs:339-344 | core/services/aliyun-drive/src/lister.rs:145-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) core/services/b2/src/core.rs:882 — core/services/b2/src/core.rs:882-887 | core/services/s3/src/core.rs:2212-2217 — 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 `core/services/b2/src/core.rs:882` 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) core/services/compfs/src/backend.rs:64 — core/services/compfs/src/backend.rs:64-69 | core/services/fs/src/backend.rs:82-87 — 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 `core/services/compfs/src/backend.rs:64` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/fs/src/backend.rs:79` calls `to_string_lossy` and `core/services/compfs/src/backend.rs:61` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) core/services/cos/src/core.rs:927 — core/services/cos/src/core.rs:927-932 | core/services/oss/src/core.rs:1234-1239 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:927` 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) core/services/dropbox/src/core.rs:552 — core/services/dropbox/src/core.rs:552-557 | core/services/gdrive/src/core.rs:1149-1154 — 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 `core/services/dropbox/src/core.rs:552` 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) core/services/foyer/src/backend.rs:271 — core/services/foyer/src/backend.rs:271-276 | core/services/moka/src/backend.rs:268-274 — before extracting anything, compare `core/services/foyer/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/foyer/src/backend.rs:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) core/services/gcs/src/core.rs:650 — core/services/gcs/src/core.rs:650-656 | core/services/s3/src/core.rs:512-517 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/s3/src/core.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `OpStat` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/s3/src/core.rs:510` calls `insert_sse_headers` and `core/services/gcs/src/core.rs:648` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) core/services/github/src/core.rs:437 — core/services/github/src/core.rs:437-442 | core/services/yandex-disk/src/core.rs:422-427 — 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 `core/services/github/src/core.rs:437` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) core/services/github/src/reader.rs:49 — core/services/github/src/reader.rs:49-55 | core/services/koofr/src/reader.rs:44-49 — 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 `core/services/github/src/reader.rs:49` 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) core/services/vercel-blob/src/writer.rs:151 — core/services/vercel-blob/src/writer.rs:151-157 | core/services/webhdfs/src/writer.rs:221-226 — 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 `core/services/vercel-blob/src/writer.rs:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) dev/src/release/package.rs:348 — dev/src/release/package.rs:348-353 | dev/src/release/package.rs:491-496 — both copies are in the same file, so extract the 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 (6 lines × 2) core/layers/foyer/src/lib.rs:126 — core/layers/foyer/src/lib.rs:126-131 | core/services/foyer/src/lib.rs:93-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) core/services/aliyun-drive/src/writer.rs:104 — core/services/aliyun-drive/src/writer.rs:104-109 | core/services/ftp/src/reader.rs:164-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) core/services/aliyun-drive/src/writer.rs:111 — core/services/aliyun-drive/src/writer.rs:111-116 | core/services/hf/src/writer.rs:76-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) core/services/gcs/src/core.rs:408 — core/services/gcs/src/core.rs:408-413 | core/services/gcs/src/core.rs:776-781 — both copies are in the same file, so extract the 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 `core/services/gcs/src/core.rs:408` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) core/services/koofr/src/config.rs:71 — core/services/koofr/src/config.rs:71-76 | core/services/lakefs/src/config.rs:95-100 — 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 `core/services/koofr/src/config.rs:71` 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×15
  • Members sharing a duplicated core (4 members, 50+ identical tokens) bindings/dotnet/src/operator.rs:519 — bindings/dotnet/src/operator.rs:519-544 | bindings/dotnet/src/operator.rs:1865-1890 | bindings/dotnet/src/operator.rs:1960-1985 | bindings/dotnet/src/operator.rs:2201-2226 — 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) bindings/dotnet/src/operator.rs:707 — bindings/dotnet/src/operator.rs:707-733 | bindings/dotnet/src/operator.rs:1628-1663 | bindings/dotnet/src/operator.rs:1760-1794 | bindings/dotnet/src/operator.rs:1960-1985 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/aliyun-drive/src/config.rs:76 — core/services/aliyun-drive/src/config.rs:76-92 | core/services/foyer/src/config.rs:64-78 | core/services/goosefs/src/config.rs:110-122 | core/services/moka/src/config.rs:52-66 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/alluxio/src/config.rs:54 — core/services/alluxio/src/config.rs:54-67 | core/services/ipfs/src/config.rs:37-50 | core/services/ipmfs/src/config.rs:37-50 | core/services/webhdfs/src/config.rs:59-72 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/alluxio/src/core.rs:51 — core/services/alluxio/src/core.rs:51-88 | core/services/alluxio/src/core.rs:164-192 | core/services/alluxio/src/core.rs:194-222 | core/services/alluxio/src/core.rs:357-380 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/cos/src/core.rs:522 — core/services/cos/src/core.rs:522-559 | core/services/gcs/src/core.rs:1044-1074 | core/services/oss/src/core.rs:618-650 | core/services/oss/src/core.rs:744-781 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/cos/src/lister.rs:142 — core/services/cos/src/lister.rs:142-156 | core/services/oss/src/lister.rs:145-159 | core/services/s3/src/lister.rs:298-312 | core/services/tos/src/lister.rs:139-153 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/dbfs/src/core.rs:267 — core/services/dbfs/src/core.rs:267-297 | core/services/lakefs/src/core.rs:358-388 | core/services/swift/src/core.rs:901-932 | core/services/webhdfs/src/core.rs:468-499 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/foyer/src/reader.rs:38 — core/services/foyer/src/reader.rs:38-59 | core/services/memcached/src/reader.rs:38-55 | core/services/mysql/src/reader.rs:39-56 | core/services/tikv/src/reader.rs:39-56 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/hf/src/core.rs:556 — core/services/hf/src/core.rs:556-597 | core/services/hf/src/core.rs:743-772 | core/services/hf/src/core.rs:949-980 | core/services/hf/src/core.rs:989-1022 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/koofr/src/core.rs:521 — core/services/koofr/src/core.rs:521-548 | core/services/seafile/src/core.rs:560-587 | core/services/upyun/src/core.rs:617-646 | core/services/vercel-blob/src/core.rs:515-540 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/persy/src/backend.rs:179 — core/services/persy/src/backend.rs:179-194 | core/services/redb/src/backend.rs:200-215 | core/services/rocksdb/src/backend.rs:147-162 | core/services/sled/src/backend.rs:171-186 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) core/services/persy/src/writer.rs:46 — core/services/persy/src/writer.rs:46-57 | core/services/redb/src/writer.rs:46-57 | core/services/rocksdb/src/writer.rs:47-58 | core/services/sled/src/writer.rs:46-57 — 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) REDACTED:151 — REDACTED:151-165 | REDACTED:189-203 | REDACTED:227-241 | REDACTED:265-279 — 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) REDACTED:170 — REDACTED:170-184 | REDACTED:208-222 | REDACTED:246-260 | REDACTED:284-298 — 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) · ×14
  • Edited copy of a member (7 corresponding lines) core/core/src/types/operator/operator.rs:2707 — core/core/src/types/operator/operator.rs:2707-2713 | core/core/src/types/operator/operator.rs:2821-2827 — 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) bindings/python/src/operator.rs:992 — bindings/python/src/operator.rs:992-998 | bindings/python/src/operator.rs:2161-2167 — 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) bindings/python/src/operator.rs:699 — bindings/python/src/operator.rs:699-706 | bindings/python/src/operator.rs:716-722 — 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) bindings/nodejs/src/lib.rs:1172 — bindings/nodejs/src/lib.rs:1172-1178 | bindings/ocaml/src/operator/lister.rs:22-28 — 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) bindings/c/src/layer.rs:99 — bindings/c/src/layer.rs:99-105 | bindings/c/src/types.rs:1497-1503 — 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) core/services/azfile/src/config.rs:44 — core/services/azfile/src/config.rs:44-50 | core/services/azfile/src/core.rs:55-61 — 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) core/services/d1/src/core.rs:41 — core/services/d1/src/core.rs:41-47 | core/services/sqlite/src/config.rs:60-67 — 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) core/services/gcs-grpc/src/core.rs:50 — core/services/gcs-grpc/src/core.rs:50-56 | core/services/gcs/src/core.rs:84-90 — 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) core/services/github/src/config.rs:53 — core/services/github/src/config.rs:53-59 | core/services/github/src/core.rs:50-56 — 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) core/services/gridfs/src/config.rs:44 — core/services/gridfs/src/config.rs:44-51 | core/services/gridfs/src/core.rs:40-46 — 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) core/services/upyun/src/config.rs:44 — core/services/upyun/src/config.rs:44-50 | core/services/upyun/src/core.rs:82-88 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) bindings/c/src/copier.rs:109 — bindings/c/src/copier.rs:109-115 | bindings/c/src/operator.rs:1444-1450 — 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) core/core/src/blocking/copy.rs:43 — core/core/src/blocking/copy.rs:43-49 | core/core/src/types/copy.rs:101-107 — 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) core/services/git/src/backend.rs:200 — core/services/git/src/backend.rs:200-206 | core/services/hf/src/backend.rs:393-399 — 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×14
  • Duplicated block (14 lines × 2) bindings/c/src/types.rs:1066 — bindings/c/src/types.rs:1066-1079 | bindings/c/src/types.rs:1292-1305 — both copies are in the same file, so extract the 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 first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&opendal_read_options` in one and `&opendal_reader_options` 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 (14 lines × 2) bindings/python/src/file.rs:99 — bindings/python/src/file.rs:99-112 | bindings/python/src/file.rs:147-160 — both copies are in the same file, so extract the 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 `bindings/python/src/file.rs:99` 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 lines × 2) core/services/azdls/src/core.rs:844 — core/services/azdls/src/core.rs:844-857 | core/services/oss/src/core.rs:1235-1248 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 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 `core/services/azdls/src/core.rs:844` 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 lines × 2) core/services/cloudflare-kv/src/core.rs:235 — core/services/cloudflare-kv/src/core.rs:235-248 | core/services/d1/src/core.rs:237-250 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) core/services/cos/src/core.rs:959 — core/services/cos/src/core.rs:959-972 | core/services/oss/src/core.rs:1257-1270 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:959` 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 lines × 2) core/services/dashmap/src/writer.rs:60 — core/services/dashmap/src/writer.rs:60-73 | core/services/moka/src/writer.rs:60-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) core/services/foyer/src/config.rs:65 — core/services/foyer/src/config.rs:65-78 | core/services/moka/src/config.rs:53-66 — 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 (14 lines × 2) core/services/gcs/src/writer.rs:314 — core/services/gcs/src/writer.rs:314-327 | core/services/gcs/src/writer.rs:411-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gcs/src/writer.rs:314` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) core/services/ghac/src/reader.rs:52 — core/services/ghac/src/reader.rs:52-65 | core/services/yandex-disk/src/reader.rs:57-70 — before extracting anything, compare `core/services/ghac/src/reader.rs` and `core/services/yandex-disk/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/ghac/src/reader.rs:52` 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) core/services/obs/src/core.rs:472 — core/services/obs/src/core.rs:472-485 | core/services/oss/src/core.rs:791-804 — before extracting anything, compare `core/services/obs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 122 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) core/services/s3/src/copier.rs:256 — core/services/s3/src/copier.rs:256-269 | core/services/s3/src/writer.rs:117-130 — 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 `core/services/s3/src/copier.rs:256` 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) core/services/surrealdb/src/core.rs:96 — core/services/surrealdb/src/core.rs:96-109 | core/services/surrealdb/src/core.rs:125-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/surrealdb/src/core.rs:96` 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 lines × 2) core/services/azfile/src/core.rs:364 — core/services/azfile/src/core.rs:364-377 | core/services/azfile/src/core.rs:391-404 — both copies are in the same file, so extract the 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 `core/services/azfile/src/core.rs:364` 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) core/services/pcloud/src/core.rs:264 — core/services/pcloud/src/core.rs:264-277 | core/services/pcloud/src/core.rs:291-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×13
  • Edited copy of a member (8 corresponding lines) core/services/hdfs-native/src/reader.rs:101 — core/services/hdfs-native/src/reader.rs:101-108 | core/services/hdfs/src/reader.rs:93-109 — 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) core/services/monoiofs/src/reader.rs:43 — core/services/monoiofs/src/reader.rs:43-50 | core/services/monoiofs/src/writer.rs:52-59 — 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) core/layers/oteltrace/src/lib.rs:266 — core/layers/oteltrace/src/lib.rs:266-273 | core/layers/tracing/src/lib.rs:351-358 — 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) bindings/python/src/operator.rs:1537 — bindings/python/src/operator.rs:1537-1547 | bindings/python/src/operator.rs:1568-1575 — 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) bindings/ruby/src/io.rs:161 — bindings/ruby/src/io.rs:161-168 | bindings/ruby/src/io.rs:186-193 — 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) core/core/src/raw/ops.rs:533 — core/core/src/raw/ops.rs:533-540 | core/core/src/raw/ops.rs:747-754 — 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) core/core/src/layers/error_context.rs:342 — core/core/src/layers/error_context.rs:342-349 | core/core/src/layers/error_context.rs:351-358 — 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) core/services/ipmfs/src/backend.rs:271 — core/services/ipmfs/src/backend.rs:271-278 | core/services/onedrive/src/backend.rs:345-352 — 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) core/core/src/types/operator/operator.rs:382 — core/core/src/types/operator/operator.rs:382-389 | core/core/src/blocking/operator.rs:931-938 — 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) dev/src/generate/dotnet.rs:749 — dev/src/generate/dotnet.rs:749-757 | dev/src/generate/metadata.rs:224-231 — 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) core/services/goosefs/src/backend.rs:481 — core/services/goosefs/src/backend.rs:481-488 | core/services/ipfs/src/backend.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) core/services/webdav/src/core.rs:100 — core/services/webdav/src/core.rs:100-108 | core/services/lakefs/src/config.rs:60-67 — 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) core/core/src/layers/simulate.rs:490 — core/core/src/layers/simulate.rs:490-497 | core/core/src/raw/oio/list/flat_list.rs:78-85 — 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.
D3 · God Classes · ClassTooLong · ×12
  • ClassTooLong: S3Core core/services/s3/src/core.rs:97 — ClassTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 31 methods, 4 blocks, lines 97-1502. The bar is 400 significant lines; this is 439 over it, 2.10× 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: Operator core/core/src/types/operator/operator.rs:196 — ClassTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 92 methods, 5 blocks, lines 196-2828. The bar is 400 significant lines; this is 431 over it, 2.08× 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: GcsCore core/services/gcs/src/core.rs:67 — ClassTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 32 methods, 4 blocks, lines 67-1107. The bar is 400 significant lines; this is 333 over it, 1.83× 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: TosCore core/services/tos/src/core.rs:61 — ClassTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 3 blocks, lines 61-917. The bar is 400 significant lines; this is 189 over it, 1.47× 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: S3Builder core/services/s3/src/backend.rs:84 — ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 52 methods, 4 blocks, lines 84-1305. The bar is 400 significant lines; this is 186 over it, 1.47× 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: AsyncOperator bindings/python/src/operator.rs:1009 — ClassTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 1009-2168. The bar is 400 significant lines; this is 170 over it, 1.43× 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: AzblobCore core/services/azblob/src/core.rs:75 — ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 30 methods, 4 blocks, lines 75-884. The bar is 400 significant lines; this is 132 over it, 1.33× 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: AliyunDriveCore core/services/aliyun-drive/src/core.rs:61 — ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 3 blocks, lines 61-615. The bar is 400 significant lines; this is 41 over it, 1.10× 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: GitCore core/services/git/src/core.rs:71 — ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 3 blocks, lines 71-660. The bar is 400 significant lines; this is 41 over it, 1.10× 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: OneDriveCore core/services/onedrive/src/core.rs:35 — ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 4 blocks, lines 35-713. The bar is 400 significant lines; this is 20 over it, 1.05× 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: OpendalStore integrations/object_store/src/store.rs:182 — ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 6 blocks, lines 182-755. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: HfCore core/services/hf/src/core.rs:421 — ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 421-1023. The bar is 400 significant lines; this is 3 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×12
  • Edited copy of a member (18 corresponding lines) core/services/cos/src/core.rs:364 — core/services/cos/src/core.rs:364-393 | core/services/obs/src/core.rs:314-331 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/azblob/src/core.rs:860 — core/services/azblob/src/core.rs:860-883 | core/services/gcs/src/core.rs:742-759 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) bindings/c/src/copier.rs:82 — bindings/c/src/copier.rs:82-102 | bindings/c/src/lister.rs:67-84 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/azdls/src/core.rs:460 — core/services/azdls/src/core.rs:460-486 | core/services/webdav/src/core.rs:305-322 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/obs/src/core.rs:471 — core/services/obs/src/core.rs:471-489 | core/services/oss/src/core.rs:790-807 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/lakefs/src/deleter.rs:39 — core/services/lakefs/src/deleter.rs:39-57 | core/services/tos/src/deleter.rs:41-58 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/layers/foyer/src/lib.rs:297 — core/layers/foyer/src/lib.rs:297-317 | core/layers/route/src/lib.rs:205-222 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/aliyun-drive/src/core.rs:117 — core/services/aliyun-drive/src/core.rs:117-136 | core/services/aliyun-drive/src/core.rs:597-614 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/core/src/layers/complete.rs:445 — core/core/src/layers/complete.rs:445-463 | core/core/src/layers/complete.rs:465-482 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) bindings/java/src/operator.rs:330 — bindings/java/src/operator.rs:330-347 | bindings/java/src/utility.rs:44-108 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) core/services/gdrive/src/core.rs:142 — core/services/gdrive/src/core.rs:142-159 | core/services/gdrive/src/core.rs:161-179 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) bindings/dotnet/OpenDAL/Operator.cs:1162 — bindings/dotnet/OpenDAL/Operator.cs:1162-1179 | bindings/dotnet/OpenDAL/Operator.cs:1192-1209 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×12
  • Edited copy of a member (10 corresponding lines) .github/scripts/release_rust/bootstrap.py:372 — .github/scripts/release_rust/bootstrap.py:372-382 | .github/scripts/release_rust/bootstrap.py:612-621 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) .github/scripts/release_rust/bootstrap.py:93 — .github/scripts/release_rust/bootstrap.py:93-102 | .github/scripts/release_rust/trusted_publishing.py:33-43 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) bindings/lua/src/lib.rs:129 — bindings/lua/src/lib.rs:129-138 | bindings/lua/src/lib.rs:140-149 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) core/core/src/services/memory/config.rs:35 — core/core/src/services/memory/config.rs:35-44 | core/services/fs/src/config.rs:38-47 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) core/layers/foyer/src/full.rs:191 — core/layers/foyer/src/full.rs:191-200 | core/layers/foyer/src/full.rs:204-213 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) integrations/object_store/src/store.rs:77 — integrations/object_store/src/store.rs:77-87 | integrations/object_store/src/store.rs:89-98 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) bindings/c/src/types.rs:252 — bindings/c/src/types.rs:252-261 | bindings/c/src/types.rs:341-350 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) core/services/lakefs/src/core.rs:40 — core/services/lakefs/src/core.rs:40-49 | core/services/webdav/src/config.rs:106-115 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) core/services/ghac/src/writer.rs:247 — core/services/ghac/src/writer.rs:247-256 | core/services/ghac/src/writer.rs:278-288 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) bindings/java/src/convert.rs:94 — bindings/java/src/convert.rs:94-105 | bindings/java/src/convert.rs:111-120 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) bindings/nodejs/src/lib.rs:266 — bindings/nodejs/src/lib.rs:266-279 | bindings/nodejs/src/lib.rs:306-315 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) core/core/src/blocking/read/buffer_iterator.rs:47 — core/core/src/blocking/read/buffer_iterator.rs:47-56 | core/core/src/blocking/read/std_bytes_iterator.rs:50-60 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×12
  • Duplicated block (15 lines × 2) bindings/c/src/operator_info.rs:316 — bindings/c/src/operator_info.rs:316-330 | bindings/python/src/capability.rs:182-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/operator_info.rs:316` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bindings/c/src/operator_info.rs:314` calls `unwrap_or` and `bindings/python/src/capability.rs:181` 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 (15 lines × 2) bindings/dotnet/src/operator.rs:1395 — bindings/dotnet/src/operator.rs:1395-1409 | bindings/dotnet/src/operator.rs:1487-1501 — both copies are in the same file, so extract the 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 `bindings/dotnet/src/operator.rs:1395` 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) core/services/b2/src/backend.rs:374 — core/services/b2/src/backend.rs:374-388 | core/services/b2/src/backend.rs:404-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) core/services/cloudflare-kv/src/core.rs:198 — core/services/cloudflare-kv/src/core.rs:198-212 | core/services/d1/src/core.rs:200-214 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) core/services/cos/src/reader.rs:64 — core/services/cos/src/reader.rs:64-78 | core/services/oss/src/reader.rs:64-78 — before extracting anything, compare `core/services/cos/src/reader.rs` and `core/services/oss/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/reader.rs:64` 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) core/services/gcs/src/core.rs:570 — core/services/gcs/src/core.rs:570-584 | core/services/gcs/src/core.rs:700-714 — both copies are in the same file, so extract the 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 `core/services/gcs/src/core.rs:570` 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 `args` to `&OpStat` in one and `&OpDelete` 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 (15 lines × 2) core/services/s3/src/core.rs:1021 — core/services/s3/src/core.rs:1021-1035 | core/services/s3/src/core.rs:1076-1090 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) core/services/s3/src/core.rs:1354 — core/services/s3/src/core.rs:1354-1368 | core/services/s3/src/core.rs:1385-1399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) core/services/tos/src/core.rs:189 — core/services/tos/src/core.rs:189-203 | core/services/tos/src/core.rs:785-799 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) core/services/upyun/src/backend.rs:295 — core/services/upyun/src/backend.rs:295-309 | core/services/vercel-blob/src/backend.rs:225-239 — before extracting anything, compare `core/services/upyun/src/backend.rs` and `core/services/vercel-blob/src/backend.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/upyun/src/backend.rs:295` 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) dev/src/generate/options.rs:165 — dev/src/generate/options.rs:165-179 | dev/src/generate/parser.rs:354-368 — 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 `dev/src/generate/options.rs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) core/services/webdav/src/core.rs:331 — core/services/webdav/src/core.rs:331-345 | core/services/webdav/src/core.rs:367-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×12
  • Duplicated block (8 lines × 3) bindings/c/src/operator.rs:310 — bindings/c/src/operator.rs:310-317 | bindings/c/src/operator.rs:368-375 | bindings/c/src/operator.rs:690-697 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `bindings/c/src/operator.rs:366` calls `is_null`, `write`, `null_mut` and `bindings/c/src/operator.rs:309` 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 × 3) core/services/azfile/src/core.rs:567 — core/services/azfile/src/core.rs:567-574 | core/services/dropbox/src/core.rs:557-564 | core/services/ghac/src/core.rs:566-573 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azfile/src/core.rs:567` 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) core/services/oss/src/core.rs:326 — core/services/oss/src/core.rs:326-333 | core/services/s3/src/core.rs:475-482 | core/services/s3/src/core.rs:551-558 — before extracting anything, compare `core/services/oss/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 3) core/services/pcloud/src/backend.rs:211 — core/services/pcloud/src/backend.rs:211-218 | core/services/pcloud/src/core.rs:93-100 | core/services/pcloud/src/core.rs:151-158 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) core/services/pcloud/src/backend.rs:314 — core/services/pcloud/src/backend.rs:314-321 | core/services/pcloud/src/backend.rs:359-366 | core/services/pcloud/src/core.rs:145-152 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/pcloud/src/backend.rs:314` 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 × 3) core/services/webhdfs/src/core.rs:296 — core/services/webhdfs/src/core.rs:296-303 | core/services/webhdfs/src/core.rs:325-332 | core/services/webhdfs/src/core.rs:389-396 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/webhdfs/src/core.rs:322` calls `is_empty`, `percent_encode_path`, `as_str` and `core/services/webhdfs/src/core.rs:295` 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 × 3) core/services/alluxio/src/backend.rs:66 — core/services/alluxio/src/backend.rs:66-73 | core/services/oss/src/backend.rs:91-98 | core/services/s3/src/backend.rs:130-137 — before extracting anything, compare `core/services/oss/src/backend.rs` and `core/services/s3/src/backend.rs` as WHOLE FILES: this scan already matched 4 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 (8 lines × 3) core/services/azblob/src/core.rs:99 — core/services/azblob/src/core.rs:99-106 | core/services/cos/src/core.rs:69-76 | core/services/obs/src/core.rs:64-71 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 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.
  • Duplicated block (8 lines × 3) core/services/azblob/src/backend.rs:632 — core/services/azblob/src/backend.rs:632-639 | core/services/s3/src/backend.rs:1436-1443 | core/services/tos/src/backend.rs:401-408 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/s3/src/backend.rs` as WHOLE FILES: this scan already matched 4 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 `core/services/azblob/src/backend.rs:632` 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) core/services/cloudflare-kv/src/config.rs:72 — core/services/cloudflare-kv/src/config.rs:72-79 | core/services/d1/src/config.rs:77-84 | core/services/koofr/src/config.rs:62-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cloudflare-kv/src/config.rs:72` 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) core/services/cloudflare-kv/src/config.rs:87 — core/services/cloudflare-kv/src/config.rs:87-94 | core/services/d1/src/config.rs:92-99 | core/services/koofr/src/config.rs:79-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cloudflare-kv/src/config.rs:87` 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) bindings/go/operator_info.go:338 — bindings/go/operator_info.go:338-345 | bindings/go/operator_info.go:350-357 | bindings/go/operator_info.go:362-369 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×11
  • Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/c/src/operator.rs:1287 — bindings/c/src/operator.rs:1287-1301 | bindings/c/src/operator.rs:1349-1363 | bindings/c/src/operator.rs:1422-1441 | bindings/c/src/operator.rs:1481-1501 | bindings/c/src/operator.rs:1523-1548 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) bindings/python/src/file.rs:97 — bindings/python/src/file.rs:97-120 | bindings/python/src/file.rs:145-172 | bindings/python/src/file.rs:186-225 | bindings/python/src/file.rs:286-315 | bindings/python/src/file.rs:323-340 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/core/src/services/memory/backend.rs:217 — core/core/src/services/memory/backend.rs:217-242 | core/services/persy/src/reader.rs:38-57 | core/services/redb/src/reader.rs:38-57 | core/services/rocksdb/src/reader.rs:38-57 | core/services/sled/src/reader.rs:38-57 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/azfile/src/core.rs:136 — core/services/azfile/src/core.rs:136-180 | core/services/cos/src/core.rs:325-356 | core/services/obs/src/core.rs:275-307 | core/services/oss/src/core.rs:177-224 | core/services/oss/src/core.rs:666-699 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/cloudflare-kv/src/core.rs:197 — core/services/cloudflare-kv/src/core.rs:197-232 | core/services/d1/src/core.rs:199-234 | core/services/dropbox/src/core.rs:551-585 | core/services/gdrive/src/core.rs:1148-1183 | core/services/tos/src/core.rs:1111-1146 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/cos/src/core.rs:94 — core/services/cos/src/core.rs:94-103 | core/services/gcs/src/core.rs:130-151 | core/services/obs/src/core.rs:89-98 | core/services/oss/src/core.rs:123-136 | core/services/tos/src/core.rs:108-122 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/cos/src/writer.rs:75 — core/services/cos/src/writer.rs:75-96 | core/services/cos/src/writer.rs:245-265 | core/services/obs/src/writer.rs:67-87 | core/services/oss/src/writer.rs:66-85 | core/services/oss/src/writer.rs:238-256 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/etcd/src/core.rs:102 — core/services/etcd/src/core.rs:102-114 | core/services/ftp/src/core.rs:59-71 | core/services/memcached/src/core.rs:254-266 | core/services/redis/src/core.rs:158-170 | core/services/sftp/src/core.rs:78-90 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/fs/src/core.rs:107 — core/services/fs/src/core.rs:107-136 | core/services/fs/src/writer.rs:180-221 | core/services/hdfs/src/core.rs:64-83 | core/services/monoiofs/src/backend.rs:110-133 | core/services/monoiofs/src/writer.rs:147-172 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/ghac/src/core.rs:560 — core/services/ghac/src/core.rs:560-588 | core/services/http/src/core.rs:169-200 | core/services/ipfs/src/core.rs:273-301 | core/services/onedrive/src/core.rs:1021-1068 | core/services/vercel-artifacts/src/core.rs:148-174 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) core/services/github/src/core.rs:436 — core/services/github/src/core.rs:436-470 | core/services/seafile/src/core.rs:560-587 | core/services/upyun/src/core.rs:617-646 | core/services/vercel-blob/src/core.rs:515-540 | core/services/yandex-disk/src/core.rs:421-449 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×11
  • Edited copy of a member (17 corresponding lines) bindings/python/src/options.rs:93 — bindings/python/src/options.rs:93-112 | bindings/python/src/options.rs:155-171 — 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) bindings/c/src/types.rs:200 — bindings/c/src/types.rs:200-218 | bindings/c/src/types.rs:305-321 — 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) core/services/azdls/src/writer.rs:133 — core/services/azdls/src/writer.rs:133-150 | core/services/azfile/src/writer.rs:125-141 — 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) dev/src/generate/options.rs:163 — dev/src/generate/options.rs:163-179 | dev/src/generate/parser.rs:351-368 — 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) core/services/redb/src/core.rs:69 — core/services/redb/src/core.rs:69-87 | core/services/redb/src/core.rs:89-105 — 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) core/layers/retry/src/lib.rs:452 — core/layers/retry/src/lib.rs:452-468 | core/layers/retry/src/lib.rs:586-604 — 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) core/core/src/types/write/futures_async_writer.rs:79 — core/core/src/types/write/futures_async_writer.rs:79-95 | core/core/src/types/write/futures_async_writer.rs:97-113 — 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) bindings/dotnet/OpenDAL/OperatorOutputStream.cs:77 — bindings/dotnet/OpenDAL/OperatorOutputStream.cs:77-93 | bindings/dotnet/OpenDAL/OperatorOutputStream.cs:102-120 — 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) bindings/haskell/src/lib.rs:838 — bindings/haskell/src/lib.rs:838-859 | bindings/haskell/src/lib.rs:876-892 — 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) core/services/fs/src/core.rs:72 — core/services/fs/src/core.rs:72-97 | core/services/monoiofs/src/core.rs:116-132 — 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) core/services/github/src/writer.rs:41 — core/services/github/src/writer.rs:41-58 | core/services/koofr/src/writer.rs:42-58 — 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 (9 corresponding lines) · ×11
  • Edited copy of a member (9 corresponding lines) bindings/java/src/operator_reader.rs:36 — bindings/java/src/operator_reader.rs:36-45 | bindings/java/src/operator_reader.rs:77-85 — 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) core/services/foundationdb/src/core.rs:58 — core/services/foundationdb/src/core.rs:58-67 | core/services/foundationdb/src/core.rs:69-77 — 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) core/services/etcd/src/config.rs:76 — core/services/etcd/src/config.rs:76-86 | core/services/tikv/src/config.rs:43-51 — 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) core/services/hf/src/writer.rs:56 — core/services/hf/src/writer.rs:56-64 | core/services/monoiofs/src/reader.rs:159-170 — 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) bindings/ocaml/src/operator/mod.rs:36 — bindings/ocaml/src/operator/mod.rs:36-44 | bindings/php/src/lib.rs:43-51 — 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) core/services/cos/src/config.rs:67 — core/services/cos/src/config.rs:67-78 | core/services/webhdfs/src/config.rs:45-53 — 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) core/services/gdrive/src/core.rs:747 — core/services/gdrive/src/core.rs:747-755 | core/services/onedrive/src/core.rs:735-743 — 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) core/core/src/raw/oio/copy/block_copy.rs:72 — core/core/src/raw/oio/copy/block_copy.rs:72-80 | core/core/src/raw/oio/copy/multipart_copy.rs:97-105 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) core/services/ftp/src/reader.rs:171 — core/services/ftp/src/reader.rs:171-179 | core/services/monoiofs/src/reader.rs:182-190 — 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) bindings/c/src/layer.rs:115 — bindings/c/src/layer.rs:115-123 | bindings/cpp/src/layer.rs:97-105 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) core/core/src/layers/correctness_check.rs:63 — core/core/src/layers/correctness_check.rs:63-71 | core/layers/capability-check/src/lib.rs:86-95 — 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×10
  • Hotspot: core/services/s3/src/backend.rs core/services/s3/src/backend.rs:931 — core/services/s3/src/backend.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in S3Builder::build at line 931. 3 of those changes were fix/bug commits, and the other 12 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/s3/src/backend.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: core/services/gcs/src/core.rs core/services/gcs/src/core.rs:2250 — core/services/gcs/src/core.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in opendal_service_gcs::core::parse_error at line 2250. 3 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/gcs/src/core.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: core/services/hf/src/core.rs core/services/hf/src/core.rs:774 — core/services/hf/src/core.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in HfCore::read at line 774. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/hf/src/core.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: core/services/cloudflare-kv/src/backend.rs core/services/cloudflare-kv/src/backend.rs:257 — core/services/cloudflare-kv/src/backend.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in CloudflareKvBackend::stat at line 257. 1 of those changes was a fix/bug commit, and the other 4 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/cloudflare-kv/src/backend.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: core/services/gdrive/src/lister.rs core/services/gdrive/src/lister.rs:400 — core/services/gdrive/src/lister.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in GdriveFlatLister::initialize at line 400. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/gdrive/src/lister.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: core/services/onedrive/src/lister.rs core/services/onedrive/src/lister.rs:63 — core/services/onedrive/src/lister.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in OneDriveLister::next_page at line 63. 1 of those changes was a fix/bug commit, and the other 2 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/onedrive/src/lister.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: core/services/cos/src/lister.rs core/services/cos/src/lister.rs:160 — core/services/cos/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CosObjectVersionsLister::next_page at line 160. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/cos/src/lister.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: core/services/oss/src/lister.rs core/services/oss/src/lister.rs:163 — core/services/oss/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in OssObjectVersionsLister::next_page at line 163. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/oss/src/lister.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: core/services/s3/src/lister.rs core/services/s3/src/lister.rs:316 — core/services/s3/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in S3ObjectVersionsLister::next_page at line 316. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/s3/src/lister.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: core/services/tos/src/lister.rs core/services/tos/src/lister.rs:157 — core/services/tos/src/lister.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in TosObjectVersionsLister::next_page at line 157. 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-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/tos/src/lister.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.
D3 · God Classes · TooManyMethods · ×10
  • TooManyMethods: Operator core/core/src/types/operator/operator.rs:196 — TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Operator bindings/dotnet/OpenDAL/Operator.cs — TooManyMethods — 584 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 30 methods; this is 39 over it, 2.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.
  • TooManyMethods: Capability bindings/go/operator_info.go:82 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: S3Builder core/services/s3/src/backend.rs:84 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AsyncOperator bindings/java/src/main/java/org/apache/opendal/AsyncOperator.java:43 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Operator core/core/src/blocking/operator.rs:127 — TooManyMethods — 47 methods, declared across 2 files: blocking/operator.rs (43), operator/builder.rs (4). The bar is 30 methods; this is 17 over it, 1.57× 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: Operator bindings/java/src/main/java/org/apache/opendal/Operator.java:32 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 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.
  • TooManyMethods: Operator bindings/nodejs/src/lib.rs:40 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GcsCore core/services/gcs/src/core.rs:67 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: S3Core core/services/s3/src/core.rs:97 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×10
  • Edited copy of a member (15 corresponding lines) core/core/src/types/delete/futures_delete_sink.rs:54 — core/core/src/types/delete/futures_delete_sink.rs:54-68 | core/core/src/types/delete/futures_delete_sink.rs:94-112 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) bindings/cpp/src/lib.rs:469 — bindings/cpp/src/lib.rs:469-486 | bindings/cpp/src/lib.rs:488-502 — 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) dev/src/generate/core_options.rs:84 — dev/src/generate/core_options.rs:84-99 | dev/src/generate/options.rs:68-82 — 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) core/services/tos/src/writer.rs:72 — core/services/tos/src/writer.rs:72-90 | core/services/upyun/src/writer.rs:49-63 — 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) bindings/go/delete.go:88 — bindings/go/delete.go:88-102 | bindings/go/reader.go:71-85 — 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) bindings/python/src/options.rs:175 — bindings/python/src/options.rs:175-192 | bindings/python/src/options.rs:196-210 — 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) core/services/ftp/src/config.rs:53 — core/services/ftp/src/config.rs:53-67 | core/services/http/src/config.rs:54-68 — 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) core/services/ghac/src/backend.rs:238 — core/services/ghac/src/backend.rs:238-252 | core/services/vercel-artifacts/src/backend.rs:176-192 — 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) core/layers/otelmetrics/src/lib.rs:472 — core/layers/otelmetrics/src/lib.rs:472-486 | core/layers/otelmetrics/src/lib.rs:493-507 — 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) core/services/etcd/src/backend.rs:280 — core/services/etcd/src/backend.rs:280-295 | core/services/sqlite/src/backend.rs:297-311 — 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 copy of a member (13 corresponding lines) · ×10
  • Edited copy of a member (13 corresponding lines) core/services/fs/src/reader.rs:162 — core/services/fs/src/reader.rs:162-174 | core/services/hdfs-native/src/reader.rs:142-159 — 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) core/core/src/services/memory/lister.rs:39 — core/core/src/services/memory/lister.rs:39-55 | core/services/moka/src/lister.rs:47-59 — 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) core/services/cacache/src/writer.rs:47 — core/services/cacache/src/writer.rs:47-59 | core/services/etcd/src/writer.rs:46-58 — 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) core/services/gdrive/src/lister.rs:71 — core/services/gdrive/src/lister.rs:71-83 | core/services/gdrive/src/lister.rs:368-382 — 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) core/services/etcd/src/lister.rs:106 — core/services/etcd/src/lister.rs:106-118 | core/services/mysql/src/lister.rs:78-90 — 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) bindings/go/reader.go:803 — bindings/go/reader.go:803-817 | bindings/go/writer.go:552-564 — 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) bindings/python/src/operator.rs:979 — bindings/python/src/operator.rs:979-991 | bindings/python/src/operator.rs:2144-2160 — 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) core/services/dbfs/src/deleter.rs:39 — core/services/dbfs/src/deleter.rs:39-52 | core/services/ipmfs/src/deleter.rs:39-51 — 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) core/core/src/raw/path.rs:27 — core/core/src/raw/path.rs:27-39 | core/core/src/raw/path.rs:47-59 — 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) bindings/dotnet/OpenDAL/Layer/RetryLayer.cs:60 — bindings/dotnet/OpenDAL/Layer/RetryLayer.cs:60-75 | bindings/dotnet/OpenDAL/Layer/TimeoutLayer.cs:45-57 — 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 (11 corresponding lines) · ×10
  • Edited copy of a member (11 corresponding lines) core/services/surrealdb/src/config.rs:51 — core/services/surrealdb/src/config.rs:51-61 | core/services/surrealdb/src/core.rs:44-54 — 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) bindings/python/src/operator.rs:355 — bindings/python/src/operator.rs:355-366 | bindings/python/src/operator.rs:2132-2142 — 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) core/layers/fastmetrics/src/lib.rs:170 — core/layers/fastmetrics/src/lib.rs:170-180 | core/layers/prometheus-client/src/lib.rs:114-124 — 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) bindings/c/src/operator.rs:198 — bindings/c/src/operator.rs:198-208 | bindings/c/src/operator.rs:225-235 — 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) core/layers/concurrent-limit/src/lib.rs:373 — core/layers/concurrent-limit/src/lib.rs:373-384 | core/layers/throttle/src/lib.rs:255-265 — 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) core/services/b2/src/writer.rs:201 — core/services/b2/src/writer.rs:201-211 | core/services/webhdfs/src/deleter.rs:40-50 — 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) integrations/dav-server/src/file.rs:108 — integrations/dav-server/src/file.rs:108-120 | integrations/dav-server/src/file.rs:160-170 — 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) core/core/src/raw/oio/list/page_list.rs:89 — core/core/src/raw/oio/list/page_list.rs:89-100 | core/services/gcs-grpc/src/lister.rs:114-124 — 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) core/core/src/types/compose/composer.rs:43 — core/core/src/types/compose/composer.rs:43-54 | core/core/src/types/delete/deleter.rs:91-101 — 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) core/services/b2/src/lister.rs:49 — core/services/b2/src/lister.rs:49-60 | core/services/oss/src/lister.rs:51-61 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×10
  • Duplicated block (10 lines × 3) core/layers/prometheus-client/src/lib.rs:205 — core/layers/prometheus-client/src/lib.rs:205-214 | core/layers/prometheus-client/src/lib.rs:233-242 | core/layers/prometheus-client/src/lib.rs:245-254 — 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 `core/layers/prometheus-client/src/lib.rs:205` 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, `core/layers/prometheus-client/src/lib.rs:232` calls `default` and `core/layers/prometheus-client/src/lib.rs:244` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) core/services/azblob/src/core.rs:155 — core/services/azblob/src/core.rs:155-164 | core/services/gcs/src/core.rs:103-112 | core/services/oss/src/core.rs:104-113 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/core.rs:120` calls `remove` and `core/services/azblob/src/core.rs:166` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) core/services/azdls/src/core.rs:849 — core/services/azdls/src/core.rs:849-858 | core/services/azfile/src/core.rs:568-577 | core/services/oss/src/core.rs:1240-1249 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azdls/src/core.rs:849` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 3) core/services/b2/src/backend.rs:392 — core/services/b2/src/backend.rs:392-402 | core/services/b2/src/backend.rs:425-435 | core/services/b2/src/backend.rs:449-458 — 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 `core/services/b2/src/backend.rs:392` 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) core/services/b2/src/core.rs:353 — core/services/b2/src/core.rs:353-362 | core/services/b2/src/core.rs:613-622 | core/services/b2/src/core.rs:644-653 — 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 `core/services/b2/src/core.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 (10 lines × 3) core/services/gcs/src/core.rs:180 — core/services/gcs/src/core.rs:180-189 | core/services/gcs/src/core.rs:580-589 | core/services/gcs/src/core.rs:710-719 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `&OpDelete` 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 (10 lines × 3) core/services/pcloud/src/backend.rs:312 — core/services/pcloud/src/backend.rs:312-321 | core/services/pcloud/src/backend.rs:357-366 | core/services/pcloud/src/deleter.rs:46-55 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/pcloud/src/backend.rs:312` 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 × 3) core/services/ghac/src/backend.rs:188 — core/services/ghac/src/backend.rs:188-197 | core/services/upyun/src/core.rs:566-575 | dev/src/release/mod.rs:275-284 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (10 lines × 3) core/services/seafile/src/core.rs:267 — core/services/seafile/src/core.rs:267-276 | core/services/seafile/src/core.rs:325-334 | core/services/seafile/src/core.rs:361-370 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (10 lines × 3) bindings/go/copy.go:203 — bindings/go/copy.go:203-212 | bindings/go/copy.go:217-226 | bindings/go/delete.go:151-160 — 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.
D3 · God Classes · MethodTooLong · ×9
  • MethodTooLong: S3Builder.build core/services/s3/src/backend.rs:931 — MethodTooLong — build runs 258 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 158 over it, 2.58× 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: PrometheusLayerBuilder.register core/layers/prometheus/src/lib.rs:286 — MethodTooLong — register runs 174 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 74 over it, 1.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OssBuilder.build core/services/oss/src/backend.rs:412 — MethodTooLong — build runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AzblobBuilder.build core/services/azblob/src/backend.rs:312 — MethodTooLong — build runs 136 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 36 over it, 1.36× 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: GcsBuilder.build core/services/gcs/src/backend.rs:254 — MethodTooLong — build runs 136 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 36 over it, 1.36× 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: OtelMetricsLayerBuilder.register core/layers/otelmetrics/src/lib.rs:169 — MethodTooLong — register runs 134 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 34 over it, 1.34× 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: PrometheusClientLayerBuilder.register core/layers/prometheus-client/src/lib.rs:204 — MethodTooLong — register runs 130 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 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GdriveFlatLister.initialize core/services/gdrive/src/lister.rs:400 — MethodTooLong — initialize runs 126 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GdriveBackend.rename core/services/gdrive/src/backend.rs:499 — MethodTooLong — rename runs 113 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 13 over it, 1.13× 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 (21 corresponding lines) · ×9
  • Edited copy of a member (21 corresponding lines) integrations/object_store/src/service/core.rs:27 — integrations/object_store/src/service/core.rs:27-54 | integrations/object_store/src/service/core.rs:57-104 — 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) core/core/src/raw/ops.rs:554 — core/core/src/raw/ops.rs:554-576 | core/core/src/raw/ops.rs:791-811 — 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) core/services/ipmfs/src/reader.rs:43 — core/services/ipmfs/src/reader.rs:43-63 | core/services/webhdfs/src/reader.rs:49-71 — 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) bindings/c/src/types.rs:765 — bindings/c/src/types.rs:765-785 | bindings/c/src/types.rs:1287-1309 — 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) core/services/compfs/src/reader.rs:74 — core/services/compfs/src/reader.rs:74-95 | core/services/fs/src/reader.rs:64-84 — 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) core/services/memcached/src/binary.rs:160 — core/services/memcached/src/binary.rs:160-187 | core/services/memcached/src/binary.rs:226-246 — 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) core/services/azblob/src/writer.rs:155 — core/services/azblob/src/writer.rs:155-175 | core/services/azdls/src/writer.rs:196-222 — 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) core/services/swift/src/core.rs:132 — core/services/swift/src/core.rs:132-155 | core/services/swift/src/core.rs:442-462 — 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) bindings/python/src/operator.rs:1493 — bindings/python/src/operator.rs:1493-1516 | bindings/python/src/operator.rs:1784-1804 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×9
  • Edited copy of a member (26 corresponding lines) core/services/gcs/src/reader.rs:54 — core/services/gcs/src/reader.rs:54-83 | core/services/s3/src/reader.rs:51-76 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/webdav/src/core.rs:274 — core/services/webdav/src/core.rs:274-299 | core/services/webdav/src/core.rs:398-423 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/memcached/src/binary.rs:111 — core/services/memcached/src/binary.rs:111-136 | core/services/memcached/src/binary.rs:189-224 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/fs/src/deleter.rs:35 — core/services/fs/src/deleter.rs:35-60 | core/services/monoiofs/src/deleter.rs:36-64 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/azblob/src/core.rs:475 — core/services/azblob/src/core.rs:475-508 | core/services/azblob/src/core.rs:530-555 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/azblob/src/core.rs:712 — core/services/azblob/src/core.rs:712-740 | core/services/obs/src/core.rs:219-244 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/services/azdls/src/backend.rs:513 — core/services/azdls/src/backend.rs:513-538 | core/services/koofr/src/backend.rs:357-386 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) dev/src/generate/python.rs:225 — dev/src/generate/python.rs:225-250 | dev/src/generate/python.rs:299-330 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) core/layers/logging/src/lib.rs:761 — core/layers/logging/src/lib.rs:761-789 | core/layers/logging/src/lib.rs:844-869 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×9
  • Edited copy of a member (16 corresponding lines) bindings/python/src/operator.rs:789 — bindings/python/src/operator.rs:789-804 | bindings/python/src/operator.rs:1672-1688 — 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) bindings/c/src/operator.rs:139 — bindings/c/src/operator.rs:139-154 | bindings/c/src/presign.rs:91-107 — 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) core/core/src/layers/error_context.rs:302 — core/core/src/layers/error_context.rs:302-317 | core/core/src/layers/error_context.rs:319-340 — 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) core/services/b2/src/deleter.rs:39 — core/services/b2/src/deleter.rs:39-56 | core/services/dropbox/src/deleter.rs:39-54 — 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) core/services/azblob/src/copier.rs:115 — core/services/azblob/src/copier.rs:115-130 | core/services/azblob/src/copier.rs:154-170 — 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) core/services/azblob/src/writer.rs:136 — core/services/azblob/src/writer.rs:136-151 | core/services/azblob/src/writer.rs:193-208 — 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) bindings/nodejs/src/options.rs:496 — bindings/nodejs/src/options.rs:496-511 | bindings/python/src/options.rs:214-229 — 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) core/services/pcloud/src/core.rs:463 — core/services/pcloud/src/core.rs:463-478 | core/services/pcloud/src/core.rs:480-495 — 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) core/services/sftp/src/core.rs:57 — core/services/sftp/src/core.rs:57-76 | core/services/etcd/src/core.rs:85-100 — 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 · Duplicated block (13 lines × 2) · ×9
  • Duplicated block (13 lines × 2) bindings/c/src/layer.rs:48 — bindings/c/src/layer.rs:48-60 | bindings/cpp/src/layer.rs:47-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. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/layer.rs:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `op` to `core::Operator` in one and `od::Operator` 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 (13 lines × 2) bindings/c/src/operator.rs:310 — bindings/c/src/operator.rs:310-322 | bindings/c/src/operator.rs:368-380 — both copies are in the same file, so extract the 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 `bindings/c/src/operator.rs:310` 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, `bindings/c/src/operator.rs:366` calls `is_null`, `write`, `null_mut` and `bindings/c/src/operator.rs:309` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) core/services/cos/src/backend.rs:456 — core/services/cos/src/backend.rs:456-468 | core/services/oss/src/backend.rs:785-797 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/oss/src/backend.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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/backend.rs:456` 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) core/services/dbfs/src/config.rs:49 — core/services/dbfs/src/config.rs:49-61 | core/services/pcloud/src/config.rs:57-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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 (13 lines × 2) core/services/hdfs-native/src/config.rs:64 — core/services/hdfs-native/src/config.rs:64-76 | core/services/hdfs/src/config.rs:69-81 — 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 (13 lines × 2) core/services/memcached/src/binary.rs:165 — core/services/memcached/src/binary.rs:165-177 | core/services/memcached/src/binary.rs:231-243 — both copies are in the same file, so extract the 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 `core/services/memcached/src/binary.rs:165` 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 × 2) core/services/oss/src/core.rs:382 — core/services/oss/src/core.rs:382-394 | core/services/oss/src/core.rs:417-429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/oss/src/core.rs:382` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) core/services/tos/src/copier.rs:148 — core/services/tos/src/copier.rs:148-160 | core/services/tos/src/writer.rs:101-113 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `core/services/tos/src/copier.rs:148` 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) core/services/pcloud/src/core.rs:466 — core/services/pcloud/src/core.rs:466-478 | core/services/pcloud/src/core.rs:483-495 — both copies are in the same file, so extract the 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 `core/services/pcloud/src/core.rs:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×9
  • Duplicated block (7 lines × 3) core/layers/fastmetrics/src/lib.rs:171 — core/layers/fastmetrics/src/lib.rs:171-177 | core/layers/prometheus-client/src/lib.rs:115-121 | core/layers/prometheus/src/lib.rs:203-209 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/layers/fastmetrics/src/lib.rs:171` 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) core/services/alluxio/src/core.rs:76 — core/services/alluxio/src/core.rs:76-83 | core/services/alluxio/src/core.rs:211-217 | core/services/alluxio/src/core.rs:369-375 — 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 `core/services/alluxio/src/core.rs:76` 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) core/services/alluxio/src/core.rs:177 — core/services/alluxio/src/core.rs:177-183 | core/services/alluxio/src/core.rs:209-216 | core/services/alluxio/src/core.rs:367-374 — 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 `core/services/alluxio/src/core.rs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 3) core/services/azblob/src/core.rs:244 — core/services/azblob/src/core.rs:244-250 | core/services/azblob/src/core.rs:309-315 | core/services/s3/src/core.rs:590-596 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 3) core/services/cos/src/writer.rs:57 — core/services/cos/src/writer.rs:57-63 | core/services/obs/src/writer.rs:51-57 | core/services/oss/src/writer.rs:50-56 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) core/services/gcs/src/core.rs:264 — core/services/gcs/src/core.rs:264-270 | core/services/http/src/core.rs:75-81 | core/services/http/src/core.rs:124-130 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) core/services/ghac/src/core.rs:150 — core/services/ghac/src/core.rs:150-157 | core/services/ghac/src/core.rs:286-293 | core/services/ghac/src/core.rs:395-401 — 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 `core/services/ghac/src/core.rs:150` 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) core/services/gridfs/src/config.rs:65 — core/services/gridfs/src/config.rs:65-71 | core/services/mongodb/src/config.rs:67-73 | core/services/surrealdb/src/config.rs:75-81 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gridfs/src/config.rs:65` 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 `uri` to `&OperatorUri` in one and `&opendal_core::OperatorUri` 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 (7 lines × 3) core/services/azblob/src/reader.rs:52 — core/services/azblob/src/reader.rs:52-58 | core/services/gcs/src/reader.rs:55-61 | core/services/s3/src/reader.rs:52-58 — before extracting anything, compare `core/services/azblob/src/reader.rs` and `core/services/gcs/src/reader.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 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×9
  • Duplicated block (5 lines × 2) core/core/src/raw/ops.rs:558 — core/core/src/raw/ops.rs:558-562 | core/core/src/raw/ops.rs:794-798 — both copies are in the same file, so extract the 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 `core/core/src/raw/ops.rs:558` 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 `value` to `options::ReadOptions` in one and `options::StatOptions` 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 (5 lines × 2) core/services/aliyun-drive/src/backend.rs:228 — core/services/aliyun-drive/src/backend.rs:228-232 | core/services/aliyun-drive/src/writer.rs:74-78 — 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 `core/services/aliyun-drive/src/backend.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 (5 lines × 2) core/services/oss/src/core.rs:321 — core/services/oss/src/core.rs:321-326 | core/services/oss/src/core.rs:415-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) core/services/pcloud/src/core.rs:137 — core/services/pcloud/src/core.rs:137-141 | core/services/yandex-disk/src/core.rs:182-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/pcloud/src/core.rs:137` 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) core/services/azblob/src/core.rs:518 — core/services/azblob/src/core.rs:518-522 | core/services/oss/src/core.rs:557-561 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:518` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) core/services/cloudflare-kv/src/config.rs:81 — core/services/cloudflare-kv/src/config.rs:81-85 | core/services/d1/src/config.rs:86-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cloudflare-kv/src/config.rs:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) core/services/redis/src/config.rs:82 — core/services/redis/src/config.rs:82-86 | core/services/swift/src/config.rs:67-71 — 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 `core/services/redis/src/config.rs:82` 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 `uri` to `&OperatorUri` in one and `&opendal_core::OperatorUri` 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 (5 lines × 2) core/core/src/types/operator/operator.rs:2709 — core/core/src/types/operator/operator.rs:2709-2713 | core/core/src/types/operator/operator.rs:2823-2827 — both copies are in the same file, so extract the 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 `core/core/src/types/operator/operator.rs:2709` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) core/services/persy/src/core.rs:55 — core/services/persy/src/core.rs:55-59 | core/services/persy/src/core.rs:96-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/persy/src/core.rs:55` 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.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×8
  • Edited copy of a member (25 corresponding lines) core/services/mini_moka/src/backend.rs:92 — core/services/mini_moka/src/backend.rs:92-135 | core/services/moka/src/backend.rs:147-196 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/services/persy/src/core.rs:69 — core/services/persy/src/core.rs:69-93 | core/services/persy/src/core.rs:95-130 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/services/goosefs/src/core.rs:484 — core/services/goosefs/src/core.rs:484-508 | core/services/goosefs/src/core.rs:518-544 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/services/oss/src/core.rs:523 — core/services/oss/src/core.rs:523-547 | core/services/tos/src/core.rs:527-554 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/core/src/types/buffer.rs:322 — core/core/src/types/buffer.rs:322-346 | core/core/src/types/buffer.rs:554-590 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) dev/src/release/package.rs:314 — dev/src/release/package.rs:314-338 | dev/src/release/package.rs:447-480 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/services/github/src/core.rs:114 — core/services/github/src/core.rs:114-138 | core/services/github/src/core.rs:145-170 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) core/services/pcloud/src/core.rs:403 — core/services/pcloud/src/core.rs:403-427 | core/services/pcloud/src/core.rs:433-460 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×8
  • Edited copy of a member (19 corresponding lines) core/layers/retry/src/lib.rs:396 — core/layers/retry/src/lib.rs:396-418 | core/layers/retry/src/lib.rs:426-444 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) core/services/oss/src/core.rs:262 — core/services/oss/src/core.rs:262-280 | core/services/oss/src/core.rs:289-312 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) bindings/cpp/src/async.rs:247 — bindings/cpp/src/async.rs:247-265 | bindings/cpp/src/async.rs:267-285 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) core/services/ipfs/src/core.rs:49 — core/services/ipfs/src/core.rs:49-67 | core/services/ipfs/src/core.rs:83-103 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) bindings/dotnet/src/operator.rs:1212 — bindings/dotnet/src/operator.rs:1212-1230 | bindings/dotnet/src/operator.rs:1477-1501 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) core/core/src/layers/complete.rs:349 — core/core/src/layers/complete.rs:349-367 | core/core/src/layers/complete.rs:407-425 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) core/services/pcloud/src/core.rs:179 — core/services/pcloud/src/core.rs:179-198 | core/services/yandex-disk/src/core.rs:205-223 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) core/services/etcd/src/backend.rs:234 — core/services/etcd/src/backend.rs:234-256 | core/services/foyer/src/backend.rs:215-233 — 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 (6 corresponding lines) · ×8
  • Edited copy of a member (6 corresponding lines) core/layers/hotpath/src/lib.rs:288 — core/layers/hotpath/src/lib.rs:288-293 | core/layers/tracing/src/lib.rs:171-180 — 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) core/core/src/services/memory/backend.rs:164 — core/core/src/services/memory/backend.rs:164-171 | core/services/redb/src/backend.rs:248-253 — 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) core/services/mini_moka/src/core.rs:38 — core/services/mini_moka/src/core.rs:38-43 | core/services/moka/src/core.rs:39-44 — 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) bindings/c/src/layer.rs:139 — bindings/c/src/layer.rs:139-144 | bindings/cpp/src/layer.rs:83-88 — 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) integrations/dav-server/src/metadata.rs:41 — integrations/dav-server/src/metadata.rs:41-46 | integrations/unftp-sbe/src/lib.rs:101-109 — 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) core/services/aliyun-drive/src/config.rs:65 — core/services/aliyun-drive/src/config.rs:65-70 | core/services/aliyun-drive/src/core.rs:74-79 — 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) core/services/gdrive/src/config.rs:48 — core/services/gdrive/src/config.rs:48-53 | core/services/gdrive/src/core.rs:56-61 — 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) scripts/release_lifecycle.py:53 — scripts/release_lifecycle.py:53-58 | scripts/sign_source_release.py:36-46 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×8
  • Duplicated block (11 lines × 3) bindings/c/src/types.rs:767 — bindings/c/src/types.rs:767-777 | bindings/c/src/types.rs:1063-1073 | bindings/c/src/types.rs:1289-1299 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `&opendal_stat_options` in one and `&opendal_read_options` 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 × 3) core/layers/retry/src/lib.rs:341 — core/layers/retry/src/lib.rs:341-351 | core/layers/retry/src/lib.rs:560-570 | core/layers/retry/src/lib.rs:591-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 `core/layers/retry/src/lib.rs:341` 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 × 3) core/layers/retry/src/lib.rs:872 — core/layers/retry/src/lib.rs:872-882 | core/layers/retry/src/lib.rs:974-984 | core/layers/retry/src/lib.rs:1038-1048 — 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 `core/layers/retry/src/lib.rs:872` 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 × 3) core/services/gridfs/src/config.rs:79 — core/services/gridfs/src/config.rs:79-89 | core/services/mongodb/src/config.rs:81-91 | core/services/surrealdb/src/config.rs:95-105 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gridfs/src/config.rs:79` 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 × 3) core/services/oss/src/core.rs:334 — core/services/oss/src/core.rs:334-344 | core/services/oss/src/core.rs:386-396 | core/services/oss/src/core.rs:421-431 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) core/services/redb/src/config.rs:40 — core/services/redb/src/config.rs:40-50 | core/services/rocksdb/src/config.rs:41-51 | core/services/sled/src/config.rs:51-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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 × 3) core/services/azfile/src/core.rs:137 — core/services/azfile/src/core.rs:137-147 | core/services/azfile/src/core.rs:190-201 | core/services/azfile/src/core.rs:334-345 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (11 lines × 3) bindings/c/src/reader.rs:72 — bindings/c/src/reader.rs:72-82 | bindings/c/src/reader.rs:111-121 | bindings/c/src/writer.rs:69-79 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/reader.rs:72` 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×8
  • Duplicated block (9 lines × 3) core/services/azblob/src/reader.rs:68 — core/services/azblob/src/reader.rs:68-76 | core/services/gcs/src/reader.rs:75-83 | core/services/s3/src/reader.rs:68-76 — before extracting anything, compare `core/services/azblob/src/reader.rs` and `core/services/gcs/src/reader.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/reader.rs:68` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) core/services/b2/src/core.rs:101 — core/services/b2/src/core.rs:101-110 | core/services/gdrive/src/core.rs:776-784 | core/services/webhdfs/src/core.rs:196-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/b2/src/core.rs:101` 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 × 3) core/services/cos/src/core.rs:95 — core/services/cos/src/core.rs:95-103 | core/services/obs/src/core.rs:90-98 | core/services/oss/src/core.rs:128-136 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/oss/src/core.rs:128` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/oss/src/core.rs:125` calls `Ok` and `core/services/cos/src/core.rs:94` 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 × 3) core/services/cos/src/lister.rs:255 — core/services/cos/src/lister.rs:255-263 | core/services/oss/src/lister.rs:258-266 | core/services/tos/src/lister.rs:245-253 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) core/services/gridfs/src/config.rs:69 — core/services/gridfs/src/config.rs:69-77 | core/services/mongodb/src/config.rs:71-79 | core/services/surrealdb/src/config.rs:85-93 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gridfs/src/config.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 (9 lines × 3) core/services/dbfs/src/writer.rs:59 — core/services/dbfs/src/writer.rs:59-67 | core/services/ipmfs/src/writer.rs:43-52 | core/services/webhdfs/src/writer.rs:58-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/dbfs/src/writer.rs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) core/services/s3/src/core.rs:918 — core/services/s3/src/core.rs:918-926 | core/services/s3/src/core.rs:970-978 | core/services/s3/src/core.rs:1493-1501 — 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 `core/services/s3/src/core.rs:918` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) core/services/mysql/src/core.rs:71 — core/services/mysql/src/core.rs:71-79 | core/services/postgresql/src/core.rs:69-77 | core/services/sqlite/src/core.rs:73-81 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×7
  • Change-coupling hub: error_context.rs → lib.rs, lib.rs, lib.rs, lib.rs, lib.rs, lib.rs core/core/src/layers/error_context.rs — `core/core/src/layers/error_context.rs` changes together with 6 other files — `core/layers/await-tree/src/lib.rs`, `core/layers/concurrent-limit/src/lib.rs`, `core/layers/logging/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/retry/src/lib.rs`, `core/layers/tracing/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
  • Change-coupling hub: lister.rs → lister.rs, lister.rs, lister.rs, lister.rs core/services/s3/src/lister.rs — `core/services/s3/src/lister.rs` changes together with 4 other files — `core/services/azblob/src/lister.rs`, `core/services/gcs/src/lister.rs`, `core/services/obs/src/lister.rs`, `core/services/oss/src/lister.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: lib.rs → lib.rs, lib.rs, lib.rs, lib.rs core/layers/concurrent-limit/src/lib.rs — `core/layers/concurrent-limit/src/lib.rs` changes together with 4 other files — `core/layers/logging/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/retry/src/lib.rs`, `core/layers/tracing/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: lib.rs → lib.rs, lib.rs, lib.rs core/layers/logging/src/lib.rs — `core/layers/logging/src/lib.rs` changes together with 3 other files — `core/layers/await-tree/src/lib.rs`, `core/layers/metrics/src/lib.rs`, `core/layers/tracing/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: backend.rs → uri.rs, backend.rs, backend.rs core/services/s3/src/backend.rs — `core/services/s3/src/backend.rs` changes together with 3 other files — `core/core/src/raw/http_util/uri.rs`, `core/services/http/src/backend.rs`, `core/services/obs/src/backend.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
  • Change-coupling hub: backend.rs → backend.rs, backend.rs, backend.rs, backend.rs core/services/azblob/src/backend.rs — `core/services/azblob/src/backend.rs` changes together with 4 other files — `core/services/azdls/src/backend.rs`, `core/services/azfile/src/backend.rs`, `core/services/http/src/backend.rs`, `core/services/s3/src/backend.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
  • Change-coupling hub: backend.rs → backend.rs, backend.rs, backend.rs, backend.rs core/services/gridfs/src/backend.rs — `core/services/gridfs/src/backend.rs` changes together with 4 other files — `core/services/mysql/src/backend.rs`, `core/services/postgresql/src/backend.rs`, `core/services/redis/src/backend.rs`, `core/services/sqlite/src/backend.rs` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×7
  • Edited copies of one member (4 members, 15+ corresponding lines) core/services/foundationdb/src/backend.rs:151 — core/services/foundationdb/src/backend.rs:151-169 | core/services/foyer/src/backend.rs:270-284 | core/services/memcached/src/backend.rs:289-304 | core/services/tikv/src/backend.rs:174-189 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) REDACTED:32 — REDACTED:32-46 | REDACTED:49-63 | REDACTED:66-80 | REDACTED:83-97 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) bindings/c/src/operator.rs:434 — bindings/c/src/operator.rs:434-450 | bindings/c/src/operator.rs:663-677 | bindings/c/src/operator.rs:980-996 | bindings/c/src/operator.rs:1104-1120 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) bindings/go/reader.go:686 — bindings/go/reader.go:686-701 | bindings/go/reader.go:764-779 | bindings/go/stat.go:307-321 | bindings/go/writer.go:504-519 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) bindings/lua/src/lib.rs:81 — bindings/lua/src/lib.rs:81-95 | bindings/lua/src/lib.rs:97-111 | bindings/lua/src/lib.rs:113-127 | bindings/lua/src/lib.rs:151-165 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) core/services/azblob/src/writer.rs:177 — core/services/azblob/src/writer.rs:177-191 | core/services/swift/src/writer.rs:61-79 | core/services/vercel-blob/src/writer.rs:57-72 | core/services/webhdfs/src/writer.rs:54-68 — 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.
  • Edited copies of one member (4 members, 15+ corresponding lines) bindings/go/reader.go:724 — bindings/go/reader.go:724-738 | bindings/go/stat.go:248-262 | bindings/go/stat.go:286-300 | bindings/go/writer.go:455-469 — 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 copy of a member (12 corresponding lines) · ×7
  • Edited copy of a member (12 corresponding lines) bindings/nodejs/src/lib.rs:334 — bindings/nodejs/src/lib.rs:334-346 | bindings/nodejs/src/lib.rs:401-412 — 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) core/services/ghac/src/core.rs:197 — core/services/ghac/src/core.rs:197-208 | core/services/ghac/src/core.rs:215-230 — 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) bindings/go/reader.go:648 — bindings/go/reader.go:648-659 | bindings/go/reader.go:664-675 — 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) core/services/b2/src/backend.rs:251 — core/services/b2/src/backend.rs:251-262 | core/services/seafile/src/backend.rs:218-233 — 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) core/services/dashmap/src/lister.rs:33 — core/services/dashmap/src/lister.rs:33-46 | core/services/mini_moka/src/lister.rs:32-43 — 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) core/services/foyer/src/core.rs:177 — core/services/foyer/src/core.rs:177-188 | core/services/foyer/src/core.rs:190-201 — 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) bindings/dotnet/src/presign.rs:65 — bindings/dotnet/src/presign.rs:65-80 | bindings/dotnet/src/operator.rs:190-201 — 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 · Duplicated block (6 lines × 3) · ×7
  • Duplicated block (6 lines × 3) bindings/c/src/operator.rs:488 — bindings/c/src/operator.rs:488-493 | bindings/c/src/operator.rs:1028-1033 | bindings/c/src/operator.rs:1152-1157 — 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 `bindings/c/src/operator.rs:488` 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 × 3) bindings/c/src/operator.rs:987 — bindings/c/src/operator.rs:987-992 | bindings/c/src/operator.rs:1039-1044 | bindings/c/src/writer.rs:119-124 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/c/src/operator.rs:987` 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 × 3) core/services/azblob/src/core.rs:1325 — core/services/azblob/src/core.rs:1325-1330 | core/services/azdls/src/core.rs:831-836 | core/services/azfile/src/core.rs:556-561 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:1325` 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 × 3) core/services/koofr/src/backend.rs:335 — core/services/koofr/src/backend.rs:335-341 | core/services/upyun/src/backend.rs:304-309 | core/services/vercel-blob/src/backend.rs:234-239 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/upyun/src/backend.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/koofr/src/backend.rs:335` 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 × 3) core/core/src/raw/oio/write/block_write.rs:163 — core/core/src/raw/oio/write/block_write.rs:163-168 | core/core/src/raw/oio/write/multipart_write.rs:246-251 | core/core/src/raw/oio/write/position_write.rs:119-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (6 lines × 3) core/services/azfile/src/core.rs:378 — core/services/azfile/src/core.rs:378-383 | core/services/azfile/src/core.rs:405-410 | core/services/cos/src/core.rs:310-316 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azfile/src/core.rs:378` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 3) core/services/azfile/src/core.rs:175 — core/services/azfile/src/core.rs:175-180 | core/services/cos/src/core.rs:474-480 | core/services/oss/src/core.rs:694-699 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azfile/src/core.rs:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D2 · Cognitive Complexity · odev · ×6
  • odev::generate::python::format_text (cognitive 28) dev/src/generate/python.rs:115 — odev::generate::python::format_text has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 5 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • odev::generate::metadata::parse (cognitive 22) dev/src/generate/metadata.rs:75 — odev::generate::metadata::parse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • odev::generate::docs::generate (cognitive 19) dev/src/generate/docs.rs:160 — odev::generate::docs::generate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (5 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • odev::generate::docs::build (cognitive 16) dev/src/generate/docs.rs:393 — odev::generate::docs::build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • odev::generate::metadata::classify (cognitive 16) dev/src/generate/metadata.rs:173 — odev::generate::metadata::classify has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), match/switch 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • odev::release::package::sync_workspace_internal_dependency_versions_in_dependencies (cognitive 16) dev/src/release/package.rs:482 — odev::release::package::sync_workspace_internal_dependency_versions_in_dependencies has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · TooManyFields · ×6
  • TooManyFields: Capability core/core/src/types/capability.rs:65 — TooManyFields — 90 stored fields. The bar is 30 stored fields; this is 60 over it, 3.00× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: opendalCapability REDACTED:22 — TooManyFields — 57 stored fields. The bar is 30 stored fields; this is 27 over it, 1.90× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: opendal_capability bindings/c/src/operator_info.rs:45 — TooManyFields — 57 stored fields. The bar is 30 stored fields; this is 27 over it, 1.90× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: Capability bindings/python/src/capability.rs:29 — TooManyFields — 48 stored fields beside 1 method. The bar is 30 stored fields; this is 18 over it, 1.60× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: S3Config core/services/s3/src/config.rs:34 — TooManyFields — 41 stored fields. The bar is 30 stored fields; this is 11 over it, 1.37× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
  • TooManyFields: Capability bindings/cpp/src/lib.rs:186 — TooManyFields — 32 stored fields. The bar is 30 stored fields; this is 2 over it, 1.07× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×6
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/aliyun-drive/src/backend.rs:258 — core/services/aliyun-drive/src/backend.rs:258-316 | core/services/koofr/src/backend.rs:303-349 | core/services/lakefs/src/backend.rs:304-333 | core/services/obs/src/backend.rs:404-433 | core/services/onedrive/src/backend.rs:305-327 | core/services/pcloud/src/backend.rs:284-342 | core/services/upyun/src/backend.rs:286-315 | core/services/vercel-blob/src/backend.rs:216-245 | core/services/webdav/src/backend.rs:346-385 | core/services/yandex-disk/src/backend.rs:189-223 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/aliyun-drive/src/core.rs:208 — core/services/aliyun-drive/src/core.rs:208-233 | core/services/aliyun-drive/src/core.rs:271-309 | core/services/aliyun-drive/src/core.rs:323-353 | core/services/aliyun-drive/src/core.rs:376-398 | core/services/aliyun-drive/src/core.rs:405-427 | core/services/aliyun-drive/src/core.rs:435-457 | core/services/aliyun-drive/src/core.rs:459-479 | core/services/aliyun-drive/src/core.rs:487-509 | core/services/aliyun-drive/src/core.rs:516-537 | core/services/aliyun-drive/src/core.rs:545-589 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/azblob/src/config.rs:105 — core/services/azblob/src/config.rs:105-117 | core/services/b2/src/config.rs:68-80 | core/services/cos/src/config.rs:84-96 | core/services/gcs-grpc/src/config.rs:80-89 | core/services/gcs/src/config.rs:127-139 | core/services/obs/src/config.rs:61-73 | core/services/oss/src/config.rs:136-148 | core/services/s3/src/config.rs:409-421 | core/services/tos/src/config.rs:105-117 | core/services/upyun/src/config.rs:56-68 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/b2/src/core.rs:174 — core/services/b2/src/core.rs:174-207 | core/services/b2/src/core.rs:214-255 | core/services/b2/src/core.rs:368-402 | core/services/pcloud/src/core.rs:66-115 | core/services/seafile/src/core.rs:158-188 | core/services/seafile/src/core.rs:265-299 | core/services/seafile/src/core.rs:323-356 | core/services/seafile/src/core.rs:359-392 | core/services/yandex-disk/src/core.rs:70-107 | core/services/yandex-disk/src/core.rs:125-162 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/cos/src/lister.rs:62 — core/services/cos/src/lister.rs:62-126 | core/services/cos/src/lister.rs:160-271 | core/services/obs/src/lister.rs:59-122 | core/services/oss/src/lister.rs:65-129 | core/services/oss/src/lister.rs:163-274 | core/services/s3/src/lister.rs:74-165 | core/services/s3/src/lister.rs:200-282 | core/services/s3/src/lister.rs:316-427 | core/services/tos/src/lister.rs:61-124 | core/services/tos/src/lister.rs:157-261 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) core/services/foundationdb/src/writer.rs:46 — core/services/foundationdb/src/writer.rs:46-57 | core/services/gridfs/src/writer.rs:47-58 | core/services/memcached/src/writer.rs:47-58 | core/services/mongodb/src/writer.rs:46-57 | core/services/mysql/src/writer.rs:46-57 | core/services/postgresql/src/writer.rs:46-57 | core/services/redis/src/writer.rs:47-58 | core/services/sqlite/src/writer.rs:45-56 | core/services/surrealdb/src/writer.rs:46-57 | core/services/tikv/src/writer.rs:46-57 — These 10 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 10 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 10 times.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×6
  • Edited copy of a member (27 corresponding lines) core/services/webdav/src/core.rs:329 — core/services/webdav/src/core.rs:329-355 | core/services/webdav/src/core.rs:363-391 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) core/services/azblob/src/core.rs:827 — core/services/azblob/src/core.rs:827-854 | core/services/azdls/src/core.rs:566-592 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) core/services/surrealdb/src/core.rs:90 — core/services/surrealdb/src/core.rs:90-116 | core/services/surrealdb/src/core.rs:118-152 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) bindings/python/src/file.rs:599 — bindings/python/src/file.rs:599-632 | bindings/python/src/file.rs:641-667 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) core/core/src/raw/path.rs:151 — core/core/src/raw/path.rs:151-177 | core/core/src/raw/path.rs:180-212 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) bindings/dotnet/OpenDAL/OperatorInputStream.cs:70 — bindings/dotnet/OpenDAL/OperatorInputStream.cs:70-96 | bindings/dotnet/OpenDAL/OperatorInputStream.cs:105-132 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×6
  • Edited copy of a member (23 corresponding lines) core/services/ghac/src/reader.rs:43 — core/services/ghac/src/reader.rs:43-65 | core/services/yandex-disk/src/reader.rs:48-70 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) core/layers/tail-cut/src/lib.rs:343 — core/layers/tail-cut/src/lib.rs:343-365 | core/layers/tail-cut/src/lib.rs:535-559 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) core/services/webhdfs/src/core.rs:155 — core/services/webhdfs/src/core.rs:155-177 | core/services/webhdfs/src/core.rs:252-283 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) core/services/b2/src/writer.rs:97 — core/services/b2/src/writer.rs:97-119 | core/services/upyun/src/writer.rs:65-88 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) bindings/dotnet/OpenDAL/Operator.cs:1352 — bindings/dotnet/OpenDAL/Operator.cs:1352-1374 | bindings/dotnet/OpenDAL/Operator.cs:1384-1407 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) core/services/dashmap/src/backend.rs:86 — core/services/dashmap/src/backend.rs:86-110 | core/services/moka/src/backend.rs:208-230 — 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 (22 corresponding lines) · ×6
  • Edited copy of a member (22 corresponding lines) bindings/nodejs/src/options.rs:216 — bindings/nodejs/src/options.rs:216-241 | bindings/nodejs/src/options.rs:333-354 — 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) core/services/azfile/src/core.rs:362 — core/services/azfile/src/core.rs:362-383 | core/services/azfile/src/core.rs:389-410 — 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) core/services/hf/src/core.rs:522 — core/services/hf/src/core.rs:522-543 | core/services/hf/src/core.rs:610-636 — 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) core/services/tos/src/core.rs:128 — core/services/tos/src/core.rs:128-150 | core/services/tos/src/core.rs:156-177 — 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) core/core/src/raw/oio/write/block_write.rs:175 — core/core/src/raw/oio/write/block_write.rs:175-196 | core/core/src/raw/oio/write/position_write.rs:128-150 — 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) core/services/ftp/src/backend.rs:209 — core/services/ftp/src/backend.rs:209-232 | core/services/ftp/src/deleter.rs:40-61 — 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 copy of a member (14 corresponding lines) · ×6
  • Edited copy of a member (14 corresponding lines) bindings/c/src/operator.rs:286 — bindings/c/src/operator.rs:286-299 | bindings/c/src/operator.rs:308-326 — 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) core/services/cacache/src/core.rs:36 — core/services/cacache/src/core.rs:36-49 | core/services/cacache/src/core.rs:81-95 — 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) bindings/dotnet/src/operator.rs:239 — bindings/dotnet/src/operator.rs:239-255 | bindings/java/src/layer.rs:45-58 — 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) core/services/cloudflare-kv/src/core.rs:59 — core/services/cloudflare-kv/src/core.rs:59-76 | core/services/cloudflare-kv/src/core.rs:78-91 — 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) core/services/azblob/src/core.rs:112 — core/services/azblob/src/core.rs:112-125 | core/services/gcs/src/core.rs:102-123 — 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) core/services/cacache/src/core.rs:51 — core/services/cacache/src/core.rs:51-64 | core/services/cacache/src/core.rs:66-79 — 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 · Duplicated block (16 lines × 2) · ×6
  • Duplicated block (16 lines × 2) bindings/c/src/operator.rs:864 — bindings/c/src/operator.rs:864-879 | bindings/c/src/operator.rs:925-940 — both copies are in the same file, so extract the 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 (16 lines × 2) core/core/src/raw/http_util/multipart.rs:424 — core/core/src/raw/http_util/multipart.rs:424-439 | core/core/src/raw/http_util/multipart.rs:608-623 — both copies are in the same file, so extract the 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 `core/core/src/raw/http_util/multipart.rs:424` 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 (16 lines × 2) core/services/azblob/src/writer.rs:55 — core/services/azblob/src/writer.rs:55-70 | core/services/azdls/src/writer.rs:98-113 — 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 (16 lines × 2) core/services/b2/src/writer.rs:75 — core/services/b2/src/writer.rs:75-90 | core/services/b2/src/writer.rs:179-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 `core/services/b2/src/writer.rs:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) core/services/oss/src/lister.rs:74 — core/services/oss/src/lister.rs:74-89 | core/services/tos/src/lister.rs:70-85 — before extracting anything, compare `core/services/oss/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 135 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/oss/src/lister.rs:74` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 2) core/services/tos/src/core.rs:624 — core/services/tos/src/core.rs:624-639 | core/services/tos/src/core.rs:860-875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×6
  • Duplicated block (14 lines × 4) core/layers/retry/src/lib.rs:786 — core/layers/retry/src/lib.rs:786-799 | core/layers/retry/src/lib.rs:818-831 | core/layers/retry/src/lib.rs:849-862 | core/layers/retry/src/lib.rs:880-893 — 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 `core/layers/retry/src/lib.rs:786` 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 × 4) core/services/cos/src/lister.rs:99 — core/services/cos/src/lister.rs:99-112 | core/services/s3/src/lister.rs:136-149 | core/services/s3/src/lister.rs:253-266 | core/services/tos/src/lister.rs:96-109 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:99` 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 × 4) core/services/cos/src/lister.rs:143 — core/services/cos/src/lister.rs:143-156 | core/services/oss/src/lister.rs:146-159 | core/services/s3/src/lister.rs:299-312 | core/services/tos/src/lister.rs:140-153 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core` to `Arc<CosCore>` in one and `Arc<OssCore>` 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 (14 lines × 4) core/services/lakefs/src/reader.rs:64 — core/services/lakefs/src/reader.rs:64-77 | core/services/obs/src/reader.rs:64-77 | core/services/swift/src/reader.rs:64-77 | core/services/tos/src/reader.rs:65-78 — before extracting anything, compare `core/services/lakefs/src/reader.rs` and `core/services/obs/src/reader.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/lakefs/src/reader.rs:64` 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 × 4) core/services/pcloud/src/core.rs:207 — core/services/pcloud/src/core.rs:207-221 | core/services/pcloud/src/core.rs:237-250 | core/services/pcloud/src/core.rs:320-334 | core/services/pcloud/src/core.rs:350-364 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (14 lines × 4) REDACTED:172 — REDACTED:172-185 | REDACTED:210-223 | REDACTED:248-261 | REDACTED:286-299 — 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 `REDACTED:172` 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×6
  • Duplicated block (9 lines × 4) bindings/dotnet/src/operator.rs:867 — bindings/dotnet/src/operator.rs:867-875 | bindings/dotnet/src/operator.rs:922-930 | bindings/dotnet/src/operator.rs:977-985 | bindings/dotnet/src/operator.rs:1032-1040 — 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 `bindings/dotnet/src/operator.rs:867` 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) core/services/azblob/src/core.rs:159 — core/services/azblob/src/core.rs:159-167 | core/services/cos/src/core.rs:79-87 | core/services/obs/src/core.rs:74-82 | core/services/oss/src/core.rs:108-116 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/core.rs:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/oss/src/core.rs:105` calls `Ok` and `core/services/cos/src/core.rs:78` 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) core/services/cos/src/core.rs:407 — core/services/cos/src/core.rs:407-415 | core/services/obs/src/core.rs:344-352 | core/services/s3/src/core.rs:900-908 | core/services/s3/src/core.rs:942-950 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/s3/src/core.rs:940` calls `push` and `core/services/cos/src/core.rs:405` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 4) core/services/etcd/src/core.rs:106 — core/services/etcd/src/core.rs:106-114 | core/services/memcached/src/core.rs:258-266 | core/services/redis/src/core.rs:162-170 | core/services/sftp/src/core.rs:82-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/etcd/src/core.rs:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) core/services/fs/src/core.rs:116 — core/services/fs/src/core.rs:116-124 | core/services/fs/src/writer.rs:211-219 | core/services/monoiofs/src/backend.rs:123-131 | core/services/monoiofs/src/writer.rs:162-170 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/fs/src/core.rs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 4) core/services/azdls/src/reader.rs:69 — core/services/azdls/src/reader.rs:69-77 | core/services/cos/src/reader.rs:70-78 | core/services/onedrive/src/reader.rs:78-86 | core/services/oss/src/reader.rs:70-78 — before extracting anything, compare `core/services/azdls/src/reader.rs` and `core/services/cos/src/reader.rs` as WHOLE FILES: 87% 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azdls/src/reader.rs:69` 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×5
  • Repeated repair: core/services/hf/src/reader.rs core/services/hf/src/reader.rs:145 — core/services/hf/src/reader.rs changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is HfReader::open at line 145), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(services/hf): restore reader-local XET resolution reuse (#8285)”; “fix(services/hf): make resolve cache opt-in (#8282)”; “fix(services/hf): pin the xet probe range and drop dead http-mode classification (#8263)”; “fix(services/hf): follow case redirects instead of resolving the canonical repo id (#8225)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/hf/src/reader.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.
  • Repeated repair: scripts/release_lifecycle.py scripts/release_lifecycle.py:560 — scripts/release_lifecycle.py changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is release_lifecycle.nexus_release at line 560), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(release): validate declarations and published state correctly (#8322)”; “fix(ci): publish dotnet packages only from final release tags (#8311)”; “fix(release): include unlabeled PRs and preserve version titles (#8308)”; “fix(release): publish approved source before optional distributions (#8304)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- scripts/release_lifecycle.py`: 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.
  • Repeated repair: bindings/java/src/executor.rs bindings/java/src/executor.rs:224 — bindings/java/src/executor.rs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is opendal_java::executor::executor_or_default at line 224), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(bindings/java): validate executor worker counts (#8439)”; “fix(bindings/java): use defining class loader on executor threads (#8293)”; “fix(bindings/java): release default executor after its last owner (#8289)”; “fix(bindings/java): install default HTTP transport on load (#8288)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- bindings/java/src/executor.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.
  • Repeated repair: website/docusaurus.config.js website/docusaurus.config.js:181 — website/docusaurus.config.js changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is generate:prepare at line 181), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(website): reuse Rust LLM documentation artifacts (#8275)”; “fix(website): generate badges and resolve images offline (#8272)”; “fix(website): dedupe theme-common to stop mobile navbar crash (#8265)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- website/docusaurus.config.js`: 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.
  • Repeated repair: core/services/hf/src/lister.rs core/services/hf/src/lister.rs:121 — core/services/hf/src/lister.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is HfLister::next_page at line 121), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(services/hf): drop the trailing slash from the root tree URL (#8243)”; “fix(services/hf): follow case redirects instead of resolving the canonical repo id (#8225)”; “fix: Canonicalize HuggingFace IDs to avoid inconsistent API (#8108)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 04:13:43 +08:00' --until='2026-11-14 04:13:43 +08:00' --full-history --no-merges -- core/services/hf/src/lister.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.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×5
  • Edited copy of a member (29 corresponding lines) core/services/gdrive/src/core.rs:311 — core/services/gdrive/src/core.rs:311-339 | core/services/gdrive/src/core.rs:350-393 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) core/services/git/src/core.rs:260 — core/services/git/src/core.rs:260-299 | core/services/git/src/core.rs:363-391 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) core/services/b2/src/core.rs:141 — core/services/b2/src/core.rs:141-169 | core/services/lakefs/src/core.rs:89-117 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) core/services/github/src/backend.rs:199 — core/services/github/src/backend.rs:199-227 | core/services/webhdfs/src/backend.rs:296-332 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) bindings/c/src/layer.rs:38 — bindings/c/src/layer.rs:38-66 | bindings/cpp/src/layer.rs:37-65 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×5
  • Edited copy of a member (33 corresponding lines) bindings/python/src/operator.rs:225 — bindings/python/src/operator.rs:225-257 | bindings/python/src/operator.rs:1034-1067 — 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) core/services/gridfs/src/config.rs:57 — core/services/gridfs/src/config.rs:57-89 | core/services/mongodb/src/config.rs:59-91 — 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) core/services/koofr/src/core.rs:370 — core/services/koofr/src/core.rs:370-402 | core/services/koofr/src/core.rs:409-441 — 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) core/services/pcloud/src/backend.rs:350 — core/services/pcloud/src/backend.rs:350-385 | core/services/pcloud/src/deleter.rs:41-73 — 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) core/services/etcd/src/backend.rs:297 — core/services/etcd/src/backend.rs:297-329 | core/services/sqlite/src/backend.rs:225-259 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×5
  • Edited copy of a member (30 corresponding lines) core/core/src/types/copy.rs:139 — core/core/src/types/copy.rs:139-168 | core/core/src/types/list.rs:66-99 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) core/layers/retry/src/lib.rs:770 — core/layers/retry/src/lib.rs:770-799 | core/layers/retry/src/lib.rs:801-831 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) core/services/tos/src/core.rs:623 — core/services/tos/src/core.rs:623-652 | core/services/tos/src/core.rs:859-891 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) core/layers/metrics/src/lib.rs:176 — core/layers/metrics/src/lib.rs:176-205 | core/layers/otelmetrics/src/lib.rs:435-464 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (30 corresponding lines) core/services/s3/src/core.rs:1210 — core/services/s3/src/core.rs:1210-1245 | core/services/upyun/src/core.rs:380-409 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 15+ corresponding lines) bindings/java/src/async_operator.rs:537 — bindings/java/src/async_operator.rs:537-551 | bindings/java/src/async_operator.rs:576-590 | bindings/java/src/async_operator.rs:616-630 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) core/core/src/types/operator/operator.rs:690 — core/core/src/types/operator/operator.rs:690-706 | core/core/src/types/operator/operator.rs:801-815 | core/core/src/types/operator/operator.rs:1145-1160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) core/core/src/types/buffer.rs:218 — core/core/src/types/buffer.rs:218-232 | core/core/src/types/buffer.rs:533-551 | core/core/src/types/buffer.rs:757-776 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) core/services/koofr/src/deleter.rs:39 — core/services/koofr/src/deleter.rs:39-53 | core/services/upyun/src/deleter.rs:39-53 | core/services/yandex-disk/src/deleter.rs:39-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) core/services/s3/src/lister.rs:54 — core/services/s3/src/lister.rs:54-70 | core/services/s3/src/lister.rs:181-196 | core/services/tos/src/lister.rs:43-57 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×5
  • Duplicated block (18 lines × 2) core/layers/retry/src/lib.rs:843 — core/layers/retry/src/lib.rs:843-860 | core/layers/retry/src/lib.rs:874-891 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/layers/retry/src/lib.rs:843` 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) core/services/gridfs/src/config.rs:58 — core/services/gridfs/src/config.rs:58-75 | core/services/mongodb/src/config.rs:60-77 — before extracting anything, compare `core/services/gridfs/src/config.rs` and `core/services/mongodb/src/config.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gridfs/src/config.rs:58` 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 `uri` to `&OperatorUri` in one and `&opendal_core::OperatorUri` 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 (18 lines × 2) core/services/hf/src/core.rs:1898 — core/services/hf/src/core.rs:1898-1915 | core/services/webdav/src/core.rs:1711-1728 — 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 `core/services/hf/src/core.rs:1898` 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) core/services/koofr/src/core.rs:378 — core/services/koofr/src/core.rs:378-395 | core/services/koofr/src/core.rs:417-434 — both copies are in the same file, so extract the 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 `core/services/koofr/src/core.rs:378` 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) core/services/s3/src/core.rs:255 — core/services/s3/src/core.rs:255-272 | core/services/s3/src/core.rs:292-309 — both copies are in the same file, so extract the 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 `core/services/s3/src/core.rs:255` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×5
  • Duplicated block (17 lines × 2) core/services/cos/src/core.rs:151 — core/services/cos/src/core.rs:151-167 | core/services/obs/src/core.rs:135-151 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (17 lines × 2) core/services/cos/src/core.rs:413 — core/services/cos/src/core.rs:413-429 | core/services/obs/src/core.rs:350-366 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.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 (17 lines × 2) core/services/cos/src/core.rs:437 — core/services/cos/src/core.rs:437-453 | core/services/s3/src/core.rs:986-1002 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 (17 lines × 2) core/services/gdrive/src/lister.rs:165 — core/services/gdrive/src/lister.rs:165-181 | core/services/gdrive/src/lister.rs:524-540 — both copies are in the same file, so extract the 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 `core/services/gdrive/src/lister.rs:165` 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) core/services/git/src/core.rs:280 — core/services/git/src/core.rs:280-296 | core/services/git/src/core.rs:340-356 — both copies are in the same file, so extract the 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 `core/services/git/src/core.rs:280` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×5
  • Duplicated block (9–10 lines × 2) core/services/azblob/src/core.rs:725 — core/services/azblob/src/core.rs:725-734 | core/services/gcs/src/core.rs:593-601 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–10 lines × 2) core/services/cos/src/core.rs:259 — core/services/cos/src/core.rs:259-267 | core/services/oss/src/core.rs:426-435 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:259` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `&OpDelete` 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 (9–10 lines × 2) core/services/cos/src/lister.rs:115 — core/services/cos/src/lister.rs:115-123 | core/services/tos/src/lister.rs:227-236 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 147 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:115` 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, `core/services/tos/src/lister.rs:225` calls `version`, `is_current`, `Some` and `core/services/cos/src/lister.rs:114` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9–10 lines × 2) core/services/ghac/src/core.rs:285 — core/services/ghac/src/core.rs:285-294 | core/services/ghac/src/core.rs:394-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/ghac/src/core.rs:285` 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–10 lines × 2) bindings/dart/lib/opendal.dart:45 — bindings/dart/lib/opendal.dart:45-54 | bindings/dart/lib/opendal.dart:70-78 — both copies are in the same file, so extract the 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 `bindings/dart/lib/opendal.dart:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×5
  • Duplicated block (9 lines × 5) core/layers/observe-metrics-common/src/lib.rs:759 — core/layers/observe-metrics-common/src/lib.rs:759-767 | core/layers/observe-metrics-common/src/lib.rs:890-898 | core/layers/observe-metrics-common/src/lib.rs:925-933 | core/layers/observe-metrics-common/src/lib.rs:956-964 | core/layers/observe-metrics-common/src/lib.rs:1054-1062 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 5) core/services/cacache/src/reader.rs:47 — core/services/cacache/src/reader.rs:47-55 | core/services/dashmap/src/reader.rs:49-57 | core/services/etcd/src/reader.rs:47-56 | core/services/mini_moka/src/reader.rs:49-58 | core/services/moka/src/reader.rs:49-57 — before extracting anything, compare `core/services/dashmap/src/reader.rs` and `core/services/moka/src/reader.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cacache/src/reader.rs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 5) core/services/pcloud/src/core.rs:83 — core/services/pcloud/src/core.rs:83-91 | core/services/seafile/src/core.rs:170-178 | core/services/seafile/src/core.rs:280-288 | core/services/seafile/src/core.rs:338-346 | core/services/seafile/src/core.rs:374-382 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/pcloud/src/core.rs:83` 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 × 5) core/services/webhdfs/src/core.rs:64 — core/services/webhdfs/src/core.rs:64-72 | core/services/webhdfs/src/core.rs:98-106 | core/services/webhdfs/src/core.rs:293-301 | core/services/webhdfs/src/core.rs:386-394 | core/services/webhdfs/src/core.rs:413-421 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/webhdfs/src/core.rs:64` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/webhdfs/src/core.rs:397` calls `extension`, `ServiceOperation` and `core/services/webhdfs/src/core.rs:304` 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 × 5) core/services/ftp/src/backend.rs:81 — core/services/ftp/src/backend.rs:81-89 | core/services/koofr/src/backend.rs:98-106 | core/services/pcloud/src/backend.rs:94-102 | core/services/seafile/src/backend.rs:95-103 | core/services/upyun/src/backend.rs:90-98 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/pcloud/src/backend.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×5
  • Duplicated block (7 lines × 4) core/services/azdls/src/core.rs:75 — core/services/azdls/src/core.rs:75-81 | core/services/azfile/src/core.rs:65-71 | core/services/gcs/src/core.rs:94-100 | core/services/oss/src/core.rs:95-101 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) bindings/java/src/operator.rs:169 — bindings/java/src/operator.rs:169-175 | bindings/java/src/operator.rs:195-201 | bindings/java/src/operator.rs:282-288 | bindings/java/src/operator_output_stream.rs:94-100 — 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 `bindings/java/src/operator.rs:169` 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) core/services/cos/src/core.rs:550 — core/services/cos/src/core.rs:550-558 | core/services/gcs/src/core.rs:1066-1073 | core/services/oss/src/core.rs:643-649 | core/services/oss/src/core.rs:774-780 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 8 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/core.rs:550` 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, `core/services/oss/src/core.rs:639` calls `header`, `format_content_md5`, `as_bytes` and `core/services/gcs/src/core.rs:1062` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) core/services/azfile/src/core.rs:213 — core/services/azfile/src/core.rs:213-219 | core/services/cos/src/core.rs:505-513 | core/services/gcs/src/core.rs:1029-1036 | core/services/oss/src/core.rs:728-734 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azfile/src/core.rs:213` 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) core/services/aliyun-drive/src/config.rs:82 — core/services/aliyun-drive/src/config.rs:82-89 | core/services/foyer/src/config.rs:68-75 | core/services/goosefs/src/config.rs:114-120 | core/services/moka/src/config.rs:56-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/config.rs:82` 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 first that the copies are not typed on the same thing: the declarations holding them bind `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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.
D10 · Test Quality · No assertions · ×4
  • No assertions: DeleteBehavior_DeletingMissingPath_IsAllowed bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:68 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: DeleteBehavior_DeletingMissingPath_IsAllowedAsync bindings/dotnet/OpenDAL.Tests/Behavior/DeleteBehaviorTest.cs:79 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ListBehavior_Check_Succeeds bindings/dotnet/OpenDAL.Tests/Behavior/ListBehaviorTest.cs:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ListBehavior_Check_SucceedsAsync bindings/dotnet/OpenDAL.Tests/Behavior/ListBehaviorTest.cs:45 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D3 · God Classes · FunctionTooLong · ×4
  • FunctionTooLong: odev::generate::dotnet::options_class dev/src/generate/dotnet.rs:537 — FunctionTooLong — odev::generate::dotnet::options_class runs 153 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 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: opendal::init_default_registry_inner core/src/lib.rs:74 — FunctionTooLong — opendal::init_default_registry_inner runs 136 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 36 over it, 1.36× 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: odev::generate::dotnet::metadata_field dev/src/generate/dotnet.rs:341 — FunctionTooLong — odev::generate::dotnet::metadata_field runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: index.SearchBar website/src/theme/SearchBar/index.jsx:65 — FunctionTooLong — SearchBar runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) 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 · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/alluxio/src/core.rs:90 — core/services/alluxio/src/core.rs:90-130 | core/services/alluxio/src/core.rs:132-162 | core/services/alluxio/src/core.rs:224-255 | core/services/alluxio/src/core.rs:261-292 | core/services/b2/src/core.rs:80-131 | core/services/gdrive/src/core.rs:758-805 | core/services/webhdfs/src/core.rs:179-216 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/cacache/src/reader.rs:38 — core/services/cacache/src/reader.rs:38-58 | core/services/cloudflare-kv/src/reader.rs:51-146 | core/services/dashmap/src/reader.rs:38-60 | core/services/etcd/src/reader.rs:38-59 | core/services/foyer/src/reader.rs:38-59 | core/services/mini_moka/src/reader.rs:38-61 | core/services/moka/src/reader.rs:38-60 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/cos/src/core.rs:921 — core/services/cos/src/core.rs:921-986 | core/services/dbfs/src/core.rs:267-297 | core/services/ipmfs/src/core.rs:210-248 | core/services/lakefs/src/core.rs:358-388 | core/services/obs/src/core.rs:706-741 | core/services/oss/src/core.rs:1228-1285 | core/services/webhdfs/src/core.rs:468-499 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
  • Members sharing a duplicated core (7 members, 50+ identical tokens) core/services/foundationdb/src/backend.rs:96 — core/services/foundationdb/src/backend.rs:96-114 | core/services/gridfs/src/backend.rs:165-187 | core/services/memcached/src/backend.rs:234-252 | core/services/mongodb/src/backend.rs:180-202 | core/services/postgresql/src/backend.rs:157-175 | core/services/surrealdb/src/backend.rs:211-229 | core/services/tikv/src/backend.rs:125-143 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication · Edited copy of a member (43 corresponding lines) · ×4
  • Edited copy of a member (43 corresponding lines) core/services/koofr/src/lister.rs:49 — core/services/koofr/src/lister.rs:49-91 | core/services/upyun/src/lister.rs:51-104 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) core/services/tos/src/copier.rs:213 — core/services/tos/src/copier.rs:213-255 | core/services/tos/src/writer.rs:160-202 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) core/services/s3/src/copier.rs:42 — core/services/s3/src/copier.rs:42-85 | core/services/tos/src/copier.rs:37-79 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (43 corresponding lines) core/services/alluxio/src/backend.rs:80 — core/services/alluxio/src/backend.rs:80-122 | core/services/dbfs/src/backend.rs:84-131 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×4
  • Edited copy of a member (24 corresponding lines) core/services/http/src/reader.rs:50 — core/services/http/src/reader.rs:50-73 | core/services/ipfs/src/reader.rs:43-66 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) bindings/c/src/reader.rs:93 — bindings/c/src/reader.rs:93-121 | bindings/c/src/writer.rs:56-79 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) core/services/webhdfs/src/writer.rs:70 — core/services/webhdfs/src/writer.rs:70-96 | core/services/webhdfs/src/writer.rs:152-175 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) core/layers/logging/src/lib.rs:633 — core/layers/logging/src/lib.rs:633-656 | core/layers/logging/src/lib.rs:658-684 — 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 · Duplicated block (21 lines × 2) · ×4
  • Duplicated block (21 lines × 2) bindings/haskell/src/lib.rs:332 — bindings/haskell/src/lib.rs:332-352 | bindings/haskell/src/lib.rs:383-403 — both copies are in the same file, so extract the 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 `bindings/haskell/src/lib.rs:332` 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 (21 lines × 2) core/services/cos/src/lister.rs:251 — core/services/cos/src/lister.rs:251-271 | core/services/oss/src/lister.rs:254-274 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:251` 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 (21 lines × 2) core/core/src/types/operator/operator.rs:1488 — core/core/src/types/operator/operator.rs:1488-1508 | core/core/src/types/operator/operator.rs:1534-1554 — both copies are in the same file, so extract the 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 `core/core/src/types/operator/operator.rs:1488` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) bindings/go/operator.go:145 — bindings/go/operator.go:145-165 | bindings/go/operator.go:169-189 — both copies are in the same file, so extract the 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 `bindings/go/operator.go:145` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×4
  • Duplicated block (20 lines × 2) core/core/src/raw/http_util/multipart.rs:451 — core/core/src/raw/http_util/multipart.rs:451-470 | core/core/src/raw/http_util/multipart.rs:487-506 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/raw/http_util/multipart.rs:451` 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) core/core/src/raw/ops.rs:444 — core/core/src/raw/ops.rs:444-463 | core/core/src/raw/ops.rs:1117-1136 — both copies are in the same file, so extract the 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 `core/core/src/raw/ops.rs:444` 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) core/services/rocksdb/src/lister.rs:44 — core/services/rocksdb/src/lister.rs:44-63 | core/services/sled/src/lister.rs:44-63 — 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 (20 lines × 2) core/services/s3/src/core.rs:1255 — core/services/s3/src/core.rs:1255-1274 | core/services/s3/src/core.rs:1307-1326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×4
  • Duplicated block (19 lines × 2) core/services/azdls/src/config.rs:82 — core/services/azdls/src/config.rs:82-100 | core/services/azfile/src/config.rs:57-75 — 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 `core/services/azdls/src/config.rs:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) core/services/s3/src/lister.rs:147 — core/services/s3/src/lister.rs:147-165 | core/services/s3/src/lister.rs:264-282 — both copies are in the same file, so extract the 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 `core/services/s3/src/lister.rs:147` 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 (19 lines × 2) core/services/yandex-disk/src/core.rs:84 — core/services/yandex-disk/src/core.rs:84-102 | core/services/yandex-disk/src/core.rs:139-157 — both copies are in the same file, so extract the 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 `core/services/yandex-disk/src/core.rs:84` 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 (19 lines × 2) integrations/object_store/src/service/core.rs:33 — integrations/object_store/src/service/core.rs:33-51 | integrations/object_store/src/service/core.rs:60-78 — both copies are in the same file, so extract the 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 first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `&OpRead` 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 · Duplicated block (13 lines × 3) · ×4
  • Duplicated block (13 lines × 3) core/services/compfs/src/core.rs:72 — core/services/compfs/src/core.rs:72-84 | core/services/fs/src/core.rs:49-61 | core/services/monoiofs/src/core.rs:99-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 3) core/services/cos/src/core.rs:137 — core/services/cos/src/core.rs:137-149 | core/services/cos/src/core.rs:251-263 | core/services/cos/src/core.rs:292-304 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (13 lines × 3) core/services/oss/src/lister.rs:76 — core/services/oss/src/lister.rs:76-89 | core/services/s3/src/lister.rs:212-224 | core/services/tos/src/lister.rs:72-85 — before extracting anything, compare `core/services/oss/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 174 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/oss/src/lister.rs:76` 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 × 3) core/services/azblob/src/lister.rs:67 — core/services/azblob/src/lister.rs:67-79 | core/services/cos/src/lister.rs:69-81 | core/services/obs/src/lister.rs:66-78 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/lister.rs:67` 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×4
  • Duplicated block (12 lines × 4) core/core/src/raw/ops.rs:115 — core/core/src/raw/ops.rs:115-126 | core/core/src/raw/ops.rs:862-873 | core/core/src/raw/ops.rs:1110-1121 | core/core/src/raw/ops.rs:1296-1307 — 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 `core/core/src/raw/ops.rs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 4) core/services/azdls/src/core.rs:885 — core/services/azdls/src/core.rs:885-896 | core/services/azfile/src/core.rs:621-632 | core/services/cos/src/core.rs:959-970 | core/services/oss/src/core.rs:1257-1268 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azdls/src/core.rs:885` 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) core/services/fs/src/core.rs:110 — core/services/fs/src/core.rs:110-121 | core/services/hdfs/src/core.rs:68-79 | core/services/monoiofs/src/backend.rs:117-128 | core/services/monoiofs/src/writer.rs:156-167 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 4) core/services/dbfs/src/backend.rs:218 — core/services/dbfs/src/backend.rs:218-229 | core/services/onedrive/src/backend.rs:275-286 | core/services/vercel-artifacts/src/backend.rs:206-217 | core/services/webdav/src/backend.rs:303-314 — before extracting anything, compare `core/services/dbfs/src/backend.rs` and `core/services/onedrive/src/backend.rs` as WHOLE FILES: this scan already matched 3 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×4
  • Duplicated block (11–12 lines × 2) core/services/cos/src/core.rs:940 — core/services/cos/src/core.rs:940-951 | core/services/oss/src/core.rs:1245-1255 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:940` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/cos/src/core.rs:938` calls `as_u16` and `core/services/oss/src/core.rs:1244` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–12 lines × 2) core/services/gdrive/src/backend.rs:162 — core/services/gdrive/src/backend.rs:162-173 | core/services/onedrive/src/backend.rs:168-178 — before extracting anything, compare `core/services/gdrive/src/backend.rs` and `core/services/onedrive/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gdrive/src/backend.rs:162` 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–12 lines × 2) core/services/oss/src/backend.rs:773 — core/services/oss/src/backend.rs:773-783 | core/services/swift/src/backend.rs:383-394 — before extracting anything, compare `core/services/oss/src/backend.rs` and `core/services/swift/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/oss/src/backend.rs:773` 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–12 lines × 2) core/services/pcloud/src/core.rs:123 — core/services/pcloud/src/core.rs:123-134 | core/services/seafile/src/core.rs:310-320 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/seafile/src/core.rs:310` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/seafile/src/core.rs:308` calls `get_download_url` and `core/services/pcloud/src/core.rs:122` 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×4
  • Duplicated block (11 lines × 4) core/services/cos/src/lister.rs:161 — core/services/cos/src/lister.rs:161-171 | core/services/oss/src/lister.rs:164-174 | core/services/s3/src/lister.rs:317-327 | core/services/tos/src/lister.rs:158-168 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut PageContext` in one and `&mut oio::PageContext` 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 × 4) core/services/persy/src/backend.rs:180 — core/services/persy/src/backend.rs:180-190 | core/services/redb/src/backend.rs:201-211 | core/services/rocksdb/src/backend.rs:148-158 | core/services/sled/src/backend.rs:172-182 — before extracting anything, compare `core/services/persy/src/backend.rs` and `core/services/redb/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/persy/src/backend.rs:180` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 4) core/services/persy/src/writer.rs:47 — core/services/persy/src/writer.rs:47-57 | core/services/redb/src/writer.rs:47-57 | core/services/rocksdb/src/writer.rs:48-58 | core/services/sled/src/writer.rs:47-57 — before extracting anything, compare `core/services/persy/src/writer.rs` and `core/services/redb/src/writer.rs` as WHOLE FILES: 84% 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 (11 lines × 4) core/services/github/src/backend.rs:241 — core/services/github/src/backend.rs:241-251 | core/services/koofr/src/backend.rs:265-275 | core/services/pcloud/src/backend.rs:246-256 | core/services/yandex-disk/src/backend.rs:258-268 — before extracting anything, compare `core/services/github/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×4
  • Duplicated block (8–9 lines × 2) core/services/cos/src/core.rs:472 — core/services/cos/src/core.rs:472-480 | core/services/oss/src/core.rs:692-699 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:472` 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–9 lines × 2) core/services/ipfs/src/core.rs:275 — core/services/ipfs/src/core.rs:275-283 | core/services/vercel-artifacts/src/core.rs:150-157 — 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 `core/services/ipfs/src/core.rs:275` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8–9 lines × 2) core/services/ipmfs/src/reader.rs:48 — core/services/ipmfs/src/reader.rs:48-55 | core/services/webhdfs/src/reader.rs:55-63 — 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 `core/services/ipmfs/src/reader.rs:48` 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–9 lines × 2) core/services/koofr/src/backend.rs:114 — core/services/koofr/src/backend.rs:114-121 | core/services/pcloud/src/backend.rs:110-118 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/pcloud/src/backend.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/koofr/src/backend.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×4
  • Duplicated block (8 lines × 5) bindings/c/src/operator.rs:1288 — bindings/c/src/operator.rs:1288-1295 | bindings/c/src/operator.rs:1350-1357 | bindings/c/src/operator.rs:1423-1430 | bindings/c/src/operator.rs:1483-1490 | bindings/c/src/operator.rs:1525-1532 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (8 lines × 5) core/services/cos/src/lister.rs:105 — core/services/cos/src/lister.rs:105-112 | core/services/s3/src/lister.rs:142-149 | core/services/s3/src/lister.rs:259-266 | core/services/tos/src/lister.rs:102-109 | core/services/tos/src/lister.rs:240-247 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:105` 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, `core/services/tos/src/lister.rs:238` calls `deleted` and `core/services/cos/src/lister.rs:102` 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 × 5) core/services/fs/src/core.rs:114 — core/services/fs/src/core.rs:114-122 | core/services/fs/src/writer.rs:209-217 | core/services/hdfs/src/core.rs:72-79 | core/services/monoiofs/src/backend.rs:121-129 | core/services/monoiofs/src/writer.rs:160-168 — before extracting anything, compare `core/services/fs/src/core.rs` and `core/services/monoiofs/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/fs/src/core.rs:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 5) core/services/gridfs/src/backend.rs:231 — core/services/gridfs/src/backend.rs:231-238 | core/services/mongodb/src/backend.rs:246-253 | core/services/mysql/src/backend.rs:227-234 | core/services/redis/src/backend.rs:354-361 | core/services/surrealdb/src/backend.rs:273-280 — before extracting anything, compare `core/services/gridfs/src/backend.rs` and `core/services/mongodb/src/backend.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gridfs/src/backend.rs:231` 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.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×4
  • Duplicated block (7 lines × 6) core/services/alluxio/src/core.rs:146 — core/services/alluxio/src/core.rs:146-152 | core/services/alluxio/src/core.rs:239-245 | core/services/alluxio/src/core.rs:276-282 | core/services/b2/src/core.rs:102-110 | core/services/gdrive/src/core.rs:776-784 | core/services/webhdfs/src/core.rs:196-205 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/alluxio/src/core.rs:146` 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 × 6) core/services/dropbox/src/core.rs:185 — core/services/dropbox/src/core.rs:185-191 | core/services/dropbox/src/core.rs:209-215 | core/services/dropbox/src/core.rs:251-257 | core/services/dropbox/src/core.rs:276-282 | core/services/dropbox/src/core.rs:303-309 | core/services/dropbox/src/core.rs:330-336 — 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 `core/services/dropbox/src/core.rs:185` 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, `core/services/dropbox/src/core.rs:250` calls `unwrap_or` and `core/services/dropbox/src/core.rs:184` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 6) bindings/java/src/operator.rs:73 — bindings/java/src/operator.rs:73-79 | bindings/java/src/operator.rs:140-146 | bindings/java/src/operator.rs:222-228 | bindings/java/src/operator.rs:253-259 | bindings/java/src/operator.rs:317-323 | bindings/java/src/operator_output_stream.rs:42-48 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `bindings/java/src/operator.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 (7 lines × 6) core/services/azblob/src/core.rs:847 — core/services/azblob/src/core.rs:847-854 | core/services/azdls/src/core.rs:585-592 | core/services/cos/src/core.rs:421-429 | core/services/cos/src/core.rs:617-625 | core/services/obs/src/core.rs:358-366 | core/services/oss/src/core.rs:595-601 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:847` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×4
  • Duplicated block (6 lines × 5) bindings/c/src/operator.rs:365 — bindings/c/src/operator.rs:365-370 | bindings/c/src/operator.rs:547-552 | bindings/c/src/operator.rs:598-603 | bindings/c/src/operator.rs:664-669 | bindings/c/src/operator.rs:687-692 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 5) core/services/azdls/src/core.rs:361 — core/services/azdls/src/core.rs:361-366 | core/services/gcs/src/core.rs:254-259 | core/services/http/src/core.rs:67-73 | core/services/http/src/core.rs:116-122 | core/services/swift/src/core.rs:396-401 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 4 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/core.rs:260` calls `Some`, `if_version_match`, `header` and `core/services/azdls/src/core.rs:367` 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 (6 lines × 5) core/services/azfile/src/core.rs:158 — core/services/azfile/src/core.rs:158-164 | core/services/cos/src/core.rs:338-344 | core/services/obs/src/core.rs:288-294 | core/services/oss/src/core.rs:180-186 | core/services/oss/src/core.rs:671-676 — before extracting anything, compare `core/services/azfile/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 5) core/services/etcd/src/core.rs:105 — core/services/etcd/src/core.rs:105-110 | core/services/ftp/src/core.rs:62-67 | core/services/memcached/src/core.rs:257-262 | core/services/redis/src/core.rs:161-166 | core/services/sftp/src/core.rs:81-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/etcd/src/core.rs:105` 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×4
  • Duplicated block (5 lines × 4) core/services/foyer/src/reader.rs:39 — core/services/foyer/src/reader.rs:39-44 | core/services/memcached/src/reader.rs:39-43 | core/services/mysql/src/reader.rs:40-44 | core/services/tikv/src/reader.rs:40-44 — before extracting anything, compare `core/services/memcached/src/reader.rs` and `core/services/mysql/src/reader.rs` as WHOLE FILES: 83% 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/foyer/src/reader.rs:39` 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) core/services/hf/src/core.rs:577 — core/services/hf/src/core.rs:577-581 | core/services/hf/src/core.rs:752-756 | core/services/hf/src/core.rs:967-972 | core/services/hf/src/core.rs:1011-1016 — 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 `core/services/hf/src/core.rs:577` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/hf/src/core.rs:1009` calls `header` and `core/services/hf/src/core.rs:750` 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 (5 lines × 4) core/core/src/blocking/read/buffer_iterator.rs:61 — core/core/src/blocking/read/buffer_iterator.rs:61-65 | core/core/src/blocking/read/reader.rs:117-121 | core/core/src/blocking/read/std_bytes_iterator.rs:65-69 | core/core/src/blocking/write/writer.rs:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (5 lines × 4) core/services/azblob/src/core.rs:654 — core/services/azblob/src/core.rs:654-658 | core/services/azblob/src/core.rs:706-710 | core/services/gcs/src/core.rs:825-829 | core/services/gcs/src/core.rs:940-944 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:654` 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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (6 members, 50+ identical tokens) core/services/dropbox/src/core.rs:181 — core/services/dropbox/src/core.rs:181-199 | core/services/dropbox/src/core.rs:205-234 | core/services/dropbox/src/core.rs:242-265 | core/services/dropbox/src/core.rs:271-290 | core/services/dropbox/src/core.rs:297-317 | core/services/dropbox/src/core.rs:324-344 — 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) core/services/gridfs/src/backend.rs:224 — core/services/gridfs/src/backend.rs:224-238 | core/services/mongodb/src/backend.rs:239-253 | core/services/mysql/src/backend.rs:220-234 | core/services/postgresql/src/backend.rs:212-229 | core/services/redis/src/backend.rs:347-361 | core/services/surrealdb/src/backend.rs:266-280 — 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) core/services/webhdfs/src/core.rs:59 — core/services/webhdfs/src/core.rs:59-83 | core/services/webhdfs/src/core.rs:93-148 | core/services/webhdfs/src/core.rs:289-307 | core/services/webhdfs/src/core.rs:314-336 | core/services/webhdfs/src/core.rs:382-403 | core/services/webhdfs/src/core.rs:409-430 — 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 copies of one member (3 members, 33+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 33+ corresponding lines) core/services/http/src/core.rs:60 — core/services/http/src/core.rs:60-96 | core/services/http/src/core.rs:109-141 | core/services/webdav/src/core.rs:178-221 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 33+ corresponding lines) core/core/src/types/operator/operator.rs:1481 — core/core/src/types/operator/operator.rs:1481-1518 | core/core/src/types/operator/operator.rs:1527-1559 | core/core/src/types/operator/operator.rs:1671-1703 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 33+ corresponding lines) core/services/dashmap/src/writer.rs:50 — core/services/dashmap/src/writer.rs:50-83 | core/services/mini_moka/src/writer.rs:49-82 | core/services/moka/src/writer.rs:49-81 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×3
  • Edited copy of a member (35 corresponding lines) dev/src/generate/dotnet.rs:213 — dev/src/generate/dotnet.rs:213-249 | dev/src/generate/dotnet.rs:251-285 — 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.
  • Edited copy of a member (35 corresponding lines) core/services/upyun/src/core.rs:335 — core/services/upyun/src/core.rs:335-371 | core/services/upyun/src/core.rs:448-482 — 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.
  • Edited copy of a member (35 corresponding lines) dev/src/release/package.rs:344 — dev/src/release/package.rs:344-379 | dev/src/release/package.rs:487-521 — 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 copies of one member (3 members, 27+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 27+ corresponding lines) core/services/vercel-blob/src/core.rs:95 — core/services/vercel-blob/src/core.rs:95-122 | core/services/vercel-blob/src/core.rs:161-187 | core/services/vercel-blob/src/core.rs:194-225 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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, 27+ corresponding lines) core/services/vercel-blob/src/core.rs:324 — core/services/vercel-blob/src/core.rs:324-351 | core/services/vercel-blob/src/core.rs:361-387 | core/services/vercel-blob/src/core.rs:395-421 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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, 27+ corresponding lines) bindings/dotnet/OpenDAL/OperatorInputStream.cs:145 — bindings/dotnet/OpenDAL/OperatorInputStream.cs:145-177 | bindings/dotnet/OpenDAL/OperatorOutputStream.cs:173-199 | bindings/dotnet/OpenDAL/OperatorOutputStream.cs:206-245 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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 (20 corresponding lines) · ×3
  • Edited copy of a member (20 corresponding lines) core/services/s3/src/writer.rs:51 — core/services/s3/src/writer.rs:51-70 | core/services/tos/src/writer.rs:49-68 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) core/services/vercel-blob/src/backend.rs:163 — core/services/vercel-blob/src/backend.rs:163-182 | core/services/yandex-disk/src/backend.rs:237-256 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) .github/scripts/release_rust/plan.py:152 — .github/scripts/release_rust/plan.py:152-174 | .github/scripts/release_rust/publish.py:261-280 — 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 copies of one member (3 members, 24+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 24+ corresponding lines) bindings/dotnet/src/operator.rs:601 — bindings/dotnet/src/operator.rs:601-624 | bindings/dotnet/src/operator.rs:811-836 | bindings/dotnet/src/operator.rs:2042-2065 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) core/services/azfile/src/core.rs:105 — core/services/azfile/src/core.rs:105-128 | core/services/azfile/src/core.rs:189-219 | core/services/azfile/src/core.rs:333-356 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 24+ corresponding lines) core/services/cos/src/backend.rs:410 — core/services/cos/src/backend.rs:410-433 | core/services/oss/src/backend.rs:738-762 | core/services/s3/src/backend.rs:1399-1428 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 18+ corresponding lines) core/services/azblob/src/core.rs:1259 — core/services/azblob/src/core.rs:1259-1276 | core/services/azdls/src/core.rs:765-782 | core/services/azfile/src/core.rs:518-535 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) core/services/d1/src/core.rs:84 — core/services/d1/src/core.rs:84-111 | core/services/d1/src/core.rs:113-135 | core/services/d1/src/core.rs:162-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 18+ corresponding lines) bindings/go/copier.go:139 — bindings/go/copier.go:139-158 | bindings/go/copier.go:163-182 | bindings/go/writer.go:418-435 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 12+ corresponding lines) core/services/ipmfs/src/writer.rs:40 — core/services/ipmfs/src/writer.rs:40-52 | core/services/seafile/src/writer.rs:48-59 | core/services/upyun/src/writer.rs:123-138 | core/services/yandex-disk/src/writer.rs:42-55 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) core/services/azfile/src/backend.rs:432 — core/services/azfile/src/backend.rs:432-443 | core/services/dbfs/src/backend.rs:258-272 | core/services/upyun/src/backend.rs:323-335 | core/services/yandex-disk/src/backend.rs:167-181 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 12+ corresponding lines) core/core/src/types/operator/operator.rs:1199 — core/core/src/types/operator/operator.rs:1199-1213 | core/core/src/types/operator/operator.rs:1377-1388 | core/core/src/types/operator/operator.rs:1395-1406 | core/core/src/types/operator/operator.rs:1613-1624 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 6+ corresponding lines) core/layers/logging/src/lib.rs:350 — core/layers/logging/src/lib.rs:350-355 | core/layers/logging/src/lib.rs:425-430 | core/layers/logging/src/lib.rs:462-467 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) bindings/python/src/layers/capability_override.rs:47 — bindings/python/src/layers/capability_override.rs:47-55 | bindings/python/src/layers/concurrent_limit.rs:54-60 | bindings/python/src/layers/mime_guess.rs:54-59 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) core/services/etcd/src/core.rs:54 — core/services/etcd/src/core.rs:54-59 | core/services/memcached/src/core.rs:216-221 | core/services/sftp/src/core.rs:155-160 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 4) · ×3
  • Duplicated block (21 lines × 4) core/services/cos/src/backend.rs:606 — core/services/cos/src/backend.rs:606-626 | core/services/gcs/src/backend.rs:618-638 | core/services/obs/src/backend.rs:461-481 | core/services/oss/src/backend.rs:840-860 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/gcs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/backend.rs:606` 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 first that the copies are not typed on the same thing: the declarations holding them bind `args` to `OpCompose` in one and `OpList` 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 (21 lines × 4) core/services/cos/src/writer.rs:144 — core/services/cos/src/writer.rs:144-164 | core/services/obs/src/writer.rs:141-161 | core/services/oss/src/writer.rs:141-161 | core/services/tos/src/writer.rs:134-154 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:144` 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 (21 lines × 4) core/services/gcs/src/core.rs:227 — core/services/gcs/src/core.rs:227-247 | core/services/gcs/src/core.rs:623-643 | core/services/s3/src/core.rs:476-496 | core/services/s3/src/core.rs:552-572 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/s3/src/core.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `OpStat` 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 · Duplicated block (18–19 lines × 2) · ×3
  • Duplicated block (18–19 lines × 2) core/core/src/layers/simulate.rs:579 — core/core/src/layers/simulate.rs:579-596 | core/core/src/raw/oio/list/flat_list.rs:176-194 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/core/src/layers/simulate.rs:579` 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–19 lines × 2) core/services/s3/src/copier.rs:204 — core/services/s3/src/copier.rs:204-222 | core/services/s3/src/copier.rs:371-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/s3/src/copier.rs:204` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/s3/src/copier.rs:223` calls `is_empty`, `last_modified`, `parse` and `core/services/s3/src/copier.rs:389` 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 (18–19 lines × 2) core/services/azfile/src/core.rs:226 — core/services/azfile/src/core.rs:226-243 | core/services/azfile/src/core.rs:250-268 — both copies are in the same file, so extract the 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×3
  • Duplicated block (15–16 lines × 2) core/layers/foyer/src/lib.rs:298 — core/layers/foyer/src/lib.rs:298-312 | core/layers/route/src/lib.rs:206-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (15–16 lines × 2) core/services/gcs-grpc/src/writer.rs:148 — core/services/gcs-grpc/src/writer.rs:148-162 | core/services/gcs-grpc/src/writer.rs:258-273 — both copies are in the same file, so extract the 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 `core/services/gcs-grpc/src/writer.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 (15–16 lines × 2) core/services/s3/src/core.rs:436 — core/services/s3/src/core.rs:436-451 | core/services/s3/src/core.rs:1009-1023 — both copies are in the same file, so extract the 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×3
  • Duplicated block (15 lines × 4) bindings/dotnet/src/operator.rs:719 — bindings/dotnet/src/operator.rs:719-733 | bindings/dotnet/src/operator.rs:1649-1663 | bindings/dotnet/src/operator.rs:1780-1794 | bindings/dotnet/src/operator.rs:1971-1985 — 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 `bindings/dotnet/src/operator.rs:719` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) bindings/dotnet/src/operator.rs:877 — bindings/dotnet/src/operator.rs:877-891 | bindings/dotnet/src/operator.rs:932-946 | bindings/dotnet/src/operator.rs:987-1001 | bindings/dotnet/src/operator.rs:1042-1056 — 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 `bindings/dotnet/src/operator.rs:877` 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 × 4) REDACTED:152 — REDACTED:152-166 | REDACTED:190-204 | REDACTED:228-242 | REDACTED:266-280 — 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 `REDACTED:152` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×3
  • Duplicated block (13–14 lines × 2) core/services/cos/src/core.rs:300 — core/services/cos/src/core.rs:300-312 | core/services/oss/src/core.rs:391-404 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.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 (13–14 lines × 2) core/services/cos/src/writer.rs:252 — core/services/cos/src/writer.rs:252-265 | core/services/oss/src/writer.rs:244-256 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/oss/src/writer.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:252` 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–14 lines × 2) core/services/dashmap/src/writer.rs:53 — core/services/dashmap/src/writer.rs:53-65 | core/services/mini_moka/src/writer.rs:52-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×3
  • Duplicated block (13 lines × 5) bindings/python/src/file.rs:98 — bindings/python/src/file.rs:98-110 | bindings/python/src/file.rs:146-158 | bindings/python/src/file.rs:187-199 | bindings/python/src/file.rs:292-304 | bindings/python/src/file.rs:324-336 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (13 lines × 5) core/services/ghac/src/core.rs:576 — core/services/ghac/src/core.rs:576-588 | core/services/http/src/core.rs:188-200 | core/services/ipfs/src/core.rs:289-301 | core/services/onedrive/src/core.rs:1056-1068 | core/services/vercel-artifacts/src/core.rs:162-174 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/ghac/src/core.rs:576` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/ghac/src/core.rs:575` calls `to_bytes` and `core/services/http/src/core.rs:186` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 5) core/services/github/src/core.rs:458 — core/services/github/src/core.rs:458-470 | core/services/seafile/src/core.rs:575-587 | core/services/upyun/src/core.rs:634-646 | core/services/vercel-blob/src/core.rs:528-540 | core/services/yandex-disk/src/core.rs:437-449 — before extracting anything, compare `core/services/seafile/src/core.rs` and `core/services/vercel-blob/src/core.rs` as WHOLE FILES: this scan already matched 3 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 `core/services/github/src/core.rs:458` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–13 lines × 3) · ×3
  • Duplicated block (11–13 lines × 3) core/services/azblob/src/core.rs:244 — core/services/azblob/src/core.rs:244-256 | core/services/s3/src/core.rs:512-522 | core/services/s3/src/core.rs:590-602 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/core.rs:244` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11–13 lines × 3) core/services/cloudflare-kv/src/reader.rs:136 — core/services/cloudflare-kv/src/reader.rs:136-146 | core/services/etcd/src/reader.rs:45-56 | core/services/foyer/src/reader.rs:47-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cloudflare-kv/src/reader.rs:136` 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–13 lines × 3) core/services/foundationdb/src/backend.rs:152 — core/services/foundationdb/src/backend.rs:152-164 | core/services/memcached/src/backend.rs:290-300 | core/services/tikv/src/backend.rs:175-185 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/memcached/src/backend.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/foundationdb/src/backend.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. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×3
  • Duplicated block (12–13 lines × 2) core/services/alluxio/src/core.rs:113 — core/services/alluxio/src/core.rs:113-125 | core/services/alluxio/src/core.rs:146-157 — both copies are in the same file, so extract the 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 `core/services/alluxio/src/core.rs:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) core/services/cos/src/core.rs:491 — core/services/cos/src/core.rs:491-502 | core/services/s3/src/core.rs:1211-1223 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–13 lines × 2) core/services/cos/src/writer.rs:84 — core/services/cos/src/writer.rs:84-96 | core/services/oss/src/writer.rs:74-85 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/oss/src/writer.rs` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 129 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:84` 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×3
  • Duplicated block (10–11 lines × 2) core/layers/retry/src/lib.rs:948 — core/layers/retry/src/lib.rs:948-957 | core/layers/retry/src/lib.rs:979-989 — both copies are in the same file, so extract the 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 `core/layers/retry/src/lib.rs:948` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (10–11 lines × 2) core/services/azblob/src/core.rs:306 — core/services/azblob/src/core.rs:306-315 | core/services/azblob/src/core.rs:614-624 — both copies are in the same file, so extract the 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–11 lines × 2) core/services/cos/src/core.rs:267 — core/services/cos/src/core.rs:267-276 | core/services/obs/src/core.rs:229-239 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×3
  • Duplicated block (8–9 lines × 3) core/services/alluxio/src/core.rs:145 — core/services/alluxio/src/core.rs:145-152 | core/services/alluxio/src/core.rs:237-245 | core/services/alluxio/src/core.rs:274-282 — 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 `core/services/alluxio/src/core.rs:145` 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–9 lines × 3) core/services/cos/src/backend.rs:442 — core/services/cos/src/backend.rs:442-449 | core/services/oss/src/backend.rs:771-778 | core/services/swift/src/backend.rs:381-389 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/oss/src/backend.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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/backend.rs:442` 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–9 lines × 3) core/services/gcs/src/core.rs:191 — core/services/gcs/src/core.rs:191-198 | core/services/gcs/src/core.rs:252-259 | core/services/http/src/core.rs:65-73 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/core.rs:260` calls `Some`, `if_version_match`, `header` and `core/services/http/src/core.rs:75` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×3
  • Duplicated block (7 lines × 5) core/services/cos/src/core.rs:410 — core/services/cos/src/core.rs:410-416 | core/services/cos/src/core.rs:602-609 | core/services/obs/src/core.rs:347-353 | core/services/oss/src/core.rs:580-587 | core/services/s3/src/core.rs:903-909 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:410` 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 × 5) core/services/pcloud/src/core.rs:83 — core/services/pcloud/src/core.rs:83-91 | core/services/seafile/src/core.rs:338-346 | core/services/seafile/src/core.rs:374-382 | core/services/yandex-disk/src/core.rs:89-95 | core/services/yandex-disk/src/core.rs:144-150 — before extracting anything, compare `core/services/pcloud/src/core.rs` and `core/services/seafile/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/pcloud/src/core.rs:83` 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 × 5) core/services/gdrive/src/backend.rs:323 — core/services/gdrive/src/backend.rs:323-329 | core/services/gdrive/src/backend.rs:428-434 | core/services/gdrive/src/backend.rs:464-471 | core/services/gdrive/src/backend.rs:540-546 | core/services/gdrive/src/backend.rs:608-614 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gdrive/src/backend.rs:323` 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.
D4 · Code Duplication · Duplicated block (6 lines × 9) · ×3
  • Duplicated block (6 lines × 9) core/services/aliyun-drive/src/backend.rs:259 — core/services/aliyun-drive/src/backend.rs:259-265 | core/services/koofr/src/backend.rs:305-311 | core/services/lakefs/src/backend.rs:306-312 | core/services/obs/src/backend.rs:406-411 | core/services/onedrive/src/backend.rs:307-313 | core/services/pcloud/src/backend.rs:286-292 | core/services/upyun/src/backend.rs:288-294 | core/services/vercel-blob/src/backend.rs:218-224 | core/services/yandex-disk/src/backend.rs:191-197 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/backend.rs:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `OpList` in one and `OpWrite` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/koofr/src/backend.rs:304` calls `clone` and `core/services/aliyun-drive/src/backend.rs:258` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 9) core/services/koofr/src/backend.rs:304 — core/services/koofr/src/backend.rs:304-309 | core/services/lakefs/src/backend.rs:305-310 | core/services/obs/src/backend.rs:405-410 | core/services/onedrive/src/backend.rs:306-311 | core/services/pcloud/src/backend.rs:285-290 | core/services/upyun/src/backend.rs:287-292 | core/services/vercel-blob/src/backend.rs:217-222 | core/services/webdav/src/backend.rs:347-352 | core/services/yandex-disk/src/backend.rs:190-195 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/lakefs/src/backend.rs` as WHOLE FILES: this scan already matched 5 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `OpList` in one and `OpWrite` 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 (6 lines × 9) core/services/azblob/src/backend.rs:116 — core/services/azblob/src/backend.rs:116-123 | core/services/azdls/src/backend.rs:111-118 | core/services/azfile/src/backend.rs:93-100 | core/services/cos/src/backend.rs:83-89 | core/services/ipfs/src/backend.rs:78-85 | core/services/obs/src/backend.rs:84-90 | core/services/tos/src/backend.rs:85-90 | core/services/vercel-artifacts/src/backend.rs:62-67 | core/services/webhdfs/src/backend.rs:79-85 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×3
  • Duplicated block (6 lines × 4) core/services/http/src/core.rs:170 — core/services/http/src/core.rs:170-175 | core/services/ipfs/src/core.rs:274-279 | core/services/obs/src/core.rs:707-712 | core/services/vercel-artifacts/src/core.rs:149-154 — before extracting anything, compare `core/services/http/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 5 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 `core/services/http/src/core.rs:170` 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) core/services/koofr/src/core.rs:522 — core/services/koofr/src/core.rs:522-527 | core/services/seafile/src/core.rs:561-566 | core/services/upyun/src/core.rs:618-623 | core/services/vercel-blob/src/core.rs:516-521 — before extracting anything, compare `core/services/seafile/src/core.rs` and `core/services/vercel-blob/src/core.rs` as WHOLE FILES: this scan already matched 3 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 `core/services/koofr/src/core.rs:522` 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) core/services/azblob/src/core.rs:275 — core/services/azblob/src/core.rs:275-280 | core/services/cos/src/core.rs:122-127 | core/services/gcs/src/core.rs:290-295 | core/services/obs/src/core.rs:117-123 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/core.rs:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
R4 · Test Coverage · No test reaches this file · ×3
  • No test reaches this file bindings/nodejs/index.cjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bindings/nodejs/scripts/header.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bindings/nodejs/theme/index.tsx:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D2 · Cognitive Complexity · opendal_service_webdav · ×2
  • opendal_service_webdav::core::parse_user_metadata_from_xml (cognitive 54) core/services/webdav/src/core.rs:610 — opendal_service_webdav::core::parse_user_metadata_from_xml has cognitive complexity 54 (threshold 15). Drivers by points: if/else 10 (39 pts), loops 3 (7 pts), match/switch 2 (5 pts), boolean chains 3 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • opendal_service_webdav::core::check_proppatch_response (cognitive 16) core/services/webdav/src/core.rs:725 — opendal_service_webdav::core::check_proppatch_response has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · S3Builder · ×2
  • S3Builder::build (cognitive 50) core/services/s3/src/backend.rs:931 — S3Builder::build has cognitive complexity 50 (threshold 15). Drivers by points: if/else 36 (40 pts), match/switch 8, boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • S3Builder::resolve_s3_express_config (cognitive 16) core/services/s3/src/backend.rs:667 — S3Builder::resolve_s3_express_config has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · GdriveFlatLister · ×2
  • GdriveFlatLister::initialize (cognitive 47) core/services/gdrive/src/lister.rs:400 — GdriveFlatLister::initialize has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (26 pts), match/switch 9 (19 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • GdriveFlatLister::process_batch (cognitive 18) core/services/gdrive/src/lister.rs:613 — GdriveFlatLister::process_batch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GdriveBackend · ×2
  • GdriveBackend::rename (cognitive 33) core/services/gdrive/src/backend.rs:499 — GdriveBackend::rename has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (32 pts), match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • GdriveBackend::copy (cognitive 17) core/services/gdrive/src/backend.rs:399 — GdriveBackend::copy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (3 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · OssBuilder · ×2
  • OssBuilder::build (cognitive 28) core/services/oss/src/backend.rs:412 — OssBuilder::build has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (23 pts), match/switch 3, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • OssBuilder::parse_endpoint (cognitive 21) core/services/oss/src/backend.rs:191 — OssBuilder::parse_endpoint has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 5 (10 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · S3Copier · ×2
  • S3Copier::copy_once (cognitive 19) core/services/s3/src/copier.rs:174 — S3Copier::copy_once has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • S3Copier::complete_copy (cognitive 17) core/services/s3/src/copier.rs:337 — S3Copier::complete_copy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (13 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (13 members, 50+ identical tokens) bindings/haskell/src/lib.rs:153 — bindings/haskell/src/lib.rs:153-177 | bindings/haskell/src/lib.rs:199-228 | bindings/haskell/src/lib.rs:245-269 | bindings/haskell/src/lib.rs:286-310 | bindings/haskell/src/lib.rs:329-361 | bindings/haskell/src/lib.rs:380-412 | bindings/haskell/src/lib.rs:429-453 | bindings/haskell/src/lib.rs:470-494 | bindings/haskell/src/lib.rs:511-535 | bindings/haskell/src/lib.rs:552-582 | bindings/haskell/src/lib.rs:691-724 | bindings/haskell/src/lib.rs:743-767 | bindings/haskell/src/lib.rs:786-816 — These 13 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 13 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 13 times.
  • Members sharing a duplicated core (13 members, 50+ identical tokens) core/services/d1/src/reader.rs:40 — core/services/d1/src/reader.rs:40-59 | core/services/foundationdb/src/reader.rs:38-60 | core/services/gridfs/src/reader.rs:38-57 | core/services/memcached/src/reader.rs:38-55 | core/services/mongodb/src/reader.rs:38-57 | core/services/mysql/src/reader.rs:39-56 | core/services/persy/src/reader.rs:38-57 | core/services/postgresql/src/reader.rs:38-60 | core/services/redb/src/reader.rs:38-57 | core/services/rocksdb/src/reader.rs:38-57 | core/services/sled/src/reader.rs:38-57 | core/services/surrealdb/src/reader.rs:38-57 | core/services/tikv/src/reader.rs:39-56 — These 13 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 13 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 13 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (8 members, 50+ identical tokens) bindings/c/src/presign.rs:128 — bindings/c/src/presign.rs:128-137 | bindings/c/src/presign.rs:152-166 | bindings/c/src/presign.rs:180-189 | bindings/c/src/presign.rs:204-218 | bindings/c/src/presign.rs:232-240 | bindings/c/src/presign.rs:255-285 | bindings/c/src/presign.rs:299-308 | bindings/c/src/presign.rs:323-337 — These 8 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 8 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 8 times.
  • Members sharing a duplicated core (8 members, 50+ identical tokens) core/services/compfs/src/config.rs:35 — core/services/compfs/src/config.rs:35-45 | core/services/dashmap/src/config.rs:37-47 | core/services/dropbox/src/config.rs:53-63 | core/services/gdrive/src/config.rs:59-69 | core/services/mini_moka/src/config.rs:52-62 | core/services/monoiofs/src/config.rs:40-50 | core/services/vercel-blob/src/config.rs:49-59 | core/services/yandex-disk/src/config.rs:49-59 — These 8 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 8 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 8 times.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×2
  • Edited copy of a member (52 corresponding lines) core/services/redis/src/reader.rs:38 — core/services/redis/src/reader.rs:38-90 | core/services/sqlite/src/reader.rs:39-90 — 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.
  • Edited copy of a member (52 corresponding lines) core/services/s3/src/copier.rs:276 — core/services/s3/src/copier.rs:276-335 | core/services/s3/src/writer.rs:192-243 — 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 (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) core/services/b2/src/core.rs:881 — core/services/b2/src/core.rs:881-914 | core/services/s3/src/core.rs:2211-2252 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) core/core/src/raw/http_util/multipart.rs:210 — core/core/src/raw/http_util/multipart.rs:210-243 | core/core/src/raw/http_util/multipart.rs:588-623 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (42 corresponding lines) · ×2
  • Edited copy of a member (42 corresponding lines) core/services/cos/src/backend.rs:441 — core/services/cos/src/backend.rs:441-482 | core/services/swift/src/backend.rs:380-425 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (42 corresponding lines) core/services/swift/src/core.rs:240 — core/services/swift/src/core.rs:240-281 | core/services/tos/src/core.rs:773-821 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) core/services/s3/src/core.rs:1254 — core/services/s3/src/core.rs:1254-1297 | core/services/s3/src/core.rs:1306-1345 — 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.
  • Edited copy of a member (40 corresponding lines) core/services/github/src/core.rs:283 — core/services/github/src/core.rs:283-322 | core/services/seafile/src/core.rs:435-478 — 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 (38 corresponding lines) · ×2
  • Edited copy of a member (38 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs:183 — core/core/src/raw/oio/copy/block_copy.rs:183-220 | core/core/src/raw/oio/copy/multipart_copy.rs:252-289 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (38 corresponding lines) core/core/src/layers/correctness_check.rs:73 — core/core/src/layers/correctness_check.rs:73-110 | core/core/src/layers/correctness_check.rs:121-162 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 24+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 24+ corresponding lines) core/services/aliyun-drive/src/reader.rs:50 — core/services/aliyun-drive/src/reader.rs:50-78 | core/services/dropbox/src/reader.rs:50-76 | core/services/pcloud/src/reader.rs:48-73 | core/services/seafile/src/reader.rs:48-71 | core/services/upyun/src/reader.rs:43-66 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 24+ corresponding lines) core/layers/logging/src/lib.rs:579 — core/layers/logging/src/lib.rs:579-606 | core/layers/logging/src/lib.rs:686-709 | core/layers/logging/src/lib.rs:711-734 | core/layers/logging/src/lib.rs:898-933 | core/layers/logging/src/lib.rs:939-970 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×2
  • Edited copy of a member (37 corresponding lines) core/services/s3/src/core.rs:640 — core/services/s3/src/core.rs:640-676 | core/services/s3/src/core.rs:685-727 — 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.
  • Edited copy of a member (37 corresponding lines) core/services/dropbox/src/backend.rs:240 — core/services/dropbox/src/backend.rs:240-281 | core/services/ipmfs/src/backend.rs:198-234 — 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 copies of one member (3 members, 31+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 31+ corresponding lines) core/layers/dtrace/src/lib.rs:307 — core/layers/dtrace/src/lib.rs:307-337 | core/layers/dtrace/src/lib.rs:341-378 | core/layers/dtrace/src/lib.rs:380-410 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 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, 31+ corresponding lines) core/services/s3/src/core.rs:208 — core/services/s3/src/core.rs:208-238 | core/services/s3/src/core.rs:245-275 | core/services/s3/src/core.rs:281-312 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 22+ corresponding lines) core/services/dbfs/src/core.rs:54 — core/services/dbfs/src/core.rs:54-77 | core/services/dbfs/src/core.rs:83-109 | core/services/dbfs/src/core.rs:116-140 | core/services/dbfs/src/core.rs:166-187 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 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, 22+ corresponding lines) core/services/koofr/src/core.rs:242 — core/services/koofr/src/core.rs:242-263 | core/services/koofr/src/core.rs:270-293 | core/services/koofr/src/core.rs:340-363 | core/services/koofr/src/core.rs:443-466 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 20+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 20+ corresponding lines) core/services/b2/src/writer.rs:71 — core/services/b2/src/writer.rs:71-95 | core/services/dropbox/src/writer.rs:73-92 | core/services/koofr/src/writer.rs:62-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) core/services/cos/src/backend.rs:336 — core/services/cos/src/backend.rs:336-365 | core/services/oss/src/backend.rs:668-693 | core/services/swift/src/backend.rs:264-283 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 22+ corresponding lines) core/services/vercel-artifacts/src/core.rs:49 — core/services/vercel-artifacts/src/core.rs:49-73 | core/services/vercel-artifacts/src/core.rs:81-103 | core/services/vercel-artifacts/src/core.rs:109-130 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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, 22+ corresponding lines) core/services/mysql/src/core.rs:45 — core/services/mysql/src/core.rs:45-68 | core/services/postgresql/src/core.rs:45-66 | core/services/sqlite/src/core.rs:48-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 14+ corresponding lines) core/layers/logging/src/lib.rs:300 — core/layers/logging/src/lib.rs:300-323 | core/layers/logging/src/lib.rs:325-348 | core/layers/logging/src/lib.rs:357-370 | core/layers/logging/src/lib.rs:378-401 | core/layers/logging/src/lib.rs:432-455 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 14+ corresponding lines) core/services/mysql/src/core.rs:92 — core/services/mysql/src/core.rs:92-107 | core/services/mysql/src/core.rs:109-122 | core/services/postgresql/src/core.rs:111-124 | core/services/sqlite/src/core.rs:169-183 | core/services/sqlite/src/core.rs:185-198 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 21+ corresponding lines) core/services/mysql/src/core.rs:70 — core/services/mysql/src/core.rs:70-90 | core/services/postgresql/src/core.rs:68-88 | core/services/sqlite/src/core.rs:72-92 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 21+ corresponding lines) core/services/upyun/src/core.rs:122 — core/services/upyun/src/core.rs:122-143 | core/services/upyun/src/core.rs:145-165 | core/services/upyun/src/core.rs:212-232 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 13+ corresponding lines) core/layers/dtrace/src/lib.rs:414 — core/layers/dtrace/src/lib.rs:414-426 | core/layers/dtrace/src/lib.rs:428-440 | core/layers/dtrace/src/lib.rs:442-454 | core/layers/dtrace/src/lib.rs:456-468 — 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.
  • Edited copies of one member (4 members, 13+ corresponding lines) core/core/src/types/operator/operator.rs:1227 — core/core/src/types/operator/operator.rs:1227-1240 | core/core/src/types/operator/operator.rs:1442-1454 | core/core/src/types/operator/operator.rs:1462-1474 | core/core/src/types/operator/operator.rs:1652-1664 — 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 (8 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (8 members, 13+ corresponding lines) bindings/java/src/async_operator.rs:127 — bindings/java/src/async_operator.rs:127-144 | bindings/java/src/async_operator.rs:168-181 | bindings/java/src/async_operator.rs:245-260 | bindings/java/src/async_operator.rs:328-343 | bindings/java/src/async_operator.rs:367-383 | bindings/java/src/async_operator.rs:407-423 | bindings/java/src/async_operator.rs:445-460 | bindings/java/src/async_operator.rs:484-496 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
  • Edited copies of one member (8 members, 13+ corresponding lines) core/services/cos/src/writer.rs:202 — core/services/cos/src/writer.rs:202-216 | core/services/gcs/src/writer.rs:180-193 | core/services/obs/src/writer.rs:199-213 | core/services/oss/src/writer.rs:196-209 | core/services/s3/src/copier.rs:412-424 | core/services/s3/src/writer.rs:327-340 | core/services/tos/src/copier.rs:257-269 | core/services/tos/src/writer.rs:204-217 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 8+ corresponding lines) core/services/memcached/src/core.rs:65 — core/services/memcached/src/core.rs:65-72 | core/services/memcached/src/core.rs:80-87 | core/services/memcached/src/core.rs:89-96 | core/services/memcached/src/core.rs:98-105 — 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.
  • Edited copies of one member (4 members, 8+ corresponding lines) bindings/c/src/copier.rs:119 — bindings/c/src/copier.rs:119-128 | bindings/c/src/operator.rs:78-85 | bindings/c/src/operator_info.rs:214-221 | bindings/c/src/reader.rs:125-134 — 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 (3 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 10+ corresponding lines) core/services/aliyun-drive/src/core.rs:360 — core/services/aliyun-drive/src/core.rs:360-369 | core/services/seafile/src/core.rs:307-320 | core/services/yandex-disk/src/core.rs:169-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) core/services/azblob/src/core.rs:154 — core/services/azblob/src/core.rs:154-167 | core/services/cos/src/core.rs:78-87 | core/services/oss/src/core.rs:103-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (6 members, 9+ corresponding lines) core/core/src/layers/error_context.rs:102 — core/core/src/layers/error_context.rs:102-111 | core/core/src/layers/error_context.rs:113-122 | core/core/src/layers/error_context.rs:130-140 | core/core/src/layers/error_context.rs:142-151 | core/core/src/layers/error_context.rs:189-197 | core/core/src/layers/error_context.rs:199-208 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
  • Edited copies of one member (6 members, 9+ corresponding lines) core/services/dashmap/src/backend.rs:192 — core/services/dashmap/src/backend.rs:192-200 | core/services/mini_moka/src/backend.rs:278-289 | core/services/moka/src/backend.rs:338-348 | core/services/mysql/src/backend.rs:267-276 | core/services/rocksdb/src/backend.rs:194-202 | core/services/sled/src/backend.rs:218-226 — 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 (3 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 8+ corresponding lines) core/layers/foyer/src/lib.rs:100 — core/layers/foyer/src/lib.rs:100-108 | core/layers/foyer/src/lib.rs:136-143 | core/services/foyer/src/lib.rs:103-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) core/core/src/layers/error_context.rs:398 — core/core/src/layers/error_context.rs:398-411 | core/core/src/layers/error_context.rs:413-420 | core/core/src/layers/error_context.rs:422-429 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 9+ corresponding lines) core/core/src/blocking/read/reader.rs:78 — core/core/src/blocking/read/reader.rs:78-86 | core/core/src/blocking/read/reader.rs:91-100 | core/core/src/blocking/read/reader.rs:104-112 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) core/services/git/src/config.rs:83 — core/services/git/src/config.rs:83-92 | core/services/git/src/core.rs:84-93 | core/services/memcached/src/config.rs:59-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 8+ corresponding lines) core/services/dbfs/src/backend.rs:242 — core/services/dbfs/src/backend.rs:242-250 | core/services/github/src/backend.rs:264-271 | core/services/upyun/src/backend.rs:271-278 | core/services/vercel-blob/src/backend.rs:247-254 | core/services/yandex-disk/src/backend.rs:281-288 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) core/services/d1/src/config.rs:49 — core/services/d1/src/config.rs:49-56 | core/services/mongodb/src/config.rs:45-53 | core/services/mongodb/src/core.rs:40-47 | core/services/mysql/src/config.rs:54-61 | core/services/postgresql/src/config.rs:54-61 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 7+ corresponding lines) core/services/pcloud/src/config.rs:44 — core/services/pcloud/src/config.rs:44-50 | core/services/pcloud/src/core.rs:45-51 | core/services/seafile/src/config.rs:48-55 | core/services/seafile/src/core.rs:54-61 — 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) bindings/dotnet/OpenDAL/Layer/CapabilityOverrideLayer.cs:50 — bindings/dotnet/OpenDAL/Layer/CapabilityOverrideLayer.cs:50-56 | bindings/dotnet/OpenDAL/Layer/ConcurrentLimitLayer.cs:73-83 | bindings/dotnet/OpenDAL/Layer/MimeGuessLayer.cs:40-46 | bindings/dotnet/OpenDAL/Layer/ThrottleLayer.cs:75-81 — 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 (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) core/layers/foyer/src/lib.rs:94 — core/layers/foyer/src/lib.rs:94-98 | core/services/foyer/src/lib.rs:54-59 — 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) core/layers/concurrent-limit/src/lib.rs:296 — core/layers/concurrent-limit/src/lib.rs:296-300 | core/layers/tail-cut/src/lib.rs:420-424 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×2
  • Duplicated block (41 lines × 2) core/services/cloudflare-kv/src/backend.rs:328 — core/services/cloudflare-kv/src/backend.rs:328-368 | core/services/cloudflare-kv/src/reader.rs:93-133 — 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. 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 (41 lines × 2) core/services/tos/src/core.rs:235 — core/services/tos/src/core.rs:235-275 | core/services/tos/src/core.rs:355-395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2
  • Duplicated block (28 lines × 2) core/services/azdls/src/core.rs:885 — core/services/azdls/src/core.rs:885-912 | core/services/azfile/src/core.rs:621-648 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azdls/src/core.rs:885` 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 (28 lines × 2) core/services/cos/src/lister.rs:66 — core/services/cos/src/lister.rs:66-93 | core/services/obs/src/lister.rs:63-90 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:66` 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.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×2
  • Duplicated block (27 lines × 2) core/services/s3/src/core.rs:650 — core/services/s3/src/core.rs:650-676 | core/services/s3/src/core.rs:701-727 — both copies are in the same file, so extract the 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 `core/services/s3/src/core.rs:650` 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 (27 lines × 2) core/core/src/raw/oio/copy/block_copy.rs:279 — core/core/src/raw/oio/copy/block_copy.rs:279-305 | core/core/src/raw/oio/copy/multipart_copy.rs:352-378 — before extracting anything, compare `core/core/src/raw/oio/copy/block_copy.rs` and `core/core/src/raw/oio/copy/multipart_copy.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. 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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) core/layers/retry/src/lib.rs:1009 — core/layers/retry/src/lib.rs:1009-1028 | core/layers/retry/src/lib.rs:1040-1059 | core/layers/retry/src/lib.rs:1071-1090 — 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 `core/layers/retry/src/lib.rs:1009` 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 lines × 3) core/services/cos/src/writer.rs:224 — core/services/cos/src/writer.rs:224-243 | core/services/obs/src/writer.rs:221-240 | core/services/oss/src/writer.rs:217-236 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:224` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–19 lines × 4) · ×2
  • Duplicated block (18–19 lines × 4) core/services/cos/src/lister.rs:198 — core/services/cos/src/lister.rs:198-215 | core/services/oss/src/lister.rs:201-218 | core/services/s3/src/lister.rs:354-371 | core/services/tos/src/lister.rs:190-208 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut PageContext` in one and `&mut oio::PageContext` 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 (18–19 lines × 4) core/services/cos/src/writer.rs:137 — core/services/cos/src/writer.rs:137-154 | core/services/obs/src/writer.rs:133-151 | core/services/oss/src/writer.rs:133-151 | core/services/s3/src/writer.rs:156-173 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×2
  • Duplicated block (16–18 lines × 2) core/services/dashmap/src/backend.rs:88 — core/services/dashmap/src/backend.rs:88-105 | core/services/moka/src/backend.rs:210-225 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/dashmap/src/backend.rs:88` 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 `core` to `DashmapCore` in one and `MokaCore` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/moka/src/backend.rs:226` calls `to_string` and `core/services/dashmap/src/backend.rs:106` 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 (16–18 lines × 2) dev/src/generate/dotnet.rs:234 — dev/src/generate/dotnet.rs:234-249 | dev/src/generate/dotnet.rs:268-285 — both copies are in the same file, so extract the 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 `dev/src/generate/dotnet.rs:234` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `dev/src/generate/dotnet.rs:232` calls `add_template` and `dev/src/generate/dotnet.rs:268` 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×2
  • Duplicated block (17–18 lines × 2) core/services/gcs-grpc/src/backend.rs:179 — core/services/gcs-grpc/src/backend.rs:179-195 | core/services/gcs/src/backend.rs:282-299 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/backend.rs:302` calls `no_env`, `no_well_known` and `core/services/gcs-grpc/src/backend.rs:196` 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 (17–18 lines × 2) core/services/postgresql/src/core.rs:46 — core/services/postgresql/src/core.rs:46-62 | core/services/sqlite/src/core.rs:49-66 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×2
  • Duplicated block (16–17 lines × 2) core/services/azblob/src/backend.rs:409 — core/services/azblob/src/backend.rs:409-424 | core/services/azdls/src/backend.rs:301-317 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/azdls/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azdls/src/backend.rs:301` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16–17 lines × 2) core/services/s3/src/copier.rs:295 — core/services/s3/src/copier.rs:295-311 | core/services/s3/src/writer.rs:213-228 — 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 `core/services/s3/src/copier.rs:295` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×2
  • Duplicated block (16 lines × 3) core/services/azblob/src/core.rs:1261 — core/services/azblob/src/core.rs:1261-1276 | core/services/azdls/src/core.rs:767-782 | core/services/azfile/src/core.rs:520-535 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:1261` 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 (16 lines × 3) core/services/mysql/src/core.rs:46 — core/services/mysql/src/core.rs:46-63 | core/services/postgresql/src/core.rs:46-61 | core/services/sqlite/src/core.rs:49-65 — before extracting anything, compare `core/services/postgresql/src/core.rs` and `core/services/sqlite/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×2
  • Duplicated block (15–16 lines × 3) core/services/cos/src/core.rs:403 — core/services/cos/src/core.rs:403-418 | core/services/obs/src/core.rs:341-355 | core/services/s3/src/core.rs:896-911 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–16 lines × 3) core/services/cos/src/writer.rs:102 — core/services/cos/src/writer.rs:102-117 | core/services/obs/src/writer.rs:93-107 | core/services/oss/src/writer.rs:91-106 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:102` 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×2
  • Duplicated block (15 lines × 3) bindings/python/src/file.rs:498 — bindings/python/src/file.rs:498-512 | bindings/python/src/file.rs:609-623 | bindings/python/src/file.rs:644-658 — 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 `bindings/python/src/file.rs:498` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 3) core/services/smb/src/backend.rs:293 — core/services/smb/src/backend.rs:293-307 | core/services/smb/src/copier.rs:59-73 | core/services/smb/src/copier.rs:107-121 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/smb/src/backend.rs:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×2
  • Duplicated block (12 lines × 3) core/core/src/raw/oio/write/block_write.rs:138 — core/core/src/raw/oio/write/block_write.rs:138-149 | core/core/src/raw/oio/write/multipart_write.rs:219-230 | core/core/src/raw/oio/write/position_write.rs:94-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/raw/oio/write/block_write.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/core/src/raw/oio/write/multipart_write.rs:233` calls `with_context`, `to_string` and `core/core/src/raw/oio/write/block_write.rs:152` 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) core/services/git/src/core.rs:278 — core/services/git/src/core.rs:278-289 | core/services/git/src/core.rs:338-349 | core/services/git/src/core.rs:378-389 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (11 lines × 13) · ×2
  • Duplicated block (11 lines × 13) bindings/haskell/src/lib.rs:154 — bindings/haskell/src/lib.rs:154-164 | bindings/haskell/src/lib.rs:200-210 | bindings/haskell/src/lib.rs:246-256 | bindings/haskell/src/lib.rs:287-297 | bindings/haskell/src/lib.rs:330-340 | bindings/haskell/src/lib.rs:381-391 | bindings/haskell/src/lib.rs:430-440 | bindings/haskell/src/lib.rs:471-481 | bindings/haskell/src/lib.rs:512-522 | bindings/haskell/src/lib.rs:553-563 | bindings/haskell/src/lib.rs:692-702 | bindings/haskell/src/lib.rs:744-754 | bindings/haskell/src/lib.rs:787-797 — all 13 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 `bindings/haskell/src/lib.rs:154` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 13) core/services/d1/src/reader.rs:49 — core/services/d1/src/reader.rs:49-59 | core/services/foundationdb/src/reader.rs:50-60 | core/services/gridfs/src/reader.rs:47-57 | core/services/memcached/src/reader.rs:45-55 | core/services/mongodb/src/reader.rs:47-57 | core/services/mysql/src/reader.rs:46-56 | core/services/persy/src/reader.rs:47-57 | core/services/postgresql/src/reader.rs:50-60 | core/services/redb/src/reader.rs:47-57 | core/services/rocksdb/src/reader.rs:47-57 | core/services/sled/src/reader.rs:47-57 | core/services/surrealdb/src/reader.rs:47-57 | core/services/tikv/src/reader.rs:46-56 — before extracting anything, compare `core/services/foundationdb/src/reader.rs` and `core/services/gridfs/src/reader.rs` as WHOLE FILES: 84% 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/d1/src/reader.rs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×2
  • Duplicated block (11 lines × 5) core/services/cloudflare-kv/src/core.rs:222 — core/services/cloudflare-kv/src/core.rs:222-232 | core/services/d1/src/core.rs:224-234 | core/services/dropbox/src/core.rs:575-585 | core/services/gdrive/src/core.rs:1173-1183 | core/services/tos/src/core.rs:1136-1146 — before extracting anything, compare `core/services/cloudflare-kv/src/core.rs` and `core/services/d1/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cloudflare-kv/src/core.rs:222` 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 × 5) core/core/src/services/memory/deleter.rs:31 — core/core/src/services/memory/deleter.rs:31-41 | core/services/persy/src/deleter.rs:31-41 | core/services/redb/src/deleter.rs:31-41 | core/services/rocksdb/src/deleter.rs:31-41 | core/services/sled/src/deleter.rs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/services/memory/deleter.rs:31` 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 first that the copies are not typed on the same thing: the declarations holding them bind `core` to `Arc<MemoryCore>` in one and `Arc<PersyCore>` 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 · Duplicated block (10–11 lines × 3) · ×2
  • Duplicated block (10–11 lines × 3) core/services/gcs/src/core.rs:1090 — core/services/gcs/src/core.rs:1090-1099 | core/services/obs/src/core.rs:479-489 | core/services/oss/src/core.rs:798-807 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gcs/src/core.rs:1090` 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–11 lines × 3) core/services/s3/src/core.rs:497 — core/services/s3/src/core.rs:497-506 | core/services/s3/src/core.rs:573-582 | core/services/s3/src/core.rs:746-756 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `OpStat` in one and `&OpDelete` 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 · Duplicated block (9–10 lines × 3) · ×2
  • Duplicated block (9–10 lines × 3) core/services/cos/src/writer.rs:82 — core/services/cos/src/writer.rs:82-91 | core/services/obs/src/writer.rs:74-82 | core/services/oss/src/writer.rs:72-80 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:82` 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 (9–10 lines × 3) core/services/gcs/src/core.rs:131 — core/services/gcs/src/core.rs:131-140 | core/services/oss/src/core.rs:124-133 | core/services/tos/src/core.rs:109-117 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/core.rs:148` calls `remove` and `core/services/oss/src/core.rs:135` 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×2
  • Duplicated block (8–10 lines × 2) core/core/src/raw/oio/write/block_write.rs:201 — core/core/src/raw/oio/write/block_write.rs:201-208 | core/core/src/raw/oio/write/multipart_write.rs:329-338 — 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 `core/core/src/raw/oio/write/block_write.rs:201` 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–10 lines × 2) core/services/webhdfs/src/core.rs:184 — core/services/webhdfs/src/core.rs:184-193 | core/services/webhdfs/src/core.rs:265-272 — both copies are in the same file, so extract the 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 `core/services/webhdfs/src/core.rs:184` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/webhdfs/src/core.rs:264` calls `percent_encode_path` and `core/services/webhdfs/src/core.rs:183` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×2
  • Duplicated block (8–9 lines × 4) core/services/azdls/src/core.rs:359 — core/services/azdls/src/core.rs:359-366 | core/services/cos/src/core.rs:265-273 | core/services/http/src/core.rs:114-122 | core/services/obs/src/core.rs:227-235 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–9 lines × 4) core/services/cos/src/core.rs:135 — core/services/cos/src/core.rs:135-142 | core/services/cos/src/core.rs:249-256 | core/services/cos/src/core.rs:290-297 | core/services/s3/src/core.rs:740-748 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/s3/src/core.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:135` 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 `args` to `&OpStat` in one and `&OpDelete` 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.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: OpenDAL (SwiftPM) — OpenDAL (SwiftPM): 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: opendal-core — opendal-core: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 97 project(s), so it's rigid to change.
D1 · Cyclomatic Complexity · S3Builder · ×1
  • S3Builder::build (cyclomatic 40) core/services/s3/src/backend.rs:931 — S3Builder::build has cyclomatic complexity 40 (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.
D1 · Cyclomatic Complexity · Storage.init (cyclomatic 32) · ×1
  • Storage.init (cyclomatic 32) bindings/dart/lib/opendal.dart:32 — Storage.init has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · opendal_service_webdav · ×1
  • opendal_service_webdav::core::parse_user_metadata_from_xml (cyclomatic 29) core/services/webdav/src/core.rs:610 — opendal_service_webdav::core::parse_user_metadata_from_xml has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GdriveFlatLister · ×1
  • GdriveFlatLister::initialize (cyclomatic 24) core/services/gdrive/src/lister.rs:400 — GdriveFlatLister::initialize has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CorrectnessService · ×1
  • CorrectnessService::compose (cyclomatic 22) core/core/src/layers/correctness_check.rs:339 — CorrectnessService::compose has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · OssBuilder · ×1
  • OssBuilder::build (cyclomatic 21) core/services/oss/src/backend.rs:412 — OssBuilder::build has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · ServicerFlatLister · ×1
  • ServicerFlatLister::next (cyclomatic 20) core/core/src/layers/simulate.rs:501 — ServicerFlatLister::next has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FlatLister · ×1
  • FlatLister::next (cyclomatic 20) core/core/src/raw/oio/list/flat_list.rs:89 — FlatLister::next has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CloudflareKvBackend · ×1
  • CloudflareKvBackend::stat (cyclomatic 20) core/services/cloudflare-kv/src/backend.rs:257 — CloudflareKvBackend::stat has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GdriveLister · ×1
  • GdriveLister::next_page (cyclomatic 20) core/services/gdrive/src/lister.rs:123 — GdriveLister::next_page has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OneDriveLister · ×1
  • OneDriveLister::next_page (cyclomatic 19) core/services/onedrive/src/lister.rs:63 — OneDriveLister::next_page has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HfCore · ×1
  • HfCore::read (cyclomatic 18) core/services/hf/src/core.rs:774 — HfCore::read has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.SearchBar (cyclomatic 18) · ×1
  • index.SearchBar (cyclomatic 18) website/src/theme/SearchBar/index.jsx:65 — index.SearchBar has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 99, 130, 82, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · opendal_service_gcs · ×1
  • opendal_service_gcs::core::parse_error (cyclomatic 17) core/services/gcs/src/core.rs:2250 — opendal_service_gcs::core::parse_error 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.
D1 · Cyclomatic Complexity · SmbLister · ×1
  • SmbLister::query (cyclomatic 17) core/services/smb/src/lister.rs:51 — SmbLister::query 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.
D1 · Cyclomatic Complexity · odev · ×1
  • odev::generate::python::format_text (cyclomatic 17) dev/src/generate/python.rs:115 — odev::generate::python::format_text 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.
D1 · Cyclomatic Complexity · opendal.newOpendalReadOptions (cyclomatic 17) · ×1
  • opendal.newOpendalReadOptions (cyclomatic 17) bindings/go/reader.go:234 — opendal.newOpendalReadOptions has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal 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.
D1 · Cyclomatic Complexity · CosObjectVersionsLister · ×1
  • CosObjectVersionsLister::next_page (cyclomatic 16) core/services/cos/src/lister.rs:160 — CosObjectVersionsLister::next_page 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.
D1 · Cyclomatic Complexity · FsLister · ×1
  • FsLister::next (cyclomatic 16) core/services/fs/src/lister.rs:50 — FsLister::next 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.
D1 · Cyclomatic Complexity · OssObjectVersionsLister · ×1
  • OssObjectVersionsLister::next_page (cyclomatic 16) core/services/oss/src/lister.rs:163 — OssObjectVersionsLister::next_page 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.
D1 · Cyclomatic Complexity · S3ObjectVersionsLister · ×1
  • S3ObjectVersionsLister::next_page (cyclomatic 16) core/services/s3/src/lister.rs:316 — S3ObjectVersionsLister::next_page 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.
D1 · Cyclomatic Complexity · TosObjectVersionsLister · ×1
  • TosObjectVersionsLister::next_page (cyclomatic 16) core/services/tos/src/lister.rs:157 — TosObjectVersionsLister::next_page 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.
D2 · Cognitive Complexity · Storage.init (cognitive 45) · ×1
  • Storage.init (cognitive 45) bindings/dart/lib/opendal.dart:32 — Storage.init has cognitive complexity 45 (threshold 15). Drivers by points: if/else 21 (33 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ServicerFlatLister · ×1
  • ServicerFlatLister::next (cognitive 38) core/core/src/layers/simulate.rs:501 — ServicerFlatLister::next has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 5 (14 pts), loops 2 (4 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · FlatLister · ×1
  • FlatLister::next (cognitive 38) core/core/src/raw/oio/list/flat_list.rs:89 — FlatLister::next has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 5 (14 pts), loops 2 (4 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · OneDriveLister · ×1
  • OneDriveLister::next_page (cognitive 38) core/services/onedrive/src/lister.rs:63 — OneDriveLister::next_page has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (30 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HfCore · ×1
  • HfCore::read (cognitive 31) core/services/hf/src/core.rs:774 — HfCore::read has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 3 (8 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SmbLister · ×1
  • SmbLister::query (cognitive 31) core/services/smb/src/lister.rs:51 — SmbLister::query has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (23 pts), match/switch 4 (5 pts), loops 2, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · local-images.localImages.rehype.<returned closure> (cognitive 30) · ×1
  • local-images.localImages.rehype.<returned closure> (cognitive 30) website/plugins/local-images.js:124 — local-images.localImages.rehype.<returned closure> has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 2 (7 pts), boolean chains 3, loops 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CloudflareKvBackend · ×1
  • CloudflareKvBackend::stat (cognitive 28) core/services/cloudflare-kv/src/backend.rs:257 — CloudflareKvBackend::stat has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 7, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CosObjectVersionsLister · ×1
  • CosObjectVersionsLister::next_page (cognitive 28) core/services/cos/src/lister.rs:160 — CosObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OssObjectVersionsLister · ×1
  • OssObjectVersionsLister::next_page (cognitive 28) core/services/oss/src/lister.rs:163 — OssObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · S3ObjectVersionsLister · ×1
  • S3ObjectVersionsLister::next_page (cognitive 28) core/services/s3/src/lister.rs:316 — S3ObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TosObjectVersionsLister · ×1
  • TosObjectVersionsLister::next_page (cognitive 28) core/services/tos/src/lister.rs:157 — TosObjectVersionsLister::next_page has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (23 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GcsGrpcWriter · ×1
  • GcsGrpcWriter::drive_pending (cognitive 27) core/services/gcs-grpc/src/writer.rs:201 — GcsGrpcWriter::drive_pending has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (20 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GdriveLister · ×1
  • GdriveLister::next_page (cognitive 27) core/services/gdrive/src/lister.rs:123 — GdriveLister::next_page has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 5 (7 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · YandexDiskLister · ×1
  • YandexDiskLister::next_page (cognitive 27) core/services/yandex-disk/src/lister.rs:56 — YandexDiskLister::next_page has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 1 (3 pts), match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CratesIoClient._request (cognitive 27) · ×1
  • CratesIoClient._request (cognitive 27) .github/scripts/release_rust/bootstrap.py:110 — CratesIoClient._request has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (8 pts), boolean chains 4, error handling 2 (4 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwiftLister · ×1
  • SwiftLister::next_page (cognitive 26) core/services/swift/src/lister.rs:62 — SwiftLister::next_page has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CloudflareKvLister · ×1
  • CloudflareKvLister::next_page (cognitive 25) core/services/cloudflare-kv/src/lister.rs:125 — CloudflareKvLister::next_page has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · GithubLister · ×1
  • GithubLister::next_page (cognitive 25) core/services/github/src/lister.rs:46 — GithubLister::next_page has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · main.fetch_issues (cognitive 24) · ×1
  • main.fetch_issues (cognitive 24) .github/scripts/weekly_update/main.py:80 — main.fetch_issues has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 2, loops 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · GdriveDeleter · ×1
  • GdriveDeleter::delete_once (cognitive 22) core/services/gdrive/src/deleter.rs:39 — GdriveDeleter::delete_once has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), match/switch 4 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ServiceParser · ×1
  • ServiceParser::parse_field (cognitive 22) dev/src/generate/parser.rs:287 — ServiceParser::parse_field has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · local-images.localImages.plugin.postBuild (cognitive 22) · ×1
  • local-images.localImages.plugin.postBuild (cognitive 22) website/plugins/local-images.js:176 — local-images.localImages.plugin.postBuild has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 13). Of this number, 16 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CorrectnessService · ×1
  • CorrectnessService::compose (cognitive 21) core/core/src/layers/correctness_check.rs:339 — CorrectnessService::compose has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 10. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · LakefsConfig · ×1
  • LakefsConfig::from_uri (cognitive 21) core/services/lakefs/src/config.rs:73 — LakefsConfig::from_uri has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RedisConfig · ×1
  • RedisConfig::from_uri (cognitive 21) core/services/redis/src/config.rs:81 — RedisConfig::from_uri has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DropboxLister · ×1
  • DropboxLister::next_page (cognitive 20) core/services/dropbox/src/lister.rs:54 — DropboxLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), match/switch 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GdrivePathIndex · ×1
  • GdrivePathIndex::ensure_dir (cognitive 20) core/services/gdrive/src/path_index.rs:256 — GdrivePathIndex::ensure_dir has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (6 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PcloudLister · ×1
  • PcloudLister::next_page (cognitive 20) core/services/pcloud/src/lister.rs:46 — PcloudLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 1 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · WebhdfsLister · ×1
  • WebhdfsLister::next_page (cognitive 20) core/services/webhdfs/src/lister.rs:47 — WebhdfsLister::next_page has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (6 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · bootstrap.preflight_authenticated (cognitive 20) · ×1
  • bootstrap.preflight_authenticated (cognitive 20) .github/scripts/release_rust/bootstrap.py:330 — bootstrap.preflight_authenticated has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CloudflareKvReader · ×1
  • CloudflareKvReader::open (cognitive 19) core/services/cloudflare-kv/src/reader.rs:51 — CloudflareKvReader::open has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · S3ListerV1 · ×1
  • S3ListerV1::next_page (cognitive 19) core/services/s3/src/lister.rs:74 — S3ListerV1::next_page has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · opendal.newOpendalWriteOptions (cognitive 19) · ×1
  • opendal.newOpendalWriteOptions (cognitive 19) bindings/go/writer.go:188 — opendal.newOpendalWriteOptions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 1 (2 pts) (nesting depth added 5). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · MokaBackend · ×1
  • MokaBackend::stat (cognitive 18) core/services/moka/src/backend.rs:267 — MokaBackend::stat has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TosDeleter · ×1
  • TosDeleter::delete_batch (cognitive 18) core/services/tos/src/deleter.rs:60 — TosDeleter::delete_batch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · opendal.newOpendalReadOptions (cognitive 18) · ×1
  • opendal.newOpendalReadOptions (cognitive 18) bindings/go/reader.go:234 — opendal.newOpendalReadOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17 (18 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 2 belong to one function literal 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.
D2 · Cognitive Complexity · FsLister · ×1
  • FsLister::next (cognitive 17) core/services/fs/src/lister.rs:50 — FsLister::next has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (6 pts), loops 1 (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · OperatorInputStream.read (cognitive 17) · ×1
  • OperatorInputStream.read (cognitive 17) bindings/java/src/main/java/org/apache/opendal/OperatorInputStream.java:76 — OperatorInputStream.read has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plan.plan (cognitive 17) · ×1
  • plan.plan (cognitive 17) .github/scripts/release_rust/plan.py:97 — plan.plan has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · publish.publish_package (cognitive 17) · ×1
  • publish.publish_package (cognitive 17) .github/scripts/release_rust/publish.py:207 — publish.publish_package has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OpWrite · ×1
  • OpWrite::from_options (cognitive 16) core/core/src/raw/ops.rs:856 — OpWrite::from_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OpCompose · ×1
  • OpCompose::from_options (cognitive 16) core/core/src/raw/ops.rs:1104 — OpCompose::from_options has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BufferSink · ×1
  • BufferSink::poll_close (cognitive 16) core/core/src/types/write/buffer_sink.rs:111 — BufferSink::poll_close has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 3 (7 pts), loops 1 (nesting depth added 9). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AzblobBuilder · ×1
  • AzblobBuilder::build (cognitive 16) core/services/azblob/src/backend.rs:312 — AzblobBuilder::build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), match/switch 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GcsLister · ×1
  • GcsLister::next_page (cognitive 16) core/services/gcs/src/lister.rs:50 — GcsLister::next_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · S3ListerV2 · ×1
  • S3ListerV2::next_page (cognitive 16) core/services/s3/src/lister.rs:200 — S3ListerV2::next_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SqliteBackend · ×1
  • SqliteBackend::stat (cognitive 16) core/services/sqlite/src/backend.rs:225 — SqliteBackend::stat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TikvConfig · ×1
  • TikvConfig::from_uri (cognitive 16) core/services/tikv/src/config.rs:57 — TikvConfig::from_uri has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WebdavLister · ×1
  • WebdavLister::next_page (cognitive 16) core/services/webdav/src/lister.rs:47 — WebdavLister::next_page has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.SearchBar (cognitive 16) · ×1
  • index.SearchBar (cognitive 16) website/src/theme/SearchBar/index.jsx:65 — index.SearchBar has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 7. Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 99, 130, 82, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D3 · God Classes · TooManyFunctions · ×1
  • TooManyFunctions: opendal_java::async_operator bindings/java/src/async_operator.rs:49 — TooManyFunctions — 36 free functions. The bar is 30 free functions; this is 6 over it, 1.20× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (4 members, 24 shared lines) · ×1
  • Near-duplicate member family (4 members, 24 shared lines) bindings/dotnet/src/operator.rs:866 — bindings/dotnet/src/operator.rs:866-891 | bindings/dotnet/src/operator.rs:921-946 | bindings/dotnet/src/operator.rs:976-1001 | bindings/dotnet/src/operator.rs:1031-1056 — These 4 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 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, 16 shared lines) · ×1
  • Near-duplicate member family (4 members, 16 shared lines) core/core/src/raw/ops.rs:112 — core/core/src/raw/ops.rs:112-158 | core/core/src/raw/ops.rs:859-931 | core/core/src/raw/ops.rs:1107-1172 | core/core/src/raw/ops.rs:1293-1342 — These 4 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 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, 15 shared lines) · ×1
  • Near-duplicate member family (4 members, 15 shared lines) core/services/cos/src/core.rs:402 — core/services/cos/src/core.rs:402-429 | core/services/cos/src/core.rs:594-625 | core/services/obs/src/core.rs:340-366 | core/services/oss/src/core.rs:571-601 — These 4 members are variants of one another: a block of 15 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 pair (86 shared lines) · ×1
  • Near-duplicate member pair (86 shared lines) core/core/src/layers/simulate.rs:501 — core/core/src/layers/simulate.rs:501-605 | core/core/src/raw/oio/list/flat_list.rs:89-205 — These two members are variants of one another: 86 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 · Near-duplicate member pair (44 shared lines) · ×1
  • Near-duplicate member pair (44 shared lines) core/services/azdls/src/core.rs:826 — core/services/azdls/src/core.rs:826-912 | core/services/azfile/src/core.rs:551-648 — These two members are variants of one another: 44 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 · Near-duplicate member pair (25 shared lines) · ×1
  • Near-duplicate member pair (25 shared lines) core/services/oss/src/core.rs:320 — core/services/oss/src/core.rs:320-377 | core/services/s3/src/core.rs:544-621 — These two members are variants of one another: 25 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 · Near-duplicate member pair (21 shared lines) · ×1
  • Near-duplicate member pair (21 shared lines) core/services/cloudflare-kv/src/config.rs:57 — core/services/cloudflare-kv/src/config.rs:57-94 | core/services/d1/src/config.rs:62-99 — These two members are variants of one another: 21 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 (11 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (11 members, 50+ identical tokens) core/layers/observe-metrics-common/src/lib.rs:756 — core/layers/observe-metrics-common/src/lib.rs:756-785 | core/layers/observe-metrics-common/src/lib.rs:787-811 | core/layers/observe-metrics-common/src/lib.rs:813-842 | core/layers/observe-metrics-common/src/lib.rs:850-879 | core/layers/observe-metrics-common/src/lib.rs:887-916 | core/layers/observe-metrics-common/src/lib.rs:923-951 | core/layers/observe-metrics-common/src/lib.rs:953-982 | core/layers/observe-metrics-common/src/lib.rs:984-1013 | core/layers/observe-metrics-common/src/lib.rs:1015-1044 | core/layers/observe-metrics-common/src/lib.rs:1051-1080 | core/layers/observe-metrics-common/src/lib.rs:1101-1136 — These 11 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 11 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 11 times.
D4 · Code Duplication · Edited copy of a member (89 corresponding lines) · ×1
  • Edited copy of a member (89 corresponding lines) core/services/ghac/src/core.rs:101 — core/services/ghac/src/core.rs:101-195 | core/services/ghac/src/core.rs:232-320 — These two members are one piece of code written twice and then edited apart: 89 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (76 corresponding lines) · ×1
  • Edited copy of a member (76 corresponding lines) core/layers/fastmetrics/src/lib.rs:411 — core/layers/fastmetrics/src/lib.rs:411-488 | core/layers/prometheus-client/src/lib.rs:411-486 — These two members are one piece of code written twice and then edited apart: 76 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (91 corresponding lines) · ×1
  • Edited copy of a member (91 corresponding lines) core/services/s3/src/core.rs:796 — core/services/s3/src/core.rs:796-886 | core/services/s3/src/core.rs:1104-1200 — These two members are one piece of code written twice and then edited apart: 91 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (80 corresponding lines) · ×1
  • Edited copy of a member (80 corresponding lines) core/services/cos/src/backend.rs:502 — core/services/cos/src/backend.rs:502-591 | core/services/s3/src/backend.rs:1463-1542 — These two members are one piece of code written twice and then edited apart: 80 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (70 corresponding lines) · ×1
  • Edited copy of a member (70 corresponding lines) core/services/s3/src/copier.rs:174 — core/services/s3/src/copier.rs:174-247 | core/services/s3/src/copier.rs:341-410 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) bindings/go/reader.go:234 — bindings/go/reader.go:234-301 | bindings/go/reader.go:403-457 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 55+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 55+ corresponding lines) core/services/gcs/src/core.rs:614 — core/services/gcs/src/core.rs:614-668 | core/services/s3/src/core.rs:469-537 | core/services/tos/src/core.rs:234-312 | core/services/tos/src/core.rs:354-426 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 55 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 (86 corresponding lines) · ×1
  • Edited copy of a member (86 corresponding lines) core/services/gdrive/src/backend.rs:133 — core/services/gdrive/src/backend.rs:133-218 | core/services/onedrive/src/backend.rs:124-212 — These two members are one piece of code written twice and then edited apart: 86 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (50 corresponding lines) · ×1
  • Edited copy of a member (50 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs:227 — core/core/src/raw/oio/copy/block_copy.rs:227-276 | core/core/src/raw/oio/copy/multipart_copy.rs:296-349 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 59+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 59+ corresponding lines) core/services/koofr/src/backend.rs:113 — core/services/koofr/src/backend.rs:113-178 | core/services/pcloud/src/backend.rs:109-167 | core/services/seafile/src/backend.rs:119-183 | core/services/upyun/src/backend.rs:105-177 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 59 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 (53 corresponding lines) · ×1
  • Edited copy of a member (53 corresponding lines) bindings/c/src/operator_info.rs:270 — bindings/c/src/operator_info.rs:270-330 | bindings/python/src/capability.rs:144-196 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) core/services/mongodb/src/backend.rs:117 — core/services/mongodb/src/backend.rs:117-167 | core/services/surrealdb/src/backend.rs:133-198 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) core/services/gcs/src/core.rs:169 — core/services/gcs/src/core.rs:169-210 | core/services/gcs/src/core.rs:569-607 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) core/core/src/raw/oio/copy/block_copy.rs:117 — core/core/src/raw/oio/copy/block_copy.rs:117-170 | core/core/src/raw/oio/copy/multipart_copy.rs:142-195 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) bindings/python/src/operator.rs:392 — bindings/python/src/operator.rs:392-438 | bindings/python/src/operator.rs:1198-1245 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) core/services/s3/src/core.rs:406 — core/services/s3/src/core.rs:406-452 | core/services/tos/src/core.rs:184-227 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) core/services/s3/src/deleter.rs:68 — core/services/s3/src/deleter.rs:68-112 | core/services/swift/src/deleter.rs:54-105 — 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 (3 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 43+ corresponding lines) core/services/mysql/src/backend.rs:108 — core/services/mysql/src/backend.rs:108-150 | core/services/postgresql/src/backend.rs:102-144 | core/services/sqlite/src/backend.rs:106-149 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 37+ corresponding lines) core/services/azdls/src/config.rs:81 — core/services/azdls/src/config.rs:81-123 | core/services/azfile/src/config.rs:56-98 | core/services/swift/src/config.rs:66-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 44+ corresponding lines) core/core/src/layers/correctness_check.rs:181 — core/core/src/layers/correctness_check.rs:181-227 | core/core/src/layers/correctness_check.rs:234-280 | core/core/src/layers/correctness_check.rs:294-337 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) core/services/s3/src/core.rs:1412 — core/services/s3/src/core.rs:1412-1450 | core/services/tos/src/core.rs:489-519 — 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 (6 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 27+ corresponding lines) core/services/cos/src/reader.rs:50 — core/services/cos/src/reader.rs:50-78 | core/services/lakefs/src/reader.rs:50-77 | core/services/obs/src/reader.rs:50-77 | core/services/oss/src/reader.rs:50-78 | core/services/swift/src/reader.rs:50-77 | core/services/tos/src/reader.rs:52-78 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 27 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 (5 members, 35+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 35+ corresponding lines) core/services/azdls/src/core.rs:122 — core/services/azdls/src/core.rs:122-159 | core/services/azdls/src/core.rs:347-382 | core/services/obs/src/core.rs:130-164 | core/services/swift/src/core.rs:289-329 | core/services/swift/src/core.rs:382-416 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 35 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 30+ corresponding lines) core/services/mysql/src/config.rs:67 — core/services/mysql/src/config.rs:67-96 | core/services/postgresql/src/config.rs:67-96 | core/services/sqlite/src/config.rs:73-102 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 34+ corresponding lines) core/services/oss/src/core.rs:457 — core/services/oss/src/core.rs:457-493 | core/services/s3/src/core.rs:936-978 | core/services/tos/src/core.rs:687-723 | core/services/tos/src/core.rs:733-766 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 34 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) core/services/azdls/src/reader.rs:50 — core/services/azdls/src/reader.rs:50-77 | core/services/onedrive/src/reader.rs:50-86 | core/services/webdav/src/reader.rs:66-93 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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 (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) core/core/src/raw/oio/write/block_write.rs:118 — core/core/src/raw/oio/write/block_write.rs:118-161 | core/core/src/raw/oio/write/position_write.rs:82-117 — 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 copies of one member (4 members, 33+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 33+ corresponding lines) core/services/cos/src/core.rs:188 — core/services/cos/src/core.rs:188-234 | core/services/cos/src/core.rs:436-480 | core/services/obs/src/core.rs:172-204 | core/services/upyun/src/core.rs:173-210 — 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 copies of one member (7 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 24+ corresponding lines) core/services/azblob/src/backend.rs:659 — core/services/azblob/src/backend.rs:659-687 | core/services/cos/src/backend.rs:598-626 | core/services/gcs/src/backend.rs:607-638 | core/services/obs/src/backend.rs:453-481 | core/services/oss/src/backend.rs:829-860 | core/services/s3/src/backend.rs:1549-1577 | core/services/tos/src/backend.rs:428-451 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 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) core/services/lakefs/src/core.rs:231 — core/services/lakefs/src/core.rs:231-262 | core/services/swift/src/core.rs:336-375 — 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 copies of one member (8 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 30+ corresponding lines) core/layers/retry/src/lib.rs:737 — core/layers/retry/src/lib.rs:737-766 | core/layers/retry/src/lib.rs:833-862 | core/layers/retry/src/lib.rs:864-893 | core/layers/retry/src/lib.rs:897-926 | core/layers/retry/src/lib.rs:966-995 | core/layers/retry/src/lib.rs:999-1028 | core/layers/retry/src/lib.rs:1030-1059 | core/layers/retry/src/lib.rs:1061-1090 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 30 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 copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) bindings/c/src/operator.rs:364 — bindings/c/src/operator.rs:364-387 | bindings/c/src/operator.rs:597-621 | bindings/c/src/operator.rs:686-705 | bindings/c/src/operator.rs:1027-1048 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 29+ corresponding lines) core/services/oss/src/core.rs:379 — core/services/oss/src/core.rs:379-407 | core/services/s3/src/core.rs:739-776 | core/services/tos/src/core.rs:442-472 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 26+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 26+ corresponding lines) core/services/b2/src/core.rs:439 — core/services/b2/src/core.rs:439-465 | core/services/b2/src/core.rs:471-496 | core/services/b2/src/core.rs:593-622 | core/services/b2/src/core.rs:624-653 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 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, 22+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 22+ corresponding lines) bindings/go/copier.go:76 — bindings/go/copier.go:76-99 | bindings/go/reader.go:501-522 | bindings/go/stat.go:61-82 | bindings/go/writer.go:58-79 | bindings/go/writer.go:327-356 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 22 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) core/services/obs/src/writer.rs:167 — core/services/obs/src/writer.rs:167-197 | core/services/oss/src/writer.rs:167-194 — 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 (4 members, 25+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 25+ corresponding lines) core/services/upyun/src/core.rs:239 — core/services/upyun/src/core.rs:239-267 | core/services/upyun/src/core.rs:274-302 | core/services/upyun/src/core.rs:304-328 | core/services/upyun/src/core.rs:416-440 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 23+ corresponding lines) core/services/dbfs/src/core.rs:142 — core/services/dbfs/src/core.rs:142-164 | core/services/dbfs/src/core.rs:193-216 | core/services/lakefs/src/core.rs:57-81 | core/services/lakefs/src/core.rs:169-193 | core/services/lakefs/src/core.rs:200-224 — These 5 members are one piece of code written 5 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 5 times and the copies 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) core/services/azdls/src/core.rs:275 — core/services/azdls/src/core.rs:275-307 | core/services/gcs/src/core.rs:1012-1036 | core/services/obs/src/core.rs:400-427 | core/services/oss/src/core.rs:712-734 — 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 (6 members, 30+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 30+ corresponding lines) core/services/b2/src/writer.rs:127 — core/services/b2/src/writer.rs:127-157 | core/services/cos/src/writer.rs:130-164 | core/services/obs/src/writer.rs:120-161 | core/services/oss/src/writer.rs:119-161 | core/services/tos/src/writer.rs:121-154 | core/services/vercel-blob/src/writer.rs:104-133 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 30 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 (6 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 19+ corresponding lines) core/services/azblob/src/backend.rs:575 — core/services/azblob/src/backend.rs:575-597 | core/services/cos/src/backend.rs:379-397 | core/services/obs/src/backend.rs:352-370 | core/services/oss/src/backend.rs:707-725 | core/services/s3/src/backend.rs:1366-1386 | core/services/webhdfs/src/backend.rs:346-369 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 19 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 (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) core/layers/capability-check/src/lib.rs:130 — core/layers/capability-check/src/lib.rs:130-156 | core/layers/capability-check/src/lib.rs:164-186 | core/layers/capability-check/src/lib.rs:286-304 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 17+ corresponding lines) core/layers/retry/src/lib.rs:320 — core/layers/retry/src/lib.rs:320-336 | core/layers/retry/src/lib.rs:338-356 | core/layers/retry/src/lib.rs:358-376 | core/layers/retry/src/lib.rs:378-394 | core/layers/retry/src/lib.rs:475-491 | core/layers/retry/src/lib.rs:493-511 | core/layers/retry/src/lib.rs:518-534 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 21+ corresponding lines) core/services/yandex-disk/src/core.rs:230 — core/services/yandex-disk/src/core.rs:230-252 | core/services/yandex-disk/src/core.rs:259-281 | core/services/yandex-disk/src/core.rs:283-303 | core/services/yandex-disk/src/core.rs:311-339 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 22+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 22+ corresponding lines) core/services/pcloud/src/core.rs:205 — core/services/pcloud/src/core.rs:205-228 | core/services/pcloud/src/core.rs:235-257 | core/services/pcloud/src/core.rs:263-284 | core/services/pcloud/src/core.rs:290-311 | core/services/pcloud/src/core.rs:318-341 | core/services/pcloud/src/core.rs:348-371 | core/services/pcloud/src/core.rs:373-396 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 22 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) core/services/compfs/src/core.rs:71 — core/services/compfs/src/core.rs:71-86 | core/services/fs/src/core.rs:48-63 | core/services/monoiofs/src/core.rs:98-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) core/services/ipmfs/src/core.rs:44 — core/services/ipmfs/src/core.rs:44-59 | core/services/ipmfs/src/core.rs:88-103 | core/services/ipmfs/src/core.rs:109-124 | core/services/ipmfs/src/core.rs:130-145 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 18+ corresponding lines) core/services/cos/src/core.rs:567 — core/services/cos/src/core.rs:567-584 | core/services/gcs/src/core.rs:1081-1099 | core/services/s3/src/core.rs:1353-1376 | core/services/s3/src/core.rs:1384-1406 | core/services/tos/src/core.rs:659-677 | core/services/tos/src/core.rs:898-916 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) core/services/cos/src/writer.rs:56 — core/services/cos/src/writer.rs:56-71 | core/services/obs/src/writer.rs:50-63 | core/services/oss/src/writer.rs:49-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 17+ corresponding lines) core/services/azdls/src/writer.rs:177 — core/services/azdls/src/writer.rs:177-194 | core/services/cos/src/writer.rs:220-243 | core/services/obs/src/writer.rs:217-240 | core/services/oss/src/writer.rs:213-236 | core/services/s3/src/writer.rs:344-360 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 17+ corresponding lines) bindings/python/src/operator.rs:1898 — bindings/python/src/operator.rs:1898-1920 | bindings/python/src/operator.rs:1974-1997 | bindings/python/src/operator.rs:2051-2074 | bindings/python/src/operator.rs:2098-2114 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 21+ corresponding lines) core/services/cos/src/writer.rs:98 — core/services/cos/src/writer.rs:98-122 | core/services/obs/src/writer.rs:89-112 | core/services/oss/src/writer.rs:87-111 | core/services/s3/src/copier.rs:249-269 | core/services/s3/src/writer.rs:108-130 | core/services/tos/src/writer.rs:92-113 | core/services/vercel-blob/src/writer.rs:74-96 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) core/layers/oteltrace/src/lib.rs:117 — core/layers/oteltrace/src/lib.rs:117-127 | core/layers/oteltrace/src/lib.rs:129-138 | core/layers/oteltrace/src/lib.rs:140-149 | core/layers/oteltrace/src/lib.rs:174-185 | core/layers/oteltrace/src/lib.rs:192-199 | core/layers/oteltrace/src/lib.rs:201-208 | core/layers/oteltrace/src/lib.rs:214-223 | core/layers/oteltrace/src/lib.rs:230-237 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) bindings/python/src/operator.rs:513 — bindings/python/src/operator.rs:513-537 | bindings/python/src/operator.rs:601-622 | bindings/python/src/operator.rs:673-689 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) bindings/dotnet/src/operator.rs:654 — bindings/dotnet/src/operator.rs:654-665 | bindings/dotnet/src/operator.rs:1821-1832 | bindings/dotnet/src/operator.rs:1917-1927 | bindings/dotnet/src/operator.rs:2157-2168 — 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 (5 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 12+ corresponding lines) core/services/cos/src/deleter.rs:40 — core/services/cos/src/deleter.rs:40-52 | core/services/obs/src/deleter.rs:39-51 | core/services/oss/src/deleter.rs:42-54 | core/services/swift/src/deleter.rs:39-52 | core/services/webdav/src/deleter.rs:40-51 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 11+ corresponding lines) core/services/b2/src/backend.rs:276 — core/services/b2/src/backend.rs:276-287 | core/services/swift/src/backend.rs:297-312 | core/services/tos/src/backend.rs:348-358 | core/services/upyun/src/backend.rs:247-258 | core/services/vercel-blob/src/backend.rs:196-208 — 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 copies of one member (5 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 13+ corresponding lines) core/services/azdls/src/backend.rs:400 — core/services/azdls/src/backend.rs:400-414 | core/services/dbfs/src/backend.rs:162-174 | core/services/github/src/backend.rs:180-197 | core/services/ipmfs/src/backend.rs:184-196 | core/services/upyun/src/backend.rs:207-219 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) core/services/cacache/src/config.rs:32 — core/services/cacache/src/config.rs:32-43 | core/services/foundationdb/src/config.rs:38-49 | core/services/persy/src/config.rs:39-50 — These 3 members are one piece of code written 3 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 3 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) bindings/dotnet/src/operator.rs:286 — bindings/dotnet/src/operator.rs:286-298 | bindings/dotnet/src/operator.rs:322-331 | bindings/dotnet/src/operator.rs:356-367 | bindings/dotnet/src/operator.rs:397-405 — 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 (7 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 13+ corresponding lines) core/services/aliyun-drive/src/backend.rs:372 — core/services/aliyun-drive/src/backend.rs:372-385 | core/services/azblob/src/backend.rs:610-624 | core/services/azdls/src/backend.rs:479-492 | core/services/azfile/src/backend.rs:398-411 | core/services/hf/src/backend.rs:379-391 | core/services/lakefs/src/backend.rs:257-272 | core/services/swift/src/backend.rs:325-340 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) core/layers/dtrace/src/lib.rs:181 — core/layers/dtrace/src/lib.rs:181-187 | core/layers/dtrace/src/lib.rs:189-198 | core/layers/dtrace/src/lib.rs:200-210 | core/layers/dtrace/src/lib.rs:218-224 | core/layers/dtrace/src/lib.rs:245-251 | core/layers/dtrace/src/lib.rs:257-263 | core/layers/dtrace/src/lib.rs:270-276 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 7+ corresponding lines) core/services/cos/src/core.rs:59 — core/services/cos/src/core.rs:59-65 | core/services/gcs-grpc/src/config.rs:67-74 | core/services/gcs/src/config.rs:114-121 | core/services/obs/src/core.rs:54-60 | core/services/oss/src/config.rs:123-130 | core/services/oss/src/core.rs:84-91 | core/services/s3/src/config.rs:396-403 | core/services/tos/src/config.rs:92-99 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) core/core/src/blocking/copy.rs:70 — core/core/src/blocking/copy.rs:70-74 | core/core/src/blocking/list.rs:67-71 | core/core/src/blocking/read/std_reader.rs:116-120 | core/core/src/blocking/write/std_writer.rs:77-81 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 6+ corresponding lines) core/services/alluxio/src/config.rs:43 — core/services/alluxio/src/config.rs:43-48 | core/services/alluxio/src/core.rs:42-47 | core/services/azblob/src/core.rs:89-95 | core/services/dbfs/src/config.rs:37-42 | core/services/hf/src/core.rs:443-449 | core/services/ipmfs/src/core.rs:35-40 | core/services/webhdfs/src/core.rs:46-51 — These 7 members are one piece of code written 7 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 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 6+ corresponding lines) core/services/ftp/src/config.rs:42 — core/services/ftp/src/config.rs:42-47 | core/services/http/src/config.rs:43-48 | core/services/http/src/core.rs:42-47 | core/services/ipfs/src/core.rs:35-40 | core/services/s3/src/core.rs:172-178 | core/services/sftp/src/config.rs:49-54 | core/services/sftp/src/core.rs:40-45 | core/services/tos/src/core.rs:84-90 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) bindings/java/src/async_operator.rs:84 — bindings/java/src/async_operator.rs:84-87 | bindings/java/src/operator.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.
D4 · Code Duplication · Duplicated block (59–60 lines × 3) · ×1
  • Duplicated block (59–60 lines × 3) core/services/cos/src/lister.rs:177 — core/services/cos/src/lister.rs:177-235 | core/services/oss/src/lister.rs:180-238 | core/services/s3/src/lister.rs:333-392 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:177` 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.
D4 · Code Duplication · Duplicated block (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) core/services/gdrive/src/backend.rs:521 — core/services/gdrive/src/backend.rs:521-572 | core/services/gdrive/src/backend.rs:589-640 — both copies are in the same file, so extract the 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 `core/services/gdrive/src/backend.rs:589` 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.
D4 · Code Duplication · Duplicated block (40–41 lines × 2) · ×1
  • Duplicated block (40–41 lines × 2) core/core/src/layers/simulate.rs:538 — core/core/src/layers/simulate.rs:538-577 | core/core/src/raw/oio/list/flat_list.rs:134-174 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/core/src/layers/simulate.rs:538` 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) core/services/s3/src/core.rs:835 — core/services/s3/src/core.rs:835-874 | core/services/s3/src/core.rs:1152-1191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/s3/src/core.rs:1150` calls `insert_sse_headers` and `core/services/s3/src/core.rs:833` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (31–38 lines × 2) · ×1
  • Duplicated block (31–38 lines × 2) core/services/gcs-grpc/src/backend.rs:196 — core/services/gcs-grpc/src/backend.rs:196-226 | core/services/gcs/src/backend.rs:305-342 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) core/services/cos/src/backend.rs:527 — core/services/cos/src/backend.rs:527-562 | core/services/s3/src/backend.rs:1494-1529 — before extracting anything, compare `core/services/cos/src/backend.rs` and `core/services/s3/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/backend.rs:527` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35–36 lines × 2) · ×1
  • Duplicated block (35–36 lines × 2) core/services/s3/src/core.rs:470 — core/services/s3/src/core.rs:470-504 | core/services/s3/src/core.rs:545-580 — both copies are in the same file, so extract the 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 `core/services/s3/src/core.rs:470` 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) core/services/gdrive/src/backend.rs:414 — core/services/gdrive/src/backend.rs:414-447 | core/services/gdrive/src/backend.rs:451-484 — both copies are in the same file, so extract the 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 `core/services/gdrive/src/backend.rs:414` 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) core/services/gcs/src/core.rs:219 — core/services/gcs/src/core.rs:219-250 | core/services/gcs/src/core.rs:615-646 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (30–31 lines × 2) · ×1
  • Duplicated block (30–31 lines × 2) core/services/cos/src/core.rs:595 — core/services/cos/src/core.rs:595-625 | core/services/oss/src/core.rs:572-601 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/oss/src/core.rs` as WHOLE FILES: this scan already matched 26 separate duplicated blocks between them, totalling at least 281 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) core/services/s3/src/copier.rs:43 — core/services/s3/src/copier.rs:43-71 | core/services/tos/src/copier.rs:38-66 — 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 `core/services/s3/src/copier.rs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28 lines × 3) · ×1
  • Duplicated block (28 lines × 3) core/services/gdrive/src/lister.rs:437 — core/services/gdrive/src/lister.rs:437-464 | core/services/gdrive/src/lister.rs:493-520 | core/services/gdrive/src/lister.rs:564-591 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) core/services/gdrive/src/core.rs:313 — core/services/gdrive/src/core.rs:313-339 | core/services/gdrive/src/core.rs:366-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gdrive/src/core.rs:313` 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) core/services/cos/src/core.rs:326 — core/services/cos/src/core.rs:326-351 | core/services/obs/src/core.rs:276-302 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) bindings/python/src/operator.rs:226 — bindings/python/src/operator.rs:226-250 | bindings/python/src/operator.rs:1035-1060 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (22–26 lines × 2) · ×1
  • Duplicated block (22–26 lines × 2) core/services/monoiofs/src/reader.rs:61 — core/services/monoiofs/src/reader.rs:61-82 | core/services/monoiofs/src/writer.rs:73-98 — 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 `core/services/monoiofs/src/reader.rs:61` 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) core/services/mini_moka/src/backend.rs:101 — core/services/mini_moka/src/backend.rs:101-125 | core/services/moka/src/backend.rs:163-187 — before extracting anything, compare `core/services/mini_moka/src/backend.rs` and `core/services/moka/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) core/services/tos/src/core.rs:283 — core/services/tos/src/core.rs:283-305 | core/services/tos/src/core.rs:399-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) core/services/mysql/src/config.rs:75 — core/services/mysql/src/config.rs:75-96 | core/services/postgresql/src/config.rs:75-96 | core/services/sqlite/src/config.rs:81-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/mysql/src/config.rs:75` 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.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) core/core/src/layers/simulate.rs:516 — core/core/src/layers/simulate.rs:516-534 | core/core/src/raw/oio/list/flat_list.rs:111-130 — before extracting anything, compare `core/core/src/layers/simulate.rs` and `core/core/src/raw/oio/list/flat_list.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/core/src/layers/simulate.rs:516` 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.
D4 · Code Duplication · Duplicated block (16–20 lines × 2) · ×1
  • Duplicated block (16–20 lines × 2) core/services/azdls/src/core.rs:84 — core/services/azdls/src/core.rs:84-103 | core/services/azfile/src/core.rs:74-89 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/azfile/src/core.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 99 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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.
D4 · Code Duplication · Duplicated block (13–20 lines × 2) · ×1
  • Duplicated block (13–20 lines × 2) core/services/gcs/src/core.rs:132 — core/services/gcs/src/core.rs:132-151 | core/services/tos/src/core.rs:110-122 — before extracting anything, compare `core/services/gcs/src/core.rs` and `core/services/tos/src/core.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/gcs/src/core.rs:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) core/layers/observe-metrics-common/src/lib.rs:824 — core/layers/observe-metrics-common/src/lib.rs:824-842 | core/layers/observe-metrics-common/src/lib.rs:861-879 | core/layers/observe-metrics-common/src/lib.rs:995-1013 | core/layers/observe-metrics-common/src/lib.rs:1026-1044 — 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 `core/layers/observe-metrics-common/src/lib.rs:824` 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.
D4 · Code Duplication · Duplicated block (17–18 lines × 7) · ×1
  • Duplicated block (17–18 lines × 7) core/services/foundationdb/src/backend.rs:98 — core/services/foundationdb/src/backend.rs:98-114 | core/services/gridfs/src/backend.rs:170-187 | core/services/memcached/src/backend.rs:236-252 | core/services/mongodb/src/backend.rs:185-202 | core/services/postgresql/src/backend.rs:159-175 | core/services/surrealdb/src/backend.rs:213-229 | core/services/tikv/src/backend.rs:127-143 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/gridfs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/foundationdb/src/backend.rs:98` 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 first that the copies are not typed on the same thing: the declarations holding them bind `core` to `FoundationdbCore` in one and `GridfsCore` 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 · Duplicated block (16–18 lines × 4) · ×1
  • Duplicated block (16–18 lines × 4) core/services/cos/src/lister.rs:173 — core/services/cos/src/lister.rs:173-188 | core/services/oss/src/lister.rs:176-191 | core/services/s3/src/lister.rs:329-344 | core/services/tos/src/lister.rs:170-187 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:173` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut PageContext` in one and `&mut oio::PageContext` 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 · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) core/services/redb/src/backend.rs:146 — core/services/redb/src/backend.rs:146-163 | core/services/rocksdb/src/backend.rs:93-110 | core/services/sled/src/backend.rs:117-134 — before extracting anything, compare `core/services/redb/src/backend.rs` and `core/services/rocksdb/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/redb/src/backend.rs:146` 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 first that the copies are not typed on the same thing: the declarations holding them bind `core` to `RedbCore` in one and `RocksdbCore` 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 · Duplicated block (17 lines × 5) · ×1
  • Duplicated block (17 lines × 5) core/layers/observe-metrics-common/src/lib.rs:769 — core/layers/observe-metrics-common/src/lib.rs:769-785 | core/layers/observe-metrics-common/src/lib.rs:900-916 | core/layers/observe-metrics-common/src/lib.rs:935-951 | core/layers/observe-metrics-common/src/lib.rs:966-982 | core/layers/observe-metrics-common/src/lib.rs:1064-1080 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/layers/observe-metrics-common/src/lib.rs:769` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) core/services/cos/src/lister.rs:244 — core/services/cos/src/lister.rs:244-259 | core/services/oss/src/lister.rs:247-262 | core/services/s3/src/lister.rs:400-416 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/cos/src/lister.rs:241` calls `content_md5`, `trim_matches` and `core/services/s3/src/lister.rs:397` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) core/services/tos/src/copier.rs:241 — core/services/tos/src/copier.rs:241-255 | core/services/tos/src/writer.rs:186-202 — before extracting anything, compare `core/services/tos/src/copier.rs` and `core/services/tos/src/writer.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 `core/services/tos/src/copier.rs:241` 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.
D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1
  • Duplicated block (13–16 lines × 2) core/services/onedrive/src/core.rs:554 — core/services/onedrive/src/core.rs:554-569 | core/services/onedrive/src/core.rs:674-686 — both copies are in the same file, so extract the 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 `core/services/onedrive/src/core.rs:554` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–15 lines × 3) · ×1
  • Duplicated block (13–15 lines × 3) core/services/cos/src/core.rs:499 — core/services/cos/src/core.rs:499-513 | core/services/gcs/src/core.rs:1022-1036 | core/services/oss/src/core.rs:722-734 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 8 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/core.rs:499` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 3) · ×1
  • Duplicated block (14–15 lines × 3) core/services/dashmap/src/reader.rs:44 — core/services/dashmap/src/reader.rs:44-57 | core/services/mini_moka/src/reader.rs:44-58 | core/services/moka/src/reader.rs:44-57 — before extracting anything, compare `core/services/dashmap/src/reader.rs` and `core/services/moka/src/reader.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 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.
D4 · Code Duplication · Duplicated block (11–15 lines × 2) · ×1
  • Duplicated block (11–15 lines × 2) core/services/s3/src/deleter.rs:85 — core/services/s3/src/deleter.rs:85-99 | core/services/tos/src/deleter.rs:78-88 — 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 `core/services/s3/src/deleter.rs:85` 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.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) core/services/s3/src/lister.rs:212 — core/services/s3/src/lister.rs:212-224 | core/services/tos/src/lister.rs:72-86 — before extracting anything, compare `core/services/s3/src/lister.rs` and `core/services/tos/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 144 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/s3/src/lister.rs:212` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 7) · ×1
  • Duplicated block (13–14 lines × 7) core/services/koofr/src/backend.rs:306 — core/services/koofr/src/backend.rs:306-319 | core/services/lakefs/src/backend.rs:307-320 | core/services/obs/src/backend.rs:407-419 | core/services/onedrive/src/backend.rs:308-321 | core/services/upyun/src/backend.rs:289-302 | core/services/vercel-blob/src/backend.rs:219-232 | core/services/yandex-disk/src/backend.rs:192-205 — before extracting anything, compare `core/services/koofr/src/backend.rs` and `core/services/lakefs/src/backend.rs` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/koofr/src/backend.rs:306` 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 `args` to `OpList` in one and `OpWrite` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/yandex-disk/src/backend.rs:207` calls `ensure_dir_exists` and `core/services/upyun/src/backend.rs:304` 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.
D4 · Code Duplication · Duplicated block (10–14 lines × 5) · ×1
  • Duplicated block (10–14 lines × 5) core/services/b2/src/core.rs:193 — core/services/b2/src/core.rs:193-202 | core/services/b2/src/core.rs:238-250 | core/services/b2/src/core.rs:387-397 | core/services/seafile/src/core.rs:171-183 | core/services/seafile/src/core.rs:281-294 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/b2/src/core.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.
D4 · Code Duplication · Duplicated block (10–14 lines × 2) · ×1
  • Duplicated block (10–14 lines × 2) core/services/http/src/core.rs:83 — core/services/http/src/core.rs:83-92 | core/services/webdav/src/core.rs:203-216 — 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 `core/services/webdav/src/core.rs:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) core/services/tos/src/core.rs:213 — core/services/tos/src/core.rs:213-226 | core/services/tos/src/core.rs:801-812 — both copies are in the same file, so extract the 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.
D4 · Code Duplication · Duplicated block (13 lines × 11) · ×1
  • Duplicated block (13 lines × 11) bindings/haskell/src/lib.rs:156 — bindings/haskell/src/lib.rs:156-168 | bindings/haskell/src/lib.rs:202-214 | bindings/haskell/src/lib.rs:248-260 | bindings/haskell/src/lib.rs:289-301 | bindings/haskell/src/lib.rs:432-444 | bindings/haskell/src/lib.rs:473-485 | bindings/haskell/src/lib.rs:514-526 | bindings/haskell/src/lib.rs:555-567 | bindings/haskell/src/lib.rs:694-706 | bindings/haskell/src/lib.rs:746-758 | bindings/haskell/src/lib.rs:789-801 — all 11 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 `bindings/haskell/src/lib.rs:156` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 6) · ×1
  • Duplicated block (12–13 lines × 6) core/services/cos/src/lister.rs:96 — core/services/cos/src/lister.rs:96-108 | core/services/obs/src/lister.rs:95-107 | core/services/oss/src/lister.rs:98-109 | core/services/s3/src/lister.rs:133-145 | core/services/s3/src/lister.rs:250-262 | core/services/tos/src/lister.rs:93-105 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/obs/src/lister.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/lister.rs:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/oss/src/lister.rs:110` calls `as_ref`, `Some` and `core/services/cos/src/lister.rs:110` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) core/services/alluxio/src/config.rs:55 — core/services/alluxio/src/config.rs:55-67 | core/services/ipfs/src/config.rs:38-50 | core/services/ipmfs/src/config.rs:38-50 | core/services/webhdfs/src/config.rs:60-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 3) · ×1
  • Duplicated block (12–13 lines × 3) core/services/cos/src/lister.rs:231 — core/services/cos/src/lister.rs:231-242 | core/services/oss/src/lister.rs:234-245 | core/services/tos/src/lister.rs:220-232 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) bindings/dotnet/src/operator.rs:1560 — bindings/dotnet/src/operator.rs:1560-1572 | bindings/dotnet/src/operator.rs:1633-1643 — both copies are in the same file, so extract the 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.
D4 · Code Duplication · Duplicated block (4–13 lines × 3) · ×1
  • Duplicated block (4–13 lines × 3) core/services/webdav/src/core.rs:633 — core/services/webdav/src/core.rs:633-645 | core/services/webdav/src/core.rs:658-670 | core/services/webdav/src/core.rs:694-697 — 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 `core/services/webdav/src/core.rs:633` 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.
D4 · Code Duplication · Duplicated block (9–12 lines × 9) · ×1
  • Duplicated block (9–12 lines × 9) core/services/b2/src/config.rs:69 — core/services/b2/src/config.rs:69-80 | core/services/cos/src/config.rs:85-96 | core/services/gcs-grpc/src/config.rs:81-89 | core/services/gcs/src/config.rs:128-139 | core/services/obs/src/config.rs:62-73 | core/services/oss/src/config.rs:137-148 | core/services/s3/src/config.rs:410-421 | core/services/tos/src/config.rs:106-117 | core/services/upyun/src/config.rs:57-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times. 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 `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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 · Duplicated block (12 lines × 7) · ×1
  • Duplicated block (12 lines × 7) core/services/cos/src/core.rs:975 — core/services/cos/src/core.rs:975-986 | core/services/dbfs/src/core.rs:285-297 | core/services/ipmfs/src/core.rs:236-248 | core/services/lakefs/src/core.rs:376-388 | core/services/obs/src/core.rs:729-741 | core/services/oss/src/core.rs:1273-1285 | core/services/webhdfs/src/core.rs:487-499 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:975` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 6) · ×1
  • Duplicated block (12 lines × 6) core/services/aliyun-drive/src/reader.rs:67 — core/services/aliyun-drive/src/reader.rs:67-78 | core/services/dropbox/src/reader.rs:65-76 | core/services/gdrive/src/reader.rs:86-97 | core/services/pcloud/src/reader.rs:62-73 | core/services/seafile/src/reader.rs:60-71 | core/services/upyun/src/reader.rs:55-66 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/reader.rs:67` 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 5) · ×1
  • Duplicated block (10–12 lines × 5) core/services/gridfs/src/backend.rs:225 — core/services/gridfs/src/backend.rs:225-234 | core/services/mongodb/src/backend.rs:240-249 | core/services/mysql/src/backend.rs:221-230 | core/services/postgresql/src/backend.rs:213-224 | core/services/surrealdb/src/backend.rs:267-276 — before extracting anything, compare `core/services/gridfs/src/backend.rs` and `core/services/mongodb/src/backend.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/gridfs/src/backend.rs:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (10–12 lines × 3) · ×1
  • Duplicated block (10–12 lines × 3) core/services/cos/src/core.rs:548 — core/services/cos/src/core.rs:548-559 | core/services/gcs/src/core.rs:1064-1074 | core/services/oss/src/core.rs:772-781 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/gcs/src/core.rs` as WHOLE FILES: this scan already matched 8 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/cos/src/core.rs:548` 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.
D4 · Code Duplication · Duplicated block (4–12 lines × 4) · ×1
  • Duplicated block (4–12 lines × 4) core/services/dbfs/src/core.rs:269 — core/services/dbfs/src/core.rs:269-280 | core/services/lakefs/src/core.rs:360-371 | core/services/swift/src/core.rs:902-906 | core/services/webhdfs/src/core.rs:469-472 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/swift/src/core.rs:902` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/dbfs/src/core.rs:269` calls `to_bytes` and `core/services/swift/src/core.rs:902` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–11 lines × 21) · ×1
  • Duplicated block (8–11 lines × 21) core/services/aliyun-drive/src/reader.rs:59 — core/services/aliyun-drive/src/reader.rs:59-68 | core/services/azblob/src/reader.rs:60-69 | core/services/azdls/src/reader.rs:57-66 | core/services/azfile/src/reader.rs:53-60 | core/services/b2/src/reader.rs:52-61 | core/services/cos/src/reader.rs:57-67 | core/services/dropbox/src/reader.rs:57-66 | core/services/ghac/src/reader.rs:48-55 | core/services/ipfs/src/reader.rs:48-56 | core/services/koofr/src/reader.rs:48-55 | core/services/lakefs/src/reader.rs:57-67 | core/services/obs/src/reader.rs:57-67 | core/services/oss/src/reader.rs:57-67 | core/services/pcloud/src/reader.rs:55-63 | core/services/seafile/src/reader.rs:53-61 | core/services/swift/src/reader.rs:57-67 | core/services/tos/src/reader.rs:59-68 | core/services/upyun/src/reader.rs:48-56 | core/services/vercel-artifacts/src/reader.rs:57-67 | core/services/vercel-blob/src/reader.rs:56-64 | core/services/yandex-disk/src/reader.rs:53-60 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/reader.rs:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 10) · ×1
  • Duplicated block (11 lines × 10) core/services/foundationdb/src/writer.rs:47 — core/services/foundationdb/src/writer.rs:47-57 | core/services/gridfs/src/writer.rs:48-58 | core/services/memcached/src/writer.rs:48-58 | core/services/mongodb/src/writer.rs:47-57 | core/services/mysql/src/writer.rs:47-57 | core/services/postgresql/src/writer.rs:47-57 | core/services/redis/src/writer.rs:48-58 | core/services/sqlite/src/writer.rs:46-56 | core/services/surrealdb/src/writer.rs:47-57 | core/services/tikv/src/writer.rs:47-57 — before extracting anything, compare `core/services/foundationdb/src/writer.rs` and `core/services/mongodb/src/writer.rs` as WHOLE FILES: 84% 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 6) · ×1
  • Duplicated block (10–11 lines × 6) core/services/aliyun-drive/src/reader.rs:65 — core/services/aliyun-drive/src/reader.rs:65-74 | core/services/dropbox/src/reader.rs:63-72 | core/services/gdrive/src/reader.rs:74-84 | core/services/pcloud/src/reader.rs:60-69 | core/services/seafile/src/reader.rs:58-67 | core/services/upyun/src/reader.rs:53-62 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/reader.rs:65` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 6) · ×1
  • Duplicated block (9–11 lines × 6) core/services/azdls/src/core.rs:138 — core/services/azdls/src/core.rs:138-146 | core/services/azdls/src/core.rs:361-369 | core/services/http/src/core.rs:67-77 | core/services/http/src/core.rs:116-126 | core/services/swift/src/core.rs:309-317 | core/services/swift/src/core.rs:396-404 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/http/src/core.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/swift/src/core.rs:394` calls `header` and `core/services/azdls/src/core.rs:359` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 4) · ×1
  • Duplicated block (9–11 lines × 4) core/services/azblob/src/core.rs:1338 — core/services/azblob/src/core.rs:1338-1348 | core/services/azdls/src/core.rs:847-855 | core/services/gcs/src/core.rs:2266-2274 | core/services/oss/src/core.rs:1238-1246 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/core.rs:1338` 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.
D4 · Code Duplication · Duplicated block (9–11 lines × 3) · ×1
  • Duplicated block (9–11 lines × 3) core/services/vercel-blob/src/core.rs:96 — core/services/vercel-blob/src/core.rs:96-106 | core/services/vercel-blob/src/core.rs:162-170 | core/services/vercel-blob/src/core.rs:195-203 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) core/services/redb/src/core.rs:70 — core/services/redb/src/core.rs:70-80 | core/services/redb/src/core.rs:90-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/redb/src/core.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. 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.
D4 · Code Duplication · Duplicated block (10 lines × 8) · ×1
  • Duplicated block (10 lines × 8) core/services/compfs/src/config.rs:36 — core/services/compfs/src/config.rs:36-45 | core/services/dashmap/src/config.rs:38-47 | core/services/dropbox/src/config.rs:54-63 | core/services/gdrive/src/config.rs:60-69 | core/services/mini_moka/src/config.rs:53-62 | core/services/monoiofs/src/config.rs:41-50 | core/services/vercel-blob/src/config.rs:50-59 | core/services/yandex-disk/src/config.rs:50-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times. 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 `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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 · Duplicated block (10 lines × 5) · ×1
  • Duplicated block (10 lines × 5) core/services/cos/src/lister.rs:105 — core/services/cos/src/lister.rs:105-114 | core/services/s3/src/lister.rs:142-151 | core/services/s3/src/lister.rs:259-268 | core/services/tos/src/lister.rs:102-111 | core/services/tos/src/lister.rs:215-224 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/s3/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 192 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `core/services/tos/src/lister.rs:211` calls `versions` and `core/services/s3/src/lister.rs:141` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) bindings/dotnet/src/operator.rs:520 — bindings/dotnet/src/operator.rs:520-529 | bindings/dotnet/src/operator.rs:1866-1874 | bindings/dotnet/src/operator.rs:1961-1969 | bindings/dotnet/src/operator.rs:2202-2210 — 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 `bindings/dotnet/src/operator.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.
D4 · Code Duplication · Duplicated block (7–10 lines × 3) · ×1
  • Duplicated block (7–10 lines × 3) core/services/cos/src/core.rs:338 — core/services/cos/src/core.rs:338-347 | core/services/obs/src/core.rs:288-297 | core/services/oss/src/core.rs:671-677 — before extracting anything, compare `core/services/cos/src/core.rs` and `core/services/obs/src/core.rs` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 241 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/core.rs:338` 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 9) · ×1
  • Duplicated block (7–9 lines × 9) core/services/azdls/src/core.rs:141 — core/services/azdls/src/core.rs:141-147 | core/services/azdls/src/core.rs:364-370 | core/services/cos/src/core.rs:161-169 | core/services/http/src/core.rs:71-79 | core/services/http/src/core.rs:120-128 | core/services/obs/src/core.rs:145-153 | core/services/oss/src/core.rs:358-366 | core/services/swift/src/core.rs:312-318 | core/services/swift/src/core.rs:399-405 — before extracting anything, compare `core/services/azdls/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azdls/src/core.rs:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) core/layers/retry/src/lib.rs:747 — core/layers/retry/src/lib.rs:747-755 | core/layers/retry/src/lib.rs:843-851 | core/layers/retry/src/lib.rs:874-882 | core/layers/retry/src/lib.rs:907-915 | core/layers/retry/src/lib.rs:976-984 | core/layers/retry/src/lib.rs:1009-1017 | core/layers/retry/src/lib.rs:1040-1048 | core/layers/retry/src/lib.rs:1071-1079 — all 8 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 `core/layers/retry/src/lib.rs:747` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 8) · ×1
  • Duplicated block (8–9 lines × 8) core/services/azblob/src/core.rs:252 — core/services/azblob/src/core.rs:252-260 | core/services/azdls/src/core.rs:144-151 | core/services/azdls/src/core.rs:367-374 | core/services/cos/src/core.rs:165-173 | core/services/obs/src/core.rs:149-157 | core/services/oss/src/core.rs:362-370 | core/services/swift/src/core.rs:315-322 | core/services/swift/src/core.rs:402-409 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6–9 lines × 5) · ×1
  • Duplicated block (6–9 lines × 5) core/core/src/services/memory/backend.rs:218 — core/core/src/services/memory/backend.rs:218-226 | core/services/persy/src/reader.rs:39-44 | core/services/redb/src/reader.rs:39-44 | core/services/rocksdb/src/reader.rs:39-44 | core/services/sled/src/reader.rs:39-44 — before extracting anything, compare `core/services/persy/src/reader.rs` and `core/services/redb/src/reader.rs` as WHOLE FILES: 84% 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/core/src/services/memory/backend.rs:218` 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 5) · ×1
  • Duplicated block (8–9 lines × 5) core/services/cos/src/writer.rs:80 — core/services/cos/src/writer.rs:80-88 | core/services/cos/src/writer.rs:250-258 | core/services/obs/src/writer.rs:72-80 | core/services/oss/src/writer.rs:70-77 | core/services/oss/src/writer.rs:242-249 — before extracting anything, compare `core/services/cos/src/writer.rs` and `core/services/obs/src/writer.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/cos/src/writer.rs:80` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7–9 lines × 4) · ×1
  • Duplicated block (7–9 lines × 4) core/services/b2/src/core.rs:191 — core/services/b2/src/core.rs:191-197 | core/services/b2/src/core.rs:385-392 | core/services/yandex-disk/src/core.rs:87-95 | core/services/yandex-disk/src/core.rs:142-150 — 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 `core/services/b2/src/core.rs:191` 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, `core/services/yandex-disk/src/core.rs:84` calls `sign` and `core/services/b2/src/core.rs:188` 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.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) core/services/azblob/src/core.rs:478 — core/services/azblob/src/core.rs:478-484 | core/services/azblob/src/core.rs:531-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 23) · ×1
  • Duplicated block (7–8 lines × 23) core/services/aliyun-drive/src/reader.rs:63 — core/services/aliyun-drive/src/reader.rs:63-70 | core/services/azblob/src/reader.rs:64-70 | core/services/azdls/src/reader.rs:61-68 | core/services/azfile/src/reader.rs:55-62 | core/services/b2/src/reader.rs:56-63 | core/services/cos/src/reader.rs:62-69 | core/services/dropbox/src/reader.rs:61-68 | core/services/gdrive/src/reader.rs:72-79 | core/services/ghac/src/reader.rs:50-57 | core/services/ipfs/src/reader.rs:51-58 | core/services/koofr/src/reader.rs:50-57 | core/services/lakefs/src/reader.rs:62-69 | core/services/obs/src/reader.rs:62-69 | core/services/onedrive/src/reader.rs:70-77 | core/services/oss/src/reader.rs:62-69 | core/services/pcloud/src/reader.rs:58-65 | core/services/seafile/src/reader.rs:56-63 | core/services/swift/src/reader.rs:62-69 | core/services/tos/src/reader.rs:63-70 | core/services/upyun/src/reader.rs:51-58 | core/services/vercel-artifacts/src/reader.rs:62-69 | core/services/vercel-blob/src/reader.rs:59-66 | core/services/yandex-disk/src/reader.rs:55-62 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/reader.rs:63` 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 2) · ×1
  • Duplicated block (6–8 lines × 2) core/services/redb/src/core.rs:42 — core/services/redb/src/core.rs:42-47 | core/services/redb/src/core.rs:52-59 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 9) · ×1
  • Duplicated block (7 lines × 9) core/services/cos/src/lister.rs:95 — core/services/cos/src/lister.rs:95-102 | core/services/cos/src/lister.rs:209-215 | core/services/oss/src/lister.rs:97-103 | core/services/oss/src/lister.rs:212-218 | core/services/s3/src/lister.rs:132-139 | core/services/s3/src/lister.rs:249-256 | core/services/s3/src/lister.rs:365-371 | core/services/tos/src/lister.rs:92-99 | core/services/tos/src/lister.rs:201-208 — before extracting anything, compare `core/services/cos/src/lister.rs` and `core/services/oss/src/lister.rs` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `&mut oio::PageContext` in one and `&mut PageContext` 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 · Duplicated block (6–7 lines × 5) · ×1
  • Duplicated block (6–7 lines × 5) core/services/foundationdb/src/reader.rs:39 — core/services/foundationdb/src/reader.rs:39-45 | core/services/gridfs/src/reader.rs:39-44 | core/services/mongodb/src/reader.rs:39-44 | core/services/postgresql/src/reader.rs:39-45 | core/services/surrealdb/src/reader.rs:39-44 — before extracting anything, compare `core/services/foundationdb/src/reader.rs` and `core/services/gridfs/src/reader.rs` as WHOLE FILES: 84% 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/foundationdb/src/reader.rs:39` 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.
D4 · Code Duplication · Duplicated block (6 lines × 13) · ×1
  • Duplicated block (6 lines × 13) core/services/azblob/src/core.rs:252 — core/services/azblob/src/core.rs:252-258 | core/services/azdls/src/core.rs:144-149 | core/services/azdls/src/core.rs:367-372 | core/services/cos/src/core.rs:165-171 | core/services/gcs/src/core.rs:264-270 | core/services/http/src/core.rs:75-81 | core/services/http/src/core.rs:124-130 | core/services/obs/src/core.rs:149-155 | core/services/oss/src/core.rs:362-368 | core/services/s3/src/core.rs:519-524 | core/services/s3/src/core.rs:598-604 | core/services/swift/src/core.rs:315-320 | core/services/swift/src/core.rs:402-407 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/azdls/src/core.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpStat` in one and `OpStat` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gcs/src/core.rs:271` calls `is_full`, `header`, `to_header` and `core/services/azblob/src/core.rs:260` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 10) · ×1
  • Duplicated block (6 lines × 10) core/layers/observe-metrics-common/src/lib.rs:759 — core/layers/observe-metrics-common/src/lib.rs:759-764 | core/layers/observe-metrics-common/src/lib.rs:790-795 | core/layers/observe-metrics-common/src/lib.rs:816-821 | core/layers/observe-metrics-common/src/lib.rs:853-858 | core/layers/observe-metrics-common/src/lib.rs:890-895 | core/layers/observe-metrics-common/src/lib.rs:925-930 | core/layers/observe-metrics-common/src/lib.rs:956-961 | core/layers/observe-metrics-common/src/lib.rs:987-992 | core/layers/observe-metrics-common/src/lib.rs:1018-1023 | core/layers/observe-metrics-common/src/lib.rs:1054-1059 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 8) · ×1
  • Duplicated block (6 lines × 8) bindings/c/src/presign.rs:129 — bindings/c/src/presign.rs:129-134 | bindings/c/src/presign.rs:153-158 | bindings/c/src/presign.rs:181-186 | bindings/c/src/presign.rs:205-210 | bindings/c/src/presign.rs:233-238 | bindings/c/src/presign.rs:256-261 | bindings/c/src/presign.rs:300-305 | bindings/c/src/presign.rs:324-329 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) core/layers/observe-metrics-common/src/lib.rs:790 — core/layers/observe-metrics-common/src/lib.rs:790-795 | core/layers/observe-metrics-common/src/lib.rs:816-821 | core/layers/observe-metrics-common/src/lib.rs:853-858 | core/layers/observe-metrics-common/src/lib.rs:987-992 | core/layers/observe-metrics-common/src/lib.rs:1018-1023 | core/layers/observe-metrics-common/src/lib.rs:1103-1108 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (4–6 lines × 4) · ×1
  • Duplicated block (4–6 lines × 4) core/core/src/raw/ops.rs:145 — core/core/src/raw/ops.rs:145-148 | core/core/src/raw/ops.rs:907-912 | core/core/src/raw/ops.rs:1145-1150 | core/core/src/raw/ops.rs:1325-1328 — 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 `core/core/src/raw/ops.rs:907` 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.
D4 · Code Duplication · Duplicated block (5 lines × 10) · ×1
  • Duplicated block (5 lines × 10) core/services/aliyun-drive/src/core.rs:223 — core/services/aliyun-drive/src/core.rs:223-227 | core/services/aliyun-drive/src/core.rs:299-303 | core/services/aliyun-drive/src/core.rs:337-342 | core/services/aliyun-drive/src/core.rs:388-392 | core/services/aliyun-drive/src/core.rs:417-421 | core/services/aliyun-drive/src/core.rs:447-451 | core/services/aliyun-drive/src/core.rs:469-473 | core/services/aliyun-drive/src/core.rs:499-503 | core/services/aliyun-drive/src/core.rs:527-531 | core/services/aliyun-drive/src/core.rs:564-569 — all 10 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 `core/services/aliyun-drive/src/core.rs:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 11) · ×1
  • Duplicated block (11 lines × 11) core/services/foundationdb/src/deleter.rs:31 — core/services/foundationdb/src/deleter.rs:31-41 | core/services/gridfs/src/deleter.rs:31-41 | core/services/memcached/src/deleter.rs:31-41 | core/services/moka/src/deleter.rs:31-41 | core/services/mongodb/src/deleter.rs:31-41 | core/services/mysql/src/deleter.rs:31-41 | core/services/postgresql/src/deleter.rs:31-41 | core/services/redis/src/deleter.rs:31-41 | core/services/sqlite/src/deleter.rs:28-38 | core/services/surrealdb/src/deleter.rs:31-41 | core/services/tikv/src/deleter.rs:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/foundationdb/src/deleter.rs:31` 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 first that the copies are not typed on the same thing: the declarations holding them bind `core` to `Arc<FoundationdbCore>` in one and `Arc<GridfsCore>` 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 · Duplicated block (8 lines × 58) · ×1
  • Duplicated block (8 lines × 58) core/services/aliyun-drive/src/backend.rs:53 — core/services/aliyun-drive/src/backend.rs:53-61 | core/services/alluxio/src/backend.rs:53-61 | core/services/azblob/src/backend.rs:93-101 | core/services/azdls/src/backend.rs:88-96 | core/services/azfile/src/backend.rs:82-90 | core/services/b2/src/backend.rs:60-68 | core/services/cloudflare-kv/src/backend.rs:85-93 | core/services/compfs/src/backend.rs:40-48 | core/services/cos/src/backend.rs:66-74 | core/services/d1/src/backend.rs:80-88 | core/services/dashmap/src/backend.rs:42-50 | core/services/dbfs/src/backend.rs:46-54 | core/services/dropbox/src/backend.rs:59-67 | core/services/etcd/src/backend.rs:77-85 | core/services/foyer/src/backend.rs:109-116 | core/services/fs/src/backend.rs:41-49 | core/services/ftp/src/backend.rs:59-67 | core/services/gcs/src/backend.rs:76-84 | core/services/gdrive/src/backend.rs:63-71 | core/services/ghac/src/backend.rs:70-78 | core/services/git/src/backend.rs:64-71 | core/services/github/src/backend.rs:57-65 | core/services/goosefs/src/backend.rs:53-60 | core/services/gridfs/src/backend.rs:68-76 | core/services/hdfs-native/src/backend.rs:47-55 | core/services/hdfs/src/backend.rs:42-50 | core/services/hf/src/backend.rs:95-103 | core/services/http/src/backend.rs:91-99 | core/services/ipfs/src/backend.rs:57-65 | core/services/ipmfs/src/backend.rs:94-102 | core/services/koofr/src/backend.rs:60-68 | core/services/memcached/src/backend.rs:64-72 | core/services/mini_moka/src/backend.rs:78-86 | core/services/moka/src/backend.rs:134-141 | core/services/mongodb/src/backend.rs:67-75 | core/services/monoiofs/src/backend.rs:44-51 | core/services/mysql/src/backend.rs:66-74 | core/services/obs/src/backend.rs:66-74 | core/services/onedrive/src/backend.rs:58-66 | core/services/opfs/src/backend.rs:44-51 | core/services/oss/src/backend.rs:73-81 | core/services/pcloud/src/backend.rs:57-65 | core/services/postgresql/src/backend.rs:60-68 | core/services/redis/src/backend.rs:119-127 | core/services/rocksdb/src/backend.rs:49-57 | core/services/s3/src/backend.rs:101-109 | core/services/seafile/src/backend.rs:56-64 | core/services/sftp/src/backend.rs:66-74 | core/services/sled/src/backend.rs:54-62 | core/services/sqlite/src/backend.rs:64-72 | core/services/surrealdb/src/backend.rs:59-67 | core/services/swift/src/backend.rs:79-87 | core/services/tos/src/backend.rs:62-69 | core/services/upyun/src/backend.rs:55-63 | core/services/vercel-blob/src/backend.rs:58-66 | core/services/webdav/src/backend.rs:97-105 | core/services/webhdfs/src/backend.rs:59-67 | core/services/yandex-disk/src/backend.rs:56-64 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) core/services/ftp/src/backend.rs:48 — core/services/ftp/src/backend.rs:48-56 | core/services/http/src/backend.rs:50-58 | core/services/ipmfs/src/backend.rs:107-114 | core/services/seafile/src/backend.rs:69-77 | core/services/sftp/src/backend.rs:54-62 | core/services/webdav/src/backend.rs:56-64 — before extracting anything, compare `core/services/ftp/src/backend.rs` and `core/services/sftp/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 34) · ×1
  • Duplicated block (12 lines × 34) core/services/aliyun-drive/src/backend.rs:348 — core/services/aliyun-drive/src/backend.rs:348-359 | core/services/alluxio/src/backend.rs:161-172 | core/services/azblob/src/backend.rs:562-573 | core/services/azdls/src/backend.rs:426-437 | core/services/azfile/src/backend.rs:355-366 | core/services/b2/src/backend.rs:263-274 | core/services/cloudflare-kv/src/backend.rs:380-391 | core/services/cos/src/backend.rs:366-377 | core/services/d1/src/backend.rs:262-273 | core/services/dropbox/src/backend.rs:282-293 | core/services/gcs/src/backend.rs:504-515 | core/services/gdrive/src/backend.rs:342-353 | core/services/ghac/src/backend.rs:253-264 | core/services/github/src/backend.rs:228-239 | core/services/hf/src/backend.rs:366-377 | core/services/http/src/backend.rs:226-237 | core/services/ipfs/src/backend.rs:178-189 | core/services/ipmfs/src/backend.rs:235-246 | core/services/koofr/src/backend.rs:252-263 | core/services/lakefs/src/backend.rs:244-255 | core/services/obs/src/backend.rs:339-350 | core/services/onedrive/src/backend.rs:262-273 | core/services/oss/src/backend.rs:694-705 | core/services/pcloud/src/backend.rs:233-244 | core/services/s3/src/backend.rs:1353-1364 | core/services/seafile/src/backend.rs:234-245 | core/services/swift/src/backend.rs:284-295 | core/services/tos/src/backend.rs:335-346 | core/services/upyun/src/backend.rs:234-245 | core/services/vercel-artifacts/src/backend.rs:193-204 | core/services/vercel-blob/src/backend.rs:183-194 | core/services/webdav/src/backend.rs:290-301 | core/services/webhdfs/src/backend.rs:333-344 | core/services/yandex-disk/src/backend.rs:224-235 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/gdrive/src/backend.rs:357` calls `build_abs_path` and `core/services/dropbox/src/backend.rs:297` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 22) · ×1
  • Duplicated block (10 lines × 22) core/services/aliyun-drive/src/backend.rs:361 — core/services/aliyun-drive/src/backend.rs:361-370 | core/services/alluxio/src/backend.rs:189-198 | core/services/azdls/src/backend.rs:468-477 | core/services/azfile/src/backend.rs:387-396 | core/services/b2/src/backend.rs:289-298 | core/services/cos/src/backend.rs:399-408 | core/services/dbfs/src/backend.rs:231-240 | core/services/dropbox/src/backend.rs:308-317 | core/services/gdrive/src/backend.rs:370-379 | core/services/github/src/backend.rs:253-262 | core/services/ipmfs/src/backend.rs:260-269 | core/services/koofr/src/backend.rs:277-286 | core/services/lakefs/src/backend.rs:287-296 | core/services/obs/src/backend.rs:372-381 | core/services/onedrive/src/backend.rs:288-297 | core/services/pcloud/src/backend.rs:258-267 | core/services/seafile/src/backend.rs:258-267 | core/services/upyun/src/backend.rs:260-269 | core/services/vercel-blob/src/backend.rs:256-265 | core/services/webdav/src/backend.rs:316-325 | core/services/webhdfs/src/backend.rs:371-380 | core/services/yandex-disk/src/backend.rs:270-279 — before extracting anything, compare `core/services/aliyun-drive/src/backend.rs` and `core/services/alluxio/src/backend.rs` as WHOLE FILES: this scan already matched 3 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) core/services/alluxio/src/backend.rs:200 — core/services/alluxio/src/backend.rs:200-207 | core/services/koofr/src/backend.rs:288-295 | core/services/pcloud/src/backend.rs:269-276 | core/services/seafile/src/backend.rs:269-276 — before extracting anything, compare `core/services/alluxio/src/backend.rs` and `core/services/koofr/src/backend.rs` as WHOLE FILES: this scan already matched 4 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) core/services/azblob/src/backend.rs:599 — core/services/azblob/src/backend.rs:599-608 | core/services/cloudflare-kv/src/backend.rs:406-415 | core/services/gcs/src/backend.rs:540-549 | core/services/oss/src/backend.rs:727-736 | core/services/s3/src/backend.rs:1388-1397 | core/services/swift/src/backend.rs:314-323 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/cloudflare-kv/src/backend.rs` as WHOLE FILES: this scan already matched 3 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.
D4 · Code Duplication · Duplicated block (5 lines × 9) · ×1
  • Duplicated block (5 lines × 9) core/services/azblob/src/core.rs:413 — core/services/azblob/src/core.rs:413-417 | core/services/azblob/src/core.rs:747-751 | core/services/azblob/src/core.rs:774-778 | core/services/cos/src/core.rs:241-246 | core/services/gcs/src/core.rs:446-450 | core/services/gcs/src/core.rs:675-681 | core/services/gcs/src/core.rs:688-693 | core/services/obs/src/core.rs:211-217 | core/services/oss/src/core.rs:608-612 — before extracting anything, compare `core/services/azblob/src/core.rs` and `core/services/cos/src/core.rs` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/core.rs:413` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `&OpWrite` in one and `&OpStat` 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 · Duplicated block (11 lines × 24) · ×1
  • Duplicated block (11 lines × 24) core/services/cacache/src/backend.rs:128 — core/services/cacache/src/backend.rs:128-138 | core/services/dashmap/src/backend.rs:160-170 | core/services/etcd/src/backend.rs:330-340 | core/services/foundationdb/src/backend.rs:170-180 | core/services/foyer/src/backend.rs:285-295 | core/services/ftp/src/backend.rs:254-264 | core/services/goosefs/src/backend.rs:450-460 | core/services/gridfs/src/backend.rs:239-249 | core/services/memcached/src/backend.rs:305-315 | core/services/mini_moka/src/backend.rs:244-254 | core/services/moka/src/backend.rs:306-316 | core/services/mongodb/src/backend.rs:254-264 | core/services/mysql/src/backend.rs:235-245 | core/services/opfs/src/backend.rs:108-118 | core/services/persy/src/backend.rs:195-205 | core/services/postgresql/src/backend.rs:230-240 | core/services/redb/src/backend.rs:216-226 | core/services/redis/src/backend.rs:363-373 | core/services/rocksdb/src/backend.rs:163-173 | core/services/sftp/src/backend.rs:258-268 | core/services/sled/src/backend.rs:187-197 | core/services/sqlite/src/backend.rs:260-270 | core/services/surrealdb/src/backend.rs:281-291 | core/services/tikv/src/backend.rs:190-200 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/foyer/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) core/services/cacache/src/backend.rs:140 — core/services/cacache/src/backend.rs:140-145 | core/services/opfs/src/backend.rs:120-124 | core/services/opfs/src/backend.rs:139-143 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `_args` to `OpList` in one and `OpWrite` 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 · Duplicated block (9 lines × 6) · ×1
  • Duplicated block (9 lines × 6) core/services/cacache/src/backend.rs:147 — core/services/cacache/src/backend.rs:147-155 | core/services/compfs/src/backend.rs:173-181 | core/services/goosefs/src/backend.rs:471-479 | core/services/monoiofs/src/backend.rs:146-154 | core/services/opfs/src/backend.rs:145-153 | core/services/sftp/src/backend.rs:274-282 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/services/sftp/src/backend.rs:284` calls `list`, `Ok`, `clone` and `core/services/compfs/src/backend.rs:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 15) · ×1
  • Duplicated block (10 lines × 15) core/services/dashmap/src/backend.rs:181 — core/services/dashmap/src/backend.rs:181-190 | core/services/foundationdb/src/backend.rs:191-200 | core/services/foyer/src/backend.rs:306-315 | core/services/gridfs/src/backend.rs:260-269 | core/services/memcached/src/backend.rs:326-335 | core/services/moka/src/backend.rs:327-336 | core/services/mongodb/src/backend.rs:275-284 | core/services/mysql/src/backend.rs:256-265 | core/services/persy/src/backend.rs:216-225 | core/services/postgresql/src/backend.rs:251-260 | core/services/redb/src/backend.rs:237-246 | core/services/redis/src/backend.rs:384-393 | core/services/sqlite/src/backend.rs:281-290 | core/services/surrealdb/src/backend.rs:302-311 | core/services/tikv/src/backend.rs:211-220 — before extracting anything, compare `core/services/dashmap/src/backend.rs` and `core/services/foyer/src/backend.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 12) · ×1
  • Duplicated block (8 lines × 12) core/services/foundationdb/src/backend.rs:182 — core/services/foundationdb/src/backend.rs:182-189 | core/services/foyer/src/backend.rs:297-304 | core/services/gridfs/src/backend.rs:251-258 | core/services/memcached/src/backend.rs:317-324 | core/services/mongodb/src/backend.rs:266-273 | core/services/mysql/src/backend.rs:247-254 | core/services/persy/src/backend.rs:207-214 | core/services/postgresql/src/backend.rs:242-249 | core/services/redb/src/backend.rs:228-235 | core/services/redis/src/backend.rs:375-382 | core/services/surrealdb/src/backend.rs:293-300 | core/services/tikv/src/backend.rs:202-209 — before extracting anything, compare `core/services/foundationdb/src/backend.rs` and `core/services/gridfs/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) core/services/azblob/src/backend.rs:667 — core/services/azblob/src/backend.rs:667-677 | core/services/cos/src/backend.rs:606-615 | core/services/gcs/src/backend.rs:618-627 | core/services/obs/src/backend.rs:461-470 — before extracting anything, compare `core/services/azblob/src/backend.rs` and `core/services/cos/src/backend.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `core/services/azblob/src/backend.rs:667` 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.
D4 · Code Duplication · Duplicated block (9 lines × 22) · ×1
  • Duplicated block (9 lines × 22) core/services/aliyun-drive/src/reader.rs:67 — core/services/aliyun-drive/src/reader.rs:67-75 | core/services/azfile/src/reader.rs:59-67 | core/services/b2/src/reader.rs:60-68 | core/services/dropbox/src/reader.rs:65-73 | core/services/gdrive/src/reader.rs:86-94 | core/services/ghac/src/reader.rs:54-62 | core/services/github/src/reader.rs:80-88 | core/services/http/src/reader.rs:62-70 | core/services/ipfs/src/reader.rs:55-63 | core/services/ipmfs/src/reader.rs:52-60 | core/services/koofr/src/reader.rs:54-62 | core/services/lakefs/src/reader.rs:66-74 | core/services/obs/src/reader.rs:66-74 | core/services/pcloud/src/reader.rs:62-70 | core/services/seafile/src/reader.rs:60-68 | core/services/swift/src/reader.rs:66-74 | core/services/tos/src/reader.rs:67-75 | core/services/upyun/src/reader.rs:55-63 | core/services/vercel-artifacts/src/reader.rs:66-74 | core/services/vercel-blob/src/reader.rs:63-71 | core/services/webhdfs/src/reader.rs:60-68 | core/services/yandex-disk/src/reader.rs:59-67 — before extracting anything, compare `core/services/aliyun-drive/src/reader.rs` and `core/services/dropbox/src/reader.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/aliyun-drive/src/reader.rs:67` 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.
D4 · Code Duplication · Duplicated block (7 lines × 10) · ×1
  • Duplicated block (7 lines × 10) core/services/azblob/src/config.rs:109 — core/services/azblob/src/config.rs:109-117 | core/services/b2/src/config.rs:72-80 | core/services/cos/src/config.rs:88-96 | core/services/gcs-grpc/src/config.rs:83-89 | core/services/gcs/src/config.rs:131-139 | core/services/obs/src/config.rs:65-73 | core/services/oss/src/config.rs:140-148 | core/services/s3/src/config.rs:413-421 | core/services/tos/src/config.rs:109-117 | core/services/upyun/src/config.rs:60-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 10 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 10 times. Read the line range as the matched WINDOW rather than a finished unit: at `core/services/azblob/src/config.rs:109` 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 first that the copies are not typed on the same thing: the declarations holding them bind `uri` to `&opendal_core::OperatorUri` in one and `&OperatorUri` 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.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: Node.js 10 bindings/nodejs/package.json:82 — bindings/nodejs/package.json declares Node.js 10 as this project's engines.node, and Node.js 10, support ended 2021-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2021-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D5 · Coupling · Unstable project opendal (Cargo) · ×1
  • Unstable project opendal (Cargo) — opendal (Cargo) has instability 0.83 with 20 dependents.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: OpendalStore (LCOM4 4) integrations/object_store/src/store.rs:182 — OpendalStore's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×1
  • Sync-over-async blocking website/plugins/specifications-docs-plugin.js:79 — `fs.readFileSync` in `includeSpecifications` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 1 typed · 22 plain JS — the untyped files are bindings/nodejs/index.cjs, bindings/nodejs/index.mjs, bindings/nodejs/scripts/header.mjs, bindings/nodejs/tests/service.test.mjs, bindings/nodejs/tests/suites/async.suite.mjs, bindings/nodejs/tests/suites/asyncDeleteOptions.suite.mjs (+16 more).
R10 · Code Duplication · Wholesale file copy (68 identical lines × 2 files) · ×1
  • Wholesale file copy (68 identical lines × 2 files) bindings/nodejs/index.cjs:24 — bindings/nodejs/index.cjs:24 · bindings/nodejs/index.mjs:24 — these 2 files are line-for-line copies of one another — 68 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R8 · Dependency Hygiene · Unused dependency '@swc-node/register' · ×1
  • Unused dependency '@swc-node/register' — Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@swc/core' · ×1
  • Unused dependency '@swc/core' — Declared in bindings/nodejs/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 69 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×25
  • Orphaned file bindings/nodejs/src/layer.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 core/edge/opfs_wasm32/src/lib.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 core/services/memcached/src/binary.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 core/services/webhdfs/src/message.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 integrations/object_store/src/service/writer.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 core/services/foyer/src/core.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 integrations/object_store/src/service/core.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 bindings/ocaml/src/operator/mod.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 bindings/c/src/layer.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 core/services/foyer/src/config.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 core/services/dropbox/src/lister.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 bindings/haskell/src/types.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file bindings/swift/OpenDAL/Sources/OpenDAL/Operator.swift: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 bindings/cpp/src/types.rs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file core/services/b2/src/lister.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 core/services/pcloud/src/lister.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 integrations/object_store/src/amazon_s3.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 core/services/sftp/src/lister.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 core/layers/foyer/src/writer.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 bindings/java/src/main/java/org/apache/opendal/WriteOptions.java: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 integrations/spring/opendal-spring-boot-starter-reactive/src/main/java/org/apache/opendal/spring/config/OpenDALReactiveAutoConfiguration.java: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 core/services/mini_moka/src/writer.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 integrations/object_store/src/service/lister.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 integrations/object_store/src/service/deleter.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 core/services/dashmap/src/writer.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.
X10 · Duplicated predicate · Duplicated predicate · ×14
  • Duplicated predicate core/services/gdrive/src/core.rs:759 — `!self.access_token.is_empty() && self.expires_in > Timestamp::now()` appears character-identically in 2 files — core/services/gdrive/src/core.rs, core/services/onedrive/src/core.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/layers/correctness_check.rs:304 — `args.if_match().is_some() && !capability.copy_with_if_match` appears character-identically in 2 files — core/core/src/layers/correctness_check.rs, core/layers/capability-check/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/gcs/src/backend.rs:577 — `args.if_match().is_some() || args.if_none_match().is_some() || args.if_version_not_match().is_some()` appears character-identically in 2 files — core/services/gcs/src/backend.rs, core/services/gcs/src/composer.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/layers/correctness_check.rs:297 — `args.if_not_exists() && !capability.copy_with_if_not_exists` appears character-identically in 2 files — core/core/src/layers/correctness_check.rs, core/layers/capability-check/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/layers/correctness_check.rs:468 — `args.if_not_exists() && !capability.restore_with_if_not_exists` appears character-identically in 2 files — core/core/src/layers/correctness_check.rs, core/layers/capability-check/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/layers/correctness_check.rs:328 — `args.source_version().is_some() && !capability.copy_with_source_version` appears character-identically in 2 files — core/core/src/layers/correctness_check.rs, core/layers/capability-check/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/layers/correctness_check.rs:465 — `args.version().is_some() && !capability.restore_with_version` appears character-identically in 2 files — core/core/src/layers/correctness_check.rs, core/layers/capability-check/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/smb/src/backend.rs:318 — `op.if_not_exists() && error.kind() == ErrorKind::AlreadyExists` appears character-identically in 2 files — core/services/smb/src/backend.rs, core/services/smb/src/copier.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/pcloud/src/backend.rs:213 — `result == 2010 || result == 2055 || result == 2002` appears character-identically in 2 files — core/services/pcloud/src/backend.rs, core/services/pcloud/src/core.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/cos/src/lister.rs:222 — `self.args.versions() || version_object.is_latest` appears character-identically in 4 files — core/services/cos/src/lister.rs, core/services/oss/src/lister.rs, core/services/s3/src/lister.rs, core/services/tos/src/lister.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/azdls/src/core.rs:819 — `self.caller_condition || delete_match_condition` appears character-identically in 2 files — core/services/azdls/src/core.rs, core/services/gcs/src/core.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/gcs-grpc/src/backend.rs:199 — `self.config.disable_vm_metadata || self.config.service_account.is_some()` appears character-identically in 2 files — core/services/gcs-grpc/src/backend.rs, core/services/gcs/src/backend.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/services/gcs/src/backend.rs:258 — `self.config.skip_signature || self.config.allow_anonymous` appears character-identically in 2 files — core/services/gcs/src/backend.rs, core/services/oss/src/backend.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate core/core/src/raw/oio/copy/block_copy.rs:186 — `self.next_offset < source_size && self.tasks.has_remaining() && scheduled < self.concurrent` appears character-identically in 2 files — core/core/src/raw/oio/copy/block_copy.rs, core/core/src/raw/oio/copy/multipart_copy.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.
D19 · Documentation Quality · Documentation · ×8
  • Documentation: no build, run or usage example bindings/nodejs/npm/darwin-arm64/README.md:1 — `darwin-arm64` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/darwin-arm64/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/darwin-x64/README.md:1 — `darwin-x64` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/darwin-x64/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/linux-arm64-gnu/README.md:1 — `linux-arm64-gnu` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/linux-arm64-gnu/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/linux-arm64-musl/README.md:1 — `linux-arm64-musl` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/linux-arm64-musl/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/linux-x64-gnu/README.md:1 — `linux-x64-gnu` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/linux-x64-gnu/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/linux-x64-musl/README.md:1 — `linux-x64-musl` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/linux-x64-musl/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/win32-arm64-msvc/README.md:1 — `win32-arm64-msvc` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/win32-arm64-msvc/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example bindings/nodejs/npm/win32-x64-msvc/README.md:1 — `win32-x64-msvc` is a published package (`package.json` without `"private": true`) and neither `bindings/nodejs/npm/win32-x64-msvc/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
P10 · Library API & versioning · Public type used only inside its own library · ×4
  • Public type used only inside its own library bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25 — `OpenDAL.Interop.Result.OpenDALResult` (bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net8.0)`, `OpenDAL.Tests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25 — `OpenDAL.Interop.Result.OpenDALResult` (bindings/dotnet/OpenDAL/Interop/Result/OpenDALResult.cs:25) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net10.0)`, `OpenDAL.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library bindings/dotnet/OpenDAL/Utilities.cs:28 — `OpenDAL.Utilities` (bindings/dotnet/OpenDAL/Utilities.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net8.0)`, `OpenDAL.Tests(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library bindings/dotnet/OpenDAL/Utilities.cs:28 — `OpenDAL.Utilities` (bindings/dotnet/OpenDAL/Utilities.cs:28) is public, and the library's own code uses it, but no other project in this repository uses it (read: `GettingStarted(net10.0)`, `OpenDAL.Tests(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
D16 · Bus Factor · Off-boarding risk · ×3
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: core/services/gcs-grpc/src/writer.rs, dev/src/release/bump.rs, scripts/label.py, core/core/src/raw/oio/copy/block_copy.rs, core/core/src/layers/capability_override.rs, core/services/gcs-grpc/src/core.rs, scripts/release_impact.py, core/services/azfile/src/lister.rs (+12 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 17 significant file(s) lose their only recent owner: bindings/dotnet/OpenDAL/Operator.cs, bindings/dotnet/OpenDAL/NativeMethods.cs, bindings/dotnet/src/buffer.rs, bindings/dotnet/src/utils.rs, dev/src/generate/metadata.rs, bindings/dotnet/src/result.rs, bindings/dotnet/OpenDAL/Interop/Buffers/WriteBuffer.cs, bindings/dotnet/OpenDAL/Utilities.cs (+9 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: core/core/src/types/delete/futures_delete_sink.rs, core/core/src/raw/std_io_util.rs, bindings/cpp/src/reader.rs. Pair on, review, or document these before any departure.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (45 single-owned of 613 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 613 of the 965 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: bindings/python/src/layers/retry.rs, bindings/python/src/layers/timeout.rs, core/core/src/raw/http_util/bytes_content_range.rs, core/services/goosefs/src/config.rs, core/services/http/src/reader.rs.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 25 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: bindings/nodejs/src/layer.rs, core/edge/opfs_wasm32/src/lib.rs, core/services/memcached/src/binary.rs, core/services/webhdfs/src/message.rs, integrations/object_store/src/service/writer.rs, core/services/foyer/src/core.rs, integrations/object_store/src/service/core.rs, bindings/ocaml/src/operator/mod.rs (and 17 more) (26 orphaned of 613 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 613 of the 965 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P3 · Security & performance tooling · Dependabot does not watch nuget/maven · ×1
  • Dependabot does not watch nuget/maven REDACTED:19 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `maven`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 31112 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults · Silent fallback default on Err · ×1
  • Silent fallback default on Err core/services/hdfs-native/src/reader.rs:64 — `read_at` turns every `Err` into `Ok(Buffer::new())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Minor — 2 finding(s)
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: opendal-service-azure-common — opendal-service-azure-common: abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: opendal-layer-observe-metrics-common — opendal-layer-observe-metrics-common: abstractness 0.11, instability 0.14, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b3a9de4f0ba84d8c801e88d12da0c46e/history.json --exit-code 0 --source .8artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b3a9de4f0ba84d8c801e88d12da0c46e/tree.json --exit-code 0 --source .4artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude bindings/dart/lib/src --exclude dev/src/generate/dotnet .373artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list bindings/dotnet/opendal.slnx package --vulnerable --include-transitive --format json101artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 2 file(s) — `bindings/dotnet/OpenDAL/Options/NativeOptionsWriter.cs`, `bindings/nodejs/generated.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1db71-a066-71cb-b7e4-eec5718402d7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Email — 1 field(s)
  • KoofrServiceConfig.Email bindings/dotnet/OpenDAL/ServiceConfig/KoofrServiceConfig.cs:34

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md