Public report of grpc/grpc-java, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 23:47 UTC · Survey ID cd_965e8ba4c241405db6fcac587550e120
grpc/grpc-java
Measured 16 November 2026, 23:46 UTC, at code version 3eb72dd
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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: 188,074 lines of product code in 45 projects, tests not counted · Estimated rebuild effort: about 3.5 person-years · Weakest lens: Production Readiness, 50.0
Findings by how serious they are
27 critical1200 serious472 minor
19 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 23:46 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 ▸
54of 54 dimensions measured by tools.
1685of 1699 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
54dimensions across 6 lenses, read from 188,074 lines of product code in 45 projects.
grpc/grpc-java falls short of our standard for production because we found no automated security scanning of the code, its secrets or its dependencies. It scores 59.5 out of 100 and is rated Adequate, and 24 of its 27 critical findings are security problems in the build pipeline and in its servers and containers.
Production Readiness, at 50.0, is the weakest lens and counts most in the score. The best first step is making the two tests that check nothing check their results, worth about 7.2 points. Adding automated security scanning would lift Production Readiness itself, also worth about 7.2. Raising Production Readiness to 70 would lift the score to about 66.6.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four settings leave the servers or containers unsafe, and three pipeline steps run downloads nobody checks. Pinning each tool to an exact version, correcting the unsafe settings and checking each download against a checksum would close these risks. Limiting each secret to its own step would fix the two secrets exposed to more of the pipeline than needed. The two tests that check nothing need to check the result they produce.
The product code is 188,074 lines, about €510,000 to rebuild. Three of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 50.0 to 70, the lowest score rated Strong, the score would rise from 59.5 to about 66.6.
Code composition: what the lines of code are
Product code 47%Tests 53%
Rebuild cost: about €510,000 · Estimate
Cost to rebuild
€170,000 to €850,000, for 2,817 to 8,936 hours of work, about 3.5 person-years for 2 to 7 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 188,074 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with OkHttpReadableBufferTest.java (2).
Raises the score by about 7.2 points · Low effort · Test Quality
2
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.
Raises the score by about 2.6 points · Low effort · ADR Quality
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 €510,000 to build again, about 3.5 person-years of work. Its weakest lens is Production Readiness, at 50.0 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7.2 points for low effort, because it clears the 2 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: 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.
60 modules, with 153 dependencies between them. 4 loops run through 14 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 20 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.
grpc.gcp.observability.logging uses grpc.gcp.observability, so a change to grpc.gcp.observability can break grpc.gcp.observability.logging, while a change to grpc.gcp.observability.logging can't break grpc.gcp.observability.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
582 pairs of types, where a type in grpc.internal uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
95 pairs of types, where a type in grpc.binder.internal uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
47 pairs of types, where a type in grpc.binder.internal uses a type in grpc.internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.binder.internal uses grpc.internal, so a change to grpc.internal can break grpc.binder.internal, while a change to grpc.binder.internal can't break grpc.internal.
Position
Below the diagonal: grpc.binder.internal uses a module listed above it, which is the healthy direction.
5→17 grpc.binder.internal uses grpc.binderpart of a loop✕
Connections
15 pairs of types, where a type in grpc.binder.internal uses a type in grpc.binder.
grpc.binder.internal uses grpc.binder, so a change to grpc.binder can break grpc.binder.internal, while a change to grpc.binder.internal can't break grpc.binder.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27 pairs of types, where a type in grpc.gcp.observability.interceptors uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.gcp.observability.interceptors uses grpc, so a change to grpc can break grpc.gcp.observability.interceptors, while a change to grpc.gcp.observability.interceptors can't break grpc.
Position
Below the diagonal: grpc.gcp.observability.interceptors uses a module listed above it, which is the healthy direction.
grpc.gcp.observability.interceptors uses grpc.gcp.observability.logging, so a change to grpc.gcp.observability.logging can break grpc.gcp.observability.interceptors, while a change to grpc.gcp.observability.interceptors can't break grpc.gcp.observability.logging.
Position
Below the diagonal: grpc.gcp.observability.interceptors uses a module listed above it, which is the healthy direction.
7→19 grpc.gcp.observability.interceptors uses grpc.gcp.observabilitypart of a loop✕
Connections
1 pair of types, where a type in grpc.gcp.observability.interceptors uses a type in grpc.gcp.observability.
grpc.gcp.observability.interceptors uses grpc.gcp.observability, so a change to grpc.gcp.observability can break grpc.gcp.observability.interceptors, while a change to grpc.gcp.observability.interceptors can't break grpc.gcp.observability.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37 pairs of types, where a type in grpc.inprocess uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
41 pairs of types, where a type in grpc.inprocess uses a type in grpc.internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.internal.testing uses grpc.stub, so a change to grpc.stub can break grpc.internal.testing, while a change to grpc.internal.testing can't break grpc.stub.
Position
Below the diagonal: grpc.internal.testing uses a module listed above it, which is the healthy direction.
79 pairs of types, where a type in grpc.netty uses a type in grpc.internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
62 pairs of types, where a type in grpc.okhttp uses a type in grpc.internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
64 pairs of types, where a type in grpc.opentelemetry uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.opentelemetry uses grpc.internal, so a change to grpc.internal can break grpc.opentelemetry, while a change to grpc.opentelemetry can't break grpc.internal.
Position
Below the diagonal: grpc.opentelemetry uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in grpc.testing.protobuf uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.testing.protobuf uses grpc.stub, so a change to grpc.stub can break grpc.testing.protobuf, while a change to grpc.testing.protobuf can't break grpc.stub.
Position
Below the diagonal: grpc.testing.protobuf uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in grpc.xds.client uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.xds.client uses grpc.internal, so a change to grpc.internal can break grpc.xds.client, while a change to grpc.xds.client can't break grpc.internal.
Position
Below the diagonal: grpc.xds.client uses a module listed above it, which is the healthy direction.
grpc.alts.internal uses grpc.internal, so a change to grpc.internal can break grpc.alts.internal, while a change to grpc.alts.internal can't break grpc.internal.
Position
Below the diagonal: grpc.alts.internal uses a module listed above it, which is the healthy direction.
grpc.alts.internal uses grpc.netty, so a change to grpc.netty can break grpc.alts.internal, while a change to grpc.alts.internal can't break grpc.netty.
Position
Below the diagonal: grpc.alts.internal uses a module listed above it, which is the healthy direction.
grpc.binder uses grpc.binder.internal, so a change to grpc.binder.internal can break grpc.binder, while a change to grpc.binder can't break grpc.binder.internal.
Position
Below the diagonal: grpc.binder uses a module listed above it, which is the healthy direction.
grpc.gcp.csm.observability uses grpc, so a change to grpc can break grpc.gcp.csm.observability, while a change to grpc.gcp.csm.observability can't break grpc.
Position
Below the diagonal: grpc.gcp.csm.observability uses a module listed above it, which is the healthy direction.
grpc.gcp.csm.observability uses grpc.opentelemetry, so a change to grpc.opentelemetry can break grpc.gcp.csm.observability, while a change to grpc.gcp.csm.observability can't break grpc.opentelemetry.
Position
Below the diagonal: grpc.gcp.csm.observability uses a module listed above it, which is the healthy direction.
grpc.gcp.observability uses grpc.gcp.observability.logging, so a change to grpc.gcp.observability.logging can break grpc.gcp.observability, while a change to grpc.gcp.observability can't break grpc.gcp.observability.logging.
Position
Below the diagonal: grpc.gcp.observability uses a module listed above it, which is the healthy direction.
grpc.gcp.observability uses grpc.gcp.observability.interceptors, so a change to grpc.gcp.observability.interceptors can break grpc.gcp.observability, while a change to grpc.gcp.observability can't break grpc.gcp.observability.interceptors.
Position
Below the diagonal: grpc.gcp.observability uses a module listed above it, which is the healthy direction.
89 pairs of types, where a type in grpc.protobuf.services uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.protobuf.services uses grpc.internal, so a change to grpc.internal can break grpc.protobuf.services, while a change to grpc.protobuf.services can't break grpc.internal.
Position
Below the diagonal: grpc.protobuf.services uses a module listed above it, which is the healthy direction.
grpc.protobuf.services uses grpc.stub, so a change to grpc.stub can break grpc.protobuf.services, while a change to grpc.protobuf.services can't break grpc.stub.
Position
Below the diagonal: grpc.protobuf.services uses a module listed above it, which is the healthy direction.
grpc.protobuf.services uses grpc.util, so a change to grpc.util can break grpc.protobuf.services, while a change to grpc.protobuf.services can't break grpc.util.
Position
Below the diagonal: grpc.protobuf.services uses a module listed above it, which is the healthy direction.
grpc.s2a.internal.handshaker uses grpc, so a change to grpc can break grpc.s2a.internal.handshaker, while a change to grpc.s2a.internal.handshaker can't break grpc.
Position
Below the diagonal: grpc.s2a.internal.handshaker uses a module listed above it, which is the healthy direction.
grpc.s2a.internal.handshaker uses grpc.internal, so a change to grpc.internal can break grpc.s2a.internal.handshaker, while a change to grpc.s2a.internal.handshaker can't break grpc.internal.
Position
Below the diagonal: grpc.s2a.internal.handshaker uses a module listed above it, which is the healthy direction.
grpc.s2a.internal.handshaker uses grpc.stub, so a change to grpc.stub can break grpc.s2a.internal.handshaker, while a change to grpc.s2a.internal.handshaker can't break grpc.stub.
Position
Below the diagonal: grpc.s2a.internal.handshaker uses a module listed above it, which is the healthy direction.
grpc.s2a.internal.handshaker uses grpc.netty, so a change to grpc.netty can break grpc.s2a.internal.handshaker, while a change to grpc.s2a.internal.handshaker can't break grpc.netty.
Position
Below the diagonal: grpc.s2a.internal.handshaker uses a module listed above it, which is the healthy direction.
grpc.xds.internal.grpcservice uses grpc, so a change to grpc can break grpc.xds.internal.grpcservice, while a change to grpc.xds.internal.grpcservice can't break grpc.
Position
Below the diagonal: grpc.xds.internal.grpcservice uses a module listed above it, which is the healthy direction.
grpc.xds.internal.grpcservice uses grpc.xds.client, so a change to grpc.xds.client can break grpc.xds.internal.grpcservice, while a change to grpc.xds.internal.grpcservice can't break grpc.xds.client.
Position
Below the diagonal: grpc.xds.internal.grpcservice uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security.certprovider uses grpc, so a change to grpc can break grpc.xds.internal.security.certprovider, while a change to grpc.xds.internal.security.certprovider can't break grpc.
Position
Below the diagonal: grpc.xds.internal.security.certprovider uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security.certprovider uses grpc.internal, so a change to grpc.internal can break grpc.xds.internal.security.certprovider, while a change to grpc.xds.internal.security.certprovider can't break grpc.internal.
Position
Below the diagonal: grpc.xds.internal.security.certprovider uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security.certprovider uses grpc.xds.client, so a change to grpc.xds.client can break grpc.xds.internal.security.certprovider, while a change to grpc.xds.internal.security.certprovider can't break grpc.xds.client.
Position
Below the diagonal: grpc.xds.internal.security.certprovider uses a module listed above it, which is the healthy direction.
26→31 grpc.xds.internal.security.certprovider uses grpc.xds.internal.securitypart of a loop✕
Connections
6 pairs of types, where a type in grpc.xds.internal.security.certprovider uses a type in grpc.xds.internal.security.
grpc.xds.internal.security.certprovider uses grpc.xds.internal.security, so a change to grpc.xds.internal.security can break grpc.xds.internal.security.certprovider, while a change to grpc.xds.internal.security.certprovider can't break grpc.xds.internal.security.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→39 grpc.xds.internal.security.certprovider uses grpc.xdspart of a loop✕
Connections
5 pairs of types, where a type in grpc.xds.internal.security.certprovider uses a type in grpc.xds.
grpc.xds.internal.security.certprovider uses grpc.xds, so a change to grpc.xds can break grpc.xds.internal.security.certprovider, while a change to grpc.xds.internal.security.certprovider can't break grpc.xds.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
grpc.s2a uses grpc.s2a.internal.handshaker, so a change to grpc.s2a.internal.handshaker can break grpc.s2a, while a change to grpc.s2a can't break grpc.s2a.internal.handshaker.
Position
Below the diagonal: grpc.s2a uses a module listed above it, which is the healthy direction.
grpc.services uses grpc.protobuf.services, so a change to grpc.protobuf.services can break grpc.services, while a change to grpc.services can't break grpc.protobuf.services.
Position
Below the diagonal: grpc.services uses a module listed above it, which is the healthy direction.
grpc.xds.internal.headermutations uses grpc, so a change to grpc can break grpc.xds.internal.headermutations, while a change to grpc.xds.internal.headermutations can't break grpc.
Position
Below the diagonal: grpc.xds.internal.headermutations uses a module listed above it, which is the healthy direction.
grpc.xds.internal.headermutations uses grpc.xds.internal.grpcservice, so a change to grpc.xds.internal.grpcservice can break grpc.xds.internal.headermutations, while a change to grpc.xds.internal.headermutations can't break grpc.xds.internal.grpcservice.
Position
Below the diagonal: grpc.xds.internal.headermutations uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security uses grpc, so a change to grpc can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.
Position
Below the diagonal: grpc.xds.internal.security uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security uses grpc.internal, so a change to grpc.internal can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.internal.
Position
Below the diagonal: grpc.xds.internal.security uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security uses grpc.netty, so a change to grpc.netty can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.netty.
Position
Below the diagonal: grpc.xds.internal.security uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security uses grpc.xds.client, so a change to grpc.xds.client can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.xds.client.
Position
Below the diagonal: grpc.xds.internal.security uses a module listed above it, which is the healthy direction.
grpc.xds.internal.security uses grpc.xds.internal.security.certprovider, so a change to grpc.xds.internal.security.certprovider can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.xds.internal.security.certprovider.
Position
Below the diagonal: grpc.xds.internal.security uses a module listed above it, which is the healthy direction.
31→39 grpc.xds.internal.security uses grpc.xdspart of a loop✕
Connections
11 pairs of types, where a type in grpc.xds.internal.security uses a type in grpc.xds.
grpc.xds.internal.security uses grpc.xds, so a change to grpc.xds can break grpc.xds.internal.security, while a change to grpc.xds.internal.security can't break grpc.xds.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
115 pairs of types, where a type in grpc.testing.integration uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.testing.integration uses grpc, so a change to grpc can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.stub, so a change to grpc.stub can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.stub.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.internal.testing, so a change to grpc.internal.testing can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.internal.testing.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.util, so a change to grpc.util can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.util.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.gcp.csm.observability, so a change to grpc.gcp.csm.observability can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.gcp.csm.observability.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.protobuf.services, so a change to grpc.protobuf.services can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.protobuf.services.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.testing.integration uses grpc.services, so a change to grpc.services can break grpc.testing.integration, while a change to grpc.testing.integration can't break grpc.services.
Position
Below the diagonal: grpc.testing.integration uses a module listed above it, which is the healthy direction.
grpc.xds.internal uses grpc.services, so a change to grpc.services can break grpc.xds.internal, while a change to grpc.xds.internal can't break grpc.services.
Position
Below the diagonal: grpc.xds.internal uses a module listed above it, which is the healthy direction.
33→39 grpc.xds.internal uses grpc.xdspart of a loop✕
Connections
3 pairs of types, where a type in grpc.xds.internal uses a type in grpc.xds.
48 pairs of types, where a type in grpc.xds.orca uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.android.integrationtest uses grpc, so a change to grpc can break grpc.android.integrationtest, while a change to grpc.android.integrationtest can't break grpc.
Position
Below the diagonal: grpc.android.integrationtest uses a module listed above it, which is the healthy direction.
grpc.android.integrationtest uses grpc.testing.integration, so a change to grpc.testing.integration can break grpc.android.integrationtest, while a change to grpc.android.integrationtest can't break grpc.testing.integration.
Position
Below the diagonal: grpc.android.integrationtest uses a module listed above it, which is the healthy direction.
32 pairs of types, where a type in grpc.xds.internal.extauthz uses a type in grpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.xds.internal.extauthz uses grpc, so a change to grpc can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extauthz uses grpc.internal, so a change to grpc.internal can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.internal.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extauthz uses grpc.stub, so a change to grpc.stub can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.stub.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extauthz uses grpc.xds.internal.grpcservice, so a change to grpc.xds.internal.grpcservice can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.xds.internal.grpcservice.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extauthz uses grpc.xds.internal.headermutations, so a change to grpc.xds.internal.headermutations can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.xds.internal.headermutations.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extauthz uses grpc.xds.internal, so a change to grpc.xds.internal can break grpc.xds.internal.extauthz, while a change to grpc.xds.internal.extauthz can't break grpc.xds.internal.
Position
Below the diagonal: grpc.xds.internal.extauthz uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extproc uses grpc, so a change to grpc can break grpc.xds.internal.extproc, while a change to grpc.xds.internal.extproc can't break grpc.
Position
Below the diagonal: grpc.xds.internal.extproc uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extproc uses grpc.xds.internal.headermutations, so a change to grpc.xds.internal.headermutations can break grpc.xds.internal.extproc, while a change to grpc.xds.internal.extproc can't break grpc.xds.internal.headermutations.
Position
Below the diagonal: grpc.xds.internal.extproc uses a module listed above it, which is the healthy direction.
grpc.xds.internal.extproc uses grpc.xds.internal, so a change to grpc.xds.internal can break grpc.xds.internal.extproc, while a change to grpc.xds.internal.extproc can't break grpc.xds.internal.
Position
Below the diagonal: grpc.xds.internal.extproc uses a module listed above it, which is the healthy direction.
grpc.xds.internal.rbac.engine uses grpc, so a change to grpc can break grpc.xds.internal.rbac.engine, while a change to grpc.xds.internal.rbac.engine can't break grpc.
Position
Below the diagonal: grpc.xds.internal.rbac.engine uses a module listed above it, which is the healthy direction.
grpc.xds.internal.rbac.engine uses grpc.xds.internal, so a change to grpc.xds.internal can break grpc.xds.internal.rbac.engine, while a change to grpc.xds.internal.rbac.engine can't break grpc.xds.internal.
Position
Below the diagonal: grpc.xds.internal.rbac.engine uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in grpc.xds uses a type in grpc.util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
104 pairs of types, where a type in grpc.xds uses a type in grpc.xds.client. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
grpc.xds uses grpc.xds.internal.grpcservice, so a change to grpc.xds.internal.grpcservice can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.grpcservice.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.xds uses grpc.xds.internal.headermutations, so a change to grpc.xds.internal.headermutations can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.headermutations.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.xds uses grpc.xds.internal.security, so a change to grpc.xds.internal.security can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.security.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.xds uses grpc.xds.internal.extauthz, so a change to grpc.xds.internal.extauthz can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.extauthz.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.xds uses grpc.xds.internal.extproc, so a change to grpc.xds.internal.extproc can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.extproc.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.xds uses grpc.xds.internal.rbac.engine, so a change to grpc.xds.internal.rbac.engine can break grpc.xds, while a change to grpc.xds can't break grpc.xds.internal.rbac.engine.
Position
Below the diagonal: grpc.xds uses a module listed above it, which is the healthy direction.
grpc.googleapis uses grpc.internal, so a change to grpc.internal can break grpc.googleapis, while a change to grpc.googleapis can't break grpc.internal.
Position
Below the diagonal: grpc.googleapis uses a module listed above it, which is the healthy direction.
grpc.googleapis uses grpc.xds.client, so a change to grpc.xds.client can break grpc.googleapis, while a change to grpc.googleapis can't break grpc.xds.client.
Position
Below the diagonal: grpc.googleapis uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
32
High / Critical
A02:2025 — Security Misconfiguration
11
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with OkHttpReadableBufferTest.java (2); Resolve the 260 No assertions finding(s) in Test Quality — start with XdsX509TrustManagerTest.java (18), TlsTest.java (12), AltsTsiTest.java (11).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with OkHttpReadableBufferTest.java (2).
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 27
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 — 1200
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 — 472
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 19
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 54 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 — 54 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1685 of 1699 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`jacocoTestReport`), uploaded by `codecov/codecov-action` and a Codecov configuration (codecov.yml) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
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. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because storage.googleapis.com — the registry that answers it — was asked and did not reply (the build stopped because storage.googleapis.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add storage.googleapis.com to the allowlist and re-run — not to build anything.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `testing/src/main/resources/certs/spiffebundle.json`, `testing/src/main/resources/certs/spiffebundle1.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D30 Dependency Vulnerabilities — 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D43 Malicious Dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the 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. Boot via AndroidApp (android-interop-testing). the Android app did not build — `./gradlew :android-interop-testing:assembleDebug` exited 1: specified:unspecified:unspecified
> Could not resolve com.android.tools:r8:8.1.44.
> Could not get resource 'https://storage.googleapis.com/r8-releases/raw/com/android/tools/r8/8.1.44/r8-8.1.…; runtime evidence skipped (launch chosen because android-interop-testing/build.gradle applies the Android application plugin and gradlew builds it).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
IC1 Incompleteness & stubs — 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. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
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").
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TestServiceClient.runTest at 40. A further 1 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 CensusTracingModule.convertStatus at 19 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: census/src/main/java/io/grpc/census/CensusTracingModule.java (CensusTracingModule.convertStatus at 19). 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.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 43 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with TestServiceClient.runTest (cyclomatic 40), FrameHandler.headers (cyclomatic 40), 1.onNext (cyclomatic 39). — 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 43 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 100 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 22 bodies over 30 down to 30 or less in Cognitive Complexity — start with 1.onNext (cognitive 61), ClusterState.edsUpdateToResult (cognitive 55), FrameHandler.headers (cognitive 54). — 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 22 together lifts Cognitive Complexity from 6.5 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.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 38 ClassTooLong finding(s) in God Classes — start with ManagedChannelImpl.java, ExternalProcessorClientInterceptor.java, OkHttpClientTransport.java. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 33 FileTooLong finding(s) in God Classes — start with ManagedChannelImpl.java, ExternalProcessorClientInterceptor.java, OkHttpClientTransport.java. — One of this dimension's main actionable groups (33 warning-level).
Resolve the 18 TooManyMethods finding(s) in God Classes — start with AbstractHttp2Headers.java, ManagedChannelImplBuilder.java, NettyChannelBuilder.java. — One of this dimension's main actionable groups (18 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
177 duplicated block group(s) detected. 5.6 % of the production lines (10,617 of 188,074) are in a reported copy. A further 201 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 86 of the 378 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.
+ 132 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 17 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with TestServiceImpl.java (2), HealthCheckingLoadBalancerFactory.java (2), LogHelper.java. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 13 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ClientAuthInterceptor.java, Utils.java, CallOptions.java. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 12 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with ControlPlaneClient.java, QueryParams.java, NettyClientHandler.java. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
45 production modules (Gradle+Bazel), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 36 of the 45 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with TlsServerCredentials.java (2), CallOptions.java, CachingRlsLbClient.java. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.3 / 10Adequategated by 2 critical 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.
35 skipped (35 with a documented reason), 262 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5833 tests.
No assertions (empty test): markAndResetWithReadShouldSucceed · ×2okhttp/src/test/java/io/grpc/okhttp/OkHttpReadableBufferTest.java:49
No assertions: corruptedCiphertext · ×260alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:144
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with OkHttpReadableBufferTest.java (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 260 No assertions finding(s) in Test Quality — start with XdsX509TrustManagerTest.java (18), TlsTest.java (12), AltsTsiTest.java (11). — One of this dimension's main actionable groups (260 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Secret scan ran and found no leaked secrets. 7 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.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 25 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 77 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 39 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 18 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with ExternalProcessorClientInterceptor.java, BootstrapperImpl.java, CdsLoadBalancer2.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.3 / 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.
38 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java. Counted over 542 of the 976 production source files in this repository: 344 are under the ~2,400-byte size floor this dimension measures over, and the remaining 90 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×4
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.
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.
257 deducted task-comment markers across 188074 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 234 TodoComment finding(s) in Explicit Debt — start with ManagedChannelImpl.java (10), RetriableStream.java (7), OkHttpClientTransport.java (6). — One of this dimension's main actionable groups (234 warning-level).
Resolve the 21 FixmeComment finding(s) in Explicit Debt — start with UndertowTransportTest.java (7), TomcatTransportTest.java (6), JettyTransportTest.java (2). — One of this dimension's main actionable groups (21 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with CsdsServiceTest.java, CallCredentialsApplyingTransportFactory.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 11 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
3 of 36 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×3xds/build.gradle:1
What to do
Resolve the 3 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
74 % of calls cross a namespace and 12 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
32 finding(s): 0 critical, 20 high, 12 medium, 0 low. 15 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 4 file(s) — `REDACTED` (line 57), `buildscripts/kokoro/upload_artifacts.sh`, `examples/gradlew` (line 72, line 173), `gradlew` (line 72, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 15 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (15 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
332 of 632 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is api/src/main/java/io/grpc/InternalChannelz.java. Counted over 632 of the 976 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3census/src/main/java/io/grpc/census/CensusStatsModule.java:1
Concentrated knowledge decay
What to do
Resolve the 329 Orphaned file finding(s) in Knowledge Freshness — start with MetricRecorder.java (2), ChannelzService.java (2), package-info.java (2). — One of this dimension's main actionable groups (329 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with CensusStatsModule.java, BinlogHelper.java, ClientCallImpl.java. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with StatusException.java, CsdsService.java, TestServiceClient.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with FailingClientTransport.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 35 platform declaration(s) and 164 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`ReadableBuffer` declares 16 abstract methods under just 14 distinct name(s): `array`, `arrayOffset`, `byteBufferSupported`, `close`, `getByteBuffer`, `hasArray`, `mark`, `markSupported`, `readBytes`, `readBytes`, `readBytes`, `readInt`, `readUnsignedByte`, `readableBytes`, `reset`, `skipBytes`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — core/src/main/java/io/grpc/internal/ReadableBuffer.java:33
What to do
Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
`getCallOptions` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/CallCredentials.java:116
`newClientStreamTracer` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/ClientStreamTracer.java:159
`createResolvingOobChannelBuilder` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/LoadBalancer.java:1182
`start` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/LoadBalancer.java:1406
`getState` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/ManagedChannel.java:84
`notifyWhenStateChanged` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/ManagedChannel.java:109
`childChannelConfigurator` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface. — api/src/main/java/io/grpc/ManagedChannelBuilder.java:686
`setMaxOutboundMessageSize` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — core/src/main/java/io/grpc/internal/AbstractClientStream.java:544
`metricsExpected` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. (×2) — interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:601, interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:1043
`getNativeSocketOptions` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — netty/src/main/java/io/grpc/netty/NettySocketSupport.java:68
`priority` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1642
`alternateService` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1648
`close` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — services/src/main/java/io/grpc/protobuf/services/BinaryLogProvider.java:107
`parseCallCredentials` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — xds/src/main/java/io/grpc/xds/GrpcBootstrapperImpl.java:212
What to do
Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×40) — binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:113, binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:118, binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:123, …
What to do
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning7.2 / 10Strong✓ 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.
31 public types in `io.grpc.alts.internal` are marked as implementation by their own namespace, folder or name: `AltsClientOptions` (alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:23, `internal`), `Builder` (alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:47, `internal`), `AltsFraming` (alts/src/main/java/io/grpc/alts/internal/AltsFraming.java:26, `internal`), `Parser` (alts/src/main/java/io/grpc/alts/internal/AltsFraming.java:254, `internal`), `AltsHandshakerOptions` (alts/src/main/java/io/grpc/alts/internal/AltsHandshakerOptions.java:22, `internal`), `AltsInternalContext` (alts/src/main/java/io/grpc/alts/internal/AltsInternalContext.java:23, `internal`), `AltsProtocolNegotiator` (alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:54, `internal`), `ClientAltsProtocolNegotiatorFactory` (alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:82, `internal`), and 23 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:23
19 public types in `io.grpc.binder.internal` are marked as implementation by their own namespace, folder or name: `Observer` (binder/src/main/java/io/grpc/binder/internal/Bindable.java:34, `internal`), `BinderClientTransport` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:72, `internal`), `BinderClientTransportFactory` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransportFactory.java:44, `internal`), `Builder` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransportFactory.java:118, `internal`), `BinderServer` (binder/src/main/java/io/grpc/binder/internal/BinderServer.java:63, `internal`), `BinderServerTransport` (binder/src/main/java/io/grpc/binder/internal/BinderServerTransport.java:38, `internal`), `BinderTransport` (binder/src/main/java/io/grpc/binder/internal/BinderTransport.java:81, `internal`), `BinderTransportSecurity` (binder/src/main/java/io/grpc/binder/internal/BinderTransportSecurity.java:51, `internal`), and 11 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — binder/src/main/java/io/grpc/binder/internal/Bindable.java:34
2 public types in `io.grpc.census.internal` are marked as implementation by their own namespace, folder or name: `DeprecatedCensusConstants` (census/src/main/java/io/grpc/census/internal/DeprecatedCensusConstants.java:27, `internal`), `ObservabilityCensusConstants` (census/src/main/java/io/grpc/census/internal/ObservabilityCensusConstants.java:45, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — census/src/main/java/io/grpc/census/internal/DeprecatedCensusConstants.java:27
117 public types in `io.grpc.internal` are marked as implementation by their own namespace, folder or name: `AbstractClientStream` (core/src/main/java/io/grpc/internal/AbstractClientStream.java:50, `internal`), `AbstractReadableBuffer` (core/src/main/java/io/grpc/internal/AbstractReadableBuffer.java:24, `internal`), `AbstractServerStream` (core/src/main/java/io/grpc/internal/AbstractServerStream.java:32, `internal`), `AbstractStream` (core/src/main/java/io/grpc/internal/AbstractStream.java:38, `internal`), `ApplicationThreadDeframer` (core/src/main/java/io/grpc/internal/ApplicationThreadDeframer.java:35, `internal`), `AtomicBackoff` (core/src/main/java/io/grpc/internal/AtomicBackoff.java:29, `internal`), `State` (core/src/main/java/io/grpc/internal/AtomicBackoff.java:48, `internal`), `AuthorityVerifier` (core/src/main/java/io/grpc/internal/AuthorityVerifier.java:22, `internal`), and 109 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — core/src/main/java/io/grpc/internal/AbstractClientStream.java:50
1 public type in `io.grpc.gcp.observability.interceptors` is marked as implementation by its own namespace, folder or name: `FactoryImpl` (gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:62, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:62
1 public type in `io.grpc.opentelemetry.internal` is marked as implementation by its own namespace, folder or name: `OpenTelemetryConstants` (opentelemetry/src/main/java/io/grpc/opentelemetry/internal/OpenTelemetryConstants.java:25, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — opentelemetry/src/main/java/io/grpc/opentelemetry/internal/OpenTelemetryConstants.java:25
1 public type in `io.grpc.s2a.internal.channel` is marked as implementation by its own namespace, folder or name: `S2AHandshakerServiceChannel` (s2a/src/main/java/io/grpc/s2a/internal/channel/S2AHandshakerServiceChannel.java:49, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — s2a/src/main/java/io/grpc/s2a/internal/channel/S2AHandshakerServiceChannel.java:49
4 public types in `io.grpc.s2a.internal.handshaker` are marked as implementation by their own namespace, folder or name: `S2AConnectionException` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AConnectionException.java:21, `internal`), `S2AIdentity` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AIdentity.java:29, `internal`), `S2AProtocolNegotiatorFactory` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AProtocolNegotiatorFactory.java:55, `internal`), `S2AStub` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AStub.java:39, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AConnectionException.java:21
2 public types in `io.grpc.s2a.internal.handshaker.tokenmanager` are marked as implementation by their own namespace, folder or name: `AccessTokenManager` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/AccessTokenManager.java:25, `internal`), `SingleTokenFetcher` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/SingleTokenFetcher.java:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/AccessTokenManager.java:25
1 public type in `io.grpc.protobuf.services.internal` is marked as implementation by its own namespace, folder or name: `HealthCheckingRoundRobinLoadBalancerProvider` (services/src/main/java/io/grpc/protobuf/services/internal/HealthCheckingRoundRobinLoadBalancerProvider.java:34, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — services/src/main/java/io/grpc/protobuf/services/internal/HealthCheckingRoundRobinLoadBalancerProvider.java:34
2 public types in `io.grpc.xds` are marked as implementation by their own namespace, folder or name: `InternalGrpcBootstrapperImpl` (xds/src/main/java/io/grpc/xds/InternalGrpcBootstrapperImpl.java:28, name ends in `Impl`), `ThreadSafeRandomImpl` (xds/src/main/java/io/grpc/xds/ThreadSafeRandom.java:30, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/InternalGrpcBootstrapperImpl.java:28
2 public types in `io.grpc.xds.client` are marked as implementation by their own namespace, folder or name: `BootstrapperImpl` (xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:44, name ends in `Impl`), `XdsClientImpl` (xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:66, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:44
15 public types in `io.grpc.xds.internal` are marked as implementation by their own namespace, folder or name: `GoogleDefaultXdsCredentialsProvider` (xds/src/main/java/io/grpc/xds/internal/GoogleDefaultXdsCredentialsProvider.java:28, `internal`), `HeaderForwardingRulesConfig` (xds/src/main/java/io/grpc/xds/internal/HeaderForwardingRulesConfig.java:28, `internal`), `InsecureXdsCredentialsProvider` (xds/src/main/java/io/grpc/xds/internal/InsecureXdsCredentialsProvider.java:28, `internal`), `MatcherParser` (xds/src/main/java/io/grpc/xds/internal/MatcherParser.java:24, `internal`), `Matchers` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:32, `internal`), `HeaderMatcher` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:38, `internal`), `Range` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:183, `internal`), `FractionMatcher` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:196, `internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/GoogleDefaultXdsCredentialsProvider.java:28
7 public types in `io.grpc.xds.internal.extauthz` are marked as implementation by their own namespace, folder or name: `Decision` (xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzResponse.java:33, `internal`), `CheckRequestBuilder` (xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java:51, `internal`), `CheckResponseHandler` (xds/src/main/java/io/grpc/xds/internal/extauthz/CheckResponseHandler.java:39, `internal`), `ExtAuthzClientCall` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzClientCall.java:41, `internal`), `ExtAuthzConfig` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzConfig.java:35, `internal`), `ExtAuthzParseException` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzParseException.java:23, `internal`), `FailingClientCall` (xds/src/main/java/io/grpc/xds/internal/extauthz/FailingClientCall.java:27, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzResponse.java:33
6 public types in `io.grpc.xds.internal.extproc` are marked as implementation by their own namespace, folder or name: `DataPlaneCallState` (xds/src/main/java/io/grpc/xds/internal/extproc/DataPlaneCallState.java:22, `internal`), `EventType` (xds/src/main/java/io/grpc/xds/internal/extproc/EventType.java:22, `internal`), `ExtProcStreamState` (xds/src/main/java/io/grpc/xds/internal/extproc/ExtProcStreamState.java:22, `internal`), `ExternalProcessorServerInterceptorMetricInstruments` (xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorServerInterceptorMetricInstruments.java:29, `internal`), `ExternalProcessorUtil` (xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:51, `internal`), `KnownLengthInputStream` (xds/src/main/java/io/grpc/xds/internal/extproc/KnownLengthInputStream.java:27, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/extproc/DataPlaneCallState.java:22
7 public types in `io.grpc.xds.internal.grpcservice` are marked as implementation by their own namespace, folder or name: `CachedChannelManager` (xds/src/main/java/io/grpc/xds/internal/grpcservice/CachedChannelManager.java:29, `internal`), `GrpcServiceConfig` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:33, `internal`), `Builder` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:46, `internal`), `GoogleGrpcConfig` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:61, `internal`), `GrpcServiceParseException` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceParseException.java:22, `internal`), `HeaderValue` (xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValue.java:28, `internal`), `HeaderValueValidationUtils` (xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValueValidationUtils.java:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/grpcservice/CachedChannelManager.java:29
10 public types in `io.grpc.xds.internal.headermutations` are marked as implementation by their own namespace, folder or name: `HeaderMutationDisallowedException` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationDisallowedException.java:25, `internal`), `HeaderMutationFilter` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationFilter.java:29, `internal`), `HeaderMutationRulesConfig` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesConfig.java:29, `internal`), `Builder` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesConfig.java:66, `internal`), `HeaderMutationRulesParseException` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesParseException.java:22, `internal`), `HeaderMutationRulesParser` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesParser.java:26, `internal`), `HeaderMutations` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutations.java:24, `internal`), `HeaderMutator` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutator.java:29, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationDisallowedException.java:25
18 public types in `io.grpc.xds.internal.rbac.engine` are marked as implementation by their own namespace, folder or name: `GrpcAuthorizationEngine` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:55, `internal`), `Action` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:84, `internal`), `AuthDecision` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:93, `internal`), `AuthConfig` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:106, `internal`), `PolicyMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:126, `internal`), `AuthenticatedMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:145, `internal`), `DestinationIpMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:179, `internal`), `SourceIpMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:193, `internal`), and 10 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:55
10 public types in `io.grpc.xds.internal.security` are marked as implementation by their own namespace, folder or name: `Closeable` (xds/src/main/java/io/grpc/xds/internal/security/Closeable.java:19, `internal`), `CommonTlsContextUtil` (xds/src/main/java/io/grpc/xds/internal/security/CommonTlsContextUtil.java:23, `internal`), `DynamicSslContextProvider` (xds/src/main/java/io/grpc/xds/internal/security/DynamicSslContextProvider.java:41, `internal`), `ReferenceCountingMap` (xds/src/main/java/io/grpc/xds/internal/security/ReferenceCountingMap.java:39, `internal`), `ValueFactory` (xds/src/main/java/io/grpc/xds/internal/security/ReferenceCountingMap.java:105, `internal`), `SecurityProtocolNegotiators` (xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:58, `internal`), `SslContextProvider` (xds/src/main/java/io/grpc/xds/internal/security/SslContextProvider.java:46, `internal`), `Callback` (xds/src/main/java/io/grpc/xds/internal/security/SslContextProvider.java:50, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/security/Closeable.java:19
10 public types in `io.grpc.xds.internal.security.certprovider` are marked as implementation by their own namespace, folder or name: `CertProviderClientSslContextProviderFactory` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderClientSslContextProviderFactory.java:37, `internal`), `CertProviderServerSslContextProviderFactory` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderServerSslContextProviderFactory.java:36, `internal`), `CertificateProvider` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:45, `internal`), `Watcher` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:50, `internal`), `DistributorWatcher` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:61, `internal`), `CertificateProviderProvider` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderProvider.java:27, `internal`), `CertificateProviderRegistry` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderRegistry.java:28, `internal`), `CertificateProviderStore` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderStore.java:35, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderClientSslContextProviderFactory.java:37
2 public types in `io.grpc.xds.internal.security.trust` are marked as implementation by their own namespace, folder or name: `CertificateUtils` (xds/src/main/java/io/grpc/xds/internal/security/trust/CertificateUtils.java:32, `internal`), `XdsTrustManagerFactory` (xds/src/main/java/io/grpc/xds/internal/security/trust/XdsTrustManagerFactory.java:50, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/internal/security/trust/CertificateUtils.java:32
1 public type in `io.grpc.xds.orca` is marked as implementation by its own namespace, folder or name: `OrcaServiceImpl` (xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:46, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:46
What to do
Hide `io.grpc.alts.internal` (`AltsClientOptions`, `Builder`, `AltsFraming`, `Parser`, `AltsHandshakerOptions`, `AltsInternalContext`, `AltsProtocolNegotiator`, `ClientAltsProtocolNegotiatorFactory`, and 23 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.binder.internal` (`Observer`, `BinderClientTransport`, `BinderClientTransportFactory`, `Builder`, `BinderServer`, `BinderServerTransport`, `BinderTransport`, `BinderTransportSecurity`, and 11 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.census.internal` (`DeprecatedCensusConstants`, `ObservabilityCensusConstants`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.internal` (`AbstractClientStream`, `AbstractReadableBuffer`, `AbstractServerStream`, `AbstractStream`, `ApplicationThreadDeframer`, `AtomicBackoff`, `State`, `AuthorityVerifier`, and 109 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.gcp.observability.interceptors` (`FactoryImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.opentelemetry.internal` (`OpenTelemetryConstants`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.s2a.internal.channel` (`S2AHandshakerServiceChannel`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.s2a.internal.handshaker` (`S2AConnectionException`, `S2AIdentity`, `S2AProtocolNegotiatorFactory`, `S2AStub`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.s2a.internal.handshaker.tokenmanager` (`AccessTokenManager`, `SingleTokenFetcher`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.protobuf.services.internal` (`HealthCheckingRoundRobinLoadBalancerProvider`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds` (`InternalGrpcBootstrapperImpl`, `ThreadSafeRandomImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.client` (`BootstrapperImpl`, `XdsClientImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal` (`GoogleDefaultXdsCredentialsProvider`, `HeaderForwardingRulesConfig`, `InsecureXdsCredentialsProvider`, `MatcherParser`, `Matchers`, `HeaderMatcher`, `Range`, `FractionMatcher`, and 7 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.extauthz` (`Decision`, `CheckRequestBuilder`, `CheckResponseHandler`, `ExtAuthzClientCall`, `ExtAuthzConfig`, `ExtAuthzParseException`, `FailingClientCall`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.extproc` (`DataPlaneCallState`, `EventType`, `ExtProcStreamState`, `ExternalProcessorServerInterceptorMetricInstruments`, `ExternalProcessorUtil`, `KnownLengthInputStream`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.grpcservice` (`CachedChannelManager`, `GrpcServiceConfig`, `Builder`, `GoogleGrpcConfig`, `GrpcServiceParseException`, `HeaderValue`, `HeaderValueValidationUtils`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.headermutations` (`HeaderMutationDisallowedException`, `HeaderMutationFilter`, `HeaderMutationRulesConfig`, `Builder`, `HeaderMutationRulesParseException`, `HeaderMutationRulesParser`, `HeaderMutations`, `HeaderMutator`, and 2 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.rbac.engine` (`GrpcAuthorizationEngine`, `Action`, `AuthDecision`, `AuthConfig`, `PolicyMatcher`, `AuthenticatedMatcher`, `DestinationIpMatcher`, `SourceIpMatcher`, and 10 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.security` (`Closeable`, `CommonTlsContextUtil`, `DynamicSslContextProvider`, `ReferenceCountingMap`, `ValueFactory`, `SecurityProtocolNegotiators`, `SslContextProvider`, `Callback`, and 2 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.security.certprovider` (`CertProviderClientSslContextProviderFactory`, `CertProviderServerSslContextProviderFactory`, `CertificateProvider`, `Watcher`, `DistributorWatcher`, `CertificateProviderProvider`, `CertificateProviderRegistry`, `CertificateProviderStore`, and 2 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.internal.security.trust` (`CertificateUtils`, `XdsTrustManagerFactory`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.grpc.xds.orca` (`OrcaServiceImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Only 25/27 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `gcp-csm-observability`, `gcp-observability/interop`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:2
`examples/example-debug/pom.xml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — examples/example-debug/pom.xml:24
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — util/src/jmh/java/io/grpc/util/HandlerRegistryBenchmark.java
What to do
Run JMH with the GC profiler (`-prof gc`, or addProfiler(GCProfiler.class)) so allocation rate regressions are visible, not just time.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
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 `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) 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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — gcp-csm-observability/src/main/java/io/grpc/gcp/csm/observability/MetadataExchanger.java:182
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/73 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
X10 Duplicated predicate — 22 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean.
AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Android app did not build — `./gradlew :android-interop-testing:assembleDebug` exited 1: specified:unspecified:unspecified
> Could not resolve com.android.tools:r8:8.1.44.
> Could not get resource 'https://storage.googleapis.com/r8-releases/raw/com/android/tools/r8/8.1.44/r8-8.1.…; runtime evidence skipped (launch chosen because android-interop-testing/build.gradle applies the Android application plugin and gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — Dependency currency not established — storage.googleapis.com did not answer
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 4 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
D43 Malicious Dependencies — Scanner failed to run — not a clean result
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 113 value object(s); 2 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (8 CQRS handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 8 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
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
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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): markAndResetWithReadShouldSucceed okhttp/src/test/java/io/grpc/okhttp/OkHttpReadableBufferTest.java:49— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): markAndResetWithReadToReadableBufferShouldSucceed okhttp/src/test/java/io/grpc/okhttp/OkHttpReadableBufferTest.java:55— Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability· Test declared unreliable · ×1
Test declared unreliable: clientCancelFromWithinMessageRead servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:263— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "flaky". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
No assertions: corruptedCiphertext alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:144— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: corruptedCounter alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:139— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: corruptedTag alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:149— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: handshake alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:104— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: handshakeSmallBuffer alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:109— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPong alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:114— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongExactFrameSize alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:119— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallBuffer alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:124— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallFrame alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:129— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallFrameSmallBuffer alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:134— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: reflectedCiphertext alts/src/test/java/io/grpc/alts/internal/AltsTsiTest.java:154— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: corruptedCiphertext alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:201— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: corruptedCounter alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:196— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: corruptedTag alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:206— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: handshake alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:161— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: handshakeSmallBuffer alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:166— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPong alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:171— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongExactFrameSize alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:176— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallBuffer alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:181— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallFrame alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:186— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: pingPongSmallFrameSmallBuffer alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:191— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: reflectedCiphertext alts/src/test/java/io/grpc/alts/internal/FakeTsiTest.java:211— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: handshakeShouldSucceed alts/src/test/java/io/grpc/alts/internal/NettyTsiHandshakerTest.java:82— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: createFrom_noAttributeValue alts/src/test/java/io/grpc/alts/AltsContextUtilTest.java:97— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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: buildsNettyServer alts/src/test/java/io/grpc/alts/AltsServerBuilderTest.java:27— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name 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.
TodoComment xds/src/test/java/io/grpc/xds/LeastRequestLoadBalancerTest.java:505— // TODO This test assumes that existing subchannels are left unchanged while the logic we have — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/test/java/io/grpc/xds/StatefulFilter.java:92— // TODO(sergiitk): to be replaced when name argument passed to the constructor. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/test/java/io/grpc/xds/XdsNameResolverTest.java:148— // TODO(chengyuanzhang): should do tests with ManagedChannelImpl. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/test/java/io/grpc/xds/XdsSecurityClientServerTest.java:366— // TODO: Change this to foo.test.gooogle.fr that needs wildcard matching after — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/test/java/io/grpc/xds/XdsServerBuilderTest.java:65— // TODO (zivy@): move certain tests down to XdsServerWrapperTest or to XdsSecurityClientServerTest — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/ConfigOrError.java:21— // TODO(zdapeng): Unify with ClientXdsClient.StructOrError, or just have parseFilterConfig() throw — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/CsdsService.java:94— // TODO(sergiitk): Add a case covering mutating handleRequest return false to true - to verify — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/EnvoyServerProtoData.java:274— // TODO(sanjaypujare): flatten structure by moving FilterChainMatch class members here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/ExtAuthzFilter.java:49— // TODO(sauravz): Implement ext_authz metrics per gRFC A92 (Section: Metrics). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/ExtAuthzFilter.java:157— // TODO(sauravz): Harden channel lifecycle management before launch. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1601— // TODO: Consider having separate classes handling normal mode and observability mode — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/FaultFilter.java:278— // TODO(zdapeng:) check effective deadline locally, and — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:127— // TODO(zivy): merge into one key and take care of this outer class visibility. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/GrpcBootstrapperImpl.java:215— // TODO(sauravzg): Currently no xDS call credentials providers are implemented (no — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/GrpcXdsTransportFactory.java:139— // TODO(zivy): support waitForReady — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/LoadBalancerConfigFactory.java:250— // TODO: support least_request once it is added to the envoy protos. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:366— // TODO(chengyuanzhang): can be more performance-friendly with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/RoutingUtils.java:34— // TODO(chengyuanzhang): clean up implementations in XdsNameResolver. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/VirtualHost.java:94— // TODO(chengyuanzhang): maybe delete me. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancer.java:106— // TODO(zdapeng): cache removed target for 15 minutes. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/XdsDependencyManager.java:972— // TODO: Once the resolution note API is available, don't throw away the error if — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/XdsNameResolverProvider.java:90— // TODO(jdcormie): java.net.URI#getAuthority incorrectly returns null for both xds:///service — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:82— // TODO(zdapeng): need to discuss how to handle unsupported values. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment xds/src/main/java/io/grpc/xds/XdsServerWrapper.java:93— // TODO(chengyuanzhang): implement cleanup. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
ClassTooLong: ManagedChannelImpl core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:126— ClassTooLong — 1362 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 962 over it, 3.41× 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: ExternalProcessorClientInterceptor xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:100— ClassTooLong — 1209 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 809 over it, 3.02× 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: OkHttpClientTransport okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:134— ClassTooLong — 1033 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 633 over it, 2.58× 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: RetriableStream core/src/main/java/io/grpc/internal/RetriableStream.java:55— ClassTooLong — 942 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 542 over it, 2.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NettyServerHandler netty/src/main/java/io/grpc/netty/NettyServerHandler.java:119— ClassTooLong — 867 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 467 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XdsNameResolver xds/src/main/java/io/grpc/xds/XdsNameResolver.java:101— ClassTooLong — 862 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 462 over it, 2.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TestServiceClient interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:89— ClassTooLong — 817 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 417 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OkHttpServerTransport okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:76— ClassTooLong — 780 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 380 over it, 1.95× 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: GrpclbState grpclb/src/main/java/io/grpc/grpclb/GrpclbState.java:91— ClassTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 377 over it, 1.94× 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: NettyClientHandler netty/src/main/java/io/grpc/netty/NettyClientHandler.java:105— ClassTooLong — 744 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 344 over it, 1.86× 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: InternalChannelz api/src/main/java/io/grpc/InternalChannelz.java:48— ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 301 over it, 1.75× 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: XdsClientImpl xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:66— ClassTooLong — 700 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 300 over it, 1.75× 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: CachingRlsLbClient rls/src/main/java/io/grpc/rls/CachingRlsLbClient.java:88— ClassTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 273 over it, 1.68× 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: ManagedChannelImplBuilder core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:76— ClassTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 219 over it, 1.55× 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: InProcessTransport inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:83— ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 217 over it, 1.54× 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: XdsServerWrapper xds/src/main/java/io/grpc/xds/XdsServerWrapper.java:85— ClassTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 216 over it, 1.54× 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: XdsDependencyManager xds/src/main/java/io/grpc/xds/XdsDependencyManager.java:67— ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 204 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BinlogHelper services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:78— ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 177 over it, 1.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OutlierDetectionLoadBalancer REDACTED:74— ClassTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 176 over it, 1.44× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ServerImpl core/src/main/java/io/grpc/internal/ServerImpl.java:94— ClassTooLong — 573 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 173 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: OpenTelemetryMetricsModule opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:84— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 154 over it, 1.39× 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: CensusStatsModule census/src/main/java/io/grpc/census/CensusStatsModule.java:79— ClassTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 146 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XdsClusterResource xds/src/main/java/io/grpc/xds/XdsClusterResource.java:59— ClassTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 124 over it, 1.31× 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: OkHttpChannelBuilder okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:90— ClassTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 400 significant lines; this is 123 over it, 1.31× 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: WeightedRoundRobinLoadBalancer xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancer.java:92— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 119 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: internal/ManagedChannelImpl.java core/src/main/java/io/grpc/internal/ManagedChannelImpl.java— FileTooLong — 1467 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ManagedChannelImpl (126-2259). The bar is 500 significant lines; this is 967 over it, 2.93× 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: xds/ExternalProcessorClientInterceptor.java xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java— FileTooLong — 1286 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ExternalProcessorClientInterceptor (100-1860). The bar is 500 significant lines; this is 786 over it, 2.57× 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: okhttp/OkHttpClientTransport.java okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java— FileTooLong — 1144 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: OkHttpClientTransport (134-1699). The bar is 500 significant lines; this is 644 over it, 2.29× 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: internal/RetriableStream.java core/src/main/java/io/grpc/internal/RetriableStream.java— FileTooLong — 976 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: RetriableStream (55-1629). The bar is 500 significant lines; this is 476 over it, 1.95× 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: netty/NettyServerHandler.java netty/src/main/java/io/grpc/netty/NettyServerHandler.java— FileTooLong — 962 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: NettyServerHandler (119-1361). The bar is 500 significant lines; this is 462 over it, 1.92× 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: xds/XdsNameResolver.java xds/src/main/java/io/grpc/xds/XdsNameResolver.java— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: XdsNameResolver (101-1353). The bar is 500 significant lines; this is 435 over it, 1.87× 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: integration/TestServiceClient.java interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java— FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: TestServiceClient (89-1158). The bar is 500 significant lines; this is 382 over it, 1.76× 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: grpclb/GrpclbState.java grpclb/src/main/java/io/grpc/grpclb/GrpclbState.java— FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: GrpclbState (91-1282). The bar is 500 significant lines; this is 343 over it, 1.69× 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: okhttp/OkHttpServerTransport.java okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java— FileTooLong — 833 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: OkHttpServerTransport (76-1232). 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: netty/NettyClientHandler.java netty/src/main/java/io/grpc/netty/NettyClientHandler.java— FileTooLong — 825 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: NettyClientHandler (105-1210). The bar is 500 significant lines; this is 325 over it, 1.65× 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: netty/ProtocolNegotiators.java netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java— FileTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 310 over it, 1.62× 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: client/XdsClientImpl.java xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java— FileTooLong — 743 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: XdsClientImpl (66-1125). The bar is 500 significant lines; this is 243 over it, 1.49× 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: rls/CachingRlsLbClient.java rls/src/main/java/io/grpc/rls/CachingRlsLbClient.java— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: CachingRlsLbClient (88-1121). The bar is 500 significant lines; this is 236 over it, 1.47× 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: grpc/InternalChannelz.java api/src/main/java/io/grpc/InternalChannelz.java— FileTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: InternalChannelz (48-1105). The bar is 500 significant lines; this is 226 over it, 1.45× 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: xds/XdsServerWrapper.java xds/src/main/java/io/grpc/xds/XdsServerWrapper.java— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: XdsServerWrapper (85-984). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: inprocess/InProcessTransport.java inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java— FileTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: InProcessTransport (83-1007). The bar is 500 significant lines; this is 180 over it, 1.36× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: internal/ManagedChannelImplBuilder.java core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java— FileTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: ManagedChannelImplBuilder (76-1086). The bar is 500 significant lines; this is 172 over it, 1.34× 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: xds/XdsDependencyManager.java xds/src/main/java/io/grpc/xds/XdsDependencyManager.java— FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: XdsDependencyManager (67-1006). The bar is 500 significant lines; this is 145 over it, 1.29× 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: internal/ServerImpl.java core/src/main/java/io/grpc/internal/ServerImpl.java— FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: ServerImpl (94-1011). The bar is 500 significant lines; this is 133 over it, 1.27× 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: services/BinlogHelper.java services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: BinlogHelper (78-880). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: OutlierDetectionLoadBalancer (74-1152). The bar is 500 significant lines; this is 113 over it, 1.23× 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: opentelemetry/OpenTelemetryMetricsModule.java opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: OpenTelemetryMetricsModule (84-891). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: census/CensusStatsModule.java census/src/main/java/io/grpc/census/CensusStatsModule.java— FileTooLong — 593 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: CensusStatsModule (79-822). The bar is 500 significant lines; this is 93 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: okhttp/OkHttpChannelBuilder.java okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: OkHttpChannelBuilder (90-937). The bar is 500 significant lines; this is 92 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: internal/InternalSubchannel.java core/src/main/java/io/grpc/internal/InternalSubchannel.java— FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: InternalSubchannel (72-897). The bar is 500 significant lines; this is 64 over it, 1.13× 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.
FixmeComment xds/src/main/java/io/grpc/xds/XdsClusterResource.java:700— // FIXME(chengyuanzhang): delete this after UpstreamTlsContext's toString() is fixed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:384— // FIXME(chengyuanzhang): use correct code — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowInteropTest.java:125— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:237— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:243— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:249— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:255— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:267— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/undertowTest/java/io/grpc/servlet/UndertowTransportTest.java:273— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatInteropTest.java:110— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:197— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:203— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:209— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:215— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:221— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/tomcatTest/java/io/grpc/servlet/TomcatTransportTest.java:227— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:207— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:220— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:480— // FIXME: it is likely wrong to pass the transportTracer here as it'll exit the lock's scope — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment core/src/main/java/io/grpc/internal/RetriableStream.java:1160— // FIXME(#7089): hedging case is broken.
TooManyMethods: AbstractHttp2Headers netty/src/main/java/io/grpc/netty/AbstractHttp2Headers.java:26— TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ManagedChannelImplBuilder core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:76— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (core/build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: NettyChannelBuilder netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:84— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (netty/build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: NettyServerBuilder netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:77— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (netty/build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: DataPlaneClientCall xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:276— TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OkHttpClientTransport okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:134— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UdsSocket android/src/main/java/io/grpc/android/UdsSocket.java:42— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: ForwardingChannelBuilder2 api/src/main/java/io/grpc/ForwardingChannelBuilder2.java:37— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: ManagedChannelBuilder api/src/main/java/io/grpc/ManagedChannelBuilder.java:31— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: BinderTransport binder/src/main/java/io/grpc/binder/internal/BinderTransport.java:81— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: NettyClientHandler netty/src/main/java/io/grpc/netty/NettyClientHandler.java:105— 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: OkHttpChannelBuilder okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:90— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (okhttp/build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: NettyServerHandler netty/src/main/java/io/grpc/netty/NettyServerHandler.java:119— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RetriableStream core/src/main/java/io/grpc/internal/RetriableStream.java:55— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Uri api/src/main/java/io/grpc/Uri.java:162— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Metadata api/src/main/java/io/grpc/Metadata.java:58— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Inbound binder/src/main/java/io/grpc/binder/internal/Inbound.java:45— 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: ForwardingServerBuilder api/src/main/java/io/grpc/ForwardingServerBuilder.java:33— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. This type is on a published API surface — a japicmp binary-compatibility gate (build.gradle) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
MethodTooLong: DataPlaneClientCall.start xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:464— MethodTooLong — start runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× 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: TestServiceClient.runTest interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:358— MethodTooLong — runTest runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: TestServiceClient.parseArgs interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:149— MethodTooLong — parseArgs runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: FrameHandler.headers okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:635— MethodTooLong — headers runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: GrpcOpenTelemetry.createMetricInstruments opentelemetry/src/main/java/io/grpc/opentelemetry/GrpcOpenTelemetry.java:203— MethodTooLong — createMetricInstruments runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: 1.onNext xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:483— MethodTooLong — onNext runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: InternalLoggingServerInterceptor.interceptCall gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:86— MethodTooLong — interceptCall runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InternalLoggingChannelInterceptor.interceptCall gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:87— MethodTooLong — interceptCall runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: ManagedChannelImpl.<init> core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:548— MethodTooLong — <init> runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: XdsClusterResource.parseNonAggregateCluster xds/src/main/java/io/grpc/xds/XdsClusterResource.java:218— MethodTooLong — parseNonAggregateCluster runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: BootstrapperImpl.bootstrapBuilder xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:124— MethodTooLong — bootstrapBuilder runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
MethodTooLong: OkHttpClientTransport.start okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:656— MethodTooLong — start runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: ServerTransportListenerImpl.streamCreatedInternal core/src/main/java/io/grpc/internal/ServerImpl.java:473— MethodTooLong — streamCreatedInternal runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: XdsTestClient.runQps interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:331— MethodTooLong — runQps runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: XdsFederationTestClient.parseArgs interop-testing/src/main/java/io/grpc/testing/integration/XdsFederationTestClient.java:65— MethodTooLong — parseArgs runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ClusterState.edsUpdateToResult xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:333— MethodTooLong — edsUpdateToResult runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NameResolverListener.onResult2 core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:1663— MethodTooLong — onResult2 runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: NettyServer.start netty/src/main/java/io/grpc/netty/NettyServer.java:225— MethodTooLong — start runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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.
Duplicated block (10 lines × 2) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:282— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:282-291 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:309-318 — both copies are in the same file, so extract the 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) interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:437— interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:437-446 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:1148-1157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:227— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:227-236 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:131-140 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:227` it begins part-way through the construct above it, so those exact lines 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:546— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:546-555 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:593-602 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:546` it does not close everything it opens, so those 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:587— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:587-596 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:612-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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:587` it does not close everything it opens, so those 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:657— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:657-666 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:443-452 — 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 `okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:657` it begins part-way through the construct above it, so those exact lines 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) xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:266— xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:266-275 | xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:283-292 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:266` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:175— interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:175-184 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:136-145 — before extracting anything, compare `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java` and `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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) netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java:286— netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java:286-295 | okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:777-786 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:366— services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:366-376 | xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.java:410-419 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:422— services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:422-431 | xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.java:460-470 — 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 `response` to `HealthCheckResponse` in one and `OrcaLoadReport` 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 × 2) xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancerProvider.java:164— xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancerProvider.java:164-173 | xds/src/main/java/io/grpc/xds/WrrLocalityLoadBalancer.java:145-154 — 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 (10 lines × 2) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:68— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:68-77 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:94-103 — before extracting anything, compare `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java` and `examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java` 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:184— examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:184-193 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:244-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:148— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:148-157 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:126-135 — before extracting anything, compare `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java` and `examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java: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 (10 lines × 2) examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:202— examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:202-211 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:183-192 — 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 `examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:60— examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:60-69 | examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:74-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java: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.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/CallCredentials.java:116— `getCallOptions` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/ClientStreamTracer.java:159— `newClientStreamTracer` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/LoadBalancer.java:1182— `createResolvingOobChannelBuilder` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/LoadBalancer.java:1406— `start` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/ManagedChannel.java:84— `getState` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/ManagedChannel.java:109— `notifyWhenStateChanged` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception api/src/main/java/io/grpc/ManagedChannelBuilder.java:686— `childChannelConfigurator` is a shipped method whose whole body only throws `UnsupportedOperationException` saying it is not implemented — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — empty body under a TODO marker core/src/main/java/io/grpc/internal/AbstractClientStream.java:544— `setMaxOutboundMessageSize` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it.
Unfinished stub — returns a placeholder under a TODO marker interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:601— `metricsExpected` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
Unfinished stub — returns a placeholder under a TODO marker interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:1043— `metricsExpected` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
Unfinished stub — returns a placeholder under a TODO marker netty/src/main/java/io/grpc/netty/NettySocketSupport.java:68— `getNativeSocketOptions` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
Unfinished stub — empty body under a TODO marker okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1642— `priority` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it.
Unfinished stub — empty body under a TODO marker okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1648— `alternateService` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it.
Unfinished stub — empty body under a TODO marker services/src/main/java/io/grpc/protobuf/services/BinaryLogProvider.java:107— `close` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it.
Unfinished stub — returns a placeholder under a TODO marker xds/src/main/java/io/grpc/xds/GrpcBootstrapperImpl.java:212— `parseCallCredentials` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×13
Edited copy of a member (9 corresponding lines) auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:120— auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:120-129 | auth/src/main/java/io/grpc/auth/GoogleAuthLibraryCallCredentials.java:185-193 — 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) netty/src/main/java/io/grpc/netty/Utils.java:256— netty/src/main/java/io/grpc/netty/Utils.java:256-266 | okhttp/src/main/java/io/grpc/okhttp/Utils.java:57-65 — 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) api/src/main/java/io/grpc/CallOptions.java:433— api/src/main/java/io/grpc/CallOptions.java:433-441 | api/src/main/java/io/grpc/LoadBalancer.java:894-902 — 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) xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:117— xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:117-125 | xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:141-149 — 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) interop-testing/src/main/java/io/grpc/testing/integration/Util.java:77— interop-testing/src/main/java/io/grpc/testing/integration/Util.java:77-86 | interop-testing/src/main/java/io/grpc/testing/integration/Util.java:88-96 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) netty/src/main/java/io/grpc/netty/NettyChannelProvider.java:63— netty/src/main/java/io/grpc/netty/NettyChannelProvider.java:63-71 | okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelProvider.java:68-78 — 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) xds/src/main/java/io/grpc/xds/internal/matcher/CelStringExtractor.java:44— xds/src/main/java/io/grpc/xds/internal/matcher/CelStringExtractor.java:44-52 | xds/src/main/java/io/grpc/xds/internal/matcher/CelMatcher.java:40-50 — 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) netty/src/main/java/io/grpc/netty/NettyServerTransport.java:258— netty/src/main/java/io/grpc/netty/NettyServerTransport.java:258-267 | netty/src/main/java/io/grpc/netty/NettyClientTransport.java:440-448 — 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/src/main/java/io/grpc/internal/KeepAliveManager.java:140— core/src/main/java/io/grpc/internal/KeepAliveManager.java:140-148 | xds/src/main/java/io/grpc/xds/client/LoadStatsManager2.java:348-357 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:413— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:413-421 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:428-436 — 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) REDACTED:64— REDACTED:64-72 | REDACTED:144-152 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientStream.java:285— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientStream.java:285-293 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerStream.java:188-197 — 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) api/src/main/java/io/grpc/TlsChannelCredentials.java:53— api/src/main/java/io/grpc/TlsChannelCredentials.java:53-61 | api/src/main/java/io/grpc/TlsServerCredentials.java:71-80 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×12
Edited copy of a member (13 corresponding lines) xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:101— xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:101-115 | xds/src/main/java/io/grpc/xds/client/LoadReportClient.java:87-99 — 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) api/src/main/java/io/grpc/QueryParams.java:95— api/src/main/java/io/grpc/QueryParams.java:95-110 | interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:364-376 — 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) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:953— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:953-966 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:903-915 — 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) netty/src/main/java/io/grpc/netty/NettyClientStream.java:177— netty/src/main/java/io/grpc/netty/NettyClientStream.java:177-194 | netty/src/main/java/io/grpc/netty/NettyServerStream.java:105-117 — 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) api/src/main/java/io/grpc/TlsChannelCredentials.java:151— api/src/main/java/io/grpc/TlsChannelCredentials.java:151-163 | api/src/main/java/io/grpc/TlsServerCredentials.java:175-187 — 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) xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:134— xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:134-149 | xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:152-164 — 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) alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:125— alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:125-137 | alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:186-198 — 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) xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java:264— xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java:264-279 | xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java:282-294 — 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/src/main/java/io/grpc/internal/DnsNameResolverProvider.java:79— core/src/main/java/io/grpc/internal/DnsNameResolverProvider.java:79-95 | grpclb/src/main/java/io/grpc/grpclb/SecretGrpclbNameResolverProvider.java:63-75 — 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/src/main/java/io/grpc/internal/RetriableStream.java:1522— core/src/main/java/io/grpc/internal/RetriableStream.java:1522-1534 | core/src/main/java/io/grpc/internal/RetriableStream.java:1537-1549 — 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) census/src/main/java/io/grpc/census/CensusTracingModule.java:394— census/src/main/java/io/grpc/census/CensusTracingModule.java:394-406 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:389-401 — 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) examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:55— examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:55-73 | examples/src/main/java/io/grpc/examples/retrying/RetryingHelloWorldClient.java:67-79 — 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) · ×12
Edited copy of a member (11 corresponding lines) api/src/main/java/io/grpc/InternalChannelz.java:145— api/src/main/java/io/grpc/InternalChannelz.java:145-155 | api/src/main/java/io/grpc/InternalChannelz.java:170-180 — 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) xds/src/main/java/io/grpc/xds/GrpcBootstrapperImpl.java:237— xds/src/main/java/io/grpc/xds/GrpcBootstrapperImpl.java:237-247 | xds/src/main/java/io/grpc/xds/GrpcServiceConfigParser.java:323-333 — 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) interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:340— interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:340-350 | interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:352-362 — 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) xds/src/main/java/io/grpc/xds/orca/OrcaMetricReportingServerInterceptor.java:115— xds/src/main/java/io/grpc/xds/orca/OrcaMetricReportingServerInterceptor.java:115-125 | xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:150-160 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) alts/src/main/java/io/grpc/alts/internal/AesGcmAeadCrypter.java:60— alts/src/main/java/io/grpc/alts/internal/AesGcmAeadCrypter.java:60-70 | alts/src/main/java/io/grpc/alts/internal/AesGcmAeadCrypter.java:74-84 — 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) binder/src/main/java/io/grpc/binder/SecurityPolicies.java:445— binder/src/main/java/io/grpc/binder/SecurityPolicies.java:445-455 | binder/src/main/java/io/grpc/binder/SecurityPolicies.java:486-497 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1047— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1047-1057 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:444-454 — 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) REDACTED:101— REDACTED:101-116 | xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:341-351 — 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) opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:874— opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:874-887 | census/src/main/java/io/grpc/census/CensusStatsModule.java:808-818 — 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) binder/src/main/java/io/grpc/binder/internal/MultiMessageClientStream.java:113— binder/src/main/java/io/grpc/binder/internal/MultiMessageClientStream.java:113-123 | binder/src/main/java/io/grpc/binder/internal/MultiMessageServerStream.java:85-95 — 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/src/main/java/io/grpc/internal/DelayedClientCall.java:420— core/src/main/java/io/grpc/internal/DelayedClientCall.java:420-430 | core/src/main/java/io/grpc/internal/DelayedStream.java:271-281 — 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) examples/src/main/java/io/grpc/examples/loadbalance/ExampleNameResolver.java:43— examples/src/main/java/io/grpc/examples/loadbalance/ExampleNameResolver.java:43-53 | examples/src/main/java/io/grpc/examples/nameresolve/ExampleNameResolver.java:41-52 — 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.
Duplicated block (12 lines × 2) core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:73— core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:73-84 | examples/src/main/java/io/grpc/examples/customloadbalance/ShufflingPickFirstLoadBalancer.java:82-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/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:835— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:835-846 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:863-874 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:835` 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:197— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:197-208 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:244-255 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 after the matched lines, `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:210` calls `maxConcurrentCallsPerConnection` and `interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:256` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:267— interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:267-278 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:199-210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) netty/src/main/java/io/grpc/netty/NettyServer.java:170— netty/src/main/java/io/grpc/netty/NettyServer.java:170-181 | netty/src/main/java/io/grpc/netty/NettyServerTransport.java:127-138 — 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. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (12 lines × 2) alts/src/main/java/io/grpc/alts/ComputeEngineChannelCredentials.java:60— alts/src/main/java/io/grpc/alts/ComputeEngineChannelCredentials.java:60-71 | alts/src/main/java/io/grpc/alts/GoogleDefaultChannelCredentials.java:105-116 — 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 (12 lines × 2) binder/src/main/java/io/grpc/binder/internal/MultiMessageClientStream.java:99— binder/src/main/java/io/grpc/binder/internal/MultiMessageClientStream.java:99-110 | binder/src/main/java/io/grpc/binder/internal/MultiMessageServerStream.java:98-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:626— netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:626-637 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:220-231 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:649— netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:649-660 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:240-251 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:72— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:72-83 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthClient.java:73-84 — before extracting anything, compare `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java` and `examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthClient.java` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:193— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:193-204 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:169-180 — before extracting anything, compare `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java` and `examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:80— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:80-91 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java:80-91 — before extracting anything, compare `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java` and `examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java` 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.
Duplicated block (9 lines × 2) alts/src/main/java/io/grpc/alts/internal/AltsHandshakerClient.java:177— alts/src/main/java/io/grpc/alts/internal/AltsHandshakerClient.java:177-185 | alts/src/main/java/io/grpc/alts/internal/AltsHandshakerClient.java:229-237 — both copies are in the same file, so extract the 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, `alts/src/main/java/io/grpc/alts/internal/AltsHandshakerClient.java:238` calls `position`, `getBytesConsumed` and `alts/src/main/java/io/grpc/alts/internal/AltsHandshakerClient.java: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 (9 lines × 2) inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:653— inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:653-661 | inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:882-890 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:653` it begins part-way through the construct above it, so those exact lines 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:829— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:829-837 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:929-937 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:829` it begins part-way through the construct above it, so those 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, `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:826` calls `setResponseSize`, `setPayload`, `newBuilder` and `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:928` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) netty/src/main/java/io/grpc/netty/TcpMetrics.java:204— netty/src/main/java/io/grpc/netty/TcpMetrics.java:204-212 | netty/src/main/java/io/grpc/netty/TcpMetrics.java:215-223 — both copies are in the same file, so extract the 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) xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:159— xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:159-167 | xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:379-387 — 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 `xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:159` it begins part-way through the construct above it, so those 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) xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:240— xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:240-248 | xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:386-394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:240` it does not close everything it opens, so those exact lines 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) api/src/main/java/io/grpc/TlsChannelCredentials.java:288— api/src/main/java/io/grpc/TlsChannelCredentials.java:288-296 | api/src/main/java/io/grpc/TlsServerCredentials.java:307-315 — before extracting anything, compare `api/src/main/java/io/grpc/TlsChannelCredentials.java` and `api/src/main/java/io/grpc/TlsServerCredentials.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) binder/src/main/java/io/grpc/binder/internal/SingleMessageClientStream.java:92— binder/src/main/java/io/grpc/binder/internal/SingleMessageClientStream.java:92-100 | binder/src/main/java/io/grpc/binder/internal/SingleMessageServerStream.java:93-101 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) core/src/main/java/io/grpc/internal/DelayedClientCall.java:483— core/src/main/java/io/grpc/internal/DelayedClientCall.java:483-491 | core/src/main/java/io/grpc/internal/DelayedStream.java:465-473 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:764— core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:764-772 | xds/src/main/java/io/grpc/xds/XdsServerBuilder.java:123-131 — 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/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:764` 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:738— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:738-746 | interop-testing/src/main/java/io/grpc/testing/integration/XdsFederationTestClient.java:285-293 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:673— netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:673-681 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:262-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:471— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:471-477 | netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:478-484 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:95— util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:95-101 | util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:124-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:95` it does not close everything it opens, so those exact lines 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) xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:199— xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:199-205 | xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:588-594 — both copies are in the same file, so extract the 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `proto` to `io.envoyproxy.envoy.config.route.v3.VirtualHost` in one and `io.envoyproxy.envoy.config.route.v3.WeightedCluster.ClusterWeight` 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:419— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:419-425 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:798-804 — 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 `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:419` it begins part-way through the construct above it, so those 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: `Address` names `io.grpc.binarylog.v1.Address` in one and `io.grpc.observabilitylog.v1.Address` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:631— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:631-637 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:415-421 — 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 `okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:631` it begins part-way through the construct above it, so those exact lines 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) api/src/main/java/io/grpc/Grpc.java:158— api/src/main/java/io/grpc/Grpc.java:158-164 | core/src/main/java/io/grpc/internal/GrpcUtil.java:546-552 — 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) api/src/main/java/io/grpc/TlsChannelCredentials.java:303— api/src/main/java/io/grpc/TlsChannelCredentials.java:303-309 | api/src/main/java/io/grpc/TlsServerCredentials.java:322-328 — before extracting anything, compare `api/src/main/java/io/grpc/TlsChannelCredentials.java` and `api/src/main/java/io/grpc/TlsServerCredentials.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) api/src/main/java/io/grpc/TlsChannelCredentials.java:350— api/src/main/java/io/grpc/TlsChannelCredentials.java:350-356 | api/src/main/java/io/grpc/TlsServerCredentials.java:379-385 — before extracting anything, compare `api/src/main/java/io/grpc/TlsChannelCredentials.java` and `api/src/main/java/io/grpc/TlsServerCredentials.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) census/src/main/java/io/grpc/census/GrpcCensus.java:109— census/src/main/java/io/grpc/census/GrpcCensus.java:109-115 | census/src/main/java/io/grpc/census/InternalCensusTracingAccessor.java:38-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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 (7 lines × 2) census/src/main/java/io/grpc/census/GrpcCensus.java:135— census/src/main/java/io/grpc/census/GrpcCensus.java:135-141 | census/src/main/java/io/grpc/census/InternalCensusTracingAccessor.java:49-55 — 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 (7 lines × 2) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:429— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:429-435 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:771-777 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:42— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:42-48 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:44-50 — before extracting anything, compare `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java` 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×11
Edited copy of a member (14 corresponding lines) protobuf/src/main/java/io/grpc/protobuf/StatusProto.java:153— protobuf/src/main/java/io/grpc/protobuf/StatusProto.java:153-166 | stub/src/main/java/io/grpc/stub/ClientCalls.java:359-374 — 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) xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:261— xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:261-275 | xds/src/main/java/io/grpc/xds/internal/security/trust/XdsX509TrustManager.java:279-292 — 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) census/src/main/java/io/grpc/census/CensusTracingModule.java:262— census/src/main/java/io/grpc/census/CensusTracingModule.java:262-277 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:161-174 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientStream.java:158— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientStream.java:158-176 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerStream.java:97-110 — 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) examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsLoadBalancerProvider.java:83— examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsLoadBalancerProvider.java:83-100 | interop-testing/src/main/java/io/grpc/testing/integration/CustomBackendMetricsLoadBalancerProvider.java:86-99 — 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) gcp-csm-observability/src/main/java/io/grpc/gcp/csm/observability/CsmObservability.java:61— gcp-csm-observability/src/main/java/io/grpc/gcp/csm/observability/CsmObservability.java:61-74 | opentelemetry/src/main/java/io/grpc/opentelemetry/GrpcOpenTelemetry.java:158-171 — 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) services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:71— services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:71-85 | services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:117-130 — 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) binder/src/main/java/io/grpc/binder/internal/SingleMessageServerStream.java:104— binder/src/main/java/io/grpc/binder/internal/SingleMessageServerStream.java:104-117 | binder/src/main/java/io/grpc/binder/internal/MultiMessageServerStream.java:112-125 — 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) examples/android/clientcache/app/src/main/java/io/grpc/clientcacheexample/ClientCacheExampleActivity.java:62— examples/android/clientcache/app/src/main/java/io/grpc/clientcacheexample/ClientCacheExampleActivity.java:62-75 | examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:60-74 — 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) examples/src/main/java/io/grpc/examples/deadline/DeadlineClient.java:51— examples/src/main/java/io/grpc/examples/deadline/DeadlineClient.java:51-64 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldClient.java:56-69 — 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) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:146— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:146-160 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:124-137 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×11
Edited copy of a member (7 corresponding lines) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:98— xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:98-104 | xds/src/main/java/io/grpc/xds/WrrLocalityLoadBalancer.java:55-62 — 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) xds/src/main/java/io/grpc/xds/ClusterImplLoadBalancer.java:110— xds/src/main/java/io/grpc/xds/ClusterImplLoadBalancer.java:110-116 | xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java:80-87 — 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) xds/src/main/java/io/grpc/xds/ClusterManagerLoadBalancer.java:62— xds/src/main/java/io/grpc/xds/ClusterManagerLoadBalancer.java:62-70 | xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:87-93 — 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) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:185— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:185-191 | netty/src/main/java/io/grpc/netty/NettyChannelProvider.java:51-58 — 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) netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:164— netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:164-170 | netty/src/main/java/io/grpc/netty/NettyServerProvider.java:44-51 — 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/src/main/java/io/grpc/internal/ChannelLoggerImpl.java:63— core/src/main/java/io/grpc/internal/ChannelLoggerImpl.java:63-69 | xds/src/main/java/io/grpc/xds/client/XdsLogger.java:60-66 — 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/src/main/java/io/grpc/internal/ClientCallImpl.java:711— core/src/main/java/io/grpc/internal/ClientCallImpl.java:711-717 | core/src/main/java/io/grpc/internal/ServerImpl.java:530-537 — 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/src/main/java/io/grpc/internal/JsonUtil.java:57— core/src/main/java/io/grpc/internal/JsonUtil.java:57-63 | core/src/main/java/io/grpc/internal/ServiceConfigUtil.java:151-157 — 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) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:551— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:551-557 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java: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) core/src/main/java/io/grpc/internal/MigratingThreadDeframer.java:120— core/src/main/java/io/grpc/internal/MigratingThreadDeframer.java:120-126 | core/src/main/java/io/grpc/internal/ServerImpl.java:604-611 — 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) examples/src/main/java/io/grpc/examples/cancellation/CancellationServer.java:64— examples/src/main/java/io/grpc/examples/cancellation/CancellationServer.java:64-70 | examples/src/main/java/io/grpc/examples/manualflowcontrol/ManualFlowControlServer.java:143-151 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) api/src/main/java/io/grpc/CallOptions.java:434— api/src/main/java/io/grpc/CallOptions.java:434-441 | api/src/main/java/io/grpc/LoadBalancer.java:895-902 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) authz/src/main/java/io/grpc/authz/AuthorizationPolicyTranslator.java:167— authz/src/main/java/io/grpc/authz/AuthorizationPolicyTranslator.java:167-174 | core/src/main/java/io/grpc/internal/SpiffeUtil.java:193-200 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:648— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:648-655 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:434-441 — 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 `okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:648` it does not close everything it opens, so those exact lines 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1476— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1476-1483 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:832-839 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:118— xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:118-125 | xds/src/main/java/io/grpc/xds/internal/matcher/PredicateEvaluator.java:142-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) api/src/main/java/io/grpc/DoubleHistogramMetricInstrument.java:30— api/src/main/java/io/grpc/DoubleHistogramMetricInstrument.java:30-37 | api/src/main/java/io/grpc/LongHistogramMetricInstrument.java:30-37 — 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 `api/src/main/java/io/grpc/DoubleHistogramMetricInstrument.java:30` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `bucketBoundaries` to `List<Double>` in one and `List<Long>` 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) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:1075— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:1075-1082 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:944-951 — 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 (8 lines × 2) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:288— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:288-295 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:171-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AProtocolNegotiatorFactory.java:186— s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AProtocolNegotiatorFactory.java:186-193 | xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:175-182 — 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) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:95— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:95-102 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java:95-102 — before extracting anything, compare `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java` and `examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java` 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.
Duplicated block (8 lines × 2) examples/src/main/java/io/grpc/examples/deadline/DeadlineServer.java:85— examples/src/main/java/io/grpc/examples/deadline/DeadlineServer.java:85-92 | examples/src/main/java/io/grpc/examples/healthservice/HealthServiceServer.java:87-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2APrivateKeyMethod.java:131— s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2APrivateKeyMethod.java:131-136 | s2a/src/main/java/io/grpc/s2a/internal/handshaker/SslContextFactory.java:129-134 — 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) xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:209— xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:209-214 | xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:225-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) xds/src/main/java/io/grpc/xds/orca/OrcaMetricReportingServerInterceptor.java:116— xds/src/main/java/io/grpc/xds/orca/OrcaMetricReportingServerInterceptor.java:116-122 | xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:153-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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) netty/src/main/java/io/grpc/netty/NettyServerHandler.java:804— netty/src/main/java/io/grpc/netty/NettyServerHandler.java:804-809 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:827-832 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `netty/src/main/java/io/grpc/netty/NettyServerHandler.java:804` it does not close everything it opens, so those 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 `cmd` to `SendGrpcFrameCommand` in one and `SendResponseHeadersCommand` 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, `netty/src/main/java/io/grpc/netty/NettyServerHandler.java:810` calls `release` and `netty/src/main/java/io/grpc/netty/NettyServerHandler.java:833` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:297— inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:297-302 | okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:950-955 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:361— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:361-366 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:282-287 — 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 (6 lines × 2) REDACTED:107— REDACTED:107-112 | xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:344-349 — 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) xds/src/main/java/io/grpc/xds/XdsChannelCredentials.java:39— xds/src/main/java/io/grpc/xds/XdsChannelCredentials.java:39-44 | xds/src/main/java/io/grpc/xds/XdsServerCredentials.java:39-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `fallback` to `ChannelCredentials` in one and `ServerCredentials` 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) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:76— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:76-82 | examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsClient.java:72-77 — 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 `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java: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.
Duplicated block (6 lines × 2) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:60— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:60-65 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:86-91 — before extracting anything, compare `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java` and `examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java` 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 `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java: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.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×9
Edited copy of a member (19 corresponding lines) xds/src/main/java/io/grpc/xds/internal/MatcherParser.java:92— xds/src/main/java/io/grpc/xds/internal/MatcherParser.java:92-110 | xds/src/main/java/io/grpc/xds/internal/MatcherParser.java:114-135 — 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) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:394— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:394-412 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:736-754 — 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) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:950— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:950-969 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:899-917 — 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) api/src/main/java/io/grpc/Metadata.java:402— api/src/main/java/io/grpc/Metadata.java:402-424 | api/src/main/java/io/grpc/Metadata.java:431-449 — 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) examples/src/main/java/io/grpc/examples/header/HeaderClientInterceptor.java:43— examples/src/main/java/io/grpc/examples/header/HeaderClientInterceptor.java:43-64 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:364-382 — 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) xds/src/main/java/io/grpc/xds/FaultFilter.java:387— xds/src/main/java/io/grpc/xds/FaultFilter.java:387-405 | xds/src/main/java/io/grpc/xds/XdsEndpointResource.java:189-210 — 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) binder/src/main/java/io/grpc/binder/internal/IntentNameResolver.java:226— binder/src/main/java/io/grpc/binder/internal/IntentNameResolver.java:226-244 | binder/src/main/java/io/grpc/binder/internal/ServiceBinding.java:272-291 — 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) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:88— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:88-106 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:114-136 — 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) examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:80— examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:80-105 | examples/src/main/java/io/grpc/examples/retrying/RetryingHelloWorldClient.java:88-106 — 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 (10 corresponding lines) · ×9
Edited copy of a member (10 corresponding lines) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1474— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1474-1483 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:830-839 — 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) netty/src/main/java/io/grpc/netty/UdsNettyChannelProvider.java:56— netty/src/main/java/io/grpc/netty/UdsNettyChannelProvider.java:56-65 | netty/src/main/java/io/grpc/netty/UdsNettyChannelProvider.java:70-80 — 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) xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:207— xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:207-216 | xds/src/main/java/io/grpc/xds/client/ControlPlaneClient.java:223-232 — 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/src/main/java/io/grpc/internal/JsonUtil.java:244— core/src/main/java/io/grpc/internal/JsonUtil.java:244-253 | core/src/main/java/io/grpc/internal/JsonUtil.java:260-270 — 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) util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:70— util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:70-79 | util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:82-91 — 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) xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValueValidationUtils.java:44— xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValueValidationUtils.java:44-53 | xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValueValidationUtils.java:59-68 — 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) testing/src/main/java/io/grpc/internal/testing/TestUtils.java:129— testing/src/main/java/io/grpc/internal/testing/TestUtils.java:129-138 | testing/src/main/java/io/grpc/testing/TestUtils.java:101-110 — 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) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:791— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:791-801 | okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:582-591 — 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) examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java:63— examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java:63-78 | examples/src/main/java/io/grpc/examples/grpcproxy/GrpcProxy.java:223-232 — 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· Edited copy of a member (16 corresponding lines) · ×8
Edited copy of a member (16 corresponding lines) netty/src/main/java/io/grpc/netty/NettyServerHandler.java:803— netty/src/main/java/io/grpc/netty/NettyServerHandler.java:803-820 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:826-841 — 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) api/src/main/java/io/grpc/NameResolverRegistry.java:102— api/src/main/java/io/grpc/NameResolverRegistry.java:102-120 | xds/src/main/java/io/grpc/xds/XdsCredentialsRegistry.java:88-103 — 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:281— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:281-296 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:308-323 — 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) protobuf-lite/src/main/java/io/grpc/protobuf/lite/ProtoLiteUtils.java:113— protobuf-lite/src/main/java/io/grpc/protobuf/lite/ProtoLiteUtils.java:113-128 | services/src/main/java/io/grpc/protobuf/services/BinaryLogProvider.java:177-192 — 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/src/main/java/io/grpc/internal/CallCredentialsApplyingTransportFactory.java:189— core/src/main/java/io/grpc/internal/CallCredentialsApplyingTransportFactory.java:189-204 | core/src/main/java/io/grpc/internal/CallCredentialsApplyingTransportFactory.java:208-224 — 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) alts/src/main/java/io/grpc/alts/AltsChannelCredentials.java:95— alts/src/main/java/io/grpc/alts/AltsChannelCredentials.java:95-111 | alts/src/main/java/io/grpc/alts/AltsServerCredentials.java:78-93 — 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:232— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:232-247 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:227-242 — 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:250— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:250-265 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:245-260 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×8
Edited copy of a member (12 corresponding lines) api/src/main/java/io/grpc/ManagedChannelRegistry.java:84— api/src/main/java/io/grpc/ManagedChannelRegistry.java:84-95 | api/src/main/java/io/grpc/ServerRegistry.java:77-88 — 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) api/src/main/java/io/grpc/Status.java:396— api/src/main/java/io/grpc/Status.java:396-408 | api/src/main/java/io/grpc/Status.java:416-427 — 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) inprocess/src/main/java/io/grpc/inprocess/InProcessServer.java:83— inprocess/src/main/java/io/grpc/inprocess/InProcessServer.java:83-94 | inprocess/src/main/java/io/grpc/inprocess/InProcessServer.java:126-137 — 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) okhttp/src/main/java/io/grpc/okhttp/AsyncSink.java:132— okhttp/src/main/java/io/grpc/okhttp/AsyncSink.java:132-149 | okhttp/src/main/java/io/grpc/okhttp/AsyncSink.java:169-180 — 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) services/src/main/java/io/grpc/protobuf/services/ProtoReflectionServiceV1.java:479— services/src/main/java/io/grpc/protobuf/services/ProtoReflectionServiceV1.java:479-492 | services/src/main/java/io/grpc/protobuf/services/ProtoReflectionServiceV1.java:511-522 — 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) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:396— xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:396-407 | xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:422-436 — 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/src/main/java/io/grpc/internal/DelayedClientCall.java:570— core/src/main/java/io/grpc/internal/DelayedClientCall.java:570-581 | core/src/main/java/io/grpc/internal/DelayedStream.java:490-501 — 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) examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:113— examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:113-124 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:71-84 — 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.
Low cohesion: CallOptions (LCOM4 12) api/src/main/java/io/grpc/CallOptions.java:42— CallOptions's methods fall into 12 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 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 8) rls/src/main/java/io/grpc/rls/CachingRlsLbClient.java:857— Builder's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 7) REDACTED:965— Builder's methods fall into 7 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 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TlsServerCredentials (LCOM4 4) api/src/main/java/io/grpc/TlsServerCredentials.java:40— TlsServerCredentials's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 4) api/src/main/java/io/grpc/TlsServerCredentials.java:241— Builder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Builder (LCOM4 4) api/src/main/java/io/grpc/Uri.java:668— Builder's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BinderClientTransport (LCOM4 4) binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:72— BinderClientTransport's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: OpenTelemetryTracingModule (LCOM4 4) opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:62— OpenTelemetryTracingModule's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×7
Edited copy of a member (15 corresponding lines) rls/src/main/java/io/grpc/rls/LinkedHashLruCache.java:216— rls/src/main/java/io/grpc/rls/LinkedHashLruCache.java:216-238 | rls/src/main/java/io/grpc/rls/LinkedHashLruCache.java:265-279 — 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) interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:222— interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:222-236 | interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:238-252 — 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/src/main/java/io/grpc/internal/Http2Ping.java:124— core/src/main/java/io/grpc/internal/Http2Ping.java:124-140 | core/src/main/java/io/grpc/internal/Http2Ping.java:148-162 — 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) api/src/main/java/io/grpc/SynchronizationContext.java:151— api/src/main/java/io/grpc/SynchronizationContext.java:151-165 | api/src/main/java/io/grpc/SynchronizationContext.java:187-202 — 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) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:668— xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:668-682 | xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:862-879 — 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) census/src/main/java/io/grpc/census/CensusStatsModule.java:485— census/src/main/java/io/grpc/census/CensusStatsModule.java:485-502 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:503-517 — 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) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:109— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:109-123 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:139-153 — 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 (8 corresponding lines) · ×7
Edited copy of a member (8 corresponding lines) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:470— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:470-477 | netty/src/main/java/io/grpc/netty/NettyServerBuilder.java:477-484 — 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) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1719— xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1719-1726 | xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1738-1745 — 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) services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:162— services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:162-169 | util/src/main/java/io/grpc/util/HealthProducerHelper.java:102-110 — 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) census/src/main/java/io/grpc/census/CensusStatsModule.java:252— census/src/main/java/io/grpc/census/CensusStatsModule.java:252-259 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:216-224 — 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/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:98— core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:98-107 | examples/src/main/java/io/grpc/examples/customloadbalance/ShufflingPickFirstLoadBalancer.java:105-112 — 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) census/src/main/java/io/grpc/census/CensusStatsModule.java:141— census/src/main/java/io/grpc/census/CensusStatsModule.java:141-148 | census/src/main/java/io/grpc/census/CensusTracingModule.java:113-120 — 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) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:136— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:136-144 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:115-122 — 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.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×6
Edited copy of a member (26 corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:409— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:409-434 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:787-812 — 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:816— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:816-846 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:849-874 — 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) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:727— xds/src/main/java/io/grpc/xds/XdsNameResolver.java:727-752 | xds/src/main/java/io/grpc/xds/XdsServerWrapper.java:627-652 — 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) xds/src/main/java/io/grpc/xds/FaultFilter.java:323— xds/src/main/java/io/grpc/xds/FaultFilter.java:323-348 | xds/src/main/java/io/grpc/xds/FaultFilter.java:351-385 — 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) netty/src/main/java/io/grpc/netty/NettyClientTransport.java:413— netty/src/main/java/io/grpc/netty/NettyClientTransport.java:413-438 | netty/src/main/java/io/grpc/netty/NettyServerTransport.java:231-256 — 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) examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsServer.java:51— examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsServer.java:51-83 | examples/src/main/java/io/grpc/examples/healthservice/HealthServiceServer.java:42-67 — 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 (17 corresponding lines) · ×6
Edited copy of a member (17 corresponding lines) xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:155— xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:155-171 | xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:370-396 — 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) netty/src/main/java/io/grpc/netty/NettyServerHandler.java:588— netty/src/main/java/io/grpc/netty/NettyServerHandler.java:588-604 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:606-626 — 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) netty/src/main/java/io/grpc/netty/InternalNettyChannelCredentials.java:41— netty/src/main/java/io/grpc/netty/InternalNettyChannelCredentials.java:41-62 | netty/src/main/java/io/grpc/netty/InternalNettyServerCredentials.java:52-68 — 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) binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:190— binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:190-215 | binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:418-434 — 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/src/main/java/io/grpc/internal/AbstractServerStream.java:312— core/src/main/java/io/grpc/internal/AbstractServerStream.java:312-329 | core/src/main/java/io/grpc/internal/AbstractServerStream.java:336-352 — 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) examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:127— examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:127-143 | examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:146-178 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) binder/src/main/java/io/grpc/binder/LifecycleOnDestroyHelper.java:46— binder/src/main/java/io/grpc/binder/LifecycleOnDestroyHelper.java:46-60 | binder/src/main/java/io/grpc/binder/LifecycleOnDestroyHelper.java:70-84 — both copies are in the same file, so extract the 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 (15 lines × 2) census/src/main/java/io/grpc/census/CensusTracingModule.java:486— census/src/main/java/io/grpc/census/CensusTracingModule.java:486-500 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:545-559 — 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 `census/src/main/java/io/grpc/census/CensusTracingModule.java:486` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: `Status` names `io.grpc.Status` in one and `io.opencensus.trace.Status` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:173— util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:173-187 | util/src/main/java/io/grpc/util/AdvancedTlsX509TrustManager.java:256-270 — 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 `util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java: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 (15 lines × 2) xds/src/main/java/io/grpc/xds/RoutingUtils.java:176— xds/src/main/java/io/grpc/xds/RoutingUtils.java:176-190 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:635-649 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:114— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:114-128 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:94-108 — 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 (15 lines × 2) examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:86— examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:86-100 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:68-82 — 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 `examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java: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 (11 lines × 2) core/src/main/java/io/grpc/internal/RetriableStream.java:199— core/src/main/java/io/grpc/internal/RetriableStream.java:199-209 | core/src/main/java/io/grpc/internal/RetriableStream.java:928-938 — both copies are in the same file, so extract the 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) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:821— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:821-831 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:851-861 — both copies are in the same file, so extract the 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) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:906— xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:906-916 | xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:919-929 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:906` it begins part-way through the construct above it, so those 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 (11 lines × 2) REDACTED:104— REDACTED:104-114 | xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:341-351 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:434— services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:434-444 | xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.java:473-484 — 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) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:110— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:110-120 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:140-150 — before extracting anything, compare `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java` and `examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java` 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.
Duplicated block (5 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/SoakClient.java:290— interop-testing/src/main/java/io/grpc/testing/integration/SoakClient.java:290-294 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:359-366 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/SoakClient.java:290` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:449— xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:449-454 | xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:479-483 — both copies are in the same file, so extract the 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 (5 lines × 2) core/src/main/java/io/grpc/internal/CertificateUtils.java:101— core/src/main/java/io/grpc/internal/CertificateUtils.java:101-105 | util/src/main/java/io/grpc/util/CertificateUtils.java:51-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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 (5 lines × 2) api/src/main/java/io/grpc/ClientInterceptors.java:58— api/src/main/java/io/grpc/ClientInterceptors.java:58-62 | api/src/main/java/io/grpc/ServerInterceptors.java:64-68 — 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 `api/src/main/java/io/grpc/ClientInterceptors.java:58` 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `interceptors` to `List<? extends ClientInterceptor>` in one and `List<? extends ServerInterceptor>` 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/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:785— core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:785-789 | core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:800-804 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift 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/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:785` it does not close everything it opens, so those exact lines 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) examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceServer.java:85— examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceServer.java:85-90 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveServer.java:88-92 — 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· Edited copy of a member (5 corresponding lines) · ×5
Edited copy of a member (5 corresponding lines) services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:83— services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:83-87 | xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.java:231-236 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) netty/src/main/java/io/grpc/netty/CreateStreamCommand.java:35— netty/src/main/java/io/grpc/netty/CreateStreamCommand.java:35-40 | netty/src/main/java/io/grpc/netty/SendResponseHeadersCommand.java:32-36 — 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) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1087— okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:1087-1091 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:345-349 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:1178— netty/src/main/java/io/grpc/netty/NettyClientHandler.java:1178-1182 | netty/src/main/java/io/grpc/netty/NettyServerHandler.java:1255-1259 — 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) examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:52— examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:52-56 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldClient.java:45-49 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:224— interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:224-236 | interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:240-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202— xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202-1214 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1248-1260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202` it does not close everything it opens, so those 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 (13 lines × 2) xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:203— xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:203-215 | xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:369-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.
Duplicated block (13 lines × 2) api/src/main/java/io/grpc/TlsChannelCredentials.java:258— api/src/main/java/io/grpc/TlsChannelCredentials.java:258-270 | api/src/main/java/io/grpc/TlsServerCredentials.java:277-289 — before extracting anything, compare `api/src/main/java/io/grpc/TlsChannelCredentials.java` and `api/src/main/java/io/grpc/TlsServerCredentials.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:48— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:48-60 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java:48-60 — before extracting anything, compare `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java` and `examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java` 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 `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java: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.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×4
Edited copy of a member (28 corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:93— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:93-120 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:135-162 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:239— xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:239-273 | xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:385-412 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:109— core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:109-156 | examples/src/main/java/io/grpc/examples/customloadbalance/ShufflingPickFirstLoadBalancer.java:114-141 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:102— xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:102-129 | xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancer.java:214-241 — 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.
Hotspot: xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:483— xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in 1.onNext at line 483. 2 of those changes were fix/bug commits, and the other 5 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:27:10 +05:30' --until='2026-11-16 22:27:10 +05:30' --full-history --no-merges -- xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java`: 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: xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:124— xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in BootstrapperImpl.bootstrapBuilder at line 124. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:27:10 +05:30' --until='2026-11-16 22:27:10 +05:30' --full-history --no-merges -- xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java`: 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: xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:333— xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ClusterState.edsUpdateToResult at line 333. 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-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:27:10 +05:30' --until='2026-11-16 22:27:10 +05:30' --full-history --no-merges -- xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java`: 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.
Change coupling: StatusException.java ↔ StatusRuntimeException.java api/src/main/java/io/grpc/StatusException.java:1— `api/src/main/java/io/grpc/StatusException.java` and `api/src/main/java/io/grpc/StatusRuntimeException.java` change together 86% of the time (12 of the 14 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; 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 `9746bb4b` allow java21 in jre matrix (#12281); `ebe2b486` api: StatusRuntimeException without stacktrace - Android compatibilit…; `e36f099b` StatusException/StatusRuntimeException hide stack trace in a simpler … — run `git show` on any of them.
Change coupling: CsdsService.java ↔ XdsClientImpl.java xds/src/main/java/io/grpc/xds/CsdsService.java:1— `xds/src/main/java/io/grpc/xds/CsdsService.java` and `xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java` change together 70% of the time (7 of the 10 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 `36fe276a` xds: add "resource_timer_is_transient_failure" server feature (#12249); `68339250` xds: remove ResourceType enum, use XdsResourceType instead (#9587) (at that commit the file was still `xds/src/main/java/io/grpc/xds/XdsClientImpl.java`); `7c4fe69d` xds: fix a concurrency issue in CSDS ClientStatus responses (#8795) (at that commit the file was still `xds/src/main/java/io/grpc/xds/ClientXdsClient.java`) — run `git show` on any of them.
Change coupling: TestServiceClient.java ↔ TestServiceServer.java interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:1— `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java` and `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java` change together 51% of the time (20 of the 39 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 20 shared commits counted here, the most recent 3 are `cf50cf8f` interop: enable OpenTelemetry tracing support in Java (#12910); `c88285f4` MCS connection scaling interop tests for Java (#12651); `7217baa7` Remove old Java 7/8 TLS testing workarounds — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:170— util/src/main/java/io/grpc/util/AdvancedTlsX509KeyManager.java:170-187 | util/src/main/java/io/grpc/util/AdvancedTlsX509TrustManager.java:253-270 — 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) auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:97— auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:97-118 | auth/src/main/java/io/grpc/auth/GoogleAuthLibraryCallCredentials.java:166-183 — 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) binder/src/main/java/io/grpc/binder/SecurityPolicies.java:231— binder/src/main/java/io/grpc/binder/SecurityPolicies.java:231-248 | binder/src/main/java/io/grpc/binder/SecurityPolicies.java:254-277 — 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 copies of one member (3 members, 13+ corresponding lines) · ×3
Edited copies of one member (3 members, 13+ corresponding lines) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:545— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:545-563 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:592-604 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:617-629 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) core/src/main/java/io/grpc/internal/DnsNameResolverProvider.java:59— core/src/main/java/io/grpc/internal/DnsNameResolverProvider.java:59-76 | grpclb/src/main/java/io/grpc/grpclb/SecretGrpclbNameResolverProvider.java:78-90 | xds/src/main/java/io/grpc/xds/XdsNameResolverProvider.java:81-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) xds/src/main/java/io/grpc/xds/ExternalProcessorFilter.java:91— xds/src/main/java/io/grpc/xds/ExternalProcessorFilter.java:91-103 | xds/src/main/java/io/grpc/xds/FaultFilter.java:110-122 | xds/src/main/java/io/grpc/xds/RbacFilter.java:100-112 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) census/src/main/java/io/grpc/census/CensusStatsModule.java:504— census/src/main/java/io/grpc/census/CensusStatsModule.java:504-525 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java:519-538 — 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) examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:166— examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:166-186 | examples/src/main/java/io/grpc/examples/retrying/RetryingHelloWorldClient.java:128-147 — 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) examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceServer.java:37— examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceServer.java:37-56 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveServer.java:42-61 — 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, 7+ corresponding lines) · ×3
Edited copies of one member (3 members, 7+ corresponding lines) stub/src/main/java/io/grpc/stub/AbstractAsyncStub.java:62— stub/src/main/java/io/grpc/stub/AbstractAsyncStub.java:62-68 | stub/src/main/java/io/grpc/stub/AbstractBlockingStub.java:63-69 | stub/src/main/java/io/grpc/stub/AbstractFutureStub.java:63-69 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:151— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:151-157 | okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:182-188 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:108-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:680— core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:680-686 | core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:187-193 | examples/src/main/java/io/grpc/examples/customloadbalance/ShufflingPickFirstLoadBalancer.java:166-172 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (20 lines × 2) netty/src/main/java/io/grpc/netty/NettyClientTransport.java:414— netty/src/main/java/io/grpc/netty/NettyClientTransport.java:414-433 | netty/src/main/java/io/grpc/netty/NettyServerTransport.java:232-251 — 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 `netty/src/main/java/io/grpc/netty/NettyClientTransport.java: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.
Duplicated block (20 lines × 2) testing/src/main/java/io/grpc/internal/testing/TestUtils.java:191— testing/src/main/java/io/grpc/internal/testing/TestUtils.java:191-210 | testing/src/main/java/io/grpc/testing/TestUtils.java:120-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) alts/src/main/java/io/grpc/alts/FailingClientCall.java:28— alts/src/main/java/io/grpc/alts/FailingClientCall.java:28-47 | xds/src/main/java/io/grpc/xds/internal/extauthz/FailingClientCall.java:34-56 — 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 (17 lines × 2) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:953— xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:953-969 | xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:990-1006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:953` 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) examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58— examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58-74 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java:46-62 — before extracting anything, compare `examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java` and `examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java` 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. Read the line range as the matched WINDOW rather than a finished unit: at `examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58` it begins part-way through the construct above it, so those exact lines 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) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:91— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:91-107 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthClient.java:97-113 — before extracting anything, compare `examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java` and `examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthClient.java` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) REDACTED:217— REDACTED:217-230 | xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancer.java:183-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. 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:33— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:33-46 | services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java:33-46 — before extracting anything, compare `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java` and `services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java` as WHOLE FILES: this scan already matched 3 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. 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) examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:139— examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:139-152 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:204-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) core/src/main/java/io/grpc/internal/ChannelTracer.java:124— core/src/main/java/io/grpc/internal/ChannelTracer.java:124-133 | xds/src/main/java/io/grpc/xds/client/XdsLogger.java:69-77 — 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 (9–10 lines × 2) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:656— xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:656-664 | xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:678-687 — both copies are in the same file, so extract the 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–10 lines × 2) examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:75— examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:75-84 | examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:98-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java: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.
HackComment xds/src/test/java/io/grpc/xds/CsdsServiceTest.java:176— // Hack to prevent the interrupted exception from propagating through to the client stub. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment core/src/main/java/io/grpc/internal/CallCredentialsApplyingTransportFactory.java:159— // Hack to allow appengine to work when using AppEngineCredentials (b/244209681) — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) api/src/main/java/io/grpc/MetricInstrumentRegistry.java:84— api/src/main/java/io/grpc/MetricInstrumentRegistry.java:84-107 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:123-145 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:164-186 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:203-227 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:244-268 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:285-307 — 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) api/src/main/java/io/grpc/MetricRecorder.java:38— api/src/main/java/io/grpc/MetricRecorder.java:38-47 | api/src/main/java/io/grpc/MetricRecorder.java:58-67 | api/src/main/java/io/grpc/MetricRecorder.java:80-89 | api/src/main/java/io/grpc/MetricRecorder.java:101-110 | api/src/main/java/io/grpc/MetricRecorder.java:121-130 | api/src/main/java/io/grpc/MetricRecorder.java:160-169 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:27— testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:27-47 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:58-78 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:89-109 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:120-140 — 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) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:72— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:72-132 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:64-86 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:68-131 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:70-133 — 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 (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) census/src/main/java/io/grpc/census/CensusTracingModule.java:467— census/src/main/java/io/grpc/census/CensusTracingModule.java:467-500 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:535-559 — 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) examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:76— examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:76-100 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:57-82 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:645— inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:645-669 | inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:873-896 — 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) examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:201— examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:201-229 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:182-205 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×2
Edited copies of one member (3 members, 21+ corresponding lines) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:539— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:539-565 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:586-606 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:611-631 — 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) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1198— xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1198-1218 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1221-1241 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1244-1264 — 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 copy of a member (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:71— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:71-93 | services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java:71-93 — 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) alts/src/main/java/io/grpc/alts/internal/NettyTsiHandshaker.java:45— alts/src/main/java/io/grpc/alts/internal/NettyTsiHandshaker.java:45-69 | alts/src/main/java/io/grpc/alts/internal/NettyTsiHandshaker.java:77-99 — 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 copies of one member (4 members, 17+ corresponding lines) · ×2
Edited copies of one member (4 members, 17+ corresponding lines) api/src/main/java/io/grpc/LoadBalancerRegistry.java:138— api/src/main/java/io/grpc/LoadBalancerRegistry.java:138-156 | api/src/main/java/io/grpc/ManagedChannelRegistry.java:134-155 | api/src/main/java/io/grpc/NameResolverRegistry.java:162-178 | xds/src/main/java/io/grpc/xds/XdsCredentialsRegistry.java:154-178 — 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.
Edited copies of one member (4 members, 17+ corresponding lines) api/src/main/java/io/grpc/LoadBalancerRegistry.java:100— api/src/main/java/io/grpc/LoadBalancerRegistry.java:100-117 | api/src/main/java/io/grpc/ManagedChannelRegistry.java:100-117 | api/src/main/java/io/grpc/NameResolverRegistry.java:125-146 | api/src/main/java/io/grpc/ServerRegistry.java:93-109 — 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 (4 members, 16+ corresponding lines) · ×2
Edited copies of one member (4 members, 16+ corresponding lines) util/src/main/java/io/grpc/util/TransmitStatusRuntimeExceptionInterceptor.java:186— util/src/main/java/io/grpc/util/TransmitStatusRuntimeExceptionInterceptor.java:186-201 | util/src/main/java/io/grpc/util/TransmitStatusRuntimeExceptionInterceptor.java:204-219 | util/src/main/java/io/grpc/util/TransmitStatusRuntimeExceptionInterceptor.java:253-268 | util/src/main/java/io/grpc/util/TransmitStatusRuntimeExceptionInterceptor.java:272-287 — 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.
Edited copies of one member (4 members, 16+ corresponding lines) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:44— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthServer.java:44-60 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthServer.java:44-60 | examples/example-tls/src/main/java/io/grpc/examples/helloworldtls/HelloWorldServerTls.java:47-62 | examples/src/main/java/io/grpc/examples/multiplex/MultiplexingServer.java:49-70 — 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 (4 members, 19+ corresponding lines) · ×2
Edited copies of one member (4 members, 19+ corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:144— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:144-162 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:165-183 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:186-205 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:211-229 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 19+ corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:136— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:136-154 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:157-176 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:179-198 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:204-224 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) netty/src/main/java/io/grpc/netty/NettyServer.java:445— netty/src/main/java/io/grpc/netty/NettyServer.java:445-448 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServer.java:161-164 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:443— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:443-448 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:298-301 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23–24 lines × 2) core/src/main/java/io/grpc/internal/DelayedClientCall.java:595— core/src/main/java/io/grpc/internal/DelayedClientCall.java:595-617 | core/src/main/java/io/grpc/internal/DelayedStream.java:526-549 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23–24 lines × 2) inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:495— inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:495-518 | inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:805-827 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:495` it does not close everything it opens, so those exact lines 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) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:49— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:49-69 | services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java:49-69 — before extracting anything, compare `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java` and `services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java` as WHOLE FILES: this scan already matched 3 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) examples/src/main/java/io/grpc/examples/loadbalance/ExampleNameResolver.java:80— examples/src/main/java/io/grpc/examples/loadbalance/ExampleNameResolver.java:80-100 | examples/src/main/java/io/grpc/examples/nameresolve/ExampleNameResolver.java:79-99 — `examples/src/main/java/io/grpc/examples/loadbalance/ExampleNameResolver.java` and `examples/src/main/java/io/grpc/examples/nameresolve/ExampleNameResolver.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 21 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:76— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java:76-93 | services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java:76-93 — before extracting anything, compare `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InetAddressUtil.java` and `services/src/main/java/io/grpc/protobuf/services/InetAddressUtil.java` as WHOLE FILES: this scan already matched 3 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:58— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:58-75 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:102-119 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:58` 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) auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:103— auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:103-118 | auth/src/main/java/io/grpc/auth/GoogleAuthLibraryCallCredentials.java:168-183 — 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 `auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:103` 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. 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 (16 lines × 2) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:164— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:164-179 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:141-156 — before extracting anything, compare `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java` and `examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:164` it does not close everything it opens, so those exact lines 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–15 lines × 2) core/src/main/java/io/grpc/internal/ClientCallImpl.java:635— core/src/main/java/io/grpc/internal/ClientCallImpl.java:635-648 | core/src/main/java/io/grpc/internal/ServerImpl.java:840-854 — 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/src/main/java/io/grpc/internal/ClientCallImpl.java:635` it does not close everything it opens, so those exact lines 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–15 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:212— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:212-226 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:256-269 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java: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. 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–14 lines × 2) binder/src/main/java/io/grpc/binder/SecurityPolicies.java:232— binder/src/main/java/io/grpc/binder/SecurityPolicies.java:232-241 | binder/src/main/java/io/grpc/binder/SecurityPolicies.java:255-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. Read the line range as the matched WINDOW rather than a finished unit: at `binder/src/main/java/io/grpc/binder/SecurityPolicies.java:232` it does not close everything it opens, so those 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–14 lines × 2) examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java:61— examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java:61-74 | examples/src/main/java/io/grpc/examples/grpcproxy/GrpcProxy.java:221-230 — 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 `examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/src/main/java/io/grpc/examples/grpcproxy/GrpcProxy.java:231` calls `shutdownNow` and `examples/example-hostname/src/main/java/io/grpc/examples/hostname/HostnameServer.java: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 (12 lines × 3) netty/src/main/java/io/grpc/netty/NettyClientTransport.java:427— netty/src/main/java/io/grpc/netty/NettyClientTransport.java:427-438 | netty/src/main/java/io/grpc/netty/NettyServer.java:476-487 | netty/src/main/java/io/grpc/netty/NettyServerTransport.java:245-256 — 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 `netty/src/main/java/io/grpc/netty/NettyClientTransport.java:427` it begins part-way through the construct above it, so those 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 (12 lines × 3) examples/src/main/java/io/grpc/examples/advanced/HelloJsonServer.java:53— examples/src/main/java/io/grpc/examples/advanced/HelloJsonServer.java:53-64 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldServerPerMethod.java:43-54 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedServer.java:51-62 — 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 `examples/src/main/java/io/grpc/examples/advanced/HelloJsonServer.java:53` it does not close everything it opens, so those exact lines 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) census/src/main/java/io/grpc/census/CensusStatsModule.java:804— census/src/main/java/io/grpc/census/CensusStatsModule.java:804-811 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryTracingModule.java:541-550 — 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 `census/src/main/java/io/grpc/census/CensusStatsModule.java:804` it does not close everything it opens, so those 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–10 lines × 2) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:603— xds/src/main/java/io/grpc/xds/XdsListenerResource.java:603-612 | xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:245-252 — 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 `xds/src/main/java/io/grpc/xds/XdsListenerResource.java:603` it begins part-way through the construct above it, so those 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–9 lines × 2) auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:121— auth/src/main/java/io/grpc/auth/ClientAuthInterceptor.java:121-129 | auth/src/main/java/io/grpc/auth/GoogleAuthLibraryCallCredentials.java:186-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8–9 lines × 2) xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:239— xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:239-246 | xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:252-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:239` it begins part-way through the construct above it, so those exact lines 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) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202— xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202-1209 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1225-1232 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1248-1255 — 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 `xds/src/main/java/io/grpc/xds/XdsNameResolver.java:1202` it does not close everything it opens, so those 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 × 3) examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58— examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58-65 | examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:64-71 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java:46-53 — before extracting anything, compare `examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java` and `examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java` 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. Read the line range as the matched WINDOW rather than a finished unit: at `examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:58` it begins part-way through the construct above it, so those exact lines 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/src/main/java/io/grpc/internal/ClientCallImpl.java:431— core/src/main/java/io/grpc/internal/ClientCallImpl.java:431-439 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:446-454 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:372-380 — 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 (9 lines × 3) examples/android/clientcache/app/src/main/java/io/grpc/clientcacheexample/ClientCacheExampleActivity.java:159— examples/android/clientcache/app/src/main/java/io/grpc/clientcacheexample/ClientCacheExampleActivity.java:159-167 | examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:115-123 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:145-153 — before extracting anything, compare `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java` and `examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java` 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 `examples/android/clientcache/app/src/main/java/io/grpc/clientcacheexample/ClientCacheExampleActivity.java: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.
Duplicated block (7 lines × 3) REDACTED:82— REDACTED:82-88 | xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:136-142 | xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancer.java:286-292 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:78— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:78-84 | examples/src/main/java/io/grpc/examples/cancellation/CancellationClient.java:185-191 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:245-251 — 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 `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–23 lines × 2) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:117— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:117-138 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:116-138 — before extracting anything, compare `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–23 lines × 2) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:112— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:112-134 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:90-111 — 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–13 lines × 2) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:391— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:391-403 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:216-225 — 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 `examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:391` 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–13 lines × 2) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:406— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:406-418 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:227-236 — 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 `examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:406` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TestServiceClient.runTest (cyclomatic 40) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:358— TestServiceClient.runTest has cyclomatic complexity 40 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FrameHandler.headers (cyclomatic 40) okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:635— FrameHandler.headers has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
1.onNext (cyclomatic 39) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:483— 1.onNext has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TestServiceClient.parseArgs (cyclomatic 37) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:149— TestServiceClient.parseArgs has cyclomatic complexity 37 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
XdsClusterResource.parseNonAggregateCluster (cyclomatic 36) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:218— XdsClusterResource.parseNonAggregateCluster has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XdsRouteConfigureResource.parseRouteAction (cyclomatic 30) xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:404— XdsRouteConfigureResource.parseRouteAction has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XdsClusterResource.validateCommonTlsContext (cyclomatic 27) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:448— XdsClusterResource.validateCommonTlsContext has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Tester.createChannelBuilder (cyclomatic 25) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:622— Tester.createChannelBuilder has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BootstrapperImpl.bootstrapBuilder (cyclomatic 25) xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:124— BootstrapperImpl.bootstrapBuilder has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResolveState.updateRoutes (cyclomatic 25) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:754— ResolveState.updateRoutes has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PickFirstLeafLoadBalancer.processSubchannelState (cyclomatic 24) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:289— PickFirstLeafLoadBalancer.processSubchannelState 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.
TestCallable.runTest (cyclomatic 23) android-interop-testing/src/main/java/io/grpc/android/integrationtest/TestCallable.java:68— TestCallable.runTest has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Sublistener.closed (cyclomatic 23) core/src/main/java/io/grpc/internal/RetriableStream.java:920— Sublistener.closed has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NameResolverListener.onResult2 (cyclomatic 22) core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:1663— NameResolverListener.onResult2 has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClusterState.edsUpdateToResult (cyclomatic 21) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:333— ClusterState.edsUpdateToResult has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Uri.create (cyclomatic 20) api/src/main/java/io/grpc/Uri.java:214— Uri.create 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.
XdsTestClient.parseArgs (cyclomatic 20) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:130— XdsTestClient.parseArgs has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
XdsListenerResource.parseHttpConnectionManager (cyclomatic 20) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:495— XdsListenerResource.parseHttpConnectionManager 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.
PickFirstLeafLoadBalancer.acceptResolvedAddresses (cyclomatic 19) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:93— PickFirstLeafLoadBalancer.acceptResolvedAddresses 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.
StressTestClient.parseArgs (cyclomatic 19) interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:136— StressTestClient.parseArgs has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NettyClientHandler.createStream (cyclomatic 19) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:640— NettyClientHandler.createStream 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.
OkHttpServerBuilder.handshakerSocketFactoryFrom (cyclomatic 19) okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:408— OkHttpServerBuilder.handshakerSocketFactoryFrom 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.
AndroidNegotiator.configureTlsExtensions (cyclomatic 18) okhttp/src/main/java/io/grpc/okhttp/OkHttpProtocolNegotiator.java:234— AndroidNegotiator.configureTlsExtensions 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.
ResourceSubscriber.onAbsent (cyclomatic 18) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:889— ResourceSubscriber.onAbsent 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.
DataPlaneClientCall.halfClose (cyclomatic 18) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1099— DataPlaneClientCall.halfClose 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.
XdsClusterResource.validateOutlierDetection (cyclomatic 18) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:373— XdsClusterResource.validateOutlierDetection 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.
RetriableStream.drain (cyclomatic 17) core/src/main/java/io/grpc/internal/RetriableStream.java:298— RetriableStream.drain 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.
TestServiceServer.parseArgs (cyclomatic 17) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:91— TestServiceServer.parseArgs 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.
OkHttpChannelBuilder.sslSocketFactoryFrom (cyclomatic 17) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:624— OkHttpChannelBuilder.sslSocketFactoryFrom 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.
MessageMarshaller.parse (cyclomatic 17) protobuf-lite/src/main/java/io/grpc/protobuf/lite/ProtoLiteUtils.java:167— MessageMarshaller.parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LoadStatsManager2.getClusterStatsReports (cyclomatic 17) xds/src/main/java/io/grpc/xds/client/LoadStatsManager2.java:160— LoadStatsManager2.getClusterStatsReports 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.
OutlierDetection.fromEnvoyOutlierDetection (cyclomatic 17) xds/src/main/java/io/grpc/xds/EnvoyServerProtoData.java:367— OutlierDetection.fromEnvoyOutlierDetection 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.
DnsNameResolver.maybeChooseServiceConfig (cyclomatic 16) core/src/main/java/io/grpc/internal/DnsNameResolver.java:469— DnsNameResolver.maybeChooseServiceConfig 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.
GzipInflatingBuffer.inflateBytes (cyclomatic 16) core/src/main/java/io/grpc/internal/GzipInflatingBuffer.java:260— GzipInflatingBuffer.inflateBytes 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.
ManagedChannelImplBuilder.getEffectiveInterceptors (cyclomatic 16) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:799— ManagedChannelImplBuilder.getEffectiveInterceptors 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.
XdsFederationTestClient.parseArgs (cyclomatic 16) interop-testing/src/main/java/io/grpc/testing/integration/XdsFederationTestClient.java:65— XdsFederationTestClient.parseArgs 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.
TestInfoInterceptor.interceptCall (cyclomatic 16) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:377— TestInfoInterceptor.interceptCall 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.
ProtocolNegotiators.from (cyclomatic 16) netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java:185— ProtocolNegotiators.from 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.
GrpcOpenTelemetry.createMetricInstruments (cyclomatic 16) opentelemetry/src/main/java/io/grpc/opentelemetry/GrpcOpenTelemetry.java:203— GrpcOpenTelemetry.createMetricInstruments has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OutlierDetectionLoadBalancerProvider.parseLoadBalancingPolicyConfigInternal (cyclomatic 16) util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:67— OutlierDetectionLoadBalancerProvider.parseLoadBalancingPolicyConfigInternal 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.
DataPlaneClientCall.drainPendingDrainingMessages (cyclomatic 16) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1369— DataPlaneClientCall.drainPendingDrainingMessages 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.
ChildHelper.updateBalancingState (cyclomatic 16) xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java:327— ChildHelper.updateBalancingState has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RingHashPicker.pickSubchannel (cyclomatic 16) xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:419— RingHashPicker.pickSubchannel 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.
1.onNext (cognitive 61) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:483— 1.onNext has cognitive complexity 61 (threshold 15). Drivers by points: if/else 33 (53 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (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.
ClusterState.edsUpdateToResult (cognitive 55) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:333— ClusterState.edsUpdateToResult has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (42 pts), loops 5 (13 pts) (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FrameHandler.headers (cognitive 54) okhttp/src/main/java/io/grpc/okhttp/OkHttpServerTransport.java:635— FrameHandler.headers has cognitive complexity 54 (threshold 15). Drivers by points: if/else 29 (41 pts), boolean chains 8, ternaries 2 (3 pts), loops 2 (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.
XdsClusterResource.parseNonAggregateCluster (cognitive 53) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:218— XdsClusterResource.parseNonAggregateCluster has cognitive complexity 53 (threshold 15). Drivers by points: if/else 21 (34 pts), boolean chains 9, error handling 4 (8 pts), loops 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sublistener.closed (cognitive 52) core/src/main/java/io/grpc/internal/RetriableStream.java:920— Sublistener.closed has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (48 pts), boolean chains 4 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ResolveState.updateRoutes (cognitive 47) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:754— ResolveState.updateRoutes has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (37 pts), loops 5 (7 pts), ternaries 2, boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsRouteConfigureResource.parseRouteAction (cognitive 47) xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:404— XdsRouteConfigureResource.parseRouteAction has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (37 pts), boolean chains 4, loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Tester.createChannelBuilder (cognitive 46) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:622— Tester.createChannelBuilder has cognitive complexity 46 (threshold 15). Drivers by points: if/else 31 (43 pts), error handling 1 (3 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.
XdsClusterResource.validateCommonTlsContext (cognitive 46) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:448— XdsClusterResource.validateCommonTlsContext has cognitive complexity 46 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 6 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BootstrapperImpl.bootstrapBuilder (cognitive 44) xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:124— BootstrapperImpl.bootstrapBuilder has cognitive complexity 44 (threshold 15). Drivers by points: if/else 19 (36 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TestServiceClient.parseArgs (cognitive 43) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:149— TestServiceClient.parseArgs has cognitive complexity 43 (threshold 15). Drivers by points: if/else 35 (41 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NameResolverListener.onResult2 (cognitive 41) core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:1663— NameResolverListener.onResult2 has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (31 pts), ternaries 4 (7 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TestInfoInterceptor.interceptCall (cognitive 37) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:377— TestInfoInterceptor.interceptCall has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), error handling 5 (14 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoadStatsManager2.getClusterStatsReports (cognitive 36) xds/src/main/java/io/grpc/xds/client/LoadStatsManager2.java:160— LoadStatsManager2.getClusterStatsReports has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 5 (11 pts), boolean chains 2 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CelCommon.checkAllowedReferences (cognitive 36) xds/src/main/java/io/grpc/xds/internal/matcher/CelCommon.java:93— CelCommon.checkAllowedReferences has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (28 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpclbState.updateServerList (cognitive 33) grpclb/src/main/java/io/grpc/grpclb/GrpclbState.java:514— GrpclbState.updateServerList has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (26 pts), loops 3 (6 pts), match/switch 1 (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RingHashPicker.pickSubchannel (cognitive 33) xds/src/main/java/io/grpc/xds/RingHashLoadBalancer.java:419— RingHashPicker.pickSubchannel has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NettyClientHandler.createStream (cognitive 32) netty/src/main/java/io/grpc/netty/NettyClientHandler.java:640— NettyClientHandler.createStream has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 1 (4 pts), boolean chains 2, error handling 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.
ResourceSubscriber.onAbsent (cognitive 32) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:889— ResourceSubscriber.onAbsent has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 2 (6 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RetriableStream.drain (cognitive 31) core/src/main/java/io/grpc/internal/RetriableStream.java:298— RetriableStream.drain has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
OkHttpServerBuilder.handshakerSocketFactoryFrom (cognitive 31) okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:408— OkHttpServerBuilder.handshakerSocketFactoryFrom has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (19 pts), error handling 3 (8 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataPlaneClientCall.handleRequestBodyResponse (cognitive 31) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1190— DataPlaneClientCall.handleRequestBodyResponse has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 3 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MessageDeframer.readRequiredBytes (cognitive 30) core/src/main/java/io/grpc/internal/MessageDeframer.java:313— MessageDeframer.readRequiredBytes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 2 (6 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.
OkHttpChannelBuilder.sslSocketFactoryFrom (cognitive 30) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:624— OkHttpChannelBuilder.sslSocketFactoryFrom has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (20 pts), error handling 3 (8 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataPlaneClientCall.drainPendingDrainingMessages (cognitive 30) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1369— DataPlaneClientCall.drainPendingDrainingMessages has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 4, 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.
ManagedChannelImplBuilder.getEffectiveInterceptors (cognitive 29) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:799— ManagedChannelImplBuilder.getEffectiveInterceptors has cognitive complexity 29 (threshold 15). Drivers by points: error handling 6 (14 pts), if/else 8 (14 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PickFirstLeafLoadBalancer.processSubchannelState (cognitive 29) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:289— PickFirstLeafLoadBalancer.processSubchannelState has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 7, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MessageMarshaller.parse (cognitive 29) protobuf-lite/src/main/java/io/grpc/protobuf/lite/ProtoLiteUtils.java:167— MessageMarshaller.parse has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), error handling 3 (5 pts), loops 1 (3 pts), boolean chains 2 (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.
DataPlaneClientCall.halfClose (cognitive 29) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1099— DataPlaneClientCall.halfClose has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnifiedMatcher.checkRecursionDepth (cognitive 28) xds/src/main/java/io/grpc/xds/internal/matcher/UnifiedMatcher.java:67— UnifiedMatcher.checkRecursionDepth has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 3 (8 pts), boolean chains 2 (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.
ConfigSelector.selectConfig (cognitive 28) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:420— ConfigSelector.selectConfig has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (9 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Uri.create (cognitive 27) api/src/main/java/io/grpc/Uri.java:214— Uri.create has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, 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.
AndroidNegotiator.configureTlsExtensions (cognitive 27) okhttp/src/main/java/io/grpc/okhttp/OkHttpProtocolNegotiator.java:234— AndroidNegotiator.configureTlsExtensions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (18 pts), error handling 4 (5 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestLimitingSubchannelPicker.pickSubchannel (cognitive 27) xds/src/main/java/io/grpc/xds/ClusterImplLoadBalancer.java:406— RequestLimitingSubchannelPicker.pickSubchannel has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
XdsListenerResource.parseHttpConnectionManager (cognitive 27) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:495— XdsListenerResource.parseHttpConnectionManager has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 4, 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.
TestCallable.runTest (cognitive 26) android-interop-testing/src/main/java/io/grpc/android/integrationtest/TestCallable.java:68— TestCallable.runTest has cognitive complexity 26 (threshold 15). Drivers by points: if/else 20, error handling 3 (6 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AdvancedTlsX509TrustManager.checkTrusted (cognitive 26) util/src/main/java/io/grpc/util/AdvancedTlsX509TrustManager.java:153— AdvancedTlsX509TrustManager.checkTrusted has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OutlierDetection.fromEnvoyOutlierDetection (cognitive 26) xds/src/main/java/io/grpc/xds/EnvoyServerProtoData.java:367— OutlierDetection.fromEnvoyOutlierDetection has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12 (20 pts), if/else 4, boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsTestClient.parseArgs (cognitive 25) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:130— XdsTestClient.parseArgs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 18 (23 pts), loops 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
FactoryImpl.<init> (cognitive 25) services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:610— FactoryImpl.<init> has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsEndpointResource.processClusterLoadAssignment (cognitive 25) xds/src/main/java/io/grpc/xds/XdsEndpointResource.java:122— XdsEndpointResource.processClusterLoadAssignment has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 4 (9 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DnsNameResolver.maybeChooseServiceConfig (cognitive 24) core/src/main/java/io/grpc/internal/DnsNameResolver.java:469— DnsNameResolver.maybeChooseServiceConfig has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (5 pts), boolean chains 3 (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.
PickFirstLeafLoadBalancer.acceptResolvedAddresses (cognitive 24) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:93— PickFirstLeafLoadBalancer.acceptResolvedAddresses has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServerImplBuilder.getTracerFactories (cognitive 23) core/src/main/java/io/grpc/internal/ServerImplBuilder.java:267— ServerImplBuilder.getTracerFactories has cognitive complexity 23 (threshold 15). Drivers by points: error handling 8 (16 pts), if/else 5 (7 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StressTestClient.parseArgs (cognitive 23) interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:136— StressTestClient.parseArgs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TestServiceServer.parseArgs (cognitive 23) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:91— TestServiceServer.parseArgs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (22 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProtocolNegotiators.from (cognitive 23) netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java:185— ProtocolNegotiators.from has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), error handling 1 (2 pts), loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OutlierDetectionLoadBalancerProvider.parseLoadBalancingPolicyConfigInternal (cognitive 23) util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:67— OutlierDetectionLoadBalancerProvider.parseLoadBalancingPolicyConfigInternal has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (23 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.
XdsClusterResource.validateOutlierDetection (cognitive 23) xds/src/main/java/io/grpc/xds/XdsClusterResource.java:373— XdsClusterResource.validateOutlierDetection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DelayedClientTransport.reprocess (cognitive 22) core/src/main/java/io/grpc/internal/DelayedClientTransport.java:288— DelayedClientTransport.reprocess has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProtocolNegotiators.from (cognitive 22) netty/src/main/java/io/grpc/netty/ProtocolNegotiators.java:112— ProtocolNegotiators.from has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (18 pts), error handling 1 (2 pts), loops 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.
OpenTelemetryMetricSink.updateMeasures (cognitive 22) opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:211— OpenTelemetryMetricSink.updateMeasures has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 2 (4 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.
EvaluateArgs.getPrincipalNames (cognitive 22) xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:303— EvaluateArgs.getPrincipalNames has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CdsLoadBalancer2.buildOutlierDetectionLbConfig (cognitive 22) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:627— CdsLoadBalancer2.buildOutlierDetectionLbConfig has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (22 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.
XdsRouteConfigureResource.parseRetryPolicy (cognitive 22) xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:527— XdsRouteConfigureResource.parseRetryPolicy has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpclbState.maybeUpdatePicker (cognitive 21) grpclb/src/main/java/io/grpc/grpclb/GrpclbState.java:863— GrpclbState.maybeUpdatePicker has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 1 (2 pts), match/switch 1, ternaries 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.
ExternalProcessorUtil.toHeaderMap (cognitive 21) xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:224— ExternalProcessorUtil.toHeaderMap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsDependencyManager.addConfigForCluster (cognitive 21) xds/src/main/java/io/grpc/xds/XdsDependencyManager.java:300— XdsDependencyManager.addConfigForCluster has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), loops 1 (2 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.
ConfigSelector.generateHash (cognitive 21) xds/src/main/java/io/grpc/xds/XdsNameResolver.java:577— ConfigSelector.generateHash has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetadataHelper.writeMetadata (cognitive 20) binder/src/main/java/io/grpc/binder/internal/MetadataHelper.java:66— MetadataHelper.writeMetadata has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts), ternaries 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.
ResponseHandler.handleStreamClosed (cognitive 20) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:1056— ResponseHandler.handleStreamClosed has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsResourceType.parse (cognitive 20) xds/src/main/java/io/grpc/xds/client/XdsResourceType.java:136— XdsResourceType.parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiscoveryState.onResourceChanged (cognitive 20) xds/src/main/java/io/grpc/xds/XdsServerWrapper.java:427— DiscoveryState.onResourceChanged has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Uri.percentDecode (cognitive 19) api/src/main/java/io/grpc/Uri.java:1051— Uri.percentDecode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClientCallImpl.startInternal (cognitive 19) core/src/main/java/io/grpc/internal/ClientCallImpl.java:188— ClientCallImpl.startInternal has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CompositeReadableBuffer.readBytes (cognitive 19) core/src/main/java/io/grpc/internal/CompositeReadableBuffer.java:202— CompositeReadableBuffer.readBytes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsTestServer.start (cognitive 19) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:198— XdsTestServer.start has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 1 (3 pts), match/switch 1 (2 pts), boolean chains 1, error handling 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.
OkHttpClientTransport.streamReadyToStart (cognitive 19) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:523— OkHttpClientTransport.streamReadyToStart has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
AndroidNegotiator.getSelectedProtocol (cognitive 19) okhttp/src/main/java/io/grpc/okhttp/OkHttpProtocolNegotiator.java:311— AndroidNegotiator.getSelectedProtocol has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 4 (8 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataPlaneListener.onMessage (cognitive 19) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:1565— DataPlaneListener.onMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Inbound.handleMessageData (cognitive 18) binder/src/main/java/io/grpc/binder/internal/Inbound.java:397— Inbound.handleMessageData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetadataHelper.readMetadata (cognitive 18) binder/src/main/java/io/grpc/binder/internal/MetadataHelper.java:126— MetadataHelper.readMetadata has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 1 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DelayedClientTransport.newStream (cognitive 18) core/src/main/java/io/grpc/internal/DelayedClientTransport.java:121— DelayedClientTransport.newStream has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManagedChannelImplBuilder.getNameResolverProvider (cognitive 18) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:901— ManagedChannelImplBuilder.getNameResolverProvider has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Index.updateGroupsHE (cognitive 18) core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:797— Index.updateGroupsHE has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
ServiceConfigState.update (cognitive 18) core/src/main/java/io/grpc/internal/ServiceConfigState.java:86— ServiceConfigState.update has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpclbLongLivedAffinityTestClient.run (cognitive 18) interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:147— GrpclbLongLivedAffinityTestClient.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TestServiceServer.start (cognitive 18) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:168— TestServiceServer.start has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsStatsWatcher.rpcCompleted (cognitive 18) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:637— XdsStatsWatcher.rpcCompleted has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsTestServer.parseArgs (cognitive 18) interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:121— XdsTestServer.parseArgs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OkHttpClientTransport.verifyAuthority (cognitive 18) okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java:553— OkHttpClientTransport.verifyAuthority has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 1 (3 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CertProviderSslContextProvider.<init> (cognitive 18) xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderSslContextProvider.java:48— CertProviderSslContextProvider.<init> has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 6 (7 pts), ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PriorityLoadBalancer.acceptResolvedAddresses (cognitive 18) xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java:90— PriorityLoadBalancer.acceptResolvedAddresses has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PriorityLoadBalancer.tryNextPriority (cognitive 18) xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java:158— PriorityLoadBalancer.tryNextPriority has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChildHelper.updateBalancingState (cognitive 18) xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java:327— ChildHelper.updateBalancingState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RoutingUtils.findVirtualHostForHostName (cognitive 18) xds/src/main/java/io/grpc/xds/RoutingUtils.java:44— RoutingUtils.findVirtualHostForHostName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsListenerResource.parseServerSideListener (cognitive 18) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:145— XdsListenerResource.parseServerSideListener has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1, ternaries 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.
XdsRouteConfigureResource.parseOverrideFilterConfigs (cognitive 18) xds/src/main/java/io/grpc/xds/XdsRouteConfigureResource.java:211— XdsRouteConfigureResource.parseOverrideFilterConfigs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (5 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BinderTransport.handleTransactionInternal (cognitive 17) binder/src/main/java/io/grpc/binder/internal/BinderTransport.java:474— BinderTransport.handleTransactionInternal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SecurityPolicies.checkPackageSignature (cognitive 17) binder/src/main/java/io/grpc/binder/SecurityPolicies.java:289— SecurityPolicies.checkPackageSignature has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpclbFallbackTestClient.parseArgs (cognitive 17) interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:83— GrpclbFallbackTestClient.parseArgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpcCleanupRule.after (cognitive 17) testing/src/main/java/io/grpc/testing/GrpcCleanupRule.java:166— GrpcCleanupRule.after has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (6 pts), error handling 1 (3 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.
XdsClientImpl.handleResourceUpdate (cognitive 17) xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:573— XdsClientImpl.handleResourceUpdate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 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.
FileWatcherCertificateProvider.checkAndReloadCertificates (cognitive 17) xds/src/main/java/io/grpc/xds/internal/security/certprovider/FileWatcherCertificateProvider.java:113— FileWatcherCertificateProvider.checkAndReloadCertificates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 3, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CsdsService.handleRequest (cognitive 17) xds/src/main/java/io/grpc/xds/CsdsService.java:120— CsdsService.handleRequest has cognitive complexity 17 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 4 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoadBalancingPolicyConverter.convertToServiceConfig (cognitive 17) xds/src/main/java/io/grpc/xds/LoadBalancerConfigFactory.java:217— LoadBalancingPolicyConverter.convertToServiceConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), error handling 1 (2 pts), boolean chains 1, loops 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.
ClientCallImpl.applyMethodConfig (cognitive 16) core/src/main/java/io/grpc/internal/ClientCallImpl.java:295— ClientCallImpl.applyMethodConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GrpclbNameResolver.resolveBalancerAddresses (cognitive 16) grpclb/src/main/java/io/grpc/grpclb/GrpclbNameResolver.java:82— GrpclbNameResolver.resolveBalancerAddresses has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StressTestClient.createChannel (cognitive 16) interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:378— StressTestClient.createChannel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), error handling 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
NettyServerHandler.onHeadersRead (cognitive 16) netty/src/main/java/io/grpc/netty/NettyServerHandler.java:458— NettyServerHandler.onHeadersRead has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
GrpcTraceBinContextPropagator.extract (cognitive 16) opentelemetry/src/main/java/io/grpc/opentelemetry/GrpcTraceBinContextPropagator.java:96— GrpcTraceBinContextPropagator.extract has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), error handling 4 (7 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ThreadSafeThreadlessExecutor.waitAndDrainWithTimeout (cognitive 16) stub/src/main/java/io/grpc/stub/ClientCalls.java:901— ThreadSafeThreadlessExecutor.waitAndDrainWithTimeout has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MatcherTree.<init> (cognitive 16) xds/src/main/java/io/grpc/xds/internal/matcher/MatcherTree.java:40— MatcherTree.<init> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CdsLoadBalancer2.acceptResolvedAddresses (cognitive 16) xds/src/main/java/io/grpc/xds/CdsLoadBalancer2.java:107— CdsLoadBalancer2.acceptResolvedAddresses has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XdsListenerResource.parseHttpFilter (cognitive 16) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:582— XdsListenerResource.parseHttpFilter has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 5, boolean chains 3, error handling 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.
Change-coupling hub: FailingClientTransport.java → InProcessTransport.java, NettyClientTransport.java, OkHttpClientTransport.java core/src/main/java/io/grpc/internal/FailingClientTransport.java— `core/src/main/java/io/grpc/internal/FailingClientTransport.java` changes together with 3 other files — `inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java`, `netty/src/main/java/io/grpc/netty/NettyClientTransport.java`, `okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java` — 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.
Near-duplicate member pair (25 shared lines) okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:624— okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:624-699 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:408-500 — 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· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (11 members, 50+ identical tokens) examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:43— examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:43-80 | examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsServer.java:44-81 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:83-155 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:76-129 | interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:90-135 | interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:136-223 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:149-315 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:91-163 | interop-testing/src/main/java/io/grpc/testing/integration/XdsFederationTestClient.java:65-180 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:130-224 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:121-194 — 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 (176 corresponding lines) · ×1
Edited copy of a member (176 corresponding lines) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:88— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:88-267 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingServerInterceptor.java:87-262 — These two members are one piece of code written twice and then edited apart: 176 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (95 corresponding lines) · ×1
Edited copy of a member (95 corresponding lines) services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:395— services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:395-497 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:499-593 — These two members are one piece of code written twice and then edited apart: 95 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:400— services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:400-495 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:505-591 — These two members are one piece of code written twice and then edited apart: 87 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:494— inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:494-539 | inprocess/src/main/java/io/grpc/inprocess/InProcessTransport.java:804-848 — 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 copy of a member (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:903— core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:903-954 | core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:959-1007 — These two members are one piece of code written twice and then edited apart: 49 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) REDACTED:133— REDACTED:133-168 | REDACTED:179-214 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:52— core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:52-95 | examples/src/main/java/io/grpc/examples/customloadbalance/ShufflingPickFirstLoadBalancer.java:66-102 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:131— services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:131-165 | services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:204-235 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:123— xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java:123-169 | xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorServerInterceptorMetricInstruments.java:51-97 — 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 (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) xds/src/main/java/io/grpc/xds/internal/matcher/HeaderMatchInput.java:63— xds/src/main/java/io/grpc/xds/internal/matcher/HeaderMatchInput.java:63-89 | xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:63-94 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 25+ corresponding lines) · ×1
Edited copies of one member (5 members, 25+ corresponding lines) core/src/main/java/io/grpc/internal/ClientCallImpl.java:598— core/src/main/java/io/grpc/internal/ClientCallImpl.java:598-631 | core/src/main/java/io/grpc/internal/ServerImpl.java:839-865 | core/src/main/java/io/grpc/internal/ServerImpl.java:868-892 | core/src/main/java/io/grpc/internal/ServerImpl.java:940-965 | core/src/main/java/io/grpc/internal/ServerImpl.java:968-993 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 18+ corresponding lines) · ×1
Edited copies of one member (5 members, 18+ corresponding lines) xds/src/main/java/io/grpc/xds/XdsListenerResource.java:344— xds/src/main/java/io/grpc/xds/XdsListenerResource.java:344-361 | xds/src/main/java/io/grpc/xds/XdsListenerResource.java:364-383 | xds/src/main/java/io/grpc/xds/XdsListenerResource.java:386-405 | xds/src/main/java/io/grpc/xds/XdsListenerResource.java:407-426 | xds/src/main/java/io/grpc/xds/XdsListenerResource.java:428-447 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) core/src/main/java/io/grpc/internal/JsonUtil.java:103— core/src/main/java/io/grpc/internal/JsonUtil.java:103-122 | core/src/main/java/io/grpc/internal/JsonUtil.java:129-153 | core/src/main/java/io/grpc/internal/JsonUtil.java:160-184 — 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 (5 members, 21+ corresponding lines) · ×1
Edited copies of one member (5 members, 21+ corresponding lines) services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:90— services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:90-112 | services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:135-157 | services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:162-184 | services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:189-209 | services/src/main/java/io/grpc/protobuf/services/ChannelzService.java:213-233 — These 5 members are one piece of code written 5 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 5 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) opentelemetry/src/main/java/io/grpc/opentelemetry/MetadataGetter.java:53— opentelemetry/src/main/java/io/grpc/opentelemetry/MetadataGetter.java:53-72 | opentelemetry/src/main/java/io/grpc/opentelemetry/MetadataGetter.java:75-90 | opentelemetry/src/main/java/io/grpc/opentelemetry/MetadataSetter.java:42-57 — 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, 22+ corresponding lines) · ×1
Edited copies of one member (4 members, 22+ corresponding lines) netty/src/main/java/io/grpc/netty/InternalProtocolNegotiators.java:48— netty/src/main/java/io/grpc/netty/InternalProtocolNegotiators.java:48-70 | netty/src/main/java/io/grpc/netty/InternalProtocolNegotiators.java:88-109 | netty/src/main/java/io/grpc/netty/InternalProtocolNegotiators.java:112-133 | netty/src/main/java/io/grpc/netty/InternalProtocolNegotiators.java:136-157 — 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, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) REDACTED:169— REDACTED:169-182 | xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java:233-246 | xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancer.java:601-616 — 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 (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:49— interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:49-70 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:42-65 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:111-128 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:99-119 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 12+ corresponding lines) · ×1
Edited copies of one member (6 members, 12+ corresponding lines) opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:94— opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:94-105 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:109-120 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:125-136 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:140-151 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:155-166 | opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricSink.java:170-181 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 14+ corresponding lines) · ×1
Edited copies of one member (5 members, 14+ corresponding lines) core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:67— core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:67-81 | core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:93-106 | core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:119-132 | core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:144-157 | core/src/main/java/io/grpc/internal/MetricRecorderImpl.java:169-182 — 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 (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) servlet/src/main/java/io/grpc/servlet/ServletAdapter.java:235— servlet/src/main/java/io/grpc/servlet/ServletAdapter.java:235-247 | servlet/src/main/java/io/grpc/servlet/ServletAdapter.java:250-264 | servlet/src/main/java/io/grpc/servlet/ServletAdapter.java:322-335 | servlet/src/main/java/io/grpc/servlet/ServletServerStream.java:207-220 — 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 (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) core/src/main/java/io/grpc/internal/JsonUtil.java:38— core/src/main/java/io/grpc/internal/JsonUtil.java:38-49 | core/src/main/java/io/grpc/internal/JsonUtil.java:85-96 | core/src/main/java/io/grpc/internal/JsonUtil.java:191-202 | core/src/main/java/io/grpc/internal/JsonUtil.java:226-237 — 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 (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:205— xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:205-215 | xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:219-230 | xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:234-244 | xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.java:248-259 — 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 (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) api/src/main/java/io/grpc/LoadBalancer.java:351— api/src/main/java/io/grpc/LoadBalancer.java:351-359 | api/src/main/java/io/grpc/NameResolver.java:884-892 | netty/src/main/java/io/grpc/netty/ProtocolNegotiationEvent.java:82-89 — 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, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:574— netty/src/main/java/io/grpc/netty/NettyChannelBuilder.java:574-583 | okhttp/src/main/java/io/grpc/okhttp/OkHttpChannelBuilder.java:344-353 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServerBuilder.java:201-210 — 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, 6+ corresponding lines) · ×1
Edited copies of one member (6 members, 6+ corresponding lines) core/src/main/java/io/grpc/internal/InternalSubchannel.java:475— core/src/main/java/io/grpc/internal/InternalSubchannel.java:475-482 | core/src/main/java/io/grpc/internal/ManagedChannelImpl.java:2050-2055 | core/src/main/java/io/grpc/internal/ServerImpl.java:747-752 | netty/src/main/java/io/grpc/netty/NettyClientTransport.java:394-400 | netty/src/main/java/io/grpc/netty/NettyServer.java:406-411 | netty/src/main/java/io/grpc/netty/NettyServerTransport.java:270-275 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) netty/src/main/java/io/grpc/netty/NettyServer.java:495— netty/src/main/java/io/grpc/netty/NettyServer.java:495-500 | okhttp/src/main/java/io/grpc/okhttp/OkHttpServer.java:182-187 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (46 lines × 2) xds/src/main/java/io/grpc/xds/RoutingUtils.java:95— xds/src/main/java/io/grpc/xds/RoutingUtils.java:95-140 | xds/src/main/java/io/grpc/xds/XdsNameResolver.java:371-416 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23 lines × 2) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:911— core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:911-933 | core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:967-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/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:911` it begins part-way through the construct above it, so those exact lines 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 × 10) examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:46— examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:46-63 | examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsServer.java:47-64 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:86-103 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:79-96 | interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:93-110 | interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:140-157 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:152-169 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:94-111 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:135-152 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:124-141 — before extracting anything, compare `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java` and `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:132` calls `of` and `examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 2) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:880— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:880-894 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:953-968 — both copies are in the same file, so extract the 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 (14–15 lines × 3) core/src/main/java/io/grpc/internal/ClientCallImpl.java:604— core/src/main/java/io/grpc/internal/ClientCallImpl.java:604-617 | core/src/main/java/io/grpc/internal/ClientCallImpl.java:640-654 | core/src/main/java/io/grpc/internal/ClientCallImpl.java:755-768 — 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/src/main/java/io/grpc/internal/ClientCallImpl.java:604` 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/src/main/java/io/grpc/internal/ClientCallImpl.java:655` calls `closeQuietly` and `core/src/main/java/io/grpc/internal/ClientCallImpl.java:618` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 4) testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:35— testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:35-47 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:66-78 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:97-109 | testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:128-140 — 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 `testing-proto/src/generated/main/grpc/io/grpc/testing/protobuf/SimpleServiceGrpc.java:35` it begins part-way through the construct above it, so those 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 (12 lines × 6) api/src/main/java/io/grpc/MetricInstrumentRegistry.java:86— api/src/main/java/io/grpc/MetricInstrumentRegistry.java:86-97 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:125-136 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:166-177 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:206-217 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:247-258 | api/src/main/java/io/grpc/MetricInstrumentRegistry.java:287-298 — 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 `api/src/main/java/io/grpc/MetricInstrumentRegistry.java:86` it does not close everything it opens, so those 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 `bucketBoundaries` to `List<Double>` in one and `List<Long>` 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, `api/src/main/java/io/grpc/MetricInstrumentRegistry.java:246` calls `checkNotNull` and `api/src/main/java/io/grpc/MetricInstrumentRegistry.java:85` 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–12 lines × 2) gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:136— gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:136-147 | gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:180-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java:179` calls `checkNotNull` and `gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/LogHelper.java: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.
Duplicated block (11 lines × 3) core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:850— core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:850-860 | core/src/main/java/io/grpc/internal/ServerImplBuilder.java:291-301 | core/src/main/java/io/grpc/internal/ServerImplBuilder.java:314-324 — 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/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java:850` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 6) api/src/main/java/io/grpc/MetricRecorder.java:39— api/src/main/java/io/grpc/MetricRecorder.java:39-47 | api/src/main/java/io/grpc/MetricRecorder.java:59-67 | api/src/main/java/io/grpc/MetricRecorder.java:81-89 | api/src/main/java/io/grpc/MetricRecorder.java:102-110 | api/src/main/java/io/grpc/MetricRecorder.java:122-130 | api/src/main/java/io/grpc/MetricRecorder.java:161-169 — 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. 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 `metricInstrument` to `DoubleCounterMetricInstrument` in one and `LongCounterMetricInstrument` 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 × 11) examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:45— examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:45-52 | examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsServer.java:46-53 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java:85-92 | interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java:78-85 | interop-testing/src/main/java/io/grpc/testing/integration/Http2Client.java:92-99 | interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.java:139-146 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceClient.java:151-158 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:93-100 | interop-testing/src/main/java/io/grpc/testing/integration/XdsFederationTestClient.java:67-74 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:134-141 | interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java:123-130 — before extracting anything, compare `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbFallbackTestClient.java` and `interop-testing/src/main/java/io/grpc/testing/integration/GrpclbLongLivedAffinityTestClient.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:45` it does not close everything it opens, so those 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, `interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.java:132` calls `of` and `examples/example-alts/src/main/java/io/grpc/examples/alts/HelloWorldAltsClient.java:44` 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–8 lines × 3) interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:544— interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:544-551 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:592-598 | interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:617-623 — 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 `interop-testing/src/main/java/io/grpc/testing/integration/TestServiceImpl.java:544` 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. 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–7 lines × 2) xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:136— xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:136-142 | xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:154-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (34 lines × 2) api/src/main/java/io/grpc/StatusException.java:38— api/src/main/java/io/grpc/StatusException.java:38-71 | api/src/main/java/io/grpc/StatusRuntimeException.java:39-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. 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 (129 lines × 2) core/src/main/java/io/grpc/internal/ForwardingClientStreamTracer.java:1— core/src/main/java/io/grpc/internal/ForwardingClientStreamTracer.java:1-130 | util/src/main/java/io/grpc/util/ForwardingClientStreamTracer.java:1-129 — before extracting anything, compare `core/src/main/java/io/grpc/internal/ForwardingClientStreamTracer.java` and `util/src/main/java/io/grpc/util/ForwardingClientStreamTracer.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `core/src/main/java/io/grpc/internal/ForwardingClientStreamTracer.java:1` it does not close everything it opens, so those 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 (116 lines × 2) netty/src/main/java/io/grpc/netty/NoopSslEngine.java:1— netty/src/main/java/io/grpc/netty/NoopSslEngine.java:1-150 | okhttp/src/main/java/io/grpc/okhttp/NoopSslSocket.java:1-116 — 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 `netty/src/main/java/io/grpc/netty/NoopSslEngine.java:1` it does not close everything it opens, so those 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 (75 lines × 2) testing/src/main/java/io/grpc/internal/testing/StreamRecorder.java:38— testing/src/main/java/io/grpc/internal/testing/StreamRecorder.java:38-112 | testing/src/main/java/io/grpc/testing/StreamRecorder.java:43-117 — before extracting anything, compare `testing/src/main/java/io/grpc/internal/testing/StreamRecorder.java` and `testing/src/main/java/io/grpc/testing/StreamRecorder.java` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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, `testing/src/main/java/io/grpc/testing/StreamRecorder.java:37` calls `ExperimentalApi` and `testing/src/main/java/io/grpc/internal/testing/StreamRecorder.java:27` 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) util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:57— util/src/main/java/io/grpc/util/OutlierDetectionLoadBalancerProvider.java:57-65 | util/src/main/java/io/grpc/util/RandomSubsettingLoadBalancerProvider.java:52-61 | xds/src/main/java/io/grpc/xds/RingHashLoadBalancerProvider.java:71-79 | xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancerProvider.java:65-73 — 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 (6 lines × 3) core/src/main/java/io/grpc/internal/ClientCallImpl.java:181— core/src/main/java/io/grpc/internal/ClientCallImpl.java:181-186 | core/src/main/java/io/grpc/internal/ClientCallImpl.java:452-457 | core/src/main/java/io/grpc/internal/ServerCallImpl.java:216-221 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 4) core/src/main/java/io/grpc/internal/DelayedClientCall.java:359— core/src/main/java/io/grpc/internal/DelayedClientCall.java:359-370 | core/src/main/java/io/grpc/internal/DelayedClientCall.java:373-384 | core/src/main/java/io/grpc/internal/DelayedClientCall.java:387-398 | core/src/main/java/io/grpc/internal/DelayedStream.java:476-487 — 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.
Near-duplicate member pair (50 shared lines) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:69— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:69-153 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:71-153 — These two members are variants of one another: 50 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 (17 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (17 members, 50+ identical tokens) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:55— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:55-66 | examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:84-94 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:52-63 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:47-58 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:52-63 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:54-65 | examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsClient.java:50-61 | examples/example-tls/src/main/java/io/grpc/examples/helloworldtls/HelloWorldClientTls.java:50-61 | examples/example-xds/src/main/java/io/grpc/examples/helloworldxds/XdsHelloWorldClient.java:49-60 | examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:63-74 | examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:51-61 | examples/src/main/java/io/grpc/examples/header/CustomHeaderClient.java:62-73 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:46-57 | examples/src/main/java/io/grpc/examples/keepalive/KeepAliveClient.java:49-60 | examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:40-50 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java:72-82 | examples/src/main/java/io/grpc/examples/waitforready/WaitForReadyClient.java:71-82 — These 17 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 17 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 17 times.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:277— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:277-348 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:125-184 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:365— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:365-431 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:190-240 — 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 copies of one member (4 members, 32+ corresponding lines) · ×1
Edited copies of one member (4 members, 32+ corresponding lines) examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:48— examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:48-82 | examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:64-107 | examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:53-84 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java:37-70 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 32 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 (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/JwtServerInterceptor.java:44— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/JwtServerInterceptor.java:44-74 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/OAuth2ServerInterceptor.java:41-72 — 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 (5 members, 26+ corresponding lines) · ×1
Edited copies of one member (5 members, 26+ corresponding lines) examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:64— examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:64-92 | examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsClient.java:67-105 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:63-99 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:82-107 | examples/src/main/java/io/grpc/examples/waitforready/WaitForReadyClient.java:88-131 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:89— examples/example-jwt-auth/src/main/java/io/grpc/examples/jwtauth/AuthClient.java:89-117 | examples/example-oauth/src/main/java/io/grpc/examples/oauth/AuthClient.java:95-123 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:191— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:191-219 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:167-194 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:145-175 — 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 copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:162— examples/src/main/java/io/grpc/examples/errordetails/ErrorDetailsExample.java:162-189 | examples/src/main/java/io/grpc/examples/errorhandling/DetailErrorSample.java:139-165 | examples/src/main/java/io/grpc/examples/errorhandling/ErrorHandlingClient.java:114-143 — 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 copies of one member (6 members, 21+ corresponding lines) · ×1
Edited copies of one member (6 members, 21+ corresponding lines) examples/example-reflection/src/main/java/io/grpc/examples/reflection/ReflectionServer.java:24— examples/example-reflection/src/main/java/io/grpc/examples/reflection/ReflectionServer.java:24-46 | examples/src/main/java/io/grpc/examples/advanced/HelloJsonServer.java:51-72 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldServerPerMethod.java:41-62 | REDACTED:44-66 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedServer.java:50-70 | examples/src/main/java/io/grpc/examples/retrying/RetryingHelloWorldServer.java:44-68 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
Duplicated block (52 lines × 2) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:70— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:70-121 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:70-121 — before extracting anything, compare `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (28 lines × 2) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:74— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:74-101 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:70-97 — before extracting anything, compare `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 3) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:94— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:94-115 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:94-115 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:92-113 — before extracting anything, compare `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:114— examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:114-134 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:90-109 — before extracting anything, compare `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19–20 lines × 2) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:330— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:330-348 | examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:412-431 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:330` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–18 lines × 5) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:82— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:82-95 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:72-89 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:167-184 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:89-100 | examples/src/main/java/io/grpc/examples/waitforready/WaitForReadyClient.java:97-114 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java` 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 `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:82` it begins part-way through the construct above it, so those 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 (17–18 lines × 2) examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:169— examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java:169-186 | examples/src/main/java/io/grpc/examples/retrying/RetryingHelloWorldClient.java:131-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `examples/src/main/java/io/grpc/examples/hedging/HedgingHelloWorldClient.java: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 (16–17 lines × 3) examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:71— examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:71-86 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:115-131 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:117-133 — before extracting anything, compare `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` 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 `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:71` 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–13 lines × 2) examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:95— examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:95-106 | examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java:124-136 — before extracting anything, compare `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java` and `examples/android/strictmode/app/src/main/java/io/grpc/strictmodehelloworldexample/StrictModeHelloworldActivity.java` 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 `examples/android/helloworld/app/src/main/java/io/grpc/helloworldexample/HelloworldActivity.java:95` 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 × 6) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:80— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:80-90 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:69-79 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:80-90 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:70-80 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:165-175 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:87-97 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` as WHOLE FILES: this scan already matched 5 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 `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:80` it begins part-way through the construct above it, so those 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, `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:77` calls `AtomicBoolean` and `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:76` 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 × 4) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:113— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:113-123 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:70-80 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:114-124 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:116-126 — before extracting anything, compare `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:113` it does not close everything it opens, so those 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, `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:125` calls `close` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:81` 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 × 17) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:57— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:57-66 | examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:85-94 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:54-63 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:49-58 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:54-63 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:56-65 | examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsClient.java:52-61 | examples/example-tls/src/main/java/io/grpc/examples/helloworldtls/HelloWorldClientTls.java:52-61 | examples/example-xds/src/main/java/io/grpc/examples/helloworldxds/XdsHelloWorldClient.java:51-60 | examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:65-74 | examples/src/main/java/io/grpc/examples/customloadbalance/CustomLoadBalanceClient.java:52-61 | examples/src/main/java/io/grpc/examples/header/CustomHeaderClient.java:64-73 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:48-57 | examples/src/main/java/io/grpc/examples/keepalive/KeepAliveClient.java:51-60 | examples/src/main/java/io/grpc/examples/loadbalance/LoadBalanceClient.java:41-50 | examples/src/main/java/io/grpc/examples/nameresolve/NameResolveClient.java:73-82 | examples/src/main/java/io/grpc/examples/waitforready/WaitForReadyClient.java:73-82 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` as WHOLE FILES: this scan already matched 5 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 `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:57` 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, `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:56` calls `info` and `examples/example-dualstack/src/main/java/io/grpc/examples/dualstack/DualStackClient.java:84` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5–10 lines × 2) examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:236— examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:236-245 | examples/src/main/java/io/grpc/examples/routeguide/RouteGuideClient.java:96-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 `examples/android/routeguide/app/src/main/java/io/grpc/routeguideexample/RouteGuideActivity.java:236` it begins part-way through the construct above it, so those exact lines 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 × 8) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:79— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:79-85 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:79-85 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:68-74 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:75-81 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:79-85 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:69-75 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:164-170 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:86-92 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` as WHOLE FILES: this scan already matched 5 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:77` calls `AtomicBoolean` and `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:76` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 10) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78-83 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:76-81 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:78-83 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:67-72 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:76-81 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:74-79 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:78-83 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:68-73 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:163-168 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:85-90 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` as WHOLE FILES: this scan already matched 5 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 `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78` it does not close everything it opens, so those 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, `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:77` calls `AtomicBoolean` and `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:76` 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 × 5) examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:66— examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:66-71 | examples/src/main/java/io/grpc/examples/healthservice/HealthServiceClient.java:165-171 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:66-72 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:161-167 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:84-89 — before extracting anything, compare `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` and `examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:66` it does not close everything it opens, so those exact lines 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 × 12) examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78— examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78-82 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityClient.java:76-80 | examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:78-82 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java:67-71 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryClient.java:76-80 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:74-78 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:78-82 | examples/example-orca/src/main/java/io/grpc/examples/orca/CustomBackendMetricsClient.java:73-78 | examples/src/main/java/io/grpc/examples/healthservice/HealthServiceClient.java:167-171 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldClient.java:68-72 | examples/src/main/java/io/grpc/examples/multiplex/SharingClient.java:163-167 | examples/src/main/java/io/grpc/examples/preserialized/PreSerializedClient.java:85-89 — before extracting anything, compare `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java` and `examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityClient.java` as WHOLE FILES: this scan already matched 5 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 `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:78` it does not close everything it opens, so those 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, `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryClient.java:77` calls `AtomicBoolean` and `examples/example-debug/src/main/java/io/grpc/examples/debug/HelloWorldDebuggableClient.java:76` 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 (25 lines × 2) REDACTED:35— REDACTED:35-59 | REDACTED:35-59 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 13) examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:137— examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java:137-141 | examples/example-gcp-observability/src/main/java/io/grpc/examples/gcpobservability/GcpObservabilityServer.java:91-95 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java:136-140 | examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/logging/LoggingOpenTelemetryServer.java:138-142 | examples/example-reflection/src/main/java/io/grpc/examples/reflection/ReflectionServer.java:75-79 | examples/example-servlet/src/main/java/io/grpc/servlet/examples/helloworld/HelloWorldServlet.java:49-53 | examples/example-tls/src/main/java/io/grpc/examples/helloworldtls/HelloWorldServerTls.java:109-113 | examples/src/main/java/io/grpc/examples/advanced/HelloJsonServer.java:100-104 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldServerAllMethods.java:104-108 | examples/src/main/java/io/grpc/examples/header/CustomHeaderServer.java:90-94 | REDACTED:95-99 | examples/src/main/java/io/grpc/examples/helloworld/HelloWorldServer.java:101-105 | examples/src/main/java/io/grpc/examples/keepalive/KeepAliveServer.java:112-116 — before extracting anything, compare `examples/example-gcp-csm-observability/src/main/java/io/grpc/examples/csmobservability/CsmObservabilityServer.java` and `examples/example-opentelemetry/src/main/java/io/grpc/example/opentelemetry/OpenTelemetryServer.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 3) examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:80— examples/src/main/java/io/grpc/examples/advanced/HelloJsonClient.java:80-93 | examples/src/main/java/io/grpc/examples/experimental/CompressingHelloWorldClient.java:75-88 | examples/src/main/java/io/grpc/examples/header/CustomHeaderClient.java:78-91 — 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.
Swallowed exception (caught, then discarded) gcp-csm-observability/src/main/java/io/grpc/gcp/csm/observability/MetadataExchanger.java:182— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Orphaned file api/src/main/java/io/grpc/InternalChannelz.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 api/src/main/java/io/grpc/Metadata.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 interop-testing/src/main/java/io/grpc/testing/integration/XdsTestClient.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 xds/src/main/java/io/grpc/xds/XdsListenerResource.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/src/main/java/io/grpc/internal/DnsNameResolver.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 interop-testing/src/main/java/io/grpc/testing/integration/StressTestClient.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 xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.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 benchmarks/src/jmh/java/io/grpc/benchmarks/netty/AbstractBenchmark.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 cronet/src/main/java/io/grpc/cronet/CronetClientStream.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 xds/src/main/java/io/grpc/xds/client/LoadStatsManager2.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 xds/src/main/java/io/grpc/xds/LoadBalancerConfigFactory.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 util/src/main/java/io/grpc/util/AdvancedTlsX509TrustManager.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 xds/src/main/java/io/grpc/xds/FilterChainMatchingProtocolNegotiators.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 api/src/main/java/io/grpc/MethodDescriptor.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 REDACTED: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 services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.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 interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.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 benchmarks/src/main/java/io/grpc/benchmarks/driver/LoadClient.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 services/src/main/java/io/grpc/protobuf/services/ChannelzProtoUtil.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 xds/src/main/java/io/grpc/xds/client/XdsClient.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 census/src/main/java/io/grpc/census/CensusTracingModule.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 api/src/main/java/io/grpc/CallOptions.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 alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.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 stub/src/main/java/io/grpc/stub/ServerCalls.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 xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.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.
Disabled test binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:113— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:118— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test binder/src/androidTest/java/io/grpc/binder/internal/BinderTransportTest.java:123— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test binder/src/test/java/io/grpc/binder/internal/RobolectricBinderTransportTest.java:484— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test binder/src/test/java/io/grpc/binder/internal/RobolectricBinderTransportTest.java:489— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test gcp-observability/src/test/java/io/grpc/gcp/observability/LoggingTest.java:85— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test gcp-observability/src/test/java/io/grpc/gcp/observability/MetricsTest.java:80— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test gcp-observability/src/test/java/io/grpc/gcp/observability/TracesTest.java:82— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test inprocess/src/test/java/io/grpc/inprocess/InProcessTransportTest.java:109— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test interop-testing/src/test/java/io/grpc/testing/integration/NettyFlowControlTest.java:115— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test netty/src/test/java/io/grpc/netty/NettyTransportTest.java:114— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:184— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:190— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:196— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:202— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:209— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:215— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:222— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:228— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:234— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:240— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:246— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:252— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:258— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test servlet/src/jettyTest/java/io/grpc/servlet/JettyTransportTest.java:264— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
+ 15 more in this group — see findings.md.
P10 · Library API & versioning· Implementation type on the public API · ×22
Implementation type on the public API alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:23— 31 public types in `io.grpc.alts.internal` are marked as implementation by their own namespace, folder or name: `AltsClientOptions` (alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:23, `internal`), `Builder` (alts/src/main/java/io/grpc/alts/internal/AltsClientOptions.java:47, `internal`), `AltsFraming` (alts/src/main/java/io/grpc/alts/internal/AltsFraming.java:26, `internal`), `Parser` (alts/src/main/java/io/grpc/alts/internal/AltsFraming.java:254, `internal`), `AltsHandshakerOptions` (alts/src/main/java/io/grpc/alts/internal/AltsHandshakerOptions.java:22, `internal`), `AltsInternalContext` (alts/src/main/java/io/grpc/alts/internal/AltsInternalContext.java:23, `internal`), `AltsProtocolNegotiator` (alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:54, `internal`), `ClientAltsProtocolNegotiatorFactory` (alts/src/main/java/io/grpc/alts/internal/AltsProtocolNegotiator.java:82, `internal`), and 23 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API binder/src/main/java/io/grpc/binder/internal/Bindable.java:34— 19 public types in `io.grpc.binder.internal` are marked as implementation by their own namespace, folder or name: `Observer` (binder/src/main/java/io/grpc/binder/internal/Bindable.java:34, `internal`), `BinderClientTransport` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransport.java:72, `internal`), `BinderClientTransportFactory` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransportFactory.java:44, `internal`), `Builder` (binder/src/main/java/io/grpc/binder/internal/BinderClientTransportFactory.java:118, `internal`), `BinderServer` (binder/src/main/java/io/grpc/binder/internal/BinderServer.java:63, `internal`), `BinderServerTransport` (binder/src/main/java/io/grpc/binder/internal/BinderServerTransport.java:38, `internal`), `BinderTransport` (binder/src/main/java/io/grpc/binder/internal/BinderTransport.java:81, `internal`), `BinderTransportSecurity` (binder/src/main/java/io/grpc/binder/internal/BinderTransportSecurity.java:51, `internal`), and 11 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API census/src/main/java/io/grpc/census/internal/DeprecatedCensusConstants.java:27— 2 public types in `io.grpc.census.internal` are marked as implementation by their own namespace, folder or name: `DeprecatedCensusConstants` (census/src/main/java/io/grpc/census/internal/DeprecatedCensusConstants.java:27, `internal`), `ObservabilityCensusConstants` (census/src/main/java/io/grpc/census/internal/ObservabilityCensusConstants.java:45, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API core/src/main/java/io/grpc/internal/AbstractClientStream.java:50— 117 public types in `io.grpc.internal` are marked as implementation by their own namespace, folder or name: `AbstractClientStream` (core/src/main/java/io/grpc/internal/AbstractClientStream.java:50, `internal`), `AbstractReadableBuffer` (core/src/main/java/io/grpc/internal/AbstractReadableBuffer.java:24, `internal`), `AbstractServerStream` (core/src/main/java/io/grpc/internal/AbstractServerStream.java:32, `internal`), `AbstractStream` (core/src/main/java/io/grpc/internal/AbstractStream.java:38, `internal`), `ApplicationThreadDeframer` (core/src/main/java/io/grpc/internal/ApplicationThreadDeframer.java:35, `internal`), `AtomicBackoff` (core/src/main/java/io/grpc/internal/AtomicBackoff.java:29, `internal`), `State` (core/src/main/java/io/grpc/internal/AtomicBackoff.java:48, `internal`), `AuthorityVerifier` (core/src/main/java/io/grpc/internal/AuthorityVerifier.java:22, `internal`), and 109 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:62— 1 public type in `io.grpc.gcp.observability.interceptors` is marked as implementation by its own namespace, folder or name: `FactoryImpl` (gcp-observability/src/main/java/io/grpc/gcp/observability/interceptors/InternalLoggingChannelInterceptor.java:62, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API opentelemetry/src/main/java/io/grpc/opentelemetry/internal/OpenTelemetryConstants.java:25— 1 public type in `io.grpc.opentelemetry.internal` is marked as implementation by its own namespace, folder or name: `OpenTelemetryConstants` (opentelemetry/src/main/java/io/grpc/opentelemetry/internal/OpenTelemetryConstants.java:25, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API s2a/src/main/java/io/grpc/s2a/internal/channel/S2AHandshakerServiceChannel.java:49— 1 public type in `io.grpc.s2a.internal.channel` is marked as implementation by its own namespace, folder or name: `S2AHandshakerServiceChannel` (s2a/src/main/java/io/grpc/s2a/internal/channel/S2AHandshakerServiceChannel.java:49, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AConnectionException.java:21— 4 public types in `io.grpc.s2a.internal.handshaker` are marked as implementation by their own namespace, folder or name: `S2AConnectionException` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AConnectionException.java:21, `internal`), `S2AIdentity` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AIdentity.java:29, `internal`), `S2AProtocolNegotiatorFactory` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AProtocolNegotiatorFactory.java:55, `internal`), `S2AStub` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2AStub.java:39, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/AccessTokenManager.java:25— 2 public types in `io.grpc.s2a.internal.handshaker.tokenmanager` are marked as implementation by their own namespace, folder or name: `AccessTokenManager` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/AccessTokenManager.java:25, `internal`), `SingleTokenFetcher` (s2a/src/main/java/io/grpc/s2a/internal/handshaker/tokenmanager/SingleTokenFetcher.java:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API services/src/main/java/io/grpc/protobuf/services/internal/HealthCheckingRoundRobinLoadBalancerProvider.java:34— 1 public type in `io.grpc.protobuf.services.internal` is marked as implementation by its own namespace, folder or name: `HealthCheckingRoundRobinLoadBalancerProvider` (services/src/main/java/io/grpc/protobuf/services/internal/HealthCheckingRoundRobinLoadBalancerProvider.java:34, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/InternalGrpcBootstrapperImpl.java:28— 2 public types in `io.grpc.xds` are marked as implementation by their own namespace, folder or name: `InternalGrpcBootstrapperImpl` (xds/src/main/java/io/grpc/xds/InternalGrpcBootstrapperImpl.java:28, name ends in `Impl`), `ThreadSafeRandomImpl` (xds/src/main/java/io/grpc/xds/ThreadSafeRandom.java:30, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:44— 2 public types in `io.grpc.xds.client` are marked as implementation by their own namespace, folder or name: `BootstrapperImpl` (xds/src/main/java/io/grpc/xds/client/BootstrapperImpl.java:44, name ends in `Impl`), `XdsClientImpl` (xds/src/main/java/io/grpc/xds/client/XdsClientImpl.java:66, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/GoogleDefaultXdsCredentialsProvider.java:28— 15 public types in `io.grpc.xds.internal` are marked as implementation by their own namespace, folder or name: `GoogleDefaultXdsCredentialsProvider` (xds/src/main/java/io/grpc/xds/internal/GoogleDefaultXdsCredentialsProvider.java:28, `internal`), `HeaderForwardingRulesConfig` (xds/src/main/java/io/grpc/xds/internal/HeaderForwardingRulesConfig.java:28, `internal`), `InsecureXdsCredentialsProvider` (xds/src/main/java/io/grpc/xds/internal/InsecureXdsCredentialsProvider.java:28, `internal`), `MatcherParser` (xds/src/main/java/io/grpc/xds/internal/MatcherParser.java:24, `internal`), `Matchers` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:32, `internal`), `HeaderMatcher` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:38, `internal`), `Range` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:183, `internal`), `FractionMatcher` (xds/src/main/java/io/grpc/xds/internal/Matchers.java:196, `internal`), and 7 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzResponse.java:33— 7 public types in `io.grpc.xds.internal.extauthz` are marked as implementation by their own namespace, folder or name: `Decision` (xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzResponse.java:33, `internal`), `CheckRequestBuilder` (xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java:51, `internal`), `CheckResponseHandler` (xds/src/main/java/io/grpc/xds/internal/extauthz/CheckResponseHandler.java:39, `internal`), `ExtAuthzClientCall` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzClientCall.java:41, `internal`), `ExtAuthzConfig` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzConfig.java:35, `internal`), `ExtAuthzParseException` (xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzParseException.java:23, `internal`), `FailingClientCall` (xds/src/main/java/io/grpc/xds/internal/extauthz/FailingClientCall.java:27, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/extproc/DataPlaneCallState.java:22— 6 public types in `io.grpc.xds.internal.extproc` are marked as implementation by their own namespace, folder or name: `DataPlaneCallState` (xds/src/main/java/io/grpc/xds/internal/extproc/DataPlaneCallState.java:22, `internal`), `EventType` (xds/src/main/java/io/grpc/xds/internal/extproc/EventType.java:22, `internal`), `ExtProcStreamState` (xds/src/main/java/io/grpc/xds/internal/extproc/ExtProcStreamState.java:22, `internal`), `ExternalProcessorServerInterceptorMetricInstruments` (xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorServerInterceptorMetricInstruments.java:29, `internal`), `ExternalProcessorUtil` (xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java:51, `internal`), `KnownLengthInputStream` (xds/src/main/java/io/grpc/xds/internal/extproc/KnownLengthInputStream.java:27, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/grpcservice/CachedChannelManager.java:29— 7 public types in `io.grpc.xds.internal.grpcservice` are marked as implementation by their own namespace, folder or name: `CachedChannelManager` (xds/src/main/java/io/grpc/xds/internal/grpcservice/CachedChannelManager.java:29, `internal`), `GrpcServiceConfig` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:33, `internal`), `Builder` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:46, `internal`), `GoogleGrpcConfig` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceConfig.java:61, `internal`), `GrpcServiceParseException` (xds/src/main/java/io/grpc/xds/internal/grpcservice/GrpcServiceParseException.java:22, `internal`), `HeaderValue` (xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValue.java:28, `internal`), `HeaderValueValidationUtils` (xds/src/main/java/io/grpc/xds/internal/grpcservice/HeaderValueValidationUtils.java:25, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationDisallowedException.java:25— 10 public types in `io.grpc.xds.internal.headermutations` are marked as implementation by their own namespace, folder or name: `HeaderMutationDisallowedException` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationDisallowedException.java:25, `internal`), `HeaderMutationFilter` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationFilter.java:29, `internal`), `HeaderMutationRulesConfig` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesConfig.java:29, `internal`), `Builder` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesConfig.java:66, `internal`), `HeaderMutationRulesParseException` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesParseException.java:22, `internal`), `HeaderMutationRulesParser` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutationRulesParser.java:26, `internal`), `HeaderMutations` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutations.java:24, `internal`), `HeaderMutator` (xds/src/main/java/io/grpc/xds/internal/headermutations/HeaderMutator.java:29, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:55— 18 public types in `io.grpc.xds.internal.rbac.engine` are marked as implementation by their own namespace, folder or name: `GrpcAuthorizationEngine` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:55, `internal`), `Action` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:84, `internal`), `AuthDecision` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:93, `internal`), `AuthConfig` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:106, `internal`), `PolicyMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:126, `internal`), `AuthenticatedMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:145, `internal`), `DestinationIpMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:179, `internal`), `SourceIpMatcher` (xds/src/main/java/io/grpc/xds/internal/rbac/engine/GrpcAuthorizationEngine.java:193, `internal`), and 10 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/security/Closeable.java:19— 10 public types in `io.grpc.xds.internal.security` are marked as implementation by their own namespace, folder or name: `Closeable` (xds/src/main/java/io/grpc/xds/internal/security/Closeable.java:19, `internal`), `CommonTlsContextUtil` (xds/src/main/java/io/grpc/xds/internal/security/CommonTlsContextUtil.java:23, `internal`), `DynamicSslContextProvider` (xds/src/main/java/io/grpc/xds/internal/security/DynamicSslContextProvider.java:41, `internal`), `ReferenceCountingMap` (xds/src/main/java/io/grpc/xds/internal/security/ReferenceCountingMap.java:39, `internal`), `ValueFactory` (xds/src/main/java/io/grpc/xds/internal/security/ReferenceCountingMap.java:105, `internal`), `SecurityProtocolNegotiators` (xds/src/main/java/io/grpc/xds/internal/security/SecurityProtocolNegotiators.java:58, `internal`), `SslContextProvider` (xds/src/main/java/io/grpc/xds/internal/security/SslContextProvider.java:46, `internal`), `Callback` (xds/src/main/java/io/grpc/xds/internal/security/SslContextProvider.java:50, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderClientSslContextProviderFactory.java:37— 10 public types in `io.grpc.xds.internal.security.certprovider` are marked as implementation by their own namespace, folder or name: `CertProviderClientSslContextProviderFactory` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderClientSslContextProviderFactory.java:37, `internal`), `CertProviderServerSslContextProviderFactory` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertProviderServerSslContextProviderFactory.java:36, `internal`), `CertificateProvider` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:45, `internal`), `Watcher` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:50, `internal`), `DistributorWatcher` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java:61, `internal`), `CertificateProviderProvider` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderProvider.java:27, `internal`), `CertificateProviderRegistry` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderRegistry.java:28, `internal`), `CertificateProviderStore` (xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProviderStore.java:35, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/internal/security/trust/CertificateUtils.java:32— 2 public types in `io.grpc.xds.internal.security.trust` are marked as implementation by their own namespace, folder or name: `CertificateUtils` (xds/src/main/java/io/grpc/xds/internal/security/trust/CertificateUtils.java:32, `internal`), `XdsTrustManagerFactory` (xds/src/main/java/io/grpc/xds/internal/security/trust/XdsTrustManagerFactory.java:50, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:46— 1 public type in `io.grpc.xds.orca` is marked as implementation by its own namespace, folder or name: `OrcaServiceImpl` (xds/src/main/java/io/grpc/xds/orca/OrcaServiceImpl.java:46, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Duplicated predicate xds/src/main/java/io/grpc/xds/ClusterManagerLoadBalancer.java:154— `!childResult.hasResult() && childResult.getDelayType() != null` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/ClusterManagerLoadBalancer.java, xds/src/main/java/io/grpc/xds/PriorityLoadBalancer.java. 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 census/src/main/java/io/grpc/census/CensusStatsModule.java:517— `activeStreams == 0 && !finishedCallToBeRecorded` appears character-identically in 2 files — census/src/main/java/io/grpc/census/CensusStatsModule.java, opentelemetry/src/main/java/io/grpc/opentelemetry/OpenTelemetryMetricsModule.java. 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 xds/src/main/java/io/grpc/xds/XdsClusterResource.java:132— `args.getBootstrapInfo() != null && args.getBootstrapInfo().certProviders() != null` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/XdsClusterResource.java, xds/src/main/java/io/grpc/xds/XdsListenerResource.java. 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 grpclb/src/main/java/io/grpc/grpclb/GrpclbLoadBalancerProvider.java:106— `childPolicies == null || childPolicies.isEmpty()` appears character-identically in 2 files — grpclb/src/main/java/io/grpc/grpclb/GrpclbLoadBalancerProvider.java, xds/src/main/java/io/grpc/xds/ClusterManagerLoadBalancerProvider.java. 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/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java:134— `config.shuffleAddressList != null && config.shuffleAddressList` appears character-identically in 2 files — core/src/main/java/io/grpc/internal/PickFirstLeafLoadBalancer.java, core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java. 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 api/src/main/java/io/grpc/NameResolverRegistry.java:110— `existing == null || existing.priority() < provider.priority()` appears character-identically in 2 files — api/src/main/java/io/grpc/NameResolverRegistry.java, xds/src/main/java/io/grpc/xds/XdsCredentialsRegistry.java. 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 api/src/main/java/io/grpc/Uri.java:928— `host.startsWith("[") && host.endsWith("]")` appears character-identically in 2 files — api/src/main/java/io/grpc/Uri.java, okhttp/src/main/java/io/grpc/okhttp/OkHttpTlsUpgrader.java. 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 xds/src/main/java/io/grpc/xds/RoutingUtils.java:95— `hostName.length() != 0 && !hostName.startsWith(".") && !hostName.endsWith(".")` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/RoutingUtils.java, xds/src/main/java/io/grpc/xds/XdsNameResolver.java. 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 xds/src/main/java/io/grpc/xds/RoutingUtils.java:122— `index != 0 && index != pattern.length() - 1` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/RoutingUtils.java, xds/src/main/java/io/grpc/xds/XdsNameResolver.java. 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 xds/src/main/java/io/grpc/xds/RoutingUtils.java:132— `index == 0 && hostName.endsWith(pattern.substring(1))` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/RoutingUtils.java, xds/src/main/java/io/grpc/xds/XdsNameResolver.java. 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 xds/src/main/java/io/grpc/xds/RoutingUtils.java:138— `index == pattern.length() - 1 && hostName.startsWith(pattern.substring(0, pattern.length() - 1))` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/RoutingUtils.java, xds/src/main/java/io/grpc/xds/XdsNameResolver.java. 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 api/src/main/java/io/grpc/TlsChannelCredentials.java:159— `keyManagers != null || trustManagers != null` appears character-identically in 2 files — api/src/main/java/io/grpc/TlsChannelCredentials.java, api/src/main/java/io/grpc/TlsServerCredentials.java. 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/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java:117— `newState == TRANSIENT_FAILURE || newState == IDLE` appears character-identically in 2 files — core/src/main/java/io/grpc/internal/PickFirstLoadBalancer.java, grpclb/src/main/java/io/grpc/grpclb/GrpclbState.java. 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 REDACTED:223— `overallState == CONNECTING || childState == CONNECTING` appears character-identically in 2 files — REDACTED, xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancer.java. 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 REDACTED:226— `overallState == IDLE || childState == IDLE` appears character-identically in 2 files — REDACTED, xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancer.java. 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 REDACTED:220— `overallState == READY || childState == READY` appears character-identically in 2 files — REDACTED, xds/src/main/java/io/grpc/xds/WeightedTargetLoadBalancer.java. 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 xds/src/main/java/io/grpc/xds/RoutingUtils.java:97— `pattern.length() != 0 && !pattern.startsWith(".") && !pattern.endsWith(".")` appears character-identically in 2 files — xds/src/main/java/io/grpc/xds/RoutingUtils.java, xds/src/main/java/io/grpc/xds/XdsNameResolver.java. 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 s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2APrivateKeyMethod.java:131— `resp.hasStatus() && resp.getStatus().getCode() != 0` appears character-identically in 3 files — s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2APrivateKeyMethod.java, s2a/src/main/java/io/grpc/s2a/internal/handshaker/S2ATrustManager.java, s2a/src/main/java/io/grpc/s2a/internal/handshaker/SslContextFactory.java. 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 services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java:329— `retryTimer != null && retryTimer.isPending()` appears character-identically in 2 files — services/src/main/java/io/grpc/protobuf/services/HealthCheckingLoadBalancerFactory.java, xds/src/main/java/io/grpc/xds/orca/OrcaOobUtil.java. 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 REDACTED:83— `state != currentConnectivityState || !picker.equals(currentPicker)` appears character-identically in 3 files — REDACTED, xds/src/main/java/io/grpc/xds/LeastRequestLoadBalancer.java, xds/src/main/java/io/grpc/xds/WeightedRoundRobinLoadBalancer.java. 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 cronet/src/main/java/io/grpc/cronet/CronetClientTransport.java:271— `status.getCode() == Code.CANCELLED || status.getCode() == Code.DEADLINE_EXCEEDED` appears character-identically in 2 files — cronet/src/main/java/io/grpc/cronet/CronetClientTransport.java, okhttp/src/main/java/io/grpc/okhttp/OkHttpClientTransport.java. 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 interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java:206— `v4Address != null && !v4Address.equals(localV4Address)` appears character-identically in 2 files — interop-testing/src/main/java/io/grpc/testing/integration/TestServiceServer.java, interop-testing/src/main/java/io/grpc/testing/integration/XdsTestServer.java. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: api/src/main/java/io/grpc/Uri.java, binder/src/main/java/io/grpc/binder/SecurityPolicies.java, binder/src/main/java/io/grpc/binder/internal/Outbound.java, binder/src/main/java/io/grpc/binder/internal/BinderServer.java, api/src/main/java/io/grpc/QueryParams.java, binder/src/main/java/io/grpc/binder/internal/OneWayBinderProxy.java, binder/src/main/java/io/grpc/binder/internal/BlockInputStream.java, binder/src/main/java/io/grpc/binder/AsyncSecurityPolicies.java (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 8 significant file(s) lose their only recent owner: xds/src/main/java/io/grpc/xds/internal/extauthz/CheckRequestBuilder.java, xds/src/main/java/io/grpc/xds/ExtAuthzFilter.java, xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzCallbackObserver.java, xds/src/main/java/io/grpc/xds/internal/extauthz/CheckResponseHandler.java, xds/src/main/java/io/grpc/xds/internal/extauthz/ExtAuthzClientCall.java, xds/src/main/java/io/grpc/xds/internal/extauthz/CertificateUtils.java, xds/src/main/java/io/grpc/xds/internal/MetricReportUtils.java, xds/src/main/java/io/grpc/xds/internal/extauthz/AuthzResponse.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 7 significant file(s) lose their only recent owner: autosharding/src/main/java/io/grpc/autosharding/AutoShardingPicker.java, xds/src/main/java/io/grpc/xds/internal/matcher/HeadersWrapper.java, autosharding/src/main/java/io/grpc/autosharding/SliceMap.java, netty/src/main/java/io/grpc/netty/GrpcHttp2ConnectionHandler.java, xds/src/main/java/io/grpc/xds/internal/matcher/GrpcCelEnvironment.java, xds/src/main/java/io/grpc/xds/internal/matcher/CelStringExtractor.java, autosharding/src/main/java/io/grpc/autosharding/PickerEndpoint.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 5 significant file(s) lose their only recent owner: xds/src/main/java/io/grpc/xds/ExternalProcessorClientInterceptor.java, xds/src/main/java/io/grpc/xds/ExternalProcessorFilter.java, xds/src/main/java/io/grpc/xds/internal/extproc/ExternalProcessorUtil.java, xds/src/main/java/io/grpc/xds/internal/security/DynamicSslContextProvider.java, core/src/main/java/io/grpc/internal/RefCountedClientTransportFactory.java. Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion xds/build.gradle:1— `xds` (34056 LoC, 186 module-visible types across 12 directories) overshoots its size bounds. 3 of 36 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion core/build.gradle:1— `core` (26405 LoC, 125 module-visible types across 1 directories) overshoots its size bounds. 3 of 36 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion api/build.gradle:1— `api` (21789 LoC, 228 module-visible types across 1 directories) overshoots its size bounds. 3 of 36 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 8.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file census/src/main/java/io/grpc/census/CensusStatsModule.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file services/src/main/java/io/grpc/protobuf/services/BinlogHelper.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file core/src/main/java/io/grpc/internal/ClientCallImpl.java:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Fat interface: ReadableBuffer (16 abstract methods) core/src/main/java/io/grpc/internal/ReadableBuffer.java:33— `ReadableBuffer` declares 16 abstract methods under just 14 distinct name(s): `array`, `arrayOffset`, `byteBufferSupported`, `close`, `getByteBuffer`, `hasArray`, `mark`, `markSupported`, `readBytes`, `readBytes`, `readBytes`, `readInt`, `readUnsignedByte`, `readableBytes`, `reset`, `skipBytes`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 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 (38 single-owned of 542 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; 542 of the 976 production source files in this repository met that bar). They are anonymized user #5 (3 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (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: netty/src/main/java/io/grpc/netty/GrpcHttp2HeadersUtils.java, api/src/main/java/io/grpc/CallCredentials.java, interop-testing/src/main/java/io/grpc/testing/integration/OpenTelemetryUtil.java, api/src/main/java/io/grpc/ServiceProviders.java, xds/src/main/java/io/grpc/xds/AddressFilter.java, core/src/main/java/io/grpc/internal/ServiceConfigUtil.java, xds/src/main/java/io/grpc/xds/internal/security/certprovider/CertificateProvider.java, api/src/context/java/io/grpc/Context.java.
No ADRs found istio-interop-testing/build.gradle:2— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `istio-interop-testing/build.gradle` makes this repository a deployable product (line 2).
Concentrated knowledge decay — 332 of 632 significant files have no living knowledge, while the repository is still being changed at a low rate (99 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 332 separate risks. Counted over 632 of the 976 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 25/27 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `gcp-csm-observability`, `gcp-observability/interop`.
No SAST REDACTED:2— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation examples/example-debug/pom.xml:24— `examples/example-debug/pom.xml` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Benchmarks don't track allocations util/src/jmh/java/io/grpc/util/HandlerRegistryBenchmark.java— A JMH/Jetpack Benchmark suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/73 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Skipped (documented): clientIgnoresTransactionFromNonServerUids binder/src/test/java/io/grpc/binder/internal/RobolectricBinderTransportTest.java:361— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): flowControlPushBack binder/src/test/java/io/grpc/binder/internal/RobolectricBinderTransportTest.java:486— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): serverAlreadyListening binder/src/test/java/io/grpc/binder/internal/RobolectricBinderTransportTest.java:491— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): endOfStreamWithInvalidGzipBlockShouldNotifyDeframerClosedWithPartialMessage core/src/test/java/io/grpc/internal/MessageDeframerTest.java:200— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): happy_eyeballs_connection_results_happen_after_get_to_end core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2760— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): happy_eyeballs_fail_then_trigger_connection_delay core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2891— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): happy_eyeballs_pick_pushes_index_over_end core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2813— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): happy_eyeballs_trigger_connection_delay core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2715— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): healthCheckWithTF_AllowsStateInconsistency core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:735— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): serialized_retries_two_passes core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2972— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): updateAddresses_identical_transient_failure core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:2159— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): updateAddresses_intersecting_transient_failure core/src/test/java/io/grpc/internal/PickFirstLeafLoadBalancerTest.java:1893— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): clientServer_interceptorCalled_logAlways gcp-observability/src/test/java/io/grpc/gcp/observability/LoggingTest.java:87— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): testMetricsExporter gcp-observability/src/test/java/io/grpc/gcp/observability/MetricsTest.java:82— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): testTracesExporter gcp-observability/src/test/java/io/grpc/gcp/observability/TracesTest.java:84— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): socketStats inprocess/src/test/java/io/grpc/inprocess/InProcessTransportTest.java:111— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): verySmallWindowMakesProgress interop-testing/src/test/java/io/grpc/testing/integration/NettyFlowControlTest.java:116— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): censusToOtelGrpcTraceBinPropagator interop-testing/src/test/java/io/grpc/testing/integration/OpenTelemetryContextPropagationTest.java:175— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): otelSpanContextPropagation interop-testing/src/test/java/io/grpc/testing/integration/OpenTelemetryContextPropagationTest.java:163— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): clientChecksInboundMetadataSize_trailer netty/src/test/java/io/grpc/netty/NettyTransportTest.java:117— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): basicMethods netty/src/test/java/io/grpc/netty/UdsNettyChannelProviderTest.java:97— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): managedChannelRegistry_newChannelBuilder netty/src/test/java/io/grpc/netty/UdsNettyChannelProviderTest.java:121— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): newChannelBuilder_success netty/src/test/java/io/grpc/netty/UdsNettyChannelProviderTest.java:103— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): newChannelBuilder_withRegistry_success netty/src/test/java/io/grpc/netty/UdsNettyChannelProviderTest.java:111— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
Skipped (documented): udsClientServerTestUsingProvider netty/src/test/java/io/grpc/netty/UdsNettyChannelProviderTest.java:133— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
+ 10 more in this group — see findings.md.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e6c1-24df-7fbf-b023-4c870d9cd683 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 27 · Warnings: 1200 · Recommendations: 437 · Info: 35 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 23:46 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.