Public report of BrighterCommand/Brighter, published 17 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, 17 November 2026, 06:43 UTC · Survey ID cd_51b947204ff74a5293f72c43d79c020d
BrighterCommand/Brighter
Measured 17 November 2026, 06:30 UTC, at code version 395425e
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAt risk
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: 147,359 lines of product code in 551 projects, tests not counted · Estimated rebuild effort: about 6.8 person-years · Weakest lens: Event-Driven, 38.2
Findings by how serious they are
249 critical1470 serious672 minor
10 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 06:30 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
78of 78 dimensions measured by tools.
2275of 2391 findings point to an exact file and line, so you can open each one in the code. The other 116 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 147,359 lines of product code in 551 projects.
BrighterCommand/Brighter is rated At risk because critical security findings are open. It scores 45.4 out of 100, which the At risk rating leaves unchanged.
Event-Driven, at 38.2, is the weakest lens and counts most in the score. The best first step is reshaping the commands and events, worth about 5.9 points. Stopping the event handlers from waiting on other services comes next, worth about 4.4 points. Raising Event-Driven to 70 would lift the score to about 51.3.
101 weaknesses in the code could be used by an attacker. Seventy-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and twenty-five settings leave the servers or containers unsafe. Fixing the weaknesses the scanner points to, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the 12 secrets exposed to more of the pipeline than needed, and the seven pipeline steps that run downloads without checking them need each download checked against a known checksum first. Saving the change and the message together would take care of the six places where data is saved and a message sent separately.
The product code is 147,359 lines, about €990,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Event-Driven rose from 38.2 to 70, the lowest score rated Strong, the score would rise from 45.4 to about 51.3.
Code composition: what the lines of code are
Business logic 7%Supporting code 11%Tests 82%Generated by tools 0%Code analyzers 0%
Rebuild cost: about €990,000 · Estimate
Cost to rebuild
€330,000 to €1,700,000, for 5,475 to 17,459 hours of work, about 6.8 person-years for 4 to 13 engineers
Difficulty of the problem
Very high, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. 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: 147,359 lines of product code, of which 40% is declarations and boilerplate, 21% straight logic and 40% logic with branches
Comment lines
The estimate prices 97,094 lines. Comment lines count towards the size of 147,359 lines but aren't priced as work.
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.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Keep one handler per command (single owner); use events for the fan-out where many subscribers react.
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 4.1 points · Medium effort · Access Controls
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 €990,000 to build again, about 6.8 person-years of work. Its weakest lens is Event-Driven, at 38.2 (Weak). Event-Driven is about whether the parts of the system can rely on the messages they send each other. Because the weakest lens counts most in the score, work on Event-Driven also moves the score most.
Based on: the rebuild estimate · the Event-Driven grade · how much each lens counts
What to do: Start with the Event-Driven actions in Top priorities.
If you do one thing first · First action
Keep one handler per command (single owner); use events for the fan-out where many subscribers react. Of all the actions in this report, it raises the score most for the work it takes: about 5.9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 273,104 lines over the last 90 days, which is about 1,107,588 lines a year. At that pace, the extra work comes to an estimated 100.1 to 600.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
167 modules, with 258 dependencies between them. 3 loops run through 8 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 127 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.
3 pairs of types, where a type in MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses a type in MessagingGateway.AzureServiceBus.ClientProvider.
MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses MessagingGateway.AzureServiceBus.ClientProvider, so a change to MessagingGateway.AzureServiceBus.ClientProvider can break MessagingGateway.AzureServiceBus.AzureServiceBusWrappers, while a change to MessagingGateway.AzureServiceBus.AzureServiceBusWrappers can't break MessagingGateway.AzureServiceBus.ClientProvider.
Position
Below the diagonal: MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses a module listed above it, which is the healthy direction.
4→14 MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses MessagingGateway.AzureServiceBuspart of a loop✕
Connections
2 pairs of types, where a type in MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses a type in MessagingGateway.AzureServiceBus.
MessagingGateway.AzureServiceBus.AzureServiceBusWrappers uses MessagingGateway.AzureServiceBus, so a change to MessagingGateway.AzureServiceBus can break MessagingGateway.AzureServiceBus.AzureServiceBusWrappers, while a change to MessagingGateway.AzureServiceBus.AzureServiceBusWrappers can't break MessagingGateway.AzureServiceBus.
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.
5→7 Observability uses CircuitBreakerpart of a loop✕
Connections
1 pair of types, where a type in Observability uses a type in CircuitBreaker.
Observability uses Paramore.Brighter, so a change to Paramore.Brighter can break Observability, while a change to Observability can't break Paramore.Brighter.
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.
Validation uses Inbox, so a change to Inbox can break Validation, while a change to Validation can't break Inbox.
Position
Below the diagonal: Validation uses a module listed above it, which is the healthy direction.
6→9 Validation uses Paramore.Brighterpart of a loop✕
Connections
26 pairs of types, where a type in Validation uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
CircuitBreaker uses Paramore.Brighter, so a change to Paramore.Brighter can break CircuitBreaker, while a change to CircuitBreaker can't break Paramore.Brighter.
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.
Transforms.Storage uses Observability, so a change to Observability can break Transforms.Storage, while a change to Transforms.Storage can't break Observability.
Position
Below the diagonal: Transforms.Storage uses a module listed above it, which is the healthy direction.
Paramore.Brighter uses FeatureSwitch, so a change to FeatureSwitch can break Paramore.Brighter, while a change to Paramore.Brighter can't break FeatureSwitch.
Position
Below the diagonal: Paramore.Brighter uses a module listed above it, which is the healthy direction.
46 pairs of types, where a type in Paramore.Brighter uses a type in Observability. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Paramore.Brighter uses Observability, so a change to Observability can break Paramore.Brighter, while a change to Paramore.Brighter can't break Observability.
Position
Below the diagonal: Paramore.Brighter uses a module listed above it, which is the healthy direction.
Paramore.Brighter uses CircuitBreaker, so a change to CircuitBreaker can break Paramore.Brighter, while a change to Paramore.Brighter can't break CircuitBreaker.
Position
Below the diagonal: Paramore.Brighter uses a module listed above it, which is the healthy direction.
Extensions.DependencyInjection uses FeatureSwitch, so a change to FeatureSwitch can break Extensions.DependencyInjection, while a change to Extensions.DependencyInjection can't break FeatureSwitch.
Position
Below the diagonal: Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
Extensions.DependencyInjection uses Observability, so a change to Observability can break Extensions.DependencyInjection, while a change to Extensions.DependencyInjection can't break Observability.
Position
Below the diagonal: Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
Extensions.DependencyInjection uses Validation, so a change to Validation can break Extensions.DependencyInjection, while a change to Extensions.DependencyInjection can't break Validation.
Position
Below the diagonal: Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
Extensions.DependencyInjection uses CircuitBreaker, so a change to CircuitBreaker can break Extensions.DependencyInjection, while a change to Extensions.DependencyInjection can't break CircuitBreaker.
Position
Below the diagonal: Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
82 pairs of types, where a type in Extensions.DependencyInjection uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Extensions.DependencyInjection uses Paramore.Brighter, so a change to Paramore.Brighter can break Extensions.DependencyInjection, while a change to Extensions.DependencyInjection can't break Paramore.Brighter.
Position
Below the diagonal: Extensions.DependencyInjection uses a module listed above it, which is the healthy direction.
MessagingGateway.AWSSQS uses Observability, so a change to Observability can break MessagingGateway.AWSSQS, while a change to MessagingGateway.AWSSQS can't break Observability.
Position
Below the diagonal: MessagingGateway.AWSSQS uses a module listed above it, which is the healthy direction.
78 pairs of types, where a type in MessagingGateway.AWSSQS uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.AWSSQS uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.AWSSQS, while a change to MessagingGateway.AWSSQS can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.AWSSQS uses a module listed above it, which is the healthy direction.
MessagingGateway.AWSSQS.V4 uses Observability, so a change to Observability can break MessagingGateway.AWSSQS.V4, while a change to MessagingGateway.AWSSQS.V4 can't break Observability.
Position
Below the diagonal: MessagingGateway.AWSSQS.V4 uses a module listed above it, which is the healthy direction.
78 pairs of types, where a type in MessagingGateway.AWSSQS.V4 uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.AWSSQS.V4 uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.AWSSQS.V4, while a change to MessagingGateway.AWSSQS.V4 can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.AWSSQS.V4 uses a module listed above it, which is the healthy direction.
MessagingGateway.AzureServiceBus uses MessagingGateway.AzureServiceBus.ClientProvider, so a change to MessagingGateway.AzureServiceBus.ClientProvider can break MessagingGateway.AzureServiceBus, while a change to MessagingGateway.AzureServiceBus can't break MessagingGateway.AzureServiceBus.ClientProvider.
Position
Below the diagonal: MessagingGateway.AzureServiceBus uses a module listed above it, which is the healthy direction.
MessagingGateway.AzureServiceBus uses MessagingGateway.AzureServiceBus.AzureServiceBusWrappers, so a change to MessagingGateway.AzureServiceBus.AzureServiceBusWrappers can break MessagingGateway.AzureServiceBus, while a change to MessagingGateway.AzureServiceBus can't break MessagingGateway.AzureServiceBus.AzureServiceBusWrappers.
Position
Below the diagonal: MessagingGateway.AzureServiceBus uses a module listed above it, which is the healthy direction.
MessagingGateway.AzureServiceBus uses Observability, so a change to Observability can break MessagingGateway.AzureServiceBus, while a change to MessagingGateway.AzureServiceBus can't break Observability.
Position
Below the diagonal: MessagingGateway.AzureServiceBus uses a module listed above it, which is the healthy direction.
71 pairs of types, where a type in MessagingGateway.AzureServiceBus uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.AzureServiceBus uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.AzureServiceBus, while a change to MessagingGateway.AzureServiceBus can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.AzureServiceBus uses a module listed above it, which is the healthy direction.
MessagingGateway.MsSql uses Observability, so a change to Observability can break MessagingGateway.MsSql, while a change to MessagingGateway.MsSql can't break Observability.
Position
Below the diagonal: MessagingGateway.MsSql uses a module listed above it, which is the healthy direction.
58 pairs of types, where a type in MessagingGateway.MsSql uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.MsSql uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.MsSql, while a change to MessagingGateway.MsSql can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.MsSql uses a module listed above it, which is the healthy direction.
MessagingGateway.Postgres uses Observability, so a change to Observability can break MessagingGateway.Postgres, while a change to MessagingGateway.Postgres can't break Observability.
Position
Below the diagonal: MessagingGateway.Postgres uses a module listed above it, which is the healthy direction.
41 pairs of types, where a type in MessagingGateway.Postgres uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.Postgres uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.Postgres, while a change to MessagingGateway.Postgres can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.Postgres uses a module listed above it, which is the healthy direction.
Outbox.DynamoDB uses Observability, so a change to Observability can break Outbox.DynamoDB, while a change to Outbox.DynamoDB can't break Observability.
Position
Below the diagonal: Outbox.DynamoDB uses a module listed above it, which is the healthy direction.
Outbox.DynamoDB uses Paramore.Brighter, so a change to Paramore.Brighter can break Outbox.DynamoDB, while a change to Outbox.DynamoDB can't break Paramore.Brighter.
Position
Below the diagonal: Outbox.DynamoDB uses a module listed above it, which is the healthy direction.
Outbox.DynamoDB.V4 uses Observability, so a change to Observability can break Outbox.DynamoDB.V4, while a change to Outbox.DynamoDB.V4 can't break Observability.
Position
Below the diagonal: Outbox.DynamoDB.V4 uses a module listed above it, which is the healthy direction.
Outbox.DynamoDB.V4 uses Paramore.Brighter, so a change to Paramore.Brighter can break Outbox.DynamoDB.V4, while a change to Outbox.DynamoDB.V4 can't break Paramore.Brighter.
Position
Below the diagonal: Outbox.DynamoDB.V4 uses a module listed above it, which is the healthy direction.
RequestValidation.Handlers uses Paramore.Brighter, so a change to Paramore.Brighter can break RequestValidation.Handlers, while a change to RequestValidation.Handlers can't break Paramore.Brighter.
Position
Below the diagonal: RequestValidation.Handlers uses a module listed above it, which is the healthy direction.
ServiceActivator uses Observability, so a change to Observability can break ServiceActivator, while a change to ServiceActivator can't break Observability.
Position
Below the diagonal: ServiceActivator uses a module listed above it, which is the healthy direction.
75 pairs of types, where a type in ServiceActivator uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ServiceActivator uses Paramore.Brighter, so a change to Paramore.Brighter can break ServiceActivator, while a change to ServiceActivator can't break Paramore.Brighter.
Position
Below the diagonal: ServiceActivator uses a module listed above it, which is the healthy direction.
AsyncAPI uses Extensions.DependencyInjection, so a change to Extensions.DependencyInjection can break AsyncAPI, while a change to AsyncAPI can't break Extensions.DependencyInjection.
Position
Below the diagonal: AsyncAPI uses a module listed above it, which is the healthy direction.
BoxProvisioning uses Observability, so a change to Observability can break BoxProvisioning, while a change to BoxProvisioning can't break Observability.
Position
Below the diagonal: BoxProvisioning uses a module listed above it, which is the healthy direction.
BoxProvisioning uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning, while a change to BoxProvisioning can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning uses a module listed above it, which is the healthy direction.
BoxProvisioning uses Extensions.DependencyInjection, so a change to Extensions.DependencyInjection can break BoxProvisioning, while a change to BoxProvisioning can't break Extensions.DependencyInjection.
Position
Below the diagonal: BoxProvisioning uses a module listed above it, which is the healthy direction.
Inbox.Firestore uses Observability, so a change to Observability can break Inbox.Firestore, while a change to Inbox.Firestore can't break Observability.
Position
Below the diagonal: Inbox.Firestore uses a module listed above it, which is the healthy direction.
Inbox.Firestore uses Paramore.Brighter, so a change to Paramore.Brighter can break Inbox.Firestore, while a change to Inbox.Firestore can't break Paramore.Brighter.
Position
Below the diagonal: Inbox.Firestore uses a module listed above it, which is the healthy direction.
Inbox.MongoDb uses Paramore.Brighter, so a change to Paramore.Brighter can break Inbox.MongoDb, while a change to Inbox.MongoDb can't break Paramore.Brighter.
Position
Below the diagonal: Inbox.MongoDb uses a module listed above it, which is the healthy direction.
MessageScheduler.Azure uses MessagingGateway.AzureServiceBus.ClientProvider, so a change to MessagingGateway.AzureServiceBus.ClientProvider can break MessageScheduler.Azure, while a change to MessageScheduler.Azure can't break MessagingGateway.AzureServiceBus.ClientProvider.
Position
Below the diagonal: MessageScheduler.Azure uses a module listed above it, which is the healthy direction.
MessageScheduler.Azure uses Observability, so a change to Observability can break MessageScheduler.Azure, while a change to MessageScheduler.Azure can't break Observability.
Position
Below the diagonal: MessageScheduler.Azure uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in MessageScheduler.Azure uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessageScheduler.Azure uses Paramore.Brighter, so a change to Paramore.Brighter can break MessageScheduler.Azure, while a change to MessageScheduler.Azure can't break Paramore.Brighter.
Position
Below the diagonal: MessageScheduler.Azure uses a module listed above it, which is the healthy direction.
MessageScheduler.Azure uses MessagingGateway.AzureServiceBus, so a change to MessagingGateway.AzureServiceBus can break MessageScheduler.Azure, while a change to MessageScheduler.Azure can't break MessagingGateway.AzureServiceBus.
Position
Below the diagonal: MessageScheduler.Azure uses a module listed above it, which is the healthy direction.
MessagingGateway.Kafka uses Observability, so a change to Observability can break MessagingGateway.Kafka, while a change to MessagingGateway.Kafka can't break Observability.
Position
Below the diagonal: MessagingGateway.Kafka uses a module listed above it, which is the healthy direction.
68 pairs of types, where a type in MessagingGateway.Kafka uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.Kafka uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.Kafka, while a change to MessagingGateway.Kafka can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.Kafka uses a module listed above it, which is the healthy direction.
MessagingGateway.RMQ.Sync uses Observability, so a change to Observability can break MessagingGateway.RMQ.Sync, while a change to MessagingGateway.RMQ.Sync can't break Observability.
Position
Below the diagonal: MessagingGateway.RMQ.Sync uses a module listed above it, which is the healthy direction.
61 pairs of types, where a type in MessagingGateway.RMQ.Sync uses a type in Paramore.Brighter. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MessagingGateway.RMQ.Sync uses Paramore.Brighter, so a change to Paramore.Brighter can break MessagingGateway.RMQ.Sync, while a change to MessagingGateway.RMQ.Sync can't break Paramore.Brighter.
Position
Below the diagonal: MessagingGateway.RMQ.Sync uses a module listed above it, which is the healthy direction.
MessagingGateway.RMQ.Sync uses Tasks, so a change to Tasks can break MessagingGateway.RMQ.Sync, while a change to MessagingGateway.RMQ.Sync can't break Tasks.
Position
Below the diagonal: MessagingGateway.RMQ.Sync uses a module listed above it, which is the healthy direction.
Outbox.Firestore uses Observability, so a change to Observability can break Outbox.Firestore, while a change to Outbox.Firestore can't break Observability.
Position
Below the diagonal: Outbox.Firestore uses a module listed above it, which is the healthy direction.
Outbox.Firestore uses Paramore.Brighter, so a change to Paramore.Brighter can break Outbox.Firestore, while a change to Outbox.Firestore can't break Paramore.Brighter.
Position
Below the diagonal: Outbox.Firestore uses a module listed above it, which is the healthy direction.
Outbox.Hosting uses Paramore.Brighter, so a change to Paramore.Brighter can break Outbox.Hosting, while a change to Outbox.Hosting can't break Paramore.Brighter.
Position
Below the diagonal: Outbox.Hosting uses a module listed above it, which is the healthy direction.
Outbox.Hosting uses Extensions.DependencyInjection, so a change to Extensions.DependencyInjection can break Outbox.Hosting, while a change to Outbox.Hosting can't break Extensions.DependencyInjection.
Position
Below the diagonal: Outbox.Hosting uses a module listed above it, which is the healthy direction.
Outbox.MongoDb uses Paramore.Brighter, so a change to Paramore.Brighter can break Outbox.MongoDb, while a change to Outbox.MongoDb can't break Paramore.Brighter.
Position
Below the diagonal: Outbox.MongoDb uses a module listed above it, which is the healthy direction.
ServiceActivator.Control.Extensions uses Extensions.DependencyInjection, so a change to Extensions.DependencyInjection can break ServiceActivator.Control.Extensions, while a change to ServiceActivator.Control.Extensions can't break Extensions.DependencyInjection.
Position
Below the diagonal: ServiceActivator.Control.Extensions uses a module listed above it, which is the healthy direction.
ServiceActivator.Control.Extensions uses ServiceActivator, so a change to ServiceActivator can break ServiceActivator.Control.Extensions, while a change to ServiceActivator.Control.Extensions can't break ServiceActivator.
Position
Below the diagonal: ServiceActivator.Control.Extensions uses a module listed above it, which is the healthy direction.
ServiceActivator.Ports.Commands uses Paramore.Brighter, so a change to Paramore.Brighter can break ServiceActivator.Ports.Commands, while a change to ServiceActivator.Ports.Commands can't break Paramore.Brighter.
Position
Below the diagonal: ServiceActivator.Ports.Commands uses a module listed above it, which is the healthy direction.
ServiceActivator.Ports.Commands uses ServiceActivator, so a change to ServiceActivator can break ServiceActivator.Ports.Commands, while a change to ServiceActivator.Ports.Commands can't break ServiceActivator.
Position
Below the diagonal: ServiceActivator.Ports.Commands uses a module listed above it, which is the healthy direction.
BoxProvisioning.MsSql uses Observability, so a change to Observability can break BoxProvisioning.MsSql, while a change to BoxProvisioning.MsSql can't break Observability.
Position
Below the diagonal: BoxProvisioning.MsSql uses a module listed above it, which is the healthy direction.
BoxProvisioning.MsSql uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning.MsSql, while a change to BoxProvisioning.MsSql can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning.MsSql uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in BoxProvisioning.MsSql uses a type in BoxProvisioning. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BoxProvisioning.MsSql uses BoxProvisioning, so a change to BoxProvisioning can break BoxProvisioning.MsSql, while a change to BoxProvisioning.MsSql can't break BoxProvisioning.
Position
Below the diagonal: BoxProvisioning.MsSql uses a module listed above it, which is the healthy direction.
BoxProvisioning.MySql uses Observability, so a change to Observability can break BoxProvisioning.MySql, while a change to BoxProvisioning.MySql can't break Observability.
Position
Below the diagonal: BoxProvisioning.MySql uses a module listed above it, which is the healthy direction.
BoxProvisioning.MySql uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning.MySql, while a change to BoxProvisioning.MySql can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning.MySql uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in BoxProvisioning.MySql uses a type in BoxProvisioning. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BoxProvisioning.MySql uses BoxProvisioning, so a change to BoxProvisioning can break BoxProvisioning.MySql, while a change to BoxProvisioning.MySql can't break BoxProvisioning.
Position
Below the diagonal: BoxProvisioning.MySql uses a module listed above it, which is the healthy direction.
BoxProvisioning.PostgreSql uses Observability, so a change to Observability can break BoxProvisioning.PostgreSql, while a change to BoxProvisioning.PostgreSql can't break Observability.
Position
Below the diagonal: BoxProvisioning.PostgreSql uses a module listed above it, which is the healthy direction.
BoxProvisioning.PostgreSql uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning.PostgreSql, while a change to BoxProvisioning.PostgreSql can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning.PostgreSql uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in BoxProvisioning.PostgreSql uses a type in BoxProvisioning. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BoxProvisioning.PostgreSql uses BoxProvisioning, so a change to BoxProvisioning can break BoxProvisioning.PostgreSql, while a change to BoxProvisioning.PostgreSql can't break BoxProvisioning.
Position
Below the diagonal: BoxProvisioning.PostgreSql uses a module listed above it, which is the healthy direction.
BoxProvisioning.Spanner uses Observability, so a change to Observability can break BoxProvisioning.Spanner, while a change to BoxProvisioning.Spanner can't break Observability.
Position
Below the diagonal: BoxProvisioning.Spanner uses a module listed above it, which is the healthy direction.
BoxProvisioning.Spanner uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning.Spanner, while a change to BoxProvisioning.Spanner can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning.Spanner uses a module listed above it, which is the healthy direction.
BoxProvisioning.Spanner uses BoxProvisioning, so a change to BoxProvisioning can break BoxProvisioning.Spanner, while a change to BoxProvisioning.Spanner can't break BoxProvisioning.
Position
Below the diagonal: BoxProvisioning.Spanner uses a module listed above it, which is the healthy direction.
BoxProvisioning.Sqlite uses Observability, so a change to Observability can break BoxProvisioning.Sqlite, while a change to BoxProvisioning.Sqlite can't break Observability.
Position
Below the diagonal: BoxProvisioning.Sqlite uses a module listed above it, which is the healthy direction.
BoxProvisioning.Sqlite uses Paramore.Brighter, so a change to Paramore.Brighter can break BoxProvisioning.Sqlite, while a change to BoxProvisioning.Sqlite can't break Paramore.Brighter.
Position
Below the diagonal: BoxProvisioning.Sqlite uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in BoxProvisioning.Sqlite uses a type in BoxProvisioning. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BoxProvisioning.Sqlite uses BoxProvisioning, so a change to BoxProvisioning can break BoxProvisioning.Sqlite, while a change to BoxProvisioning.Sqlite can't break BoxProvisioning.
Position
Below the diagonal: BoxProvisioning.Sqlite uses a module listed above it, which is the healthy direction.
Outbox.Hosting.HealthChecks uses Observability, so a change to Observability can break Outbox.Hosting.HealthChecks, while a change to Outbox.Hosting.HealthChecks can't break Observability.
Position
Below the diagonal: Outbox.Hosting.HealthChecks uses a module listed above it, which is the healthy direction.
Outbox.Hosting.HealthChecks uses CircuitBreaker, so a change to CircuitBreaker can break Outbox.Hosting.HealthChecks, while a change to Outbox.Hosting.HealthChecks can't break CircuitBreaker.
Position
Below the diagonal: Outbox.Hosting.HealthChecks uses a module listed above it, which is the healthy direction.
Outbox.Hosting.HealthChecks uses Outbox.Hosting, so a change to Outbox.Hosting can break Outbox.Hosting.HealthChecks, while a change to Outbox.Hosting.HealthChecks can't break Outbox.Hosting.
Position
Below the diagonal: Outbox.Hosting.HealthChecks uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64.8 · Adequate · gated by D4 ·
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
221
High / Critical
A02:2025 — Security Misconfiguration
42
High / Critical
A03:2025 — Software Supply Chain Failures
18
High / Critical
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
Top priorities: Keep one handler per command (single owner); use events for the fan-out where many subscribers react; Remove synchronous remote calls from message handlers — react by publishing further messages, so services stay temporally decoupled; Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Keep one handler per command (single owner); use events for the fan-out where many subscribers react.
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Resolve the 6 ADR not followed finding(s) in ADR Conformance — start with 0063-failed-delivery-context.md (3), 0045-provide-dlq-where-missing.md, 0064-validate-pipeline-assembly-and-provider-registration.md.
Per-file score 0–10 — a quality signature. Of 445 files carrying findings, judged against the Production bar: 3% slop · 46% mixed · 51% near-clean.
File
Score
Band
Worst signal
REDACTED
0.2
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.4
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.4
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
1.5
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.3
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
2.5
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.2
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.3
Slop
IaC & Container Security: High IaC: REDACTED
REDACTED
3.6
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
REDACTED Scanning: Leaked secret: REDACTED
REDACTED
4.4
Mixed
IaC & Container Security: High IaC: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.0
Mixed
Dependency Vulnerabilities: High CVE: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 249
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 — 1470
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 — 672
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 78 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 — 78 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, 2275 of 2391 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 — 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. At least one `dotnet test` target was stopped at its time budget, so the gathered reports cover only part of the suite. The overall 31.8% is a FLOOR (everything the completed runs covered really is covered), but a per-file figure from a partial gather cannot tell an untested file from one whose test project never ran — so per-file and CRAP rows are withheld rather than published as measurements. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and per-file rows can be read without a re-run.
D8 Code Coverage — 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. 5 test(s) skipped themselves while running here (their declarations do not skip them: something they need, such as a database or a device, was not available to this run). The 25 production file(s) those tests reach are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 31.8% whatever they read, rather than published as low coverage or counted toward the figure. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report of a run where those tests execute, and their files are read from it.
D8 Code Coverage — 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. 426 test(s) failed in this run, so they did not run to their end (commonly a database, container or service they need was not available here). The 255 production file(s) those tests reach are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 31.8% whatever they read, rather than published as low coverage or counted toward the figure. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report of a run where those tests pass, and their files are read from it.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — no test tier produced comparable repeat runs within its budget (unit: not included — too large to re-run within its budget; other: not included — its runs surfaced no test).
D17 Explicit Debt — 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. Explicit Debt couldn't be assessed within its 15-minute budget on a solution this large — not included in this run.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (147,359 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D31 IaC & Container Security — 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.claude/commands/refactor/comment_census.cs`, `.claude/commands/refactor/comment_only_check.cs`, `benchmarks/Paramore.Brighter.Benchmarks/BenchmarkCommand.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/Program.cs`, … (+201 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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. Render strategy: boot via AspireAppHost (REDACTED). the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence.
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. 56 further occurrence(s) are not listed individually; the score already reflects all 96.
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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
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.
P10 Library API & versioning — 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. Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
P11 BDD / executable specs — 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. BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
P7 Outbound HTTP resilience — 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. Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: ArgumentException: SyntaxTree is not part of the compilation (Parameter 'syntaxTree').
PF3 Async & latency hygiene — 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. 1589 further occurrence(s) are not listed individually; the score already reflects all 1629.
X1 Async correctness — 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. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 62 further occurrence(s) are not listed individually; the score already reflects all 102.
X18 Disposal-pattern correctness — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
X2 Cancellation propagation — 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. 128 further occurrence(s) are not listed individually; the score already reflects all 168.
Repo exclusion declarations: 5 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D25 ADR Conformance: ADR conformance checks only decisions stated in a checkable form (a ruled-out element, package or dependency, an adr-rules block, a declared delivery status): a decision written only as prose is unverifiable, and decisions never written down are not checked.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Proactor.EventLoop at 36. A further 4 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 DbSystemExtensions.ToDbName at 56 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Paramore.Brighter/Observability/DbSystemExtensions.cs (DbSystemExtensions.ToDbName at 56), REDACTED (MsSqlMessagingGateway.IsTransient at 21), REDACTED (MessageHeader.Equals at 17), src/Paramore.Brighter/Observability/MessagingSystemExtensions.cs (MessagingSystemExtensions.ToMessagingSystemName at 17). 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.
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Proactor.EventLoop (cyclomatic 36), Reactor.Run (cyclomatic 36), RocketMessageConsumer.CreateMessage (cyclomatic 28). — 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 14 together lifts Cyclomatic Complexity from 8.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.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with Proactor.EventLoop (cognitive 91), Reactor.Run (cognitive 91), OutboxProducerMediator.BulkDispatchAsync (cognitive 46). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.1 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 Classes9.4 / 10Stronggated by 27 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 TooManyMethods finding(s) in God Classes — start with DynamoDbOutbox.cs (2), RelationDatabaseOutbox.cs, CommandProcessor.cs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 9 FileTooLong finding(s) in God Classes — start with DynamoDbOutbox.cs (2), RelationDatabaseOutbox.cs, CommandProcessor.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with Reactor.cs, Proactor.cs, RocketMessageConsumer.cs. — One of this dimension's main actionable groups (4 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.
519 duplicated block group(s) detected. 19.5 % of the production lines (28,712 of 147,359) are in a reported copy. A further 1473 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 95 of the 1992 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (8 corresponding lines) · ×23src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72
+ 221 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 32 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with CommandProcessor.cs (6), MsSqlBoxProvisioningExtensions.cs (2), MySqlBoxProvisioningExtensions.cs (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 31 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with SqsInlineMessageCreator.cs (3), DynamoDbOutbox.cs (3), CompressPayloadTransformer.cs (2). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 26 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with RmqMessageCreator.cs (5), SqsInlineMessageCreator.cs (3), AwsScheduler.cs (3). — One of this dimension's main actionable groups (26 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.9 / 10Adequategated by 1 critical finding✓ 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.
Off the main sequence: Paramore.Brighter.Extensions.DependencyInjection(netstandard2.0) · ×2src/Paramore.Brighter.Extensions.DependencyInjection/Paramore.Brighter.Extensions.DependencyInjection.csproj:1
What to do
Resolve the 1 Circular dependency finding(s) in Coupling — start with Paramore.Brighter.AsyncAPI.NJsonSchema.csproj. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Off the main sequence finding(s) in Coupling — start with Paramore.Brighter.Extensions.DependencyInjection.csproj, Paramore.Brighter.MySql.csproj. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with BrighterTracer.cs, MessagePump.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 31 mechanizable ADR(s) are enforced: 31 by analyzers, 0 by tests. Cycles found: 1.
Circular dependency
What to do
Resolve the 1 Circular dependency finding(s) in Architectural Integrity. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d7_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage6.7 / 10Adequate✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No test project references Paramore.Brighter.MsSql.Azuresrc/Paramore.Brighter.MsSql.Azure/Paramore.Brighter.MsSql.Azure.csproj
No test project references Fr15Diagnosticbugfixes/0037-gcp-requeue-immediate-redelivery/diagnostic/Fr15Diagnostic.csproj
No test project references Paramore.Brighter.Dappersrc/Paramore.Brighter.Dapper/Paramore.Brighter.Dapper.csproj
No test project references pileupbugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/pileup.csproj
No test project references starvebugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/starve.csproj
What to do
Resolve the 1 No test project references Paramore.Brighter.MsSql.Azure finding(s) in Code Coverage — start with Paramore.Brighter.MsSql.Azure.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references Fr15Diagnostic finding(s) in Code Coverage — start with Fr15Diagnostic.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references Paramore.Brighter.Dapper finding(s) in Code Coverage — start with Paramore.Brighter.Dapper.csproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 12 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
83 skipped (83 with a documented reason), 3 zero-assertion, 5 synchronised by a fixed sleep, 4 racing the wall clock, 6 mock references across 6195 tests.
Races the wall clock: When_scheduling_a_post_should_preserve_context_metadata · ×4tests/Paramore.Brighter.AWSScheduler.Tests/When_scheduling_a_post_should_preserve_context_metadata.cs:48
No assertions: When_Unwrapping_A_Vanilla_Message_Mapper · ×3tests/Paramore.Brighter.Core.Tests/MessageSerialisation/When_Unwrapping_A_Vanilla_Message_Mapper.cs:39
Resolve the 5 Fixed-sleep synchronisation finding(s) in Test Quality — start with When_the_outstanding_limit_is_exceeded_with_an_async_only_outbox_should_throw.cs, When_more_callbacks_are_queued_than_the_batch_size_should_run_a_batch_at_once.cs, When_a_gcp_stream_channel_is_disposed_with_a_redelivery_buffered_after_requeue_should_return_promptly.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Races the wall clock finding(s) in Test Quality — start with When_scheduling_a_post_should_preserve_context_metadata.cs (3), When_scheduling_a_request_should_preserve_its_context_data.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 No assertions finding(s) in Test Quality — start with When_Unwrapping_A_Vanilla_Message_Mapper.cs, When_Unwrapping_A_Vanilla_Message_MapperAsync.cs, When_validating_a_luggage_store_exists.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Prerelease dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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 113 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 140 direct `PackageReference`(s), and 102 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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.
Top hotspots: src/Paramore.Brighter.ServiceActivator/Proactor.cs (8×36=288); src/Paramore.Brighter.ServiceActivator/Reactor.cs (8×36=288); src/Paramore.Brighter/OutboxProducerMediator.cs (15×16=240) Repeated repair below the complexity floor: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs (9 of 13 changes were fixes); src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs (8 of 10 changes were fixes); src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs (8 of 9 changes were fixes)
Resolve the 50 Repeated repair finding(s) in Churn × Complexity Hotspots — start with RmqMessageProducer.cs (2), RmqMessageConsumer.cs (2), DynamoDbOutbox.cs (2). — One of this dimension's main actionable groups (50 warning-level).
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with Proactor.cs, Reactor.cs, OutboxProducerMediator.cs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor7.8 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
163 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs. Counted over 755 of the 1170 production source files in this repository: 413 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×6
Further sole-owners (lower concentration)
What to do
Resolve the 6 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
548 projects, 12507 source files, 590964 hand-written lines of code (146978 production / 443986 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 771 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 1344 inter-project edges.
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.
2 of 2 documentation facets pass in full. 66 document(s) read across 98 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality9.6 / 10Exemplary✓ 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.
15 of 132 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
ADR still proposed, but the code already adopted it · ×12docs/adr/0024-scheduling-requests-and-messages.md:4detected by adr-integrity
ADR has no Consequences section · ×3docs/adr/0024-scheduling-requests-and-messages.md:16detected by adr-integrity
ADR superseded but its status says otherwisedocs/adr/0053-box-database-migration.md:4detected by adr-integrity
✓ On the Gold path — maintain.
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
doc comments repeat the names · ×73src/Paramore.Brighter/AsyncHandlerFactory.cs:29
What to do
Resolve the 91 redundant comment finding(s) in Comment Value — start with DynamoDbTableFactory.cs (4), When_a_gcp_pull_consumer_rejects_for_delivery_error_should_publish_stamped_copy_to_dlq.cs (4), When_a_gcp_pull_consumer_rejects_unacceptable_should_route_to_invalid_channel_or_dlq_async.cs (4). — One of this dimension's main actionable groups (91 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D25 · ADR Conformance3.3 / 10Weak✓ Tool-verified
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Each binding ADR read for checkable forms: a backticked element its Decision section rules out, a ruled-out package the manifests declare, a forbidden module dependency, an opt-in adr-rules block, and a declared delivery status the code does not yet carry. A prose decision with no checkable form is unverifiable, neither a finding nor a pass. Deterministic, no model. Advisory.
4 of 6 checkable records are broken by the code or by their own declared delivery (6 of 94 binding records state a rule in checkable form or declare their delivery; prose decisions are unverifiable).
ADR not followed: Provide a Dead Letter Channel Where Native Support is Missing · ×6docs/adr/0045-provide-dlq-where-missing.md:73detected by adr-prohibition
What to do
Resolve the 6 ADR not followed finding(s) in ADR Conformance — start with 0063-failed-delivery-context.md (3), 0045-provide-dlq-where-missing.md, 0064-validate-pipeline-assembly-and-provider-registration.md. — One of this dimension's main actionable groups (6 recommendation-level).
Detailed fixes: d25_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.
72 % of calls cross a namespace and 3 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
221 finding(s): 0 critical, 201 high, 20 medium, 0 low. 77 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 264 file(s) — `.claude/commands/refactor/comment_census.cs` (lines 32–33, line 92, line 109), `REDACTED` (lines 111–113), `.claude/commands/refactor/comment_only_check.cs` (line 49), `.claude/commands/spec/show_me_facts_tests.cs` (lines 1283–1285), `benchmarks/Paramore.Brighter.Benchmarks/BenchmarkCommand.cs` (line 5), … (+259 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 229 of those file(s) — `.claude/commands/refactor/comment_census.cs`, `.claude/commands/refactor/comment_only_check.cs`, `benchmarks/Paramore.Brighter.Benchmarks/BenchmarkCommand.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/Program.cs`, … (+224 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 10 of those file(s) — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs`, `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs`, `src/Paramore.Brighter.MessageScheduler.Hangfire/HangfireMessageScheduler.cs`, `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs`, `src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs`, … (+5 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. 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
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 40 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED (5), REDACTED (5). — One of this dimension's main actionable groups (40 issue-level).
Resolve the 31 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (31 issue-level).
No action in Static Analysis (SAST) — all 77 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 (77 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 25 High IaC finding(s) in IaC & Container Security — start with REDACTED (10), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (25 issue-level).
Resolve the 16 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (16 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-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.
165 of 757 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs. Counted over 757 of the 1170 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 164 Orphaned file finding(s) in Knowledge Freshness — start with DynamoDbLockingProvider.cs (2), AwsSchedulerFactory.cs (2), HeaderNames.cs (2). — One of this dimension's main actionable groups (164 recommendation-level).
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with FirestoreInbox.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with OutboxProducerMediator.cs, MessagePump.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 200 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`ServiceCollectionMessageMapperRegistryBuilder` is a singleton (one shared instance) but mutates instance state outside any lock (DefaultMessageMapper, DefaultMessageMapperAsync; e.g. `DefaultMessageMapper` at line 128). — src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionMessageMapperRegistryBuilder.cs:46
`IAmAStorageProviderAsync` is a singleton (one shared instance) but mutates instance state outside any lock (Tracer; e.g. `Tracer` at src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs line 1119, through the shared instance). — src/Paramore.Brighter/Transforms/Storage/IAmAStorageProviderAsync.cs:36
`IAmAStorageProvider` is a singleton (one shared instance) but mutates instance state outside any lock (Tracer; e.g. `Tracer` at src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs line 1112, through the shared instance). — src/Paramore.Brighter/Transforms/Storage/IAmAStorageProvider.cs:35
`TimedOutboxStaleMessageMonitor` is a singleton (one shared instance) but mutates instance state outside any lock (_loop; e.g. `_loop` at line 176). — src/Paramore.Brighter.Outbox.Hosting/TimedOutboxStaleMessageMonitor.cs:44
`TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 58). (×4) — samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:36, samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/TimedMessageGenerator.cs:36, samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs:36, …
`TimedStatusSender` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 64). — samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:37
`TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 46). — samples/TaskQueue/KafkaSchemaRegistry/GreetingsSender/TimedMessageGenerator.cs:11
`TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 37). (×3) — samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs:11, samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:11, samples/TaskQueue/MultiBus/GreetingsSender/TimedMessageGenerator.cs:11
`CommandCounter` is a singleton (one shared instance) but mutates instance state outside any lock (Counter; e.g. `Counter` at line 7). — samples/TaskQueue/MsSqlMessagingGateway/CompetingReceiverConsole/CommandCounter.cs:3
`SubscriberRegistry` is not registered, but the singleton `ServiceCollectionSubscriberRegistry` creates it and keeps it in `_registry`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_observers, _allHandlerTypes; e.g. `_observers` at line 54). — src/Paramore.Brighter/SubscriberRegistry.cs:39
`Baggage` keeps one instance of itself in the static `Empty`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_entries; e.g. `_entries` at line 77). — src/Paramore.Brighter/Observability/Baggage.cs:39
`MessageHeader` is not registered, but the singleton `Message` creates it and keeps it in `Header`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (HandledCount; e.g. `HandledCount` at line 601). — REDACTED:80
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The projects Paramore.Brighter.AsyncAPI.NJsonSchema → Paramore.Brighter.AsyncAPI → Paramore.Brighter.AsyncAPI.NJsonSchema form a reference cycle. Paramore.Brighter.AsyncAPI → Paramore.Brighter.AsyncAPI.NJsonSchema is a run-time load of its assembly by name, which no <ProjectReference> shows. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — src/Paramore.Brighter.AsyncAPI.NJsonSchema/Paramore.Brighter.AsyncAPI.NJsonSchema.csproj:17
The namespaces Paramore.Brighter ↔ Paramore.Brighter.CircuitBreaker ↔ Paramore.Brighter.Observability ↔ Paramore.Brighter.Validation depend on each other. The lightest dependency in the cycle is Paramore.Brighter → Paramore.Brighter.CircuitBreaker (Paramore.Brighter.OutboxProducerMediator → Paramore.Brighter.CircuitBreaker.IAmAnOutboxCircuitBreaker, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Paramore.Brighter/OutboxProducerMediator.cs:32
The namespaces Paramore.Brighter.MessagingGateway.AzureServiceBus ↔ Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers depend on each other. The lightest dependency in the cycle is Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers → Paramore.Brighter.MessagingGateway.AzureServiceBus (Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers.AdministrationClientWrapper → Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusSubscriptionConfiguration, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs:39
The namespaces Paramore.Brighter.ServiceActivator ↔ Paramore.Brighter.ServiceActivator.Status depend on each other. The lightest dependency in the cycle is Paramore.Brighter.ServiceActivator.Status → Paramore.Brighter.ServiceActivator (Paramore.Brighter.ServiceActivator.Status.PerformerInformation → Paramore.Brighter.ServiceActivator.ConsumerState, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/Paramore.Brighter.ServiceActivator/Status/PerformerInformation.cs:3
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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.
`IAmACommandProcessor` declares 29 members under just 11 distinct name(s): `Send`, `Send`, `Send`, `SendAsync`, `SendAsync`, `SendAsync`, `Publish`, `Publish`, `Publish`, `PublishAsync`, `PublishAsync`, `PublishAsync`, `Post`, `Post`, `Post`, `PostAsync`, `PostAsync`, `PostAsync`, `DepositPost`, `DepositPost`, `DepositPost`, `DepositPost`, `DepositPostAsync`, `DepositPostAsync`, `DepositPostAsync`, `DepositPostAsync`, `ClearOutbox`, `ClearOutboxAsync`, `Call`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 29 separate responsibilities: a caller binds to 11 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 29 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. — src/Paramore.Brighter/IAmACommandProcessor.cs:53
`IAmProducersConfiguration` declares 20 members: `ArchiveBatchSize`, `ArchiveProvider`, `ConnectionProvider`, `DistributedLock`, `MessageMapperRegistry`, `Outbox`, `OutboxBulkChunkSize`, `OutboxTimeout`, `MaxOutStandingMessages`, `MaxOutStandingCheckInterval`, `OutBoxBag`, `ProducerRegistry`, `ResponseChannelFactory`, `ReplyQueueSubscriptions`, `RequestContextFactory`, `MessageSchedulerFactory`, `RequestSchedulerFactory`, `TransactionProvider`, `UseRpc`, `DefaultBoxConfiguration`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Paramore.Brighter/ProducersConfiguration.cs:32
`IAmABrighterTracer` declares 20 members: `ActivitySource`, `CreateSpan`, `CreateReceiveSpan`, `EnrichReceiveSpan`, `PropagateConsumerContext`, `CreateSpan`, `CreateArchiveSpan`, `CreateClaimCheckSpan`, `CreateBatchSpan`, `CreateMessagePumpSpan`, `CreateMessagePumpExceptionSpan`, `CreateClearSpan`, `CreateDbSpan`, `CreateProducerSpan`, `CreateConfirmationSpan`, `EndSpan`, `EndSpans`, `LinkSpans`, `AddExceptionToSpan`, `CreateCircuitBreakerSpan`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Paramore.Brighter/Observability/IAmABrighterTracer.cs:33
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — samples/Scheduler/TickerQ/Greeting.Consumer/Program.cs:54, samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:81
`MapPost("/send-one")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:86
`MapPost("/send-multiple")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:93
`HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:28
`HomeController.SendMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:34
`HomeController.DepositMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:50
`HomeController.SaveAndRollbackMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:67
`HomeController.AddGreeting` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:114
`HomeController.Error` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:125
`GreetingsController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:26, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:26, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:26
`GreetingsController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:37, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:37, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:37
`PeopleController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:27, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:28, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:28
`PeopleController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:38, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:39, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:39
`PeopleController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:47, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:48, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:48
`MapPost("/todos")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/WebAPI/WebAPI_mTLS_TestHarness/TodoApi/Program.cs:91
`MapGet("/health")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — samples/WebAPI/WebAPI_mTLS_TestHarness/TodoApi/Program.cs:108
`MapGet($"{baseRoute}/status")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:16, src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:16, src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:16
`MapMethods($"{baseRoute}/subscriptions/{{subscriptionName}}/performers/{{numberOfPerformers:int}}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:17, src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:17, src/Paramore.Brighter.ServiceActivator.Control.Api/ApiExtensions.cs:17
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Do you agree with this assessment?
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Other · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`PaymentReceivedEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. (×2) — samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:33, samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:33
`FarewellEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. (×4) — samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9, samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9, samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9, …
`GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler. (×14) — samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33, samples/Scheduler/QuartzTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33, samples/TaskQueue/ASBTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:16, …
What to do
Remove synchronous remote calls from message handlers — react by publishing further messages, so services stay temporally decoupled.
Other · Event-Driven — Whether commands have a single handler (one owner of the decision) and fan-out is modelled with events.
Method: Roslyn scan (event-driven gated): command-shaped messages identified by convention; handler count per command checked for the exactly-one rule. Deterministic, hard fact.
`FireSchedulerMessage` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch. — src/Paramore.Brighter/Scheduler/Events/FireSchedulerMessage.cs:6
`FireSchedulerRequest` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch. — src/Paramore.Brighter/Scheduler/Events/FireSchedulerRequest.cs:8
`AddGreeting` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch. — samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/AddGreeting.cs:6
`DeletePerson` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch. — samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/DeletePerson.cs:6
`AddPerson` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch. — samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/AddPerson.cs:6
What to do
Keep one handler per command (single owner); use events for the fan-out where many subscribers react.
Other · Event-Driven — Whether events are named in the past tense (a clarity nudge — low weight).
Method: Roslyn scan (event-driven gated): domain and integration events checked for past-tense naming (-ed/-en suffix or irregular set). Naming nudge, low-weight advisory.
`EventSample` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — samples/Analyzer/AnalyzerSamples/PublicationSample.cs:37
`SampleEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe. — samples/Analyzer/AnalyzerSamples/WrapWithMapperSample.cs:44
What to do
Name new events in the past tense: they record facts that already happened. Do not rename an event that is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`GreetingsController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:35, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:35, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:35
`PeopleController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem). (×3) — samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:45, samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:46, samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:46
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
Other · Readiness — Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.
Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×16) — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumerFactory.cs:91, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqProducerRegistryFactory.cs:32, samples/Analyzer/AnalyzerSamples/WrapWithMapperSample.cs:36, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
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.
`CreateAsync` is a shipped member whose body only throws — and it is REACHED: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ChannelFactory.cs:104 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumerFactory.cs:91
`MapToRequest` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:162
`MapToRequestAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:164
The branch `if (transactionType == null)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:347
The branch `if (ServiceBusReceiver is not IAmAServiceBusRetryReceiver receiver)` throws `ChannelFailureException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:428
The branch `if (requeueScheduler is not IAmAMessageRequeueSchedulerSync && requeueScheduler is not IAmAMessageRequeueSchedulerAsync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs:66
The branch `if (async ? _scheduler is not IAmAMessageRequeueSchedulerAsync : _scheduler is not IAmAMessageRequeueSchedulerSync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumerFactory.cs:83
`CreateAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqProducerRegistryFactory.cs:32
The branch `if (batch is not MessageBatch messageBatch)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter/InMemoryMessageProducer.cs:205
The branch `if (mapperRegistry is null)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter/OutboxProducerMediator.cs:166
The branch `if (mapperRegistry is not IAmAMessageMapperRegistryAsync mapperRegistryAsync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter/OutboxProducerMediator.cs:169
The branch `if (queries is not IRelationalDatabaseOutboxTopicCountQueries topicCountQueries)` throws `NotSupportedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/Paramore.Brighter/RelationDatabaseOutbox.cs:1102
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Paramore.Brighter/Observability/BrighterTracer.cs:901
A test is skipped ("Deferred: #4240 — reject with unacceptable reason to invalid channel not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:44, tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:43
A test is skipped ("Deferred: #4240 — requeue budget exhausted to DLQ not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:63, tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:59
A test is skipped ("Erratic due to timing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Bulk_Clearing_The_PostBox_On_The_Command_Processor_Async.cs:88, tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Implicit_Clearing_The_PostBox_On_The_Command_Processor.cs:81
A test is skipped ("Requires publisher confirmation") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — tests/Paramore.Brighter.Core.Tests/CommandProcessors/Post/When_Posting_Via_A_Control_Bus_Sender_Async.cs:72
A test is skipped ("This test is fragile due to background processing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported.cs:106, tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported_Bulk.cs:106
A test is skipped ("Replace with Polly Timeout") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_failing_a_timeout_policy_check.cs:60, tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_passing_a_timeout_policy_check.cs:58
A test is skipped ("measurement — AC-39") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:70, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:132
A test is skipped ("Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×4) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:48, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:95, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_nacking_a_message_it_should_be_redelivered.cs:47, …
A test is skipped ("Deferred: #4240 — no channels configured: acknowledge and log not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:48, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:47
A test is skipped ("Deferred: #4240 — canonical plain requeue not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_should_be_redelivered.cs:46, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_should_be_redelivered.cs:40
A test is skipped ("Deferred: #4240 — requeue with delay not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:46, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:44
A test is skipped ("Deferred: #4240 — explicit zero-delay requeue not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_zero_delay_should_redeliver_immediately.cs:46, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_with_zero_delay_should_redeliver_immediately.cs:44
A test is skipped ("Deferred: #4240 — delayed send not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. (×2) — tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_sending_a_delayed_message_should_deliver_after_delay.cs:46, tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_sending_a_delayed_message_should_deliver_after_delay.cs:44
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
CONTRIBUTING.md names .NET 8, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:56
README.md names .NET 8, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:29
specs/0001-kafka-dead-letter-queue/README.md links to `../../docs/Kafka-DeadLetterQueue-Usage.md`, but `docs/Kafka-DeadLetterQueue-Usage.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0001-kafka-dead-letter-queue/README.md:41
specs/0010-aws-sqs-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0010-aws-sqs-dead-letter-queue/README.md:30
specs/0011-redis-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0011-redis-dead-letter-queue/README.md:30
specs/0012-mssql-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0012-mssql-dead-letter-queue/README.md:30
specs/0013-postgres-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0013-postgres-dead-letter-queue/README.md:30
specs/0014-rocketmq-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0014-rocketmq-dead-letter-queue/README.md:31
specs/0015-mqtt-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0015-mqtt-dead-letter-queue/README.md:30
specs/0023-asyncapi-document-generation/README.md links to `../../docs/adr/0040-asyncapi-document-generation.md`, but `docs/adr/0040-asyncapi-document-generation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — specs/0023-asyncapi-document-generation/README.md:16
docs/features/asyncapi-sdk-adoption/RESEARCH.md names .NET 6, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/features/asyncapi-sdk-adoption/RESEARCH.md:442
What to do
Reconcile the README with reality: CONTRIBUTING.md names .NET 8, but the projects target .NET 9, 10; README.md names .NET 8, but the projects target .NET 9, 10; specs/0001-kafka-dead-letter-queue/README.md links to `../../docs/Kafka-DeadLetterQueue-Usage.md`, but `docs/Kafka-DeadLetterQueue-Usage.md` does not exist; specs/0010-aws-sqs-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist; specs/0011-redis-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist.
Only 96/140 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 140, 68 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs` reports through `Console.Write…` at line 35 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:35
`samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs` reports through `Console.Write…` at line 35 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:35
`samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 72 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:72
`samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 78 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:78
`samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 84 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:84
`samples/Transforms/JustSaying/BrighterSide/Program.cs` reports through `Console.Write…` at line 63 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/Transforms/JustSaying/BrighterSide/Program.cs:63
`samples/Transforms/JustSaying/JustSayingSide/Program.cs` reports through `Console.Write…` at line 34 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/Transforms/JustSaying/JustSayingSide/Program.cs:34
`samples/Transforms/MassTransit/MBrigtherSide/Program.cs` reports through `Console.Write…` at line 63 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — samples/Transforms/MassTransit/MBrigtherSide/Program.cs:63
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
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.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
59 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×24) — src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:1120, src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:568, src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:570, …
`.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×15) — src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:92, src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:110, src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:128, …
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×12) — samples/Scheduler/TickerQ/Greeting.Consumer/Program.cs:9, samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:17, samples/TaskQueue/ASBTaskQueue/GreetingsSender.Web/Program.cs:19, …
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×32) — src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:1120, src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:570, src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:90, …
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×5) — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverWrapper.cs:85, src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:154, src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:350, …
`KafkaMessageConsumer.AcknowledgeOffset` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll). (×2) — src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:727, src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:792
`.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:56
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
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.
`command` is a `SpannerCommand`, which implements `IDisposable`, and it is created here (line 263). Every use of it in `ExecuteCreateTableIfNotExistsSafeAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:263
`command` is a `SpannerCommand`, which implements `IDisposable`, and it is created here (line 292). Every use of it in `EnsureHistoryTableAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:292
`client` is a `IAmazonScheduler`, which implements `IDisposable`, and it is created here (line 203). Every use of it in `CreateSchedulerGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. (×2) — src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:203, src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:203
`client` is never created by `GcpMessageProducer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 154). Its declared type `PublisherClient` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:154
`client` is never created by `GcpMessageProducer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 163). Its declared type `PublisherClient` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:163
`GcpPullMessageConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_purgeLock` itself (line 31), which makes that instance its own. But `_purgeLock` is named in none of the methods the disposal search covered: `DisposeAsync` (line 512), `Dispose` (line 517) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_purgeLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:31
`KafkaMessageConsumer` declares a finalizer (line 293), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:293
`sqlCmd` is a `DbCommand`, which implements `IDisposable`, and it is created here (line 175). Every use of it in `NumberOfMessageReady` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sqlCmd = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:175
`RmqMessageConsumer` declares a finalizer (line 805), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:805
`RmqMessageGateway` declares a finalizer (line 202), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:202
`RmqMessageConsumer` declares a finalizer (line 664), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:664
`RmqMessageGateway` declares a finalizer (line 188), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:188
`Channel` is a `IModel` this type creates itself, and here (line 162) a new instance is written over it — but `ConnectToBroker` itself reads through `Channel` before replacing it, so it expects an instance to be there, and nothing earlier in `ConnectToBroker` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`Channel?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:162
`sha256` is a `SHA256`, which implements `IDisposable`, and it is created here (line 1470). Every use of it in `GetShardNumber` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sha256 = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1470
`sha256` is a `SHA256`, which implements `IDisposable`, and it is created here (line 1458). Every use of it in `GetShardNumber` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sha256 = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1458
`Performer` declares a finalizer (line 93), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter.ServiceActivator/Performer.cs:93
`_channel` is never created by `Performer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 103). Its declared type `IAmAChannel` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter.ServiceActivator/Performer.cs:103
`transferUtility` is a `TransferUtility`, which implements `IDisposable`, and it is created here (line 258). Every use of it in `StoreAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var transferUtility = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:258
`transferUtility` is a `TransferUtility`, which implements `IDisposable`, and it is created here (line 259). Every use of it in `StoreAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var transferUtility = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:259
`client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 200). Every use of it in `EnsureStoreExists` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:200
`client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 222). Every use of it in `Delete` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:222
`client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 241). Every use of it in `Retrieve` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:241
`client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 266). Every use of it in `HasClaim` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:266
`client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 293). Every use of it in `Store` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:293
`client` is a `MongoClient`, which implements `IDisposable`, and it is created here (line 58). Every use of it in `MongoDbLuggageStore` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:58
`Channel` declares a finalizer (line 230), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter/Channel.cs:230
`_messageConsumer` is never created by `Channel` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 226). Its declared type `IAmAMessageConsumerSync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter/Channel.cs:226
`ChannelAsync` declares a finalizer (line 256), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Paramore.Brighter/ChannelAsync.cs:256
`_messageConsumer` is never created by `ChannelAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 227). Its declared type `IAmAMessageConsumerAsync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter/ChannelAsync.cs:227
`_messageConsumer` is never created by `ChannelAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 252). Its declared type `IAmAMessageConsumerAsync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter/ChannelAsync.cs:252
`_pipelineScope` is never created by `HandlerLifetimeScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 125). Its declared type `IAmAScope` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter/HandlerLifetimeScope.cs:125
`meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `OutboxStaleMessageMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter/Observability/OutboxStaleMessageMeter.cs:63
`meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `PublishConfirmationMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter/Observability/PublishConfirmationMeter.cs:45
`meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 68). Every use of it in `SweeperMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter/Observability/SweeperMeter.cs:68
`OutboxProducerMediator` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_backgroundClearSemaphore` itself (line 71), which makes that instance its own. But `_backgroundClearSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 211), `Dispose` (line 217), `Dispose` (line 211), `Dispose` (line 217), `DisposeQuietly` (line 255) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_backgroundClearSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Paramore.Brighter/OutboxProducerMediator.cs:71
`_pipelineScope` is never created by `TransformPipelineAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 91). Its declared type `IAmAScope` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Paramore.Brighter/TransformPipelineAsync.cs:91
`deCompressionStream` is a `Stream`, which implements `IDisposable`, and it is created here (line 154). Every use of it in `UnwrapAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deCompressionStream = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:154
`deCompressionStream` is a `Stream`, which implements `IDisposable`, and it is created here (line 231). Every use of it in `Unwrap` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deCompressionStream = …;`), which releases it at the end of the scope on every path including a throw. — src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:231
`command` is a `DbCommand`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `CheckHealthAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw. — samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs:21
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 786/949 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×30) — src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlProvisioningUnitOfWork.cs:72, src/Paramore.Brighter.BoxProvisioning/SqlBoxMigrationRunner.cs:306, src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:250, …
Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). (×5) — src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:184, src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:267, src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:517, …
Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×4) — src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:327, src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:131, src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:328, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
The guard on line 17 rejects `fullyQualifiedNameSpace` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusAzureCliCredentialClientProvider.cs:19
The guard on line 19 rejects `fullyQualifiedNameSpace` and line 21 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusChainedClientProvider.cs:21
The guard on line 24 rejects `credentialSources` and line 26 reports that rejection as `ArgumentNullException` — but the condition's own test `credentialSources.Length < 1` is true of a value that is NOT null: it is satisfied by an EMPTY `credentialSources`, and on that path `credentialSources` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusChainedClientProvider.cs:26
The guard on line 20 rejects `connectionString` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(connectionString)` is true of a value that is NOT null: it is satisfied by an EMPTY `connectionString`, and on that path `connectionString` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusConnectionStringClientProvider.cs:22
The guard on line 20 rejects `fullyQualifiedNameSpace` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×3) — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusDefaultAzureClientProvider.cs:22, src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusManagedIdentityClientProvider.cs:22, src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusVisualStudioCredentialClientProvider.cs:22
The guard on line 44 rejects `credentialSources` and line 46 reports that rejection as `ArgumentNullException` — but the condition's own test `credentialSources.Length < 1` is true of a value that is NOT null: it is satisfied by an EMPTY `credentialSources`, and on that path `credentialSources` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. — src/Paramore.Brighter.MsSql.Azure/MsSqlChainedConnectionProvider.cs:46
The guard on line 82 rejects `value` and line 84 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition. (×2) — src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:84, src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs:84
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
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.
`LogDebug` at line 70 is called with an argument built by `string.Join(",", messages.Select(m => m.Id.ToString()).ToArray())` (line 71), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — src/Paramore.Brighter/NullOutboxArchiveProvider.cs:70
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
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 a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×18) — src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:266, src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:370, src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:180, …
`catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:188
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×5) — src/Paramore.Brighter/HandlerLifetimeScope.cs:147, src/Paramore.Brighter/TransformLifetimeScope.cs:32, src/Paramore.Brighter/TransformLifetimeScopeAsync.cs:48, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — src/Paramore.Brighter.Mediator/InMemoryStateStoreAsync.cs:114
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
126/219 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~1.4 `!` suppressions per 1k syntax nodes — 653 suppression(s) across the 451489 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 35 observation(s) recorded · 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.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 20 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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 — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 39 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.
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the Aspire AppHost did not expose a crawlable HTTP endpoint in time (or only the dashboard) — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — Test reliability not included
D17 Explicit Debt — Explicit Debt not included (time budget)
D21 Naming Consistency — Naming Consistency not included (check did not complete)
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 3 exposed C# types.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D32 Data Compliance (PII/GDPR) — 206 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 4 strongly-typed id(s); 44 value object(s); 8 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an event-store package (Marten/EventStore))
P10 Library API & versioning — Library API & versioning could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
P11 BDD / executable specs — BDD / executable specs could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — Outbound HTTP resilience could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
P8 Schema migrations — Schema migrations could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
P9 Domain vs controller coverage — coverage data present for 568 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Dual write (no outbox): GreetingsController.Post samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:35— `GreetingsController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): PeopleController.Post samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:45— `PeopleController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): GreetingsController.Post samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:35— `GreetingsController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): PeopleController.Post samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:46— `PeopleController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): GreetingsController.Post samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:35— `GreetingsController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Dual write (no outbox): PeopleController.Post samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:46— `PeopleController.Post` writes to the database AND publishes to the message bus in the same flow, with no outbox referenced in this path. These two writes aren't atomic — a crash between them either loses the message (DB committed, publish failed) or emits a phantom event (publish succeeded, DB rolled back). Use the transactional outbox pattern — write the message to an outbox table in the SAME transaction as the state change, and dispatch it from there afterwards — or your platform's equivalent (a broker transaction, or an outbox library from your own ecosystem).
Namespace dependency cycle src/Paramore.Brighter/OutboxProducerMediator.cs:32— The namespaces Paramore.Brighter ↔ Paramore.Brighter.CircuitBreaker ↔ Paramore.Brighter.Observability ↔ Paramore.Brighter.Validation depend on each other. The lightest dependency in the cycle is Paramore.Brighter → Paramore.Brighter.CircuitBreaker (Paramore.Brighter.OutboxProducerMediator → Paramore.Brighter.CircuitBreaker.IAmAnOutboxCircuitBreaker, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs:39— The namespaces Paramore.Brighter.MessagingGateway.AzureServiceBus ↔ Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers depend on each other. The lightest dependency in the cycle is Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers → Paramore.Brighter.MessagingGateway.AzureServiceBus (Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusWrappers.AdministrationClientWrapper → Paramore.Brighter.MessagingGateway.AzureServiceBus.AzureServiceBusSubscriptionConfiguration, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Paramore.Brighter.ServiceActivator/Status/PerformerInformation.cs:3— The namespaces Paramore.Brighter.ServiceActivator ↔ Paramore.Brighter.ServiceActivator.Status depend on each other. The lightest dependency in the cycle is Paramore.Brighter.ServiceActivator.Status → Paramore.Brighter.ServiceActivator (Paramore.Brighter.ServiceActivator.Status.PerformerInformation → Paramore.Brighter.ServiceActivator.ConsumerState, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Project dependency cycle src/Paramore.Brighter.AsyncAPI.NJsonSchema/Paramore.Brighter.AsyncAPI.NJsonSchema.csproj:17— The projects Paramore.Brighter.AsyncAPI.NJsonSchema → Paramore.Brighter.AsyncAPI → Paramore.Brighter.AsyncAPI.NJsonSchema form a reference cycle. Paramore.Brighter.AsyncAPI → Paramore.Brighter.AsyncAPI.NJsonSchema is a run-time load of its assembly by name, which no <ProjectReference> shows. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
Orphaned knowledge src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Unfinished stub — throws NotImplementedException src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumerFactory.cs:91— `CreateAsync` is a shipped member whose body only throws — and it is REACHED: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ChannelFactory.cs:104 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs:154— src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is RmqMessageProducer.SendWithDelay at line 154), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: RMQ.Sync producer no longer records a pending confirmation for a message it only schedules”; “fix: RMQ.Sync producer no longer confirms messages pending on a replaced or recovered channel”; “fix: RMQ.Sync producer selects confirms and subscribes handlers once per channel”; “fix: a reset RMQ.Sync channel does not confirm messages pending on the old one”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:89— src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs changed 10 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is MqttMessageConsumer.MqttMessageConsumer.ctor at line 89), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: correct metrics derived from traces (#4476)”; “fix: route mapped requests by command or event type”; “fix: make MQTT consumer producer instrumentation configurable”; “fix(mqtt): catch every fault parsing a payload, and run the test in CI”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:178— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs changed 9 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is AzureServiceBusConsumer.ReceiveAsync at line 178), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(asb): address retry telemetry and configuration review”; “fix(asb)!: make retry scheduling explicit and resilient”; “fix(asb)!: isolate subscription retries”; “fix: provision the ASB subscription when creating a sync channel (#4309)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:266— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is GcpPubSubStreamMessageConsumer.ReceiveAsync at line 266), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: handle GCP Pub/Sub stream shutdown cancellation (#4537) (#4611)”; “fix(gcp): purge using a server boundary and discard late deliveries”; “fix: drain every buffered message when purging a GCP stream channel”; “fix: GCP Stream Purge names its subscription and drains the local buffer”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:246— src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is RmqMessageConsumer.Receive at line 246), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(rmq): purge prefetched and channel-buffered messages (#4614)”; “fix: RMQ.Sync channel factory declares the queue before returning (#4519)”; “fix: correct metrics derived from traces (#4476)”; “fix: release RabbitMQ connections when teardown fails”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpStreamConsumer.cs src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpStreamConsumer.cs:75— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpStreamConsumer.cs changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is GcpStreamConsumer.StopAsync at line 75), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: handle GCP Pub/Sub stream shutdown cancellation (#4537) (#4611)”; “fix(gcp): purge using a server boundary and discard late deliveries”; “fix: drain every buffered message when purging a GCP stream channel”; “fix: GCP Stream Purge names its subscription and drains the local buffer”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpStreamConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:121— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is KafkaMessageConsumer.KafkaMessageConsumer.ctor at line 121), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(kafka): make producer and consumer disposal idempotent”; “fix: correct metrics derived from traces (#4476)”; “fix: wait for Kafka topic visibility before consumer subscribes”; “fix: commit only the highest offset per partition, and fix Kafka revoke handler to actually commit”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:187— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is GcpPullMessageConsumer.ReceiveAsync at line 187), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(gcp): purge using a server boundary and discard late deliveries”; “fix: GCP Pull Purge names its subscription in the Seek request”; “fix: raise GCP Pub/Sub Pull deadline floor to stop zero-delay requeues losing messages”; “fix: correct metrics derived from traces (#4476)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs:135— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is ChannelFactory.EnsureChannelExists at line 135), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: RMQ.Async CreateAsyncChannelAsync reports provisioning failures as ChannelFailureException (#4519)”; “fix: RMQ.Async CreateAsyncChannel reports provisioning failures as ChannelFailureException (#4519)”; “fix: RMQ.Async sync channel factory reports provisioning failures as ChannelFailureException (#4519)”; “fix: RMQ.Async CreateAsyncChannelAsync declares the queue before returning (#4519)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:271— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is RmqMessageConsumer.ReceiveAsync at line 271), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(rmq): purge prefetched and channel-buffered messages (#4614)”; “fix: RMQ.Async sync channel factory declares the queue before returning (#4519)”; “fix: correct metrics derived from traces (#4476)”; “fix: release RabbitMQ connections when teardown fails”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter/CommandProcessor.cs src/Paramore.Brighter/CommandProcessor.cs:590— src/Paramore.Brighter/CommandProcessor.cs changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is CommandProcessor.PublishAsync at line 590), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: reject received messages without a handler”; “fix: keep publish resilience behavior independent of handler count”; “fix: preserve request context when scheduling requests”; “fix: route mapped requests by command or event type”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter/CommandProcessor.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscriptionConfiguration.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscriptionConfiguration.cs:148— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscriptionConfiguration.cs changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is AzureServiceBusSubscriptionConfiguration.GetRuleOptions at line 148), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(asb)!: isolate subscription retries”; “fix: renew Azure Service Bus locks during processing”; “fix: honor Azure Service Bus queue subscription settings”; “fix: reconcile Azure Service Bus subscription rules”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscriptionConfiguration.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs:134— src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is TimedOutboxSweeper.Dispose at line 134), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: schedule sweeps by elapsed time, not the wall clock”; “fix: start sweeper and confirmation threads without the caller's context”; “fix: re-check the sweep's due time after creating its timer”; “fix: keep a sweep on the sweeper thread across awaited sends”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs:60— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs changed 5 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is AzureServiceBusMessageCreator.MapToBrighterMessage at line 60), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(asb)!: isolate subscription retries”; “fix: continue Azure Service Bus traces from Diagnostic-Id”; “fix: map native Azure Service Bus partition keys”; “fix: map native Azure Service Bus subjects”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1380— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is DynamoDbOutbox.PageIndexQueryToBatchSize at line 1380), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: stop the DynamoDB overall count at the ceiling by giving each segment the whole ceiling”; “fix: bound DynamoDB scans when excluding tripped topics”; “fix: exclude tripped topics from DynamoDB outbox reads”; “fix: honor DynamoDB outbox operation timeouts”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1368— src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is DynamoDbOutbox.PageIndexQueryToBatchSize at line 1368), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: stop the DynamoDB overall count at the ceiling by giving each segment the whole ceiling”; “fix: bound DynamoDB scans when excluding tripped topics”; “fix: exclude tripped topics from DynamoDB outbox reads”; “fix: honor DynamoDB outbox operation timeouts”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:153— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is SqsMessageConsumer.RejectAsync at line 153), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sqs): validate requeue delays and pin FIFO defer ordering”; “fix: release SQS rejected messages for redelivery when DLQ routing fails”; “fix: correct metrics derived from traces (#4476)”; “fix: route mapped requests by command or event type”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:256— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is SqsMessageConsumer.RejectAsync at line 256), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(sqs): validate requeue delays and pin FIFO defer ordering”; “fix: release SQS rejected messages for redelivery when DLQ routing fails”; “fix: correct metrics derived from traces (#4476)”; “fix: route mapped requests by command or event type”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: REDACTED REDACTED:30— REDACTED changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is PostgreSqlQueries.GetOutstandingMessageCountCommand.get at line 30), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(postgres): handle duplicate messages in DataRef outbox writes”; “fix(outbox): count outstanding messages on the database server”; “fix(outbox): persist DataRef in relational writes”; “fix(postgres): preserve new outbox messages in duplicate batches”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:165— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is RmqMessageProducer.SendWithDelayAsync at line 165), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: stop concurrent RMQ.Async sends corrupting pending confirmations”; “fix: RMQ.Async producer moves confirm handlers to a replacement channel”; “fix: release RabbitMQ connections when teardown fails”; “fix: preserve shared RabbitMQ connections during gateway disposal”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessagePublisher.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessagePublisher.cs:63— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessagePublisher.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AzureServiceBusMessagePublisher.AddBrighterHeaders at line 63), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: map native Azure Service Bus partition keys”; “fix: route mapped requests by command or event type”; “fix: map native Azure Service Bus subjects”; “fix(asb): accept a relative CloudEvents source and dataschema (#4311)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessagePublisher.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqMessageProducer.cs src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqMessageProducer.cs:56— src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqMessageProducer.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is RocketMqMessageProducer.SendWithDelayAsync at line 56), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: close the ledger parser's fail-open, log harness republish failures, test the RocketMQ guard”; “fix(rocketmq): stop adding the Type property twice on every message”; “revert(rocketmq): move the duplicate Type property fix to its own PR”; “fix(rocketmq): stop adding the Type property twice, and note two compose caveats”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqMessageProducer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs:157— src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is CloudEventsTransformer.ReadCloudEventJsonMessage at line 157), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cloudevents): preserve JSON string payloads on unwrap”; “fix: handle optional CloudEvents data content types”; “fix: preserve CloudEvents JSON media type payloads”; “fix: route mapped requests by command or event type”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs:96— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is AzureServiceBusQueueConsumer.EnsureChannelAsync at line 96), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(asb): address retry telemetry and configuration review”; “fix(asb)!: make retry scheduling explicit and resilient”; “fix: renew Azure Service Bus locks during processing”; “fix: honor Azure Service Bus queue subscription settings”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs:123— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is AdministrationClientWrapper.CreateSubscriptionAsync at line 123), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(asb)!: isolate subscription retries”; “fix: preserve async queue validation errors”; “fix: honor Azure Service Bus queue subscription settings”; “fix: reconcile Azure Service Bus subscription rules”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs`: 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.
Sync-over-async blocking — 59 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:1120— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:568— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:570— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:92— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:110— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:128— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:277— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:84— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:102— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:120— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:274— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverWrapper.cs:85— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:154— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:350— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:1234— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:159— `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:288— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:248— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MsSql.Azure/MsSqlChainedConnectionProvider.cs:60— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MsSql.Azure/MsSqlDefaultAzureConnectionProvider.cs:48— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.MsSql.Azure/MsSqlManagedIdentityConnectionProvider.cs:51— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:154— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:172— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:263— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async (deadlock risk) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:1120— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:570— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:90— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:108— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:126— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:275— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:82— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:100— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:118— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:272— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverWrapper.cs:85— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:154— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:350— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:1234— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:158— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:288— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:248— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MsSql.Azure/MsSqlChainedConnectionProvider.cs:60— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MsSql.Azure/MsSqlDefaultAzureConnectionProvider.cs:48— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.MsSql.Azure/MsSqlManagedIdentityConnectionProvider.cs:51— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:154— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:171— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:263— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:355— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:432— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization samples/Scheduler/TickerQ/Greeting.Consumer/Program.cs:54— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:81— `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:86— `MapPost("/send-one")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:93— `MapPost("/send-multiple")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:28— `HomeController.Index` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:34— `HomeController.SendMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:50— `HomeController.DepositMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:67— `HomeController.SaveAndRollbackMessage` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:114— `HomeController.AddGreeting` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization REDACTED:125— `HomeController.Error` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:26— `GreetingsController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:37— `GreetingsController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:27— `PeopleController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:38— `PeopleController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/PeopleController.cs:47— `PeopleController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:26— `GreetingsController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:37— `GreetingsController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:28— `PeopleController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:39— `PeopleController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:48— `PeopleController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:26— `GreetingsController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:37— `GreetingsController.Post` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:28— `PeopleController.Get` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:39— `PeopleController.Delete` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
Duplicated block (13 lines × 2) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1026— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1026-1038 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1057-1069 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/RelationDatabaseOutbox.cs:1026` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:810— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:810-822 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:669-681 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:810` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:373— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:373-385 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:408-420 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:373` it does not close everything it opens, so those 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) REDACTED:260— REDACTED:260-272 | REDACTED:280-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 `REDACTED:260` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) REDACTED:333— REDACTED:333-345 | REDACTED:445-457 — both copies are in the same file, so extract the 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 `REDACTED:333` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/ConnectionPolicyFactory.cs:65— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ConnectionPolicyFactory.cs:65-77 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ConnectionPoolFactory.cs:68-80 — 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 `src/Paramore.Brighter.MessagingGateway.RMQ.Async/ConnectionPolicyFactory.cs:65` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:500— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:500-512 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:487-499 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:500` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:276— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:276-288 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:741-753 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:276` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:289` calls `GetFirestoreClient` and `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:754` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:289— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:289-301 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:290-302 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (13 lines × 2) src/Paramore.Brighter/CommandProcessor.cs:427— src/Paramore.Brighter/CommandProcessor.cs:427-439 | src/Paramore.Brighter/CommandProcessor.cs:445-457 — both copies are in the same file, so extract the 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) src/Paramore.Brighter/CommandProcessor.cs:540— src/Paramore.Brighter/CommandProcessor.cs:540-552 | src/Paramore.Brighter/CommandProcessor.cs:557-569 — both copies are in the same file, so extract the 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) src/Paramore.Brighter/CommandProcessor.cs:667— src/Paramore.Brighter/CommandProcessor.cs:667-679 | src/Paramore.Brighter/CommandProcessor.cs:685-697 — both copies are in the same file, so extract the 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) src/Paramore.Brighter/CommandProcessor.cs:727— src/Paramore.Brighter/CommandProcessor.cs:727-739 | src/Paramore.Brighter/CommandProcessor.cs:744-756 — both copies are in the same file, so extract the 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) src/Paramore.Brighter/CommandProcessor.cs:793— src/Paramore.Brighter/CommandProcessor.cs:793-805 | src/Paramore.Brighter/CommandProcessor.cs:811-823 — both copies are in the same file, so extract the 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) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:27— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:27-39 | src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:66-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:27` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:93— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:93-105 | src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:132-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:93` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:50— src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:50-62 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:89-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:50` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:116— src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:116-128 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:155-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:116` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:27— src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:27-39 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:66-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:27` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:93— src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:93-105 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:132-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:93` 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.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:173— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:173-185 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:256-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 `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:173` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:386— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:386-398 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:469-481 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:386` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Paramore.Brighter.Mediator/Tasks.cs:179— src/Paramore.Brighter.Mediator/Tasks.cs:179-191 | src/Paramore.Brighter.Mediator/Tasks.cs:233-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Mediator/Tasks.cs:179` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:303— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:303-315 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:304-316 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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. 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:367— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:367-379 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:356-368 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:367` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/PipelineBuilder.cs:198— src/Paramore.Brighter/PipelineBuilder.cs:198-207 | src/Paramore.Brighter/PipelineBuilder.cs:258-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/PipelineBuilder.cs:198` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:157— src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:157-166 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs: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 `src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:157` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:127— src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:127-136 | src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:204-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:127` 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 (10 lines × 2) src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:165— src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:165-174 | src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:238-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:165` 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 (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:318— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:318-327 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:351-360 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:137— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:137-146 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:140-149 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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 (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:132— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:132-141 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:182-191 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:132` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:142` calls `FromMilliseconds` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:192` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:497— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:497-506 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:565-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:497` 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 after the matched lines, `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:508` calls `ParseOrCreateTopicName` and `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:576` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:646— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:646-655 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:713-722 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:646` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:595— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:595-604 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:507-516 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:595` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:209— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:209-218 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:207-216 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:209` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:243— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:243-252 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:230-239 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (10 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:590— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:590-599 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:577-586 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (10 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1095— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1095-1104 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1083-1092 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (10 lines × 2) src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:146— src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:146-155 | src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs:145-154 — `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs` and `src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:146` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:456— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:456-465 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:462-471 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:324— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:324-333 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:324-333 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:324` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:338— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:338-347 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:340-349 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:338` 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 (10 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:518— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:518-527 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:525-534 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:518` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:323— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:323-332 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:316-325 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:323` 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.
Duplicated block (10 lines × 2) src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:21— src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:21-30 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:52-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:21` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:95— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:95-104 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:90-102 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs: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. 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, `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:93` calls `InvalidOperationException`, `ContentType` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:90` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/Paramore.Brighter/InMemoryScheduler.cs:312— src/Paramore.Brighter/InMemoryScheduler.cs:312-321 | src/Paramore.Brighter/InMemoryScheduler.cs:323-332 — both copies are in the same file, so extract the 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) src/Paramore.Brighter.DynamoDb.V4/GUIDConverter.cs:24— src/Paramore.Brighter.DynamoDb.V4/GUIDConverter.cs:24-33 | src/Paramore.Brighter.DynamoDb/GUIDConverter.cs:24-33 — `src/Paramore.Brighter.DynamoDb.V4/GUIDConverter.cs` and `src/Paramore.Brighter.DynamoDb/GUIDConverter.cs` 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 10 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. 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/KeyTopicDeliveredTimeExpression.cs:14— src/Paramore.Brighter.Outbox.DynamoDB.V4/KeyTopicDeliveredTimeExpression.cs:14-23 | src/Paramore.Brighter.Outbox.DynamoDB/KeyTopicDeliveredTimeExpression.cs:14-23 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/KeyTopicDeliveredTimeExpression.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/KeyTopicDeliveredTimeExpression.cs` 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 10 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
+ 6 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×30
Async method without CancellationToken: ReleaseLockAfterFailedBeginAsync src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlProvisioningUnitOfWork.cs:72— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RollbackWithoutMaskingAsync src/Paramore.Brighter.BoxProvisioning/SqlBoxMigrationRunner.cs:306— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PageAllMessagesAsync src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:250— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PageAllMessagesAsync src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:242— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ResumeAfterEvent src/Paramore.Brighter.Mediator/Scheduler.cs:63— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateTargetAsync src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:226— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetQueueAsync src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:318— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetOrCreateRoleArnAsync src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:92— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateTargetAsync src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:226— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetQueueAsync src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:319— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetOrCreateRoleArnAsync src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:92— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: FireSchedulerMessageAsync src/Paramore.Brighter.MessageScheduler.Hangfire/BrighterHangfireSchedulerJob.cs:16— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: FireSchedulerRequestAsync src/Paramore.Brighter.MessageScheduler.Hangfire/BrighterHangfireSchedulerJob.cs:29— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateTopicAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:200— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SetTopicMaximumMessageSizeAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:233— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetQueueArnForChannelAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:441— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteQueueAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:155— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DeleteTopicAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:181— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateSyncChannelAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:205— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: QueueExistsAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:262— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UnsubscribeFromTopicAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:304— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs:87— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PublishAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:50— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CreateAsync src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs:63— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetArnFromTopic src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs:78— No CancellationToken parameter — this work can't be stopped early once started.
+ 5 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×26
Edited copy of a member (9 corresponding lines) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:47— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:47-55 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs:48-56 — 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) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:47— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:47-55 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactoryAsync.cs:48-56 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:389— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:389-398 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:377-385 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:202— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:202-210 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:234-242 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:159— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:159-167 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:157-165 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:350— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:350-358 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:382-390 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:361— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:361-369 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:393-404 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:284— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:284-292 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:282-290 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:318— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:318-326 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:316-324 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:349— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:349-357 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:338-346 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:295— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:295-303 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:293-301 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:352— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:352-361 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:344-352 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:231— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:231-239 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:197-205 — 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:286— REDACTED:286-294 | REDACTED:310-318 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:445— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:445-453 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:448-456 — 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) src/Paramore.Brighter.Outbox.MsSql/MsSqlOutbox.cs:124— src/Paramore.Brighter.Outbox.MsSql/MsSqlOutbox.cs:124-134 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:2151-2159 — 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:557— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:557-565 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:558-566 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:206— src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:206-214 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:421-429 — 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:191— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:191-199 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:191-199 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:237— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:237-245 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:237-245 — 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) src/Paramore.Brighter.MySql.EntityFrameworkCore/MySqlEntityFrameworkTransactionProvider.cs:79— src/Paramore.Brighter.MySql.EntityFrameworkCore/MySqlEntityFrameworkTransactionProvider.cs:79-87 | src/Paramore.Brighter.PostgreSql.EntityFrameworkCore/PostgreSqlEntityFrameworkTransactionProvider.cs:78-86 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) src/Paramore.Brighter/Validation/PipelineDiagnosticWriter.cs:76— src/Paramore.Brighter/Validation/PipelineDiagnosticWriter.cs:76-84 | src/Paramore.Brighter/Validation/PipelineValidator.cs: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) src/Paramore.Brighter.Transformers.MassTransit/MassTransitMessageMapper.cs:135— src/Paramore.Brighter.Transformers.MassTransit/MassTransitMessageMapper.cs:135-143 | src/Paramore.Brighter.Transformers.MassTransit/MassTransitTransform.cs:134-142 — 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:51— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:51-59 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:51-59 — 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) src/Paramore.Brighter.Transformers.JustSaying/JsonConverters/IpAddressConverter.cs:14— src/Paramore.Brighter.Transformers.JustSaying/JsonConverters/IpAddressConverter.cs:14-22 | src/Paramore.Brighter.Transformers.JustSaying/JsonConverters/TenantConverter.cs:13-21 — 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.
+ 1 more in this group — see findings.md.
P12 · CI test-gate honesty· CI test gate excludes suites by filter · ×25
CI test gate excludes suites by filter REDACTED:107— `dotnet test tests/Paramore.Brighter.AzureServiceBus.Tests/Paramore.Brighter.AzureServiceBus.Tests.csproj --filter "FullyQualifiedName~Gat…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 1 test(s) it drops — run by no other gate before merge (categories ASB; e.g. LargeAsbMessageProducerTests.When_posting_a_large_message_via_the_bulk_producer). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:108— `dotnet test tests/Paramore.Brighter.Gcp.Tests/Paramore.Brighter.Gcp.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFactoryDeclar…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 228 test(s) it drops — run by no other gate before merge (categories GcpPubSubStream, GcpPubSubStreamOrdering, Spanner; e.g. WhenAMessageConsumerReadsMultipleMessagesShouldReceiveAllMessagesAsync.When_a_message_consumer_reads_multiple_messages_should_receive_all_messages_async, WhenInfrastructureMissingAndAssumeChannelShouldThrowExceptionAsync.When_infrastructure_missing_and_assume_channel_should_throw_exception_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:109— `dotnet test tests/Paramore.Brighter.Kafka.Tests/Paramore.Brighter.Kafka.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFactoryDe…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 34 test(s) it drops — run by no other gate before merge (categories Kafka; e.g. KafkaMessageConsumerUpdateOffsetAsync.When_a_message_is_acknowledged_update_offset, KafkaMessageConsumerCommitRevokeConcurrency.When_committing_offsets_during_revoke_should_not_race_with_background_commit). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:110— `dotnet test tests/Paramore.Brighter.MQTT.Tests/Paramore.Brighter.MQTT.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFactoryDecl…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 15 test(s) it drops — run by no other gate before merge (e.g. When_mqtt_channel_factory_creates_channel_should_use_consumer_factory.Should_create_sync_channel, When_mqtt_channel_factory_creates_channel_should_use_consumer_factory.Should_create_async_channel). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:111— `dotnet test tests/Paramore.Brighter.MSSQL.Tests/Paramore.Brighter.MSSQL.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFactoryDe…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 1 test(s) it drops — run by no other gate before merge (e.g. MsSqlHistoryTableNonDboSchemaTests.When_history_table_exists_in_a_non_dbo_schema_runner_should_still_create_it_in_dbo). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:112— `dotnet test tests/Paramore.Brighter.PostgresSQL.Tests/Paramore.Brighter.PostgresSQL.Tests.csproj --filter "FullyQualifiedName~GatewayChan…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 1 test(s) it drops — run by no other gate before merge (e.g. PostgreSqlManyProvisionersHistoryRaceTests.When_many_postgres_provisioners_race_to_create_history_table_they_should_all_complete). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:113— `dotnet test tests/Paramore.Brighter.Redis.Tests/Paramore.Brighter.Redis.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFactoryDe…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 5 test(s) it drops — run by no other gate before merge (categories Redis; e.g. RedisMessageConsumerDeliveryErrorDlqAsyncTests.When_rejecting_message_with_delivery_error_should_send_to_dlq_async, RedisMessageConsumerDeliveryErrorDlqTests.When_rejecting_message_with_delivery_error_should_send_to_dlq). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:114— `dotnet test tests/Paramore.Brighter.RMQ.Async.Tests/Paramore.Brighter.RMQ.Async.Tests.csproj --filter "FullyQualifiedName~GatewayChannelF…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_async, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:115— `dotnet test tests/Paramore.Brighter.RMQ.Sync.Tests/Paramore.Brighter.RMQ.Sync.Tests.csproj --filter "FullyQualifiedName~GatewayChannelFac…` filters with `FullyQualifiedName~GatewayChannelFactoryDeclarationTests` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_sync, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_sync). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:127— `dotnet test tests/Paramore.Brighter.AzureServiceBus.Tests/Paramore.Brighter.AzureServiceBus.Tests.csproj --filter "FullyQualifiedName~Azu…` filters with `FullyQualifiedName~AzureServiceBusProducerCreationRaceTests` — 1 test(s) it drops — run by no other gate before merge (categories ASB; e.g. LargeAsbMessageProducerTests.When_posting_a_large_message_via_the_bulk_producer). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:268— `dotnet test ./tests/Paramore.Brighter.Redis.Tests/Paramore.Brighter.Redis.Tests.csproj --filter "Fragile!=CI" --configuration Release --l…` filters with `Fragile!=CI` — 5 test(s) it drops — run by no other gate before merge (categories Redis; e.g. RedisMessageConsumerDeliveryErrorDlqAsyncTests.When_rejecting_message_with_delivery_error_should_send_to_dlq_async, RedisMessageConsumerDeliveryErrorDlqTests.When_rejecting_message_with_delivery_error_should_send_to_dlq). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:294— `dotnet test ./tests/Paramore.Brighter.MQTT.Tests/Paramore.Brighter.MQTT.Tests.csproj --filter "Category=MQTT&Fragile!=CI" --configuration…` filters with `Category=MQTT&Fragile!=CI` — 15 test(s) it drops — run by no other gate before merge (e.g. When_mqtt_channel_factory_creates_channel_should_use_consumer_factory.Should_create_sync_channel, When_mqtt_channel_factory_creates_channel_should_use_consumer_factory.Should_create_async_channel). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:325— `dotnet test ./tests/Paramore.Brighter.RMQ.Async.Tests/Paramore.Brighter.RMQ.Async.Tests.csproj --filter "Fragile!=CI&Requires!=Docker-mTL…` filters with `Fragile!=CI&Requires!=Docker-mTLS&Category!=RMQNativeDelay` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_async, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:356— `dotnet test ./tests/Paramore.Brighter.RMQ.Sync.Tests/Paramore.Brighter.RMQ.Sync.Tests.csproj --filter "Fragile!=CI&Requires!=Docker-mTLS&…` filters with `Fragile!=CI&Requires!=Docker-mTLS&Category!=RMQNativeDelay` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_sync, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_sync). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:383— `dotnet test tests/Paramore.Brighter.RMQ.Async.Tests/Paramore.Brighter.RMQ.Async.Tests.csproj --filter "Category=RMQNativeDelay" --configu…` filters with `Category=RMQNativeDelay` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_async, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:384— `dotnet test tests/Paramore.Brighter.RMQ.Sync.Tests/Paramore.Brighter.RMQ.Sync.Tests.csproj --filter "Category=RMQNativeDelay" --configura…` filters with `Category=RMQNativeDelay` — 9 test(s) it drops — run by no other gate before merge (categories RabbitMQ, MutualTLS, RMQ; e.g. RmqMutualTlsAcceptanceTests.When_connecting_with_client_certificate_can_publish_message_sync, RmqMutualTlsAcceptanceTests.When_connecting_with_mtls_can_publish_and_receive_message_sync). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:468— `dotnet test ./tests/Paramore.Brighter.Kafka.Tests/Paramore.Brighter.Kafka.Tests.csproj --filter "Category=Kafka&Category!=Confluent&Fragi…` filters with `Category=Kafka&Category!=Confluent&Fragile!=CI` — 34 test(s) it drops — run by no other gate before merge (categories Kafka; e.g. KafkaMessageConsumerUpdateOffsetAsync.When_a_message_is_acknowledged_update_offset, KafkaMessageConsumerCommitRevokeConcurrency.When_committing_offsets_during_revoke_should_not_race_with_background_commit). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:500— `dotnet test ./tests/Paramore.Brighter.PostgresSQL.Tests/Paramore.Brighter.PostgresSQL.Tests.csproj --filter "Fragile!=CI" --configuration…` filters with `Fragile!=CI` — 1 test(s) it drops — run by no other gate before merge (e.g. PostgreSqlManyProvisionersHistoryRaceTests.When_many_postgres_provisioners_race_to_create_history_table_they_should_all_complete). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:527— `dotnet test ./tests/Paramore.Brighter.MSSQL.Tests/Paramore.Brighter.MSSQL.Tests.csproj --filter "Fragile!=CI" --configuration Release --l…` filters with `Fragile!=CI` — 1 test(s) it drops — run by no other gate before merge (e.g. MsSqlHistoryTableNonDboSchemaTests.When_history_table_exists_in_a_non_dbo_schema_runner_should_still_create_it_in_dbo). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:755— `dotnet test ./tests/Paramore.Brighter.AWSScheduler.Tests/Paramore.Brighter.AWSScheduler.Tests.csproj --filter "Fragile!=CI" --configurati…` filters with `Fragile!=CI` — 27 test(s) it drops — run by no other gate before merge (e.g. SnsSchedulingMessageTest.When_Scheduling_A_Sns_Message, SnsSchedulingAsyncMessageTest.When_Scheduling_A_Sns_Message_Async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:756— `dotnet test ./tests/Paramore.Brighter.AWSScheduler.V4.Tests/Paramore.Brighter.AWSScheduler.V4.Tests.csproj --filter "Fragile!=CI" --confi…` filters with `Fragile!=CI` — 27 test(s) it drops — run by no other gate before merge (e.g. SnsSchedulingMessageTest.When_Scheduling_A_Sns_Message, SnsSchedulingAsyncMessageTest.When_Scheduling_A_Sns_Message_Async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:798— `dotnet test ./tests/Paramore.Brighter.AzureServiceBus.Tests/Paramore.Brighter.AzureServiceBus.Tests.csproj --filter "Fragile!=CI" --confi…` filters with `Fragile!=CI` — 1 test(s) it drops — run by no other gate before merge (categories ASB; e.g. LargeAsbMessageProducerTests.When_posting_a_large_message_via_the_bulk_producer). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:872— `dotnet test ./tests/Paramore.Brighter.Gcp.Tests/Paramore.Brighter.Gcp.Tests.csproj --filter "Category!=Spanner&Category!=GcpPubSubStream&…` filters with `Category!=Spanner&Category!=GcpPubSubStream&Category!=GcpPubSubStreamOrdering&Category!=GcpPubSubPurge&Fragile!=CI&Requires!=PubSubEmulator&FullyQualifiedName!~Paramore.Brighter.Gcp.Tests.MessagingGateway.Pull.&FullyQualifiedName!~Paramore.Brighter.Gcp.Tests.MessagingGateway.PullOrdering.` — 228 test(s) it drops — run by no other gate before merge (categories GcpPubSubStream, GcpPubSubStreamOrdering, Spanner; e.g. WhenAMessageConsumerReadsMultipleMessagesShouldReceiveAllMessagesAsync.When_a_message_consumer_reads_multiple_messages_should_receive_all_messages_async, WhenInfrastructureMissingAndAssumeChannelShouldThrowExceptionAsync.When_infrastructure_missing_and_assume_channel_should_throw_exception_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:875— `dotnet test ./tests/Paramore.Brighter.Gcp.Tests/Paramore.Brighter.Gcp.Tests.csproj --filter "Category=GcpPubSubPurge&Requires!=PubSubEmul…` filters with `Category=GcpPubSubPurge&Requires!=PubSubEmulator&Fragile!=CI` — 228 test(s) it drops — run by no other gate before merge (categories GcpPubSubStream, GcpPubSubStreamOrdering, Spanner; e.g. WhenAMessageConsumerReadsMultipleMessagesShouldReceiveAllMessagesAsync.When_a_message_consumer_reads_multiple_messages_should_receive_all_messages_async, WhenInfrastructureMissingAndAssumeChannelShouldThrowExceptionAsync.When_infrastructure_missing_and_assume_channel_should_throw_exception_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
CI test gate excludes suites by filter REDACTED:911— `dotnet test ./tests/Paramore.Brighter.Gcp.Tests/Paramore.Brighter.Gcp.Tests.csproj --filter "(FullyQualifiedName~Paramore.Brighter.Gcp.Te…` filters with `(FullyQualifiedName~Paramore.Brighter.Gcp.Tests.MessagingGateway.Pull.|FullyQualifiedName~Paramore.Brighter.Gcp.Tests.MessagingGateway.PullOrdering.|Category=GcpPubSubPurge)&Fragile!=CI` — 228 test(s) it drops — run by no other gate before merge (categories GcpPubSubStream, GcpPubSubStreamOrdering, Spanner; e.g. WhenAMessageConsumerReadsMultipleMessagesShouldReceiveAllMessagesAsync.When_a_message_consumer_reads_multiple_messages_should_receive_all_messages_async, WhenInfrastructureMissingAndAssumeChannelShouldThrowExceptionAsync.When_infrastructure_missing_and_assume_channel_should_throw_exception_async). Run what it drops in another job before merge (a complementary filter), or remove the filter.
Duplicated block (12 lines × 2) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:144— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:144-155 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:136-147 — `src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs` and `src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:144` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:252— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:252-263 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:253-264 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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 (12 lines × 2) src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:37— src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:37-48 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:165-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:394— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:394-405 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:400-411 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (12 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:214— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:214-225 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:246-257 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (12 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:457— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:457-468 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:460-471 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (12 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:375— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:375-386 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:363-374 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:375` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:177— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:177-188 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:162-173 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` 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 6 separate duplicated blocks between them, totalling at least 111 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:385— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:385-396 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1033-1044 — both copies are in the same file, so extract the 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 `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 × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:411— src/Paramore.Brighter.ServiceActivator/Proactor.cs:411-422 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:378-389 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:411` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/Paramore.Brighter.Transformers.JustSaying/Extensions/RequestContextExtensions.cs:30— src/Paramore.Brighter.Transformers.JustSaying/Extensions/RequestContextExtensions.cs:30-41 | src/Paramore.Brighter.Transformers.MassTransit/Extensions/RequestContextExtensions.cs:19-30 — before extracting anything, compare `src/Paramore.Brighter.Transformers.JustSaying/Extensions/RequestContextExtensions.cs` and `src/Paramore.Brighter.Transformers.MassTransit/Extensions/RequestContextExtensions.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:49— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:49-60 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:84-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:49` 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.
Duplicated block (12 lines × 2) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:109— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:109-120 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:144-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:23— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:23-34 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:23-34 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:23` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:210— src/Paramore.Brighter.ServiceActivator/Proactor.cs:210-221 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:171-182 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:210` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:84— src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:84-95 | src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs:83-94 — `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs` and `src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:62— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:62-73 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:64-75 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs` 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 6 separate duplicated blocks between them, totalling at least 106 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 (12 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:77— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:77-88 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:79-90 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs` 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 6 separate duplicated blocks between them, totalling at least 106 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 (12 lines × 2) src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:93— src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:93-104 | src/Paramore.Brighter/Policies/Handlers/ResilienceExceptionPolicyHandler.cs:114-125 — 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) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:132— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:132-143 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:135-146 — before extracting anything, compare `samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs` and `samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs` 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 `samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) samples/Transforms/JustSaying/BrighterSide/Program.cs:63— samples/Transforms/JustSaying/BrighterSide/Program.cs:63-74 | samples/Transforms/MassTransit/MBrigtherSide/Program.cs:63-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) samples/WebAPI/WebAPI_Dapper/GreetingsApp/Policies/Retry.cs:16— samples/WebAPI/WebAPI_Dapper/GreetingsApp/Policies/Retry.cs:16-43 | samples/WebAPI/WebAPI_Dapper/SalutationApp/Policies/Retry.cs:15-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) samples/Transforms/JustSaying/BrighterSide/Program.cs:38— samples/Transforms/JustSaying/BrighterSide/Program.cs:38-49 | samples/Transforms/MassTransit/MBrigtherSide/Program.cs:38-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/Transforms/JustSaying/BrighterSide/Program.cs:38` it begins part-way through the construct above it, so those exact lines 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) samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Extensions/HealthCheckExtensions.cs:11— samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Extensions/HealthCheckExtensions.cs:11-22 | samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/Extensions/HealthCheckExtensions.cs:11-22 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×23
Edited copy of a member (8 corresponding lines) src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72— src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72-79 | src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:83-90 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:510— src/Paramore.Brighter.ServiceActivator/Proactor.cs:510-517 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:443-450 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1599— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1599-1606 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1609-1616 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:292— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:292-299 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:255-262 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:236— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:236-243 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:238-245 — 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) src/Paramore.Brighter/TransformPipeline.cs:27— src/Paramore.Brighter/TransformPipeline.cs:27-34 | src/Paramore.Brighter/TransformPipelineAsync.cs:28-35 — 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) src/Paramore.Brighter/MapperMethodDiscovery.cs:39— src/Paramore.Brighter/MapperMethodDiscovery.cs:39-47 | src/Paramore.Brighter/MapperMethodDiscovery.cs:54-61 — 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) src/Paramore.Brighter.Validation.FluentValidation/FluentValidationRequestHandlerAsync.cs:53— src/Paramore.Brighter.Validation.FluentValidation/FluentValidationRequestHandlerAsync.cs:53-61 | src/Paramore.Brighter.Validation.FluentValidation/FluentValidationRequestHandler.cs:51-58 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:284— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:284-292 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:282-289 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:41— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:41-48 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:48-55 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:195— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:195-202 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:197-204 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:123— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:123-130 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:121-128 — 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) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:117— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:117-124 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:121-128 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:262— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:262-269 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:260-267 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:640— src/Paramore.Brighter.ServiceActivator/Proactor.cs:640-647 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:632-642 — 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1453— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1453-1460 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1441-1448 — 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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:196— src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:196-203 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:480-489 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/Extensions/FifoThroughPutLimitConverter.cs:17— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/Extensions/FifoThroughPutLimitConverter.cs:17-24 | src/Paramore.Brighter.MessagingGateway.AWSSQS/Extensions/FifoThroughPutLimitConverter.cs:17-24 — 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1480— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1480-1487 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1468-1475 — 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) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:85— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:85-92 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:85-92 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:31— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:31-38 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSNameExtensions.cs:31-38 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:624— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:624-631 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:627-634 — 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) samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Handlers/FIndGreetingsForPersonHandlerAsync.cs:28— samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Handlers/FIndGreetingsForPersonHandlerAsync.cs:28-35 | samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Handlers/FindPersonByNameHandlerAsync.cs:28-39 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:238— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:238-245 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:270-277 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:238` 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.
Duplicated block (8 lines × 2) src/Paramore.Brighter/WrapPipeline.cs:97— src/Paramore.Brighter/WrapPipeline.cs:97-104 | src/Paramore.Brighter/WrapPipelineAsync.cs:104-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 (8 lines × 2) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:48— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:48-55 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs:49-56 — before extracting anything, compare `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs` and `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:48— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:48-55 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactoryAsync.cs:49-56 — before extracting anything, compare `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs` and `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactoryAsync.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:203— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:203-210 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:235-242 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:160— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:160-167 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:158-165 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:285— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:285-292 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:283-290 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:319— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:319-326 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:317-324 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:350— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:350-357 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:339-346 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (8 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:870— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:870-877 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:897-904 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:870` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:391— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:391-398 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:378-385 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:391` 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.
Duplicated block (8 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:402— src/Paramore.Brighter.ServiceActivator/Proactor.cs:402-409 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:369-376 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:402` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:52— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:52-59 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:52-59 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (8 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:192— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:192-199 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:192-199 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (8 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:558— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:558-565 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:559-566 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:509— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:509-516 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:225-232 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:446— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:446-453 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:449-456 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (8 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:516— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:516-523 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:227-234 — 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) src/Paramore.Brighter.MySql.EntityFrameworkCore/MySqlEntityFrameworkTransactionProvider.cs:80— src/Paramore.Brighter.MySql.EntityFrameworkCore/MySqlEntityFrameworkTransactionProvider.cs:80-87 | src/Paramore.Brighter.PostgreSql.EntityFrameworkCore/PostgreSqlEntityFrameworkTransactionProvider.cs:79-86 — 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 (8 lines × 2) src/Paramore.Brighter.Transformers.MassTransit/MassTransitMessageMapper.cs:136— src/Paramore.Brighter.Transformers.MassTransit/MassTransitMessageMapper.cs:136-143 | src/Paramore.Brighter.Transformers.MassTransit/MassTransitTransform.cs:135-142 — 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) src/Paramore.Brighter/Validation/PipelineDiagnosticWriter.cs:77— src/Paramore.Brighter/Validation/PipelineDiagnosticWriter.cs:77-84 | src/Paramore.Brighter/Validation/PipelineValidator.cs:89-96 — 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) samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:103— samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:103-110 | samples/Scheduler/AwsTaskQueue/GreetingsReceiverConsole/Program.cs:157-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:17— samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:17-24 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:17-24 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs` and `samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs` 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:71— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:71-81 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:131-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:405— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:405-415 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:391-401 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:405` it does not close everything it opens, so those 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:371— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:371-381 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:427-437 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:371` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:855— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:855-865 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:713-723 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) REDACTED:159— REDACTED:159-169 | REDACTED:222-232 — 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 `REDACTED: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 (11 lines × 2) src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:42— src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:42-52 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:100-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:42` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:409— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:409-419 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:415-425 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:52— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:52-62 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:52-62 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs` 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 5 separate duplicated blocks between them, totalling at least 88 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 (11 lines × 2) REDACTED:199— REDACTED:199-209 | REDACTED:265-275 — both copies are in the same file, so extract the 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 `REDACTED:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:54— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:54-64 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:57-67 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:46— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:46-56 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:46-56 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Paramore.Brighter/TransformPipeline.cs:67— src/Paramore.Brighter/TransformPipeline.cs:67-77 | src/Paramore.Brighter/TransformPipelineAsync.cs:119-129 — 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:271— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:271-281 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:269-279 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:271` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:178— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:178-188 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:178-188 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:443— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:443-453 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:449-459 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:78— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:78-88 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:78-88 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs` 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 5 separate duplicated blocks between them, totalling at least 88 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:48— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:48-58 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:50-60 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs` 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 6 separate duplicated blocks between them, totalling at least 106 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:92— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:92-102 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:94-104 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs` 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 6 separate duplicated blocks between them, totalling at least 106 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 (11 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByName.cs:38— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByName.cs:38-48 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateQueueByName.cs:38-48 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByName.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateQueueByName.cs` 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 11 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 (11 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:348— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:348-358 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:348-358 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs` 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 5 separate duplicated blocks between them, totalling at least 313 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 (11 lines × 2) src/Paramore.Brighter/Channel.cs:122— src/Paramore.Brighter/Channel.cs:122-132 | src/Paramore.Brighter/ChannelAsync.cs:124-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35— samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-45 | samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-45 — before extracting anything, compare `samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs` and `samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Startup.cs:41— samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Startup.cs:41-51 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Startup.cs:37-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:237— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:237-243 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:239-245 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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 (7 lines × 2) src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:132— src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:132-138 | src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:158-164 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:132` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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) REDACTED:63— REDACTED:63-69 | REDACTED:587-593 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) REDACTED:87— REDACTED:87-93 | REDACTED:605-611 — both copies are in the same file, so extract the 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 `REDACTED:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:603` calls `DeleteSourceMessageAsync` and `REDACTED: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 (7 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:293— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:293-299 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:256-262 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:511— src/Paramore.Brighter.ServiceActivator/Proactor.cs:511-517 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:444-450 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:231— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:231-237 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:231-237 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 143 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:231` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:213— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:213-219 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:213-219 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 87 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:213` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:326— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:326-332 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:1098-1104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:297— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:297-308 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:273-279 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:297` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:115— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:115-121 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:153-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 `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:115` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/IndexQueryResult.cs:30— src/Paramore.Brighter.Outbox.DynamoDB.V4/IndexQueryResult.cs:30-36 | src/Paramore.Brighter.Outbox.DynamoDB/IndexQueryResult.cs:30-36 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/IndexQueryResult.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/IndexQueryResult.cs` 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 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/IndexQueryResult.cs:30` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/CommandProcessor.cs:996— src/Paramore.Brighter/CommandProcessor.cs:996-1002 | src/Paramore.Brighter/CommandProcessor.cs:1039-1045 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/CommandProcessor.cs:996` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Paramore.Brighter/CommandProcessor.cs:1245— src/Paramore.Brighter/CommandProcessor.cs:1245-1251 | src/Paramore.Brighter/CommandProcessor.cs:1288-1294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/CommandProcessor.cs:1245` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:92— src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:92-98 | src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandlerAsync.cs:93-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:92` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/OutboxProducerMediator.cs:396— src/Paramore.Brighter/OutboxProducerMediator.cs:396-402 | src/Paramore.Brighter/OutboxProducerMediator.cs:465-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/OutboxProducerMediator.cs:396` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:32— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:32-38 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSNameExtensions.cs:32-38 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSNameExtensions.cs` 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 2 separate duplicated blocks between them, totalling at least 27 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 (7 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:490— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:490-496 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:206-212 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:625— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:625-631 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:628-634 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (7 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:497— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:497-503 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:208-214 — 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1454— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1454-1460 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1442-1448 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (7 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1481— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1481-1487 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1469-1475 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (7 lines × 2) samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43— samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43-49 | samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43-49 — before extracting anything, compare `samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` and `samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Swallowed exception (empty catch) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:266— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:370— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:180— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:479— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:160— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:259— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:186— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:224— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:162— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:260— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:144— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:160— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.MongoDb/BaseMongoDb.cs:131— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs:213— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter/HandlerLifetimeScope.cs:147— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Paramore.Brighter/RelationalDbTransactionProvider.cs:130— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter/RelationalDbTransactionProvider.cs:142— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter/Tasks/BatchedCallbackQueue.cs:169— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter/Tasks/TaskExtensions.cs:113— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Paramore.Brighter/TransformLifetimeScope.cs:32— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Paramore.Brighter/TransformLifetimeScopeAsync.cs:48— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Paramore.Brighter/TransformPipeline.cs:62— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Paramore.Brighter/TransformPipelineAsync.cs:114— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×21
Disposable created and abandoned in the method that made it src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:263— `command` is a `SpannerCommand`, which implements `IDisposable`, and it is created here (line 263). Every use of it in `ExecuteCreateTableIfNotExistsSafeAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:292— `command` is a `SpannerCommand`, which implements `IDisposable`, and it is created here (line 292). Every use of it in `EnsureHistoryTableAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:203— `client` is a `IAmazonScheduler`, which implements `IDisposable`, and it is created here (line 203). Every use of it in `CreateSchedulerGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:203— `client` is a `IAmazonScheduler`, which implements `IDisposable`, and it is created here (line 203). Every use of it in `CreateSchedulerGroup` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:175— `sqlCmd` is a `DbCommand`, which implements `IDisposable`, and it is created here (line 175). Every use of it in `NumberOfMessageReady` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sqlCmd = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1470— `sha256` is a `SHA256`, which implements `IDisposable`, and it is created here (line 1470). Every use of it in `GetShardNumber` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sha256 = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1458— `sha256` is a `SHA256`, which implements `IDisposable`, and it is created here (line 1458). Every use of it in `GetShardNumber` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var sha256 = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:258— `transferUtility` is a `TransferUtility`, which implements `IDisposable`, and it is created here (line 258). Every use of it in `StoreAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var transferUtility = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:259— `transferUtility` is a `TransferUtility`, which implements `IDisposable`, and it is created here (line 259). Every use of it in `StoreAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var transferUtility = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:200— `client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 200). Every use of it in `EnsureStoreExists` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:222— `client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 222). Every use of it in `Delete` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:241— `client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 241). Every use of it in `Retrieve` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:266— `client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 266). Every use of it in `HasClaim` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:293— `client` is a `StorageClient`, which implements `IDisposable`, and it is created here (line 293). Every use of it in `Store` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:58— `client` is a `MongoClient`, which implements `IDisposable`, and it is created here (line 58). Every use of it in `MongoDbLuggageStore` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter/Observability/OutboxStaleMessageMeter.cs:63— `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 63). Every use of it in `OutboxStaleMessageMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter/Observability/PublishConfirmationMeter.cs:45— `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 45). Every use of it in `PublishConfirmationMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter/Observability/SweeperMeter.cs:68— `meter` is a `Meter`, which implements `IDisposable`, and it is created here (line 68). Every use of it in `SweeperMeter` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var meter = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:154— `deCompressionStream` is a `Stream`, which implements `IDisposable`, and it is created here (line 154). Every use of it in `UnwrapAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deCompressionStream = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:231— `deCompressionStream` is a `Stream`, which implements `IDisposable`, and it is created here (line 231). Every use of it in `Unwrap` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var deCompressionStream = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs:21— `command` is a `DbCommand`, which implements `IDisposable`, and it is created here (line 21). Every use of it in `CheckHealthAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var command = …;`), which releases it at the end of the scope on every path including a throw.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×20
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:295— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:295-318 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:292-312 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.ServiceActivator/Validation/ConsumerValidationRules.cs:181— src/Paramore.Brighter.ServiceActivator/Validation/ConsumerValidationRules.cs:181-204 | src/Paramore.Brighter/Validation/ProducerValidationRules.cs:77-97 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) REDACTED:57— REDACTED:57-77 | REDACTED:81-101 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.ServiceActivator/Proactor.cs:110— src/Paramore.Brighter.ServiceActivator/Proactor.cs:110-132 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:420-440 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:121— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:121-141 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:151-173 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:458— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:458-478 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:490-510 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:143— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:143-163 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:135-155 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:695— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:695-717 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:724-744 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs:169— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs:169-191 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs:335-355 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter/RelationDatabaseOutbox.cs:753— src/Paramore.Brighter/RelationDatabaseOutbox.cs:753-774 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:781-801 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:122— src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:122-142 | src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:251-271 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:169— src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:169-189 | src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:298-318 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:741— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:741-761 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:774-794 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter/InMemoryChannelFactory.cs:65— src/Paramore.Brighter/InMemoryChannelFactory.cs:65-85 | src/Paramore.Brighter/InMemoryChannelFactory.cs:93-113 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter/InMemoryChannelFactory.cs:122— src/Paramore.Brighter/InMemoryChannelFactory.cs:122-143 | src/Paramore.Brighter/InMemoryChannelFactory.cs:93-113 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:506— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:506-527 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:532-552 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:141— src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:141-161 | src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:302-322 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter/Channel.cs:138— src/Paramore.Brighter/Channel.cs:138-158 | src/Paramore.Brighter/ChannelAsync.cs:142-164 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:73— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:73-93 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:100-120 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:129— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:129-149 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs:156-176 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:144— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:144-152 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:193-201 — both copies are in the same file, so extract the 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:351— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:351-359 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:397-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1146— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1146-1154 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1134-1142 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1146` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:325— src/Paramore.Brighter.ServiceActivator/Proactor.cs:325-333 | src/Paramore.Brighter.ServiceActivator/Proactor.cs:380-388 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/Paramore.Brighter.ServiceActivator/Reactor.cs:289— src/Paramore.Brighter.ServiceActivator/Reactor.cs:289-297 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:348-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/Paramore.Brighter/Observability/BrighterTracer.cs:113— src/Paramore.Brighter/Observability/BrighterTracer.cs:113-121 | src/Paramore.Brighter/Observability/BrighterTracer.cs:404-412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Observability/BrighterTracer.cs: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.
Duplicated block (9 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:402— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:402-410 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:579-587 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:402` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:53— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:53-61 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:96-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs: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 (9 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:230— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:230-238 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:228-236 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:230` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:246— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:246-254 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:244-252 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (9 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:273— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:273-281 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:271-279 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (9 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:307— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:307-315 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:305-313 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (9 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:414— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:414-422 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:837-845 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:414` 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) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:371— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:371-379 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:333-341 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:371` 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 (9 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:70— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:70-78 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:70-78 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/UnixTimestamp.cs:38— src/Paramore.Brighter.MessagingGateway.RMQ.Async/UnixTimestamp.cs:38-46 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/UnixTimestamp.cs:38-46 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/UnixTimestamp.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/UnixTimestamp.cs` 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 9 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. 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/TopicQueryContext.cs:46— src/Paramore.Brighter.Outbox.DynamoDB.V4/TopicQueryContext.cs:46-54 | src/Paramore.Brighter.Outbox.DynamoDB/TopicQueryContext.cs:46-54 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/TopicQueryContext.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/TopicQueryContext.cs` 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 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:520— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:520-528 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:521-529 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (9 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:66— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:66-74 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:66-74 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs` 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 5 separate duplicated blocks between them, totalling at least 88 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 (9 lines × 2) samples/Transforms/AWSTransfomers/CloudEvents/GreetingsReceiverConsole/Program.cs:56— samples/Transforms/AWSTransfomers/CloudEvents/GreetingsReceiverConsole/Program.cs:56-64 | samples/Transforms/AWSTransfomers/Compression/GreetingsReceiverConsole/Program.cs:56-64 — before extracting anything, compare `samples/Transforms/AWSTransfomers/CloudEvents/GreetingsReceiverConsole/Program.cs` and `samples/Transforms/AWSTransfomers/Compression/GreetingsReceiverConsole/Program.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Temporal coupling in handler: PaymentReceivedEventHandler.Handle samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:33— `PaymentReceivedEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: PaymentReceivedEventHandler.Handle samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:33— `PaymentReceivedEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: FarewellEventHandler.Handle samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9— `FarewellEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Scheduler/QuartzTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/ASBTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:16— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: FarewellEventHandler.Handle samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9— `FarewellEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/MsSqlMessagingGateway/GreetingsReceiverConsole/GreetingEventHandler.cs:41— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: FarewellEventHandler.Handle samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9— `FarewellEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/RedisTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: FarewellEventHandler.Handle samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:9— `FarewellEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Transforms/AWSTransfomers/ClaimCheck/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Transforms/AWSTransfomers/CloudEvents/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Transforms/AWSTransfomers/Compression/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:33— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Tutorials/02-FirstMessage/GreetingsReceiver/GreetingEventHandler.cs:38— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Tutorials/03-DurableOutbox/GreetingsReceiver/GreetingEventHandler.cs:38— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
Temporal coupling in handler: GreetingEventHandler.Handle samples/Tutorials/04-Kafka/GreetingsReceiver/GreetingEventHandler.cs:38— `GreetingEventHandler.Handle` makes a synchronous remote call (a sync-over-async wait via `RequestHandler.Handle`) while handling an event. The handler now depends, in real time, on another service being up and fast — the opposite of why you went event-driven. Publish a follow-up message (or use the outbox) instead of calling out and awaiting a response inside the handler.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×19
Edited copy of a member (18 corresponding lines) src/Paramore.Brighter.MessageScheduler.Hangfire/HangfireMessageScheduler.cs:178— src/Paramore.Brighter.MessageScheduler.Hangfire/HangfireMessageScheduler.cs:178-195 | src/Paramore.Brighter.MessageScheduler.Hangfire/HangfireMessageScheduler.cs:199-224 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:228— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:228-245 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:260-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.
Edited copy of a member (18 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:422— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:422-439 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:428-445 — 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) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:43— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:43-60 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:103-120 — 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) REDACTED:255— REDACTED:255-272 | REDACTED:275-292 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqDelayedRequeue.cs:42— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqDelayedRequeue.cs:42-60 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqDelayedRequeue.cs:39-56 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:495— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:495-512 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:501-519 — 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) src/Paramore.Brighter/InMemoryOutbox.cs:362— src/Paramore.Brighter/InMemoryOutbox.cs:362-379 | src/Paramore.Brighter/InMemoryOutbox.cs:384-404 — 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) src/Paramore.Brighter.MessagingGateway.Postgres/PostgresChannelFactory.cs:38— src/Paramore.Brighter.MessagingGateway.Postgres/PostgresChannelFactory.cs:38-55 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresChannelFactory.cs:59-76 — 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) src/Paramore.Brighter/CommandProcessor.cs:1399— src/Paramore.Brighter/CommandProcessor.cs:1399-1416 | src/Paramore.Brighter/CommandProcessor.cs:1433-1450 — 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:156— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:156-176 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:622-639 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:178— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:178-195 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:343-360 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:299— src/Paramore.Brighter/RelationalDatabaseInbox.cs:299-317 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1201-1218 — 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) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:642— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:642-659 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:663-680 — 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) src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandler.cs:63— src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandler.cs:63-80 | src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandlerAsync.cs:66-83 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:264— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:264-281 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:216-233 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:472— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:472-489 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:478-495 — 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) samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:115— samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:115-132 | samples/Scheduler/QuartzTaskQueue/GreetingsPumper/Program.cs:91-108 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:35— samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:35-52 | samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/Program.cs:32-49 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (16 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:223— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:223-238 | src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:256-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:205— src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:205-220 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:238-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:205` it begins part-way through the construct above it, so those exact lines 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) src/Paramore.Brighter.Extensions.DependencyInjection/BrighterValidationHostedService.cs:80— src/Paramore.Brighter.Extensions.DependencyInjection/BrighterValidationHostedService.cs:80-95 | src/Paramore.Brighter.ServiceActivator.Extensions.Hosting/ServiceActivatorHostedService.cs:56-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:443— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:443-458 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:430-445 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:443` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/Command.cs:44— src/Paramore.Brighter/Command.cs:44-59 | src/Paramore.Brighter/Event.cs:45-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Paramore.Brighter/Command.cs:60` calls `Display` and `src/Paramore.Brighter/Event.cs:61` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:347— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:347-362 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:353-368 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:306— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:306-321 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:306-321 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:237— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:237-252 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:149-164 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:494— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:494-509 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:497-512 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:111— src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:111-126 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:97-112 — 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 `src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:111` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:75— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:75-90 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:75-90 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:95` calls `ContentType` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:95` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:483— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:483-498 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:470-485 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:483` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:683— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:683-698 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1100-1115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:683` 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:91— src/Paramore.Brighter/RelationDatabaseOutbox.cs:91-106 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:142-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/RelationDatabaseOutbox.cs:91` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:423— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:423-438 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:429-444 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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. 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:151— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:151-166 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:153-168 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:151` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByUrl.cs:25— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByUrl.cs:25-40 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateQueueByUrl.cs:25-40 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateQueueByUrl.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateQueueByUrl.cs` 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 16 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/AllTopicsScanContext.cs:45— src/Paramore.Brighter.Outbox.DynamoDB.V4/AllTopicsScanContext.cs:45-60 | src/Paramore.Brighter.Outbox.DynamoDB/AllTopicsScanContext.cs:45-60 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/AllTopicsScanContext.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/AllTopicsScanContext.cs` 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 16 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×16
Edited copy of a member (26 corresponding lines) REDACTED:74— REDACTED:74-99 | REDACTED:125-150 — 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) src/Paramore.Brighter/CommandProcessor.cs:988— src/Paramore.Brighter/CommandProcessor.cs:988-1014 | src/Paramore.Brighter/CommandProcessor.cs:1237-1262 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:45— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:45-70 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:45-70 — 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) src/Paramore.Brighter/InMemoryOutbox.cs:300— src/Paramore.Brighter/InMemoryOutbox.cs:300-325 | src/Paramore.Brighter/InMemoryOutbox.cs:561-592 — 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) src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:145— src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:145-174 | src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:222-247 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:110— src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:110-136 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:96-121 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:367— src/Paramore.Brighter/RelationDatabaseOutbox.cs:367-393 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:993-1018 — 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) src/Paramore.Brighter/InMemoryMessageConsumer.cs:282— src/Paramore.Brighter/InMemoryMessageConsumer.cs:282-307 | src/Paramore.Brighter/InMemoryMessageConsumer.cs:321-347 — 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) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:129— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:129-155 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs: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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:113— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:113-138 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:149-174 — 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) src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:93— src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:93-118 | src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:218-247 — 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) src/Paramore.Brighter.Transformers.MassTransit/MassTransitTransform.cs:56— src/Paramore.Brighter.Transformers.MassTransit/MassTransitTransform.cs:56-81 | src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs:75-110 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:116— src/Paramore.Brighter/RelationalDatabaseInbox.cs:116-141 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:217-243 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:146— src/Paramore.Brighter/RelationalDatabaseInbox.cs:146-171 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:249-275 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1223— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1223-1248 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1253-1280 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:115— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:115-140 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:122-147 — 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.
Unfinished stub — throws NotImplementedException src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumerFactory.cs:91— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqProducerRegistryFactory.cs:32— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/Analyzer/AnalyzerSamples/WrapWithMapperSample.cs:36— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Common/DbMaker/ConnectionResolver.cs:65— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:29— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:16— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:29— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:26— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:15— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:26— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException REDACTED:168— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:27— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:15— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:26— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:162— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:164— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×15
Edited copy of a member (11 corresponding lines) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumerFactory.cs:50— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumerFactory.cs:50-60 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumerFactory.cs:63-73 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:321— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:321-332 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:315-325 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandler.cs:68— src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandler.cs:68-78 | src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandlerAsync.cs:72-82 — 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) src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandlerAsync.cs:62— src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandlerAsync.cs:62-72 | src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandlerAsync.cs:72-82 — 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) src/Paramore.Brighter.ServiceActivator/ConsumerFactory.cs:52— src/Paramore.Brighter.ServiceActivator/ConsumerFactory.cs:52-62 | src/Paramore.Brighter.ServiceActivator/ConsumerFactory.cs:72-82 — 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) src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandler.cs:58— src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandler.cs:58-68 | src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandlerAsync.cs:62-72 — 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) src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:137— src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:137-147 | src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:232-242 — 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) src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandler.cs:68— src/Paramore.Brighter/Defer/Handlers/DeferMessageOnErrorHandler.cs:68-78 | src/Paramore.Brighter/Reject/Handlers/RejectMessageOnErrorHandler.cs:58-68 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:627— src/Paramore.Brighter.ServiceActivator/Proactor.cs:627-637 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:619-629 — 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) src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs:152— src/Paramore.Brighter.Outbox.Hosting/TimedOutboxSweeper.cs:152-162 | src/Paramore.Brighter.Outbox.Sqlite/SqliteOutbox.cs:160-171 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:333— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:333-343 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:339-349 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:210— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:210-220 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:208-218 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:123— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:123-133 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:126-136 — 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) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:252— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:252-262 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:244-254 — 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) samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:127— samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:127-137 | samples/Tutorials/03-DurableOutbox/GreetingsSender/Program.cs:132-142 — 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.
Stateful singleton: ServiceCollectionMessageMapperRegistryBuilder src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionMessageMapperRegistryBuilder.cs:46— `ServiceCollectionMessageMapperRegistryBuilder` is a singleton (one shared instance) but mutates instance state outside any lock (DefaultMessageMapper, DefaultMessageMapperAsync; e.g. `DefaultMessageMapper` at line 128).
Stateful singleton: IAmAStorageProviderAsync src/Paramore.Brighter/Transforms/Storage/IAmAStorageProviderAsync.cs:36— `IAmAStorageProviderAsync` is a singleton (one shared instance) but mutates instance state outside any lock (Tracer; e.g. `Tracer` at src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs line 1119, through the shared instance).
Stateful singleton: IAmAStorageProvider src/Paramore.Brighter/Transforms/Storage/IAmAStorageProvider.cs:35— `IAmAStorageProvider` is a singleton (one shared instance) but mutates instance state outside any lock (Tracer; e.g. `Tracer` at src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs line 1112, through the shared instance).
Stateful singleton: TimedOutboxStaleMessageMonitor src/Paramore.Brighter.Outbox.Hosting/TimedOutboxStaleMessageMonitor.cs:44— `TimedOutboxStaleMessageMonitor` is a singleton (one shared instance) but mutates instance state outside any lock (_loop; e.g. `_loop` at line 176).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:36— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 58).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/TimedMessageGenerator.cs:36— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 58).
Stateful singleton: TimedStatusSender samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:37— `TimedStatusSender` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 64).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/KafkaSchemaRegistry/GreetingsSender/TimedMessageGenerator.cs:11— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 46).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs:11— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 37).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:11— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 37).
Stateful singleton: CommandCounter samples/TaskQueue/MsSqlMessagingGateway/CompetingReceiverConsole/CommandCounter.cs:3— `CommandCounter` is a singleton (one shared instance) but mutates instance state outside any lock (Counter; e.g. `Counter` at line 7).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/MultiBus/GreetingsSender/TimedMessageGenerator.cs:11— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 37).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs:36— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 58).
Stateful singleton: TimedMessageGenerator samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:36— `TimedMessageGenerator` is a singleton (one shared instance) but mutates instance state outside any lock (_iteration; e.g. `_iteration` at line 58).
TooManyMethods: RelationDatabaseOutbox src/Paramore.Brighter/RelationDatabaseOutbox.cs— TooManyMethods — 1164 significant lines (blank, comment-only and punctuation-only lines excluded), 106 methods. The bar is 30 methods; this is 76 over it, 3.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CommandProcessor src/Paramore.Brighter/CommandProcessor.cs— TooManyMethods — 753 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: DynamoDbOutbox src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs— TooManyMethods — 777 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 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.
TooManyMethods: DynamoDbOutbox src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs— TooManyMethods — 765 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 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.
TooManyMethods: OutboxProducerMediator src/Paramore.Brighter/OutboxProducerMediator.cs— TooManyMethods — 721 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 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.
TooManyMethods: KafkaMessageConsumer src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs— TooManyMethods — 584 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RelationalDatabaseInbox src/Paramore.Brighter/RelationalDatabaseInbox.cs— TooManyMethods — 357 significant lines (blank, comment-only and punctuation-only lines excluded), 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: TimedOutboxStaleMessageMonitor src/Paramore.Brighter.Outbox.Hosting/TimedOutboxStaleMessageMonitor.cs— TooManyMethods — 265 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ServiceCollectionExtensions src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs— TooManyMethods — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MongoDbOutbox src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs— TooManyMethods — 647 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrighterTracer src/Paramore.Brighter/Observability/BrighterTracer.cs— TooManyMethods — 591 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RmqMessageProducer src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs— TooManyMethods — 257 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FirestoreOutbox src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs— TooManyMethods — 770 significant lines (blank, comment-only and punctuation-only lines excluded), 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: InMemoryOutbox src/Paramore.Brighter/InMemoryOutbox.cs— TooManyMethods — 355 significant lines (blank, comment-only and punctuation-only lines excluded), 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×14
Edited copy of a member (14 corresponding lines) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:167— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:167-180 | src/Paramore.Brighter.BoxProvisioning/SqlBoxMigrationRunner.cs:335-348 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:229— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:229-242 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:227-240 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:335— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:335-349 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:328-341 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:615— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:615-635 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:532-545 — 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) src/Paramore.Brighter/CommandProcessor.cs:342— src/Paramore.Brighter/CommandProcessor.cs:342-355 | src/Paramore.Brighter/CommandProcessor.cs:359-372 — 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) src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:204— src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:204-219 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxDetectionHelper.cs:202-215 — 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) src/Paramore.Brighter/RequestHandlerAsync.cs:120— src/Paramore.Brighter/RequestHandlerAsync.cs:120-133 | src/Paramore.Brighter/RequestHandlerAsync.cs:156-169 — 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) src/Paramore.Brighter/RequestHandler.cs:105— src/Paramore.Brighter/RequestHandler.cs:105-118 | src/Paramore.Brighter/RequestHandler.cs:140-153 — 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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:284— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:284-297 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:300-316 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:147— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:147-160 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:147-160 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1972— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1972-1985 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:2049-2062 — 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) src/Paramore.Brighter/InMemoryOutbox.cs:738— src/Paramore.Brighter/InMemoryOutbox.cs:738-751 | src/Paramore.Brighter/InMemoryOutbox.cs:754-767 — 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) src/Paramore.Brighter/Channel.cs:166— src/Paramore.Brighter/Channel.cs:166-179 | src/Paramore.Brighter/ChannelAsync.cs:173-186 — 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) REDACTED:35— REDACTED:35-48 | REDACTED:51-65 — 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.
Duplicated block (18 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:139— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:139-156 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:137-154 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:139` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:177— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:177-194 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:169-186 — `src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs` and `src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 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) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:123— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:123-140 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:335-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:205— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:205-222 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:418-435 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:205` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:122— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:122-139 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:122-139 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs:139— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs:139-156 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagingGatewayConnection.cs:147-164 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagingGatewayConnection.cs` 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 2 separate duplicated blocks between them, totalling at least 77 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1390— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1390-1407 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1378-1395 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1390` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:244— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:244-261 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:695-712 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:244` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:425— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:425-442 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:426-443 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226-243 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:290-307 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226` 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.
Duplicated block (18 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:310— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:310-327 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:310-327 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs` 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 5 separate duplicated blocks between them, totalling at least 313 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:310` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (18 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:83— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:83-100 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:83-100 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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) samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs:17— samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs:17-34 | samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs:17-34 — before extracting anything, compare `samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs` and `samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/HealthChecks/BrighterOutboxConnectionHealthCheck.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) samples/WebAPI/WebAPI_Common/DbMaker/GreetingsDbFactory.cs:23— samples/WebAPI/WebAPI_Common/DbMaker/GreetingsDbFactory.cs:23-40 | samples/WebAPI/WebAPI_Common/DbMaker/SalutationsDbFactory.cs:24-41 — 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 `samples/WebAPI/WebAPI_Common/DbMaker/GreetingsDbFactory.cs:23` 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:60— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:60-74 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:538-552 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Paramore.Brighter/RelationDatabaseOutbox.cs:435— src/Paramore.Brighter/RelationDatabaseOutbox.cs:435-449 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:480-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/RelationDatabaseOutbox.cs:435` it does not close everything it opens, so those exact lines 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) REDACTED:340— REDACTED:340-354 | REDACTED:364-378 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `connection` to `SqlConnection` in one and `NpgsqlConnection` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) src/Paramore.Brighter.Extensions.DependencyInjection/ScopeConfigurationValidator.cs:130— src/Paramore.Brighter.Extensions.DependencyInjection/ScopeConfigurationValidator.cs:130-144 | src/Paramore.Brighter/Validation/PipelineValidator.cs:159-173 — 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 (15 lines × 2) src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:59— src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:59-73 | src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs:58-72 — `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs` and `src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:44— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:44-58 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs:44-58 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 111 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 (15 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:176— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:176-190 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:174-188 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `basicProperties` to `IReadOnlyBasicProperties` in one and `IBasicProperties` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducerFactory.cs:49— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducerFactory.cs:49-63 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducerFactory.cs:51-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1410— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1410-1424 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1398-1412 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1410` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:48— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:48-62 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:49-63 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:322— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:322-336 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:368-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:322` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:671— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:671-685 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1147-1180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:671` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:403— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:403-418 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:441-455 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:403` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:440` calls `Select`, `ToArray` and `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:402` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:234— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:234-248 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:226-240 — `src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs` and `src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 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.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×13
Edited copy of a member (19 corresponding lines) REDACTED:52— REDACTED:52-70 | REDACTED:103-121 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:208— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:208-226 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:206-224 — 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:979— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:979-997 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:1001-1021 — 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) src/Paramore.Brighter/PipelineBuilder.cs:498— src/Paramore.Brighter/PipelineBuilder.cs:498-516 | src/Paramore.Brighter/PipelineBuilder.cs:568-590 — 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) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:191— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:191-209 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:212-230 — 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) src/Paramore.Brighter/PipelineBuilder.cs:444— src/Paramore.Brighter/PipelineBuilder.cs:444-463 | src/Paramore.Brighter/PipelineBuilder.cs:466-484 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:463— src/Paramore.Brighter.ServiceActivator/Proactor.cs:463-484 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:480-498 — 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) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:284— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:284-302 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:285-303 — 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) src/Paramore.Brighter.MsSql.Azure/MsSqlAzureConnectionProviderBase.cs:56— src/Paramore.Brighter.MsSql.Azure/MsSqlAzureConnectionProviderBase.cs:56-74 | src/Paramore.Brighter.MsSql.Azure/MsSqlAzureConnectionProviderBase.cs:77-95 — 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) src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:169— src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:169-187 | src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:276-294 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:758— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:758-776 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:638-656 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs:151— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs:151-169 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsSubscription.cs:151-169 — 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) samples/WebAPI/WebAPI_Common/DbMaker/GreetingsDbFactory.cs:16— samples/WebAPI/WebAPI_Common/DbMaker/GreetingsDbFactory.cs:16-40 | samples/WebAPI/WebAPI_Common/DbMaker/SalutationsDbFactory.cs:23-41 — 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.
Duplicated block (19 lines × 2) src/Paramore.Brighter.Transformers.JustSaying/JustSayingCommand.cs:49— src/Paramore.Brighter.Transformers.JustSaying/JustSayingCommand.cs:49-67 | src/Paramore.Brighter.Transformers.JustSaying/JustSayingEvent.cs:50-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.
Duplicated block (19 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:234— src/Paramore.Brighter.ServiceActivator/Proactor.cs:234-252 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:195-213 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:234` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:120— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:120-138 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:156-174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:120` 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.
Duplicated block (19 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:69— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:69-87 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:76-94 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:309— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:309-327 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:289-307 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs` 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 5 separate duplicated blocks between them, totalling at least 136 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 (19 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:12— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:12-30 | src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:12-30 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 153 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:12` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:472— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:472-490 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:475-493 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (19 lines × 2) src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:204— src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:204-222 | src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs:222-240 — before extracting anything, compare `src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs` and `src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:370— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:370-388 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:432-450 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:370` 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.
Duplicated block (19 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:444— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:444-462 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:445-463 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:444` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) REDACTED:31— REDACTED:31-49 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:38-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. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:49— samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:49-67 | samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/TimedMessageGenerator.cs:49-67 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs` and `samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/TimedMessageGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs:49— samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs:49-67 | samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:49-67 — before extracting anything, compare `samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs` and `samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×12
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:174— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:174-196 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:169-188 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxDetectionHelper.cs:220-239 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxDetectionHelper.cs:152-176 — 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) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:68— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:68-74 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs:69-75 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:68-74 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactoryAsync.cs:69-75 — 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:351— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:351-397 | src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:400-450 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:352-398 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:401-451 — 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) src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:36— src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:36-52 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:86-110 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:164-180 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:215-239 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:95— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:95-150 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:206-260 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:95-150 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:206-260 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:165— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:165-229 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:143-201 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:165-229 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:143-201 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:121— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:121-151 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:138-169 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:121-151 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:140-171 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:372— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:372-392 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:401-422 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:407-427 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:388-408 — 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) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:509— src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:509-521 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:455-467 | REDACTED:548-560 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:603-615 — 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) src/Paramore.Brighter/TransformPipelineBuilder.cs:95— src/Paramore.Brighter/TransformPipelineBuilder.cs:95-134 | src/Paramore.Brighter/TransformPipelineBuilder.cs:143-182 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:95-134 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:143-182 — 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) samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:10— samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:10-22 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:10-22 | samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:10-22 | samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:10-22 — 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) samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs:42— samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs:42-93 | samples/TaskQueue/KafkaDontAckOnError/GreetingsReceiverConsole/Program.cs:42-91 | samples/TaskQueue/KafkaTaskQueueWithDLQ/DlqConsole/Program.cs:42-94 | samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsReceiverConsole/Program.cs:42-95 — 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 (16 corresponding lines) · ×12
Edited copy of a member (16 corresponding lines) src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:123— src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:123-138 | src/Paramore.Brighter.MessagingGateway.MsSql/SqlQueues/MsSqlMessageQueue.cs:148-164 — 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) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:92— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:92-113 | src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:127-142 — 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) src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:92— src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:92-107 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:218-233 — 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) REDACTED:586— REDACTED:586-601 | REDACTED:604-619 — 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) src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:110— src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:110-133 | src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:213-228 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:145— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:145-169 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:143-158 — 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) src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:112— src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:112-129 | src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:181-196 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:567— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:567-590 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:483-498 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:168— src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:168-183 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:151-166 — 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) REDACTED:88— REDACTED:88-103 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlInboxMigrationCatalog.cs:77-92 — 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) src/Paramore.Brighter.MessagingGateway.MsSql/ChannelFactory.cs:75— src/Paramore.Brighter.MessagingGateway.MsSql/ChannelFactory.cs:75-90 | src/Paramore.Brighter.MessagingGateway.MsSql/ChannelFactory.cs:100-117 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:83— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:83-98 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:83-98 — 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 (23 corresponding lines) · ×12
Edited copy of a member (23 corresponding lines) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:90— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:90-112 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:97-119 — 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:865— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:865-887 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:892-915 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/ExchangeConfigurationHelper.cs:57— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ExchangeConfigurationHelper.cs:57-84 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ExchangeConfigurationHelper.cs:53-75 — 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:287— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:287-310 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:729-751 — 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) src/Paramore.Brighter/PipelineBuilder.cs:520— src/Paramore.Brighter/PipelineBuilder.cs:520-542 | src/Paramore.Brighter/PipelineBuilder.cs:595-618 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:133— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:133-155 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:113-136 — 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) src/Paramore.Brighter/TransformPipelineBuilder.cs:255— src/Paramore.Brighter/TransformPipelineBuilder.cs:255-277 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:255-277 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:107— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:107-129 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:87-109 — 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) src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:196— src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:196-218 | src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs:330-352 — 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) src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:83— src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:83-105 | src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandlerAsync.cs:83-105 — 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:294— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:294-316 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:295-317 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:36— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:36-58 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqTlsConfigurator.cs:36-58 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×12
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:273— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:273-285 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:288-300 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderResult.cs:104— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderResult.cs:104-116 | src/Paramore.Brighter.MessagingGateway.AWSSQS/HeaderResult.cs:104-116 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:451— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:451-464 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:435-447 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter/UnwrapPipeline.cs:80— src/Paramore.Brighter/UnwrapPipeline.cs:80-93 | src/Paramore.Brighter/UnwrapPipelineAsync.cs:83-95 — 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) REDACTED:122— REDACTED:122-134 | REDACTED:134-149 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.Transformers.JustSaying/Extensions/RequestContextExtensions.cs:44— src/Paramore.Brighter.Transformers.JustSaying/Extensions/RequestContextExtensions.cs:44-56 | src/Paramore.Brighter.Transformers.MassTransit/Extensions/RequestContextExtensions.cs:33-45 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter/TransformPipelineBuilder.cs:227— src/Paramore.Brighter/TransformPipelineBuilder.cs:227-239 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:227-239 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs:136— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs:136-148 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ChannelFactory.cs:117-129 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlProvisioningUnitOfWork.cs:75— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlProvisioningUnitOfWork.cs:75-92 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteProvisioningUnitOfWork.cs:100-112 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:588— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:588-605 | src/Paramore.Brighter/InMemoryMessageProducer.cs:299-311 — 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) samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:38— samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:38-50 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:38-50 — 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) samples/Transforms/JustSaying/JustSayingSide/Program.cs:33— samples/Transforms/JustSaying/JustSayingSide/Program.cs:33-45 | samples/Transforms/MassTransit/MassTransitSide/Program.cs:66-78 — 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.
Duplicated block (21 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:99— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:99-119 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:140-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:603— src/Paramore.Brighter.ServiceActivator/Proactor.cs:603-623 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:593-613 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs: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.
Duplicated block (21 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:183— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:183-203 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:183-203 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (21 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:202— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:202-222 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:185-205 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` 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 6 separate duplicated blocks between them, totalling at least 111 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (21 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:72— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:72-92 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:66-86 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (21 lines × 2) src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProviderOptions.cs:25— src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProviderOptions.cs:25-45 | src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProviderOptions.cs:25-45 — `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProviderOptions.cs` and `src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProviderOptions.cs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProviderOptions.cs:25` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:327— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:327-347 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:328-348 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (21 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:514— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:514-534 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:517-537 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (21 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:331— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:331-351 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:500-520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:772— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:772-792 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:949-969 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:55— samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:55-75 | samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs:54-74 — before extracting anything, compare `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs` and `samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs` as WHOLE FILES: this scan already matched 4 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 `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs:22— samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs:22-42 | samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/Retry.cs:22-42 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/Retry.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:251— REDACTED:251-264 | REDACTED:273-286 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:251` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:99— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:99-112 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:106-119 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:99` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:115— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:115-128 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:165-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:530— src/Paramore.Brighter.ServiceActivator/Proactor.cs:530-543 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:524-537 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:530` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:170— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:170-183 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:172-185 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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 (14 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:199— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:199-212 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:233-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:199` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1464— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1464-1477 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1452-1465 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (14 lines × 2) src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:59— src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:59-72 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:103-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:137— src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:137-150 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:181-194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:137` 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.
Duplicated block (14 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:423— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:423-436 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:458-471 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (14 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs:66— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs:66-79 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ChannelFactory.cs:65-78 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ChannelFactory.cs` 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 14 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 (14 lines × 2) samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:145— samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:145-158 | samples/Tutorials/03-DurableOutbox/GreetingsSender/Program.cs:150-163 — 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 (6 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:458— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:458-463 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:441-446 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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. 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:65— REDACTED:65-70 | REDACTED:94-99 — both copies are in the same file, so extract the 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 `REDACTED:65` 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, `REDACTED:93` calls `Add` and `REDACTED:64` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:273— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:273-278 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:288-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:273` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:151— src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:151-159 | src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:246-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:151` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:500— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:500-505 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:216-221 — 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 (6 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:130— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:130-135 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:131-136 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (6 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:507— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:507-512 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:218-223 — 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 (6 lines × 2) src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:75— src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:75-80 | src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs:76-81 — before extracting anything, compare `src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs` and `src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs` as WHOLE FILES: this scan already matched 4 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:85— samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:85-90 | samples/WebAPI/WebAPI_EFCore/Greetings_Sweeper/Program.cs:41-46 — before extracting anything, compare `samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs` and `samples/WebAPI/WebAPI_EFCore/Greetings_Sweeper/Program.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/FarewellEventMessageMapper.cs:45— samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/FarewellEventMessageMapper.cs:45-50 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/Mappers/FarewellEventMessageMapper.cs:45-50 — before extracting anything, compare `samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/FarewellEventMessageMapper.cs` and `samples/TaskQueue/AWSTaskQueue/Greetings/Ports/Mappers/FarewellEventMessageMapper.cs` 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 (6 lines × 2) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:39— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:39-44 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:30-35 — before extracting anything, compare `samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs` and `samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:28— samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:28-33 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:28-33 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×11
Edited copy of a member (17 corresponding lines) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:67— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:67-103 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:67-83 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:330— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:330-347 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:363-379 — 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) src/Paramore.Brighter.ServiceActivator/Validation/ConsumerValidationRules.cs:237— src/Paramore.Brighter.ServiceActivator/Validation/ConsumerValidationRules.cs:237-255 | src/Paramore.Brighter.ServiceActivator/Validation/ConsumerValidationRules.cs:270-286 — 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) src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:136— src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:136-152 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:262-278 — 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) REDACTED:105— REDACTED:105-123 | REDACTED:372-388 — 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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:46— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:46-62 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:71-87 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:149— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:149-166 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:152-168 — 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) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:260— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:260-276 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs:280-311 — 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) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:350— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:350-366 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:385-402 — 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) src/Paramore.Brighter/InMemoryMessageProducer.cs:323— src/Paramore.Brighter/InMemoryMessageProducer.cs:323-340 | src/Paramore.Brighter/InMemoryMessageProducer.cs:353-369 — 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) src/Paramore.Brighter/Policies/Handlers/FallbackPolicyHandler.cs:46— src/Paramore.Brighter/Policies/Handlers/FallbackPolicyHandler.cs:46-62 | src/Paramore.Brighter/Policies/Handlers/FallbackPolicyHandlerRequestHandlerAsync.cs:46-62 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×11
Edited copy of a member (12 corresponding lines) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusChannel.cs:34— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusChannel.cs:34-45 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusChannelAsync.cs:35-48 — 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) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionMessageMapperRegistryBuilder.cs:79— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionMessageMapperRegistryBuilder.cs:79-90 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionMessageMapperRegistryBuilder.cs:98-109 — 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) REDACTED:384— REDACTED:384-397 | REDACTED:236-247 — 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) REDACTED:384— REDACTED:384-397 | REDACTED:326-337 — 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) REDACTED:42— REDACTED:42-53 | REDACTED:56-68 — 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) src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandlerAsync.cs:93— src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandlerAsync.cs:93-104 | src/Paramore.Brighter/Policies/Handlers/ResilienceExceptionPolicyHandlerAsync.cs:122-133 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:541— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:541-552 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:548-559 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:567— src/Paramore.Brighter.ServiceActivator/Proactor.cs:567-578 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:558-569 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:68— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:68-79 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:68-79 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:427— src/Paramore.Brighter/RelationalDatabaseInbox.cs:427-438 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1365-1376 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:180— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:180-191 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:187-198 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×11
Edited copy of a member (10 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1211— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1211-1220 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1199-1208 — 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) src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:65— src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandler.cs:65-75 | src/Paramore.Brighter/Policies/Handlers/ExceptionPolicyHandlerAsync.cs:65-74 — 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) src/Paramore.Brighter.Inbox.DynamoDB.V4/CommandItem.cs:41— src/Paramore.Brighter.Inbox.DynamoDB.V4/CommandItem.cs:41-50 | src/Paramore.Brighter.Inbox.DynamoDB/CommandItem.cs:36-45 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:439— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:439-448 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:425-435 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:451— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:451-460 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:438-448 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:520— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:520-529 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:527-536 — 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) src/Paramore.Brighter.Outbox.MySql/MySqlOutbox.cs:84— src/Paramore.Brighter.Outbox.MySql/MySqlOutbox.cs:84-93 | src/Paramore.Brighter.Outbox.Sqlite/SqliteOutbox.cs:92-101 — 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) src/Paramore.Brighter/DontAck/Handlers/DontAckOnErrorHandler.cs:55— src/Paramore.Brighter/DontAck/Handlers/DontAckOnErrorHandler.cs:55-64 | src/Paramore.Brighter/DontAck/Handlers/DontAckOnErrorHandlerAsync.cs: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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:286— src/Paramore.Brighter/RelationalDatabaseInbox.cs:286-296 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1189-1198 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:72— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:72-81 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:72-81 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:166— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:166-175 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:148-157 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:720— src/Paramore.Brighter.ServiceActivator/Proactor.cs:720-724 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:715-719 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:351— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:351-355 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:383-387 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. 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) REDACTED:58— REDACTED:58-62 | REDACTED:86-90 — both copies are in the same file, so extract the 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, `REDACTED:93` calls `Add` and `REDACTED:65` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) REDACTED:109— REDACTED:109-113 | REDACTED:137-141 — both copies are in the same file, so extract the 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, `REDACTED:144` calls `Add` and `REDACTED:116` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72— src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72-76 | src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:83-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Spanner/SpannerOutbox.cs:72` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:129— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:129-133 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:133-137 — 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 (5 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByName.cs:78— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByName.cs:78-82 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByName.cs:78-82 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByName.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByName.cs` 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 5 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. 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:361— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:361-365 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:350-354 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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 (5 lines × 2) src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandler.cs:47— src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandler.cs:47-51 | src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandlerAsync.cs:49-53 — before extracting anything, compare `src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandler.cs` and `src/Paramore.Brighter/FeatureSwitch/Handlers/FeatureSwitchHandlerAsync.cs` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) samples/WebAPI/WebAPI_Dynamo/SalutationApp/Policies/SalutationPolicy.cs:12— samples/WebAPI/WebAPI_Dynamo/SalutationApp/Policies/SalutationPolicy.cs:12-16 | samples/WebAPI/WebAPI_EFCore/SalutationApp/Policies/SalutationPolicy.cs:12-16 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/SalutationApp/Policies/SalutationPolicy.cs` and `samples/WebAPI/WebAPI_EFCore/SalutationApp/Policies/SalutationPolicy.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) samples/AsyncAPI/KafkaAsyncAPI/Program.cs:118— samples/AsyncAPI/KafkaAsyncAPI/Program.cs:118-122 | samples/AsyncAPI/RMQAsyncAPI/Program.cs:107-111 — 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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×10
Edited copy of a member (20 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:364— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:364-386 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:355-374 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:142— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:142-161 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:142-167 — 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) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:340— src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:340-359 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:369-388 — 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) src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:146— src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:146-165 | src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:275-294 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:487— src/Paramore.Brighter.ServiceActivator/Proactor.cs:487-507 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:501-520 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:120— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:120-139 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:120-139 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:49— src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:49-68 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:49-71 — 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) src/Paramore.Brighter/OutboxProducerMediator.cs:645— src/Paramore.Brighter/OutboxProducerMediator.cs:645-664 | src/Paramore.Brighter/OutboxProducerMediator.cs:676-698 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:179— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:179-198 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:179-198 — 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) samples/TaskQueue/ASBTaskQueue/Greetings/Adaptors/Data/AzureAdAuthenticationDbConnectionInterceptor.cs:63— samples/TaskQueue/ASBTaskQueue/Greetings/Adaptors/Data/AzureAdAuthenticationDbConnectionInterceptor.cs:63-82 | samples/TaskQueue/ASBTaskQueue/Greetings/Adaptors/Data/AzureAdAuthenticationDbConnectionInterceptor.cs:85-104 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×10
Edited copy of a member (4 corresponding lines) src/Paramore.Brighter.ServiceActivator/Dispatcher.cs:263— src/Paramore.Brighter.ServiceActivator/Dispatcher.cs:263-266 | src/Paramore.Brighter/OutboxProducerMediator.cs:256-259 — 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) src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:62— src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:62-65 | src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandlerAsync.cs:62-65 — 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) src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:87— src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandler.cs:87-90 | src/Paramore.Brighter/Logging/Handlers/RequestLoggingHandlerAsync.cs:88-91 — 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) src/Paramore.Brighter/UnwrapPipeline.cs:67— src/Paramore.Brighter/UnwrapPipeline.cs:67-70 | src/Paramore.Brighter/UnwrapPipelineAsync.cs:69-72 — 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) src/Paramore.Brighter/WrapPipeline.cs:77— src/Paramore.Brighter/WrapPipeline.cs:77-80 | src/Paramore.Brighter/WrapPipelineAsync.cs:81-84 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:34— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:34-37 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:41-44 — 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) src/Paramore.Brighter/TransformLifetimeScope.cs:36— src/Paramore.Brighter/TransformLifetimeScope.cs:36-39 | src/Paramore.Brighter/TransformLifetimeScopeAsync.cs:52-55 — 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) src/Paramore.Brighter/TransformPipelineBuilder.cs:287— src/Paramore.Brighter/TransformPipelineBuilder.cs:287-290 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:287-290 — 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:354— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:354-357 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:341-344 — 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) samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:34— samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:34-37 | samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:34-37 — 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 (24 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:480— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:480-503 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:929-952 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:480` it does not close everything it opens, so those 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 `requestContext` to `RequestContext` in one and `RequestContext?` 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 (24 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:341— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:341-364 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1057-1080 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:341` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:252— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:252-275 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:252-275 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:252` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs:57— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs:57-80 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducerFactory.cs:57-80 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducerFactory.cs` 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 2 separate duplicated blocks between them, totalling at least 48 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 (24 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs:89— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs:89-112 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducerFactory.cs:89-112 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducerFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducerFactory.cs` 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 2 separate duplicated blocks between them, totalling at least 48 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 (24 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:396— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:396-419 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:431-454 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (24 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs:68— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs:68-91 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArn.cs:68-91 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArn.cs` 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 24 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 (24 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:635— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:635-658 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:622-645 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (24 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:185— src/Paramore.Brighter.ServiceActivator/Proactor.cs:185-208 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:146-169 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:185` 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 (24 lines × 2) src/Paramore.Brighter/RelationDatabaseOutbox.cs:818— src/Paramore.Brighter/RelationDatabaseOutbox.cs:818-841 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:858-881 — both copies are in the same file, so extract the 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 (17 lines × 2) REDACTED:138— REDACTED:138-154 | REDACTED:404-420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91-107 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:197-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:130— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:130-146 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:232-248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:130` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:145— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:145-161 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs:145-161 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 111 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 (17 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:49— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:49-65 | src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs:49-65 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs` 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 2 separate duplicated blocks between them, totalling at least 66 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 (17 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:159— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:159-175 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:159-175 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (17 lines × 2) src/Paramore.Brighter/PipelineBuilder.cs:214— src/Paramore.Brighter/PipelineBuilder.cs:214-230 | src/Paramore.Brighter/PipelineBuilder.cs:275-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/PipelineBuilder.cs:214` 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) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:51— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:51-67 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:160-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:51` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs:80— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs:80-96 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArnConvention.cs:80-96 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArnConvention.cs` 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 17 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 (17 lines × 2) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:87— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:87-103 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:74-90 — before extracting anything, compare `samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs` and `samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs` 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.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×10
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusAzureCliCredentialClientProvider.cs:19— The guard on line 17 rejects `fullyQualifiedNameSpace` and line 19 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusChainedClientProvider.cs:21— The guard on line 19 rejects `fullyQualifiedNameSpace` and line 21 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusChainedClientProvider.cs:26— The guard on line 24 rejects `credentialSources` and line 26 reports that rejection as `ArgumentNullException` — but the condition's own test `credentialSources.Length < 1` is true of a value that is NOT null: it is satisfied by an EMPTY `credentialSources`, and on that path `credentialSources` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusConnectionStringClientProvider.cs:22— The guard on line 20 rejects `connectionString` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(connectionString)` is true of a value that is NOT null: it is satisfied by an EMPTY `connectionString`, and on that path `connectionString` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusDefaultAzureClientProvider.cs:22— The guard on line 20 rejects `fullyQualifiedNameSpace` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusManagedIdentityClientProvider.cs:22— The guard on line 20 rejects `fullyQualifiedNameSpace` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MessagingGateway.AzureServiceBus/ClientProvider/ServiceBusVisualStudioCredentialClientProvider.cs:22— The guard on line 20 rejects `fullyQualifiedNameSpace` and line 22 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(fullyQualifiedNameSpace)` is true of a value that is NOT null: it is satisfied by an EMPTY `fullyQualifiedNameSpace`, and on that path `fullyQualifiedNameSpace` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.MsSql.Azure/MsSqlChainedConnectionProvider.cs:46— The guard on line 44 rejects `credentialSources` and line 46 reports that rejection as `ArgumentNullException` — but the condition's own test `credentialSources.Length < 1` is true of a value that is NOT null: it is satisfied by an EMPTY `credentialSources`, and on that path `credentialSources` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:84— The guard on line 82 rejects `value` and line 84 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
Argument guard throws the exception its own condition disproves src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs:84— The guard on line 82 rejects `value` and line 84 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(value)` is true of a value that is NOT null: it is satisfied by an EMPTY `value`, and on that path `value` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows this case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` (or `ArgumentOutOfRangeException` for a bound) for what the condition actually tests, or split the guard and throw each on its own condition.
FileTooLong: Paramore.Brighter/RelationDatabaseOutbox.cs src/Paramore.Brighter/RelationDatabaseOutbox.cs— FileTooLong — 1181 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 681 over it, 2.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Paramore.Brighter/CommandProcessor.cs src/Paramore.Brighter/CommandProcessor.cs— FileTooLong — 804 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 304 over it, 1.61× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 293 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs— FileTooLong — 792 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 292 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Paramore.Brighter/OutboxProducerMediator.cs src/Paramore.Brighter/OutboxProducerMediator.cs— FileTooLong — 783 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 283 over it, 1.57× 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: Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs— FileTooLong — 780 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 280 over it, 1.56× 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: Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs— FileTooLong — 651 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 151 over it, 1.30× 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: Observability/BrighterTracer.cs src/Paramore.Brighter/Observability/BrighterTracer.cs— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 99 over it, 1.20× 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.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×9
Edited copy of a member (25 corresponding lines) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:605— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:605-651 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs:661-685 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:678— src/Paramore.Brighter/RelationDatabaseOutbox.cs:678-702 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:719-744 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:281— src/Paramore.Brighter/RelationDatabaseOutbox.cs:281-305 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:319-346 — 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) src/Paramore.Brighter/TransformerFactory.cs:40— src/Paramore.Brighter/TransformerFactory.cs:40-64 | src/Paramore.Brighter/TransformerFactoryAsync.cs:38-64 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:564— src/Paramore.Brighter/RelationDatabaseOutbox.cs:564-588 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:605-630 — 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) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs:17— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs:17-41 | src/Paramore.Brighter.DynamoDb/DynamoDbTableQuery.cs:17-41 — 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) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverProvider.cs:49— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverProvider.cs:49-73 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusReceiverProvider.cs:84-108 — 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) src/Paramore.Brighter.Locking.MsSql/MsSqlLockingProvider.cs:94— src/Paramore.Brighter.Locking.MsSql/MsSqlLockingProvider.cs:94-118 | src/Paramore.Brighter.Locking.MySql/MySqlLockingProvider.cs:74-99 — 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) REDACTED:31— REDACTED:31-55 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:38-62 — 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 (7 corresponding lines) · ×9
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter.ServiceActivator/Proactor.cs:520— src/Paramore.Brighter.ServiceActivator/Proactor.cs:520-526 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:453-459 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:74— src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:74-80 | src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs:75-81 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:129— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:129-135 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:130-136 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:186— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:186-192 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:188-194 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ISqsMessageCreator.cs:34— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ISqsMessageCreator.cs:34-40 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ISqsMessageCreator.cs:34-40 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter/UnwrapPipeline.cs:53— src/Paramore.Brighter/UnwrapPipeline.cs:53-59 | src/Paramore.Brighter/WrapPipeline.cs:62-69 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter/UnwrapPipelineAsync.cs:55— src/Paramore.Brighter/UnwrapPipelineAsync.cs:55-61 | src/Paramore.Brighter/WrapPipelineAsync.cs:66-73 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs:52— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArnConvention.cs:52-58 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArnConvention.cs:52-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) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:38— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:38-44 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:29-35 — 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 (22 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs:20— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs:20-41 | src/Paramore.Brighter.DynamoDb/DynamoDbTableQuery.cs:20-41 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableQuery.cs` 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 22 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableQuery.cs:20` 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 (22 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:203— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:203-224 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:203-224 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (22 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:577— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:577-598 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:580-601 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (22 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumerFactory.cs:66— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumerFactory.cs:66-87 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumerFactory.cs:91-112 — both copies are in the same file, so extract the 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 (22 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:185— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:185-206 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:645-666 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:185` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:227— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:227-248 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:227-248 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (22 lines × 2) src/Paramore.Brighter/Policies/Handlers/ResilienceExceptionPolicyHandler.cs:66— src/Paramore.Brighter/Policies/Handlers/ResilienceExceptionPolicyHandler.cs:66-87 | src/Paramore.Brighter/Policies/Handlers/ResilienceExceptionPolicyHandlerAsync.cs:69-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:93— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:93-114 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:97-118 — 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 (22 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:107— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:107-128 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:107-128 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 87 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 (23 lines × 2) src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:208— src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:208-230 | src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:200-222 — `src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs` and `src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 68 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 (23 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:464— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:464-486 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:209-231 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (23 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:538— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:538-560 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:541-563 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (23 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs:34— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs:34-56 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducerFactory.cs:34-56 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducerFactory.cs` 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 2 separate duplicated blocks between them, totalling at least 46 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 (23 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs:65— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs:65-87 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducerFactory.cs:65-87 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducerFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducerFactory.cs` 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 2 separate duplicated blocks between them, totalling at least 46 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 (23 lines × 2) REDACTED:212— REDACTED:212-234 | REDACTED:278-300 — both copies are in the same file, so extract the 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 `REDACTED:212` 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 (23 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/Scheduler.cs:9— src/Paramore.Brighter.MessageScheduler.AWS.V4/Scheduler.cs:9-31 | src/Paramore.Brighter.MessageScheduler.AWS/Scheduler.cs:9-31 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/Scheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/Scheduler.cs` 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 23 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessageScheduler.AWS.V4/Scheduler.cs:9` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) samples/TaskQueue/KafkaSchemaRegistry/GreetingsSender/Program.cs:82— samples/TaskQueue/KafkaSchemaRegistry/GreetingsSender/Program.cs:82-104 | samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/Program.cs:56-78 — 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 (23 lines × 2) samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:88— samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:88-110 | samples/Tutorials/03-DurableOutbox/GreetingsSender/Program.cs:87-114 — 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 `samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/Program.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
P12 · CI test-gate honesty· Test project never run by CI · ×9
Test project never run by CI REDACTED:1— `REDACTED` declares 8 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.AsyncAPI.Tests/Paramore.Brighter.AsyncAPI.Tests.csproj:1— `tests/Paramore.Brighter.AsyncAPI.Tests/Paramore.Brighter.AsyncAPI.Tests.csproj` declares 46 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Azure.Tests/Paramore.Brighter.Azure.Tests.csproj:1— `tests/Paramore.Brighter.Azure.Tests/Paramore.Brighter.Azure.Tests.csproj` declares 25 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.BoxProvisioning.Tests/Paramore.Brighter.BoxProvisioning.Tests.csproj:1— `tests/Paramore.Brighter.BoxProvisioning.Tests/Paramore.Brighter.BoxProvisioning.Tests.csproj` declares 108 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Extensions.AspNetCore.Tests/Paramore.Brighter.Extensions.AspNetCore.Tests.csproj:1— `tests/Paramore.Brighter.Extensions.AspNetCore.Tests/Paramore.Brighter.Extensions.AspNetCore.Tests.csproj` declares 81 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Testing.Tests/Paramore.Brighter.Testing.Tests.csproj:1— `tests/Paramore.Brighter.Testing.Tests/Paramore.Brighter.Testing.Tests.csproj` declares 85 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Validation.DataAnnotations.Tests/Paramore.Brighter.Validation.DataAnnotations.Tests.csproj:1— `tests/Paramore.Brighter.Validation.DataAnnotations.Tests/Paramore.Brighter.Validation.DataAnnotations.Tests.csproj` declares 10 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Validation.FluentValidation.Tests/Paramore.Brighter.Validation.FluentValidation.Tests.csproj:1— `tests/Paramore.Brighter.Validation.FluentValidation.Tests/Paramore.Brighter.Validation.FluentValidation.Tests.csproj` declares 12 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Paramore.Brighter.Validation.Specification.Tests/Paramore.Brighter.Validation.Specification.Tests.csproj:1— `tests/Paramore.Brighter.Validation.Specification.Tests/Paramore.Brighter.Validation.Specification.Tests.csproj` declares 10 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×8
Edited copy of a member (28 corresponding lines) src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:138— src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:138-171 | src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:204-231 — 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) src/Paramore.Brighter/Observability/BrighterTracer.cs:358— src/Paramore.Brighter/Observability/BrighterTracer.cs:358-385 | src/Paramore.Brighter/Observability/BrighterTracer.cs:521-549 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1022— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1022-1049 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1053-1081 — 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) src/Paramore.Brighter/Observability/BrighterTracer.cs:434— src/Paramore.Brighter/Observability/BrighterTracer.cs:434-475 | src/Paramore.Brighter/Observability/BrighterTracer.cs:479-506 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:446— src/Paramore.Brighter/RelationalDatabaseInbox.cs:446-473 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1383-1410 — 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) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1287— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1287-1314 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1322-1357 — 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) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1003— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1003-1030 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:991-1018 — 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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubChannelFactory.cs:99— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubChannelFactory.cs:99-126 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubChannelFactory.cs:168-196 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×8
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter/Observability/BrighterTracer.cs:620— src/Paramore.Brighter/Observability/BrighterTracer.cs:620-649 | src/Paramore.Brighter/Observability/BrighterTracer.cs:667-699 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:321— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:321-350 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:366-396 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:58— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:58-87 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:65-94 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:402— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:402-431 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:439-468 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter/CommandProcessor.cs:870— src/Paramore.Brighter/CommandProcessor.cs:870-899 | src/Paramore.Brighter/CommandProcessor.cs:1112-1142 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter/OutboxProducerMediator.cs:1328— src/Paramore.Brighter/OutboxProducerMediator.cs:1328-1357 | src/Paramore.Brighter/OutboxProducerMediator.cs:1389-1420 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:697— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:697-732 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:595-624 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:319— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:319-348 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:320-349 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×8
Edited copy of a member (24 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:133— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:133-156 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:131-154 — 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) src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:21— src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:21-44 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresMessageProducerFactory.cs:52-78 — 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) src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:156— src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:156-180 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:282-305 — 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) src/Paramore.Brighter/RelationalDatabaseInbox.cs:576— src/Paramore.Brighter/RelationalDatabaseInbox.cs:576-599 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:603-633 — 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) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:189— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:189-212 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubStreamMessageConsumer.cs:223-246 — 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) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:540— src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:540-563 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:566-589 — 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) src/Paramore.Brighter/Observability/BrighterTracer.cs:958— src/Paramore.Brighter/Observability/BrighterTracer.cs:958-981 | src/Paramore.Brighter/Observability/BrighterTracer.cs:1002-1030 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:73— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:73-96 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:70-95 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×8
Edited copy of a member (15 corresponding lines) src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:151— src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:151-173 | src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs:246-260 — 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) src/Paramore.Brighter/Transforms/Storage/InMemoryStorageProvider.cs:99— src/Paramore.Brighter/Transforms/Storage/InMemoryStorageProvider.cs:99-117 | src/Paramore.Brighter/Transforms/Storage/InMemoryStorageProvider.cs:186-200 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) REDACTED:501— REDACTED:501-515 | REDACTED:518-532 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:165— src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:165-180 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:224-238 — 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) src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProvider.cs:19— src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProvider.cs:19-34 | src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProvider.cs:42-56 — 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) src/Paramore.Brighter/InMemoryInbox.cs:284— src/Paramore.Brighter/InMemoryInbox.cs:284-298 | src/Paramore.Brighter/InMemoryInbox.cs:312-326 — 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) src/Paramore.Brighter/InMemoryInbox.cs:192— src/Paramore.Brighter/InMemoryInbox.cs:192-206 | src/Paramore.Brighter/InMemoryOutbox.cs:231-249 — 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) src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:75— src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerInboxProvisioner.cs:75-89 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerOutboxProvisioner.cs:79-93 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×8
Edited copy of a member (5 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:663— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:663-674 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:569-573 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:167— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:167-171 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:167-171 — 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:85— src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:85-89 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:75-79 — 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) src/Paramore.Brighter.ServiceActivator/Proactor.cs:103— src/Paramore.Brighter.ServiceActivator/Proactor.cs:103-107 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:413-417 — 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) src/Paramore.Brighter.MsSql/MsSqlConnectionProvider.cs:45— src/Paramore.Brighter.MsSql/MsSqlConnectionProvider.cs:45-49 | src/Paramore.Brighter.PostgreSql/PostgreSqlConnectionProvider.cs:69-73 — 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) src/Paramore.Brighter.MySql/MySqlConnectionProvider.cs:71— src/Paramore.Brighter.MySql/MySqlConnectionProvider.cs:71-75 | src/Paramore.Brighter.Sqlite/SqliteConnectionProvider.cs:71-76 — 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) src/Paramore.Brighter.MySql/MySqlConnectionProvider.cs:59— src/Paramore.Brighter.MySql/MySqlConnectionProvider.cs:59-63 | src/Paramore.Brighter.Sqlite/SqliteConnectionProvider.cs:58-63 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) samples/Validation/DataAnnotationsSample/RegisterUserHandler.cs:38— samples/Validation/DataAnnotationsSample/RegisterUserHandler.cs:38-42 | samples/Validation/FluentValidationSample/GreetingCommandHandler.cs:38-42 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:347— The branch `if (transactionType == null)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:428— The branch `if (ServiceBusReceiver is not IAmAServiceBusRetryReceiver receiver)` throws `ChannelFailureException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs:66— The branch `if (requeueScheduler is not IAmAMessageRequeueSchedulerSync && requeueScheduler is not IAmAMessageRequeueSchedulerAsync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumerFactory.cs:83— The branch `if (async ? _scheduler is not IAmAMessageRequeueSchedulerAsync : _scheduler is not IAmAMessageRequeueSchedulerSync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws NotImplementedException src/Paramore.Brighter/InMemoryMessageProducer.cs:205— The branch `if (batch is not MessageBatch messageBatch)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter/OutboxProducerMediator.cs:166— The branch `if (mapperRegistry is null)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter/OutboxProducerMediator.cs:169— The branch `if (mapperRegistry is not IAmAMessageMapperRegistryAsync mapperRegistryAsync)` throws `ConfigurationException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
Unfinished branch — throws a "not implemented" exception src/Paramore.Brighter/RelationDatabaseOutbox.cs:1102— The branch `if (queries is not IRelationalDatabaseOutboxTopicCountQueries topicCountQueries)` throws `NotSupportedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
X18 · Disposal-pattern correctness· Disposes a dependency it does not own · ×8
Disposes a dependency it does not own src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:154— `client` is never created by `GcpMessageProducer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 154). Its declared type `PublisherClient` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:163— `client` is never created by `GcpMessageProducer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 163). Its declared type `PublisherClient` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter.ServiceActivator/Performer.cs:103— `_channel` is never created by `Performer` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 103). Its declared type `IAmAChannel` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter/Channel.cs:226— `_messageConsumer` is never created by `Channel` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 226). Its declared type `IAmAMessageConsumerSync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter/ChannelAsync.cs:227— `_messageConsumer` is never created by `ChannelAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 227). Its declared type `IAmAMessageConsumerAsync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter/ChannelAsync.cs:252— `_messageConsumer` is never created by `ChannelAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 252). Its declared type `IAmAMessageConsumerAsync` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter/HandlerLifetimeScope.cs:125— `_pipelineScope` is never created by `HandlerLifetimeScope` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 125). Its declared type `IAmAScope` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Paramore.Brighter/TransformPipelineAsync.cs:91— `_pipelineScope` is never created by `TransformPipelineAsync` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 91). Its declared type `IAmAScope` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
X18 · Disposal-pattern correctness· Finalizer on a type that owns no unmanaged resource · ×8
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:293— `KafkaMessageConsumer` declares a finalizer (line 293), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:805— `RmqMessageConsumer` declares a finalizer (line 805), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:202— `RmqMessageGateway` declares a finalizer (line 202), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:664— `RmqMessageConsumer` declares a finalizer (line 664), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:188— `RmqMessageGateway` declares a finalizer (line 188), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter.ServiceActivator/Performer.cs:93— `Performer` declares a finalizer (line 93), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter/Channel.cs:230— `Channel` declares a finalizer (line 230), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Paramore.Brighter/ChannelAsync.cs:256— `ChannelAsync` declares a finalizer (line 256), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×7
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/ConnectionPolicyFactory.cs:53— src/Paramore.Brighter.MessagingGateway.RMQ.Async/ConnectionPolicyFactory.cs:53-84 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/ConnectionPoolFactory.cs:53-87 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter/Observability/BrighterTracer.cs:111— src/Paramore.Brighter/Observability/BrighterTracer.cs:111-142 | src/Paramore.Brighter/Observability/BrighterTracer.cs:399-430 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:246— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:246-281 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:248-279 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:90— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:90-124 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:196-227 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter/TransformPipelineBuilder.cs:191— src/Paramore.Brighter/TransformPipelineBuilder.cs:191-222 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:191-222 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter/Tasks/BrighterAsyncContext.cs:238— src/Paramore.Brighter/Tasks/BrighterAsyncContext.cs:238-271 | src/Paramore.Brighter/Tasks/BrighterAsyncContext.cs:278-309 — 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.
Edited copy of a member (32 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:209— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:209-250 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:186-217 — 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 (6 corresponding lines) · ×7
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter/Monitoring/Mappers/MonitorEventMessageMapper.cs:30— src/Paramore.Brighter/Monitoring/Mappers/MonitorEventMessageMapper.cs:30-35 | samples/TaskQueue/RMQTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:38-43 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:223— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:223-228 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:189-194 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:158— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:158-163 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:139-144 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:532— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:532-537 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:539-544 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter.MySql/MySqlTransactionProvider.cs:108— src/Paramore.Brighter.MySql/MySqlTransactionProvider.cs:108-113 | src/Paramore.Brighter.PostgreSql/PostgreSqlTransactionProvider.cs:107-112 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:360— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:360-365 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:349-354 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:23— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:23-29 | samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/GreetingMadeMessageMapperAsync.cs:21-26 — 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 (20 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:830— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:830-849 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:683-702 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:121— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:121-140 | src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:128-147 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:121` 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 (20 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:71— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:71-90 | src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:71-90 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 153 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 (20 lines × 2) src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:87— src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:87-106 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:216-235 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:58— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs:58-77 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSNameExtensions.cs:58-77 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSNameExtensions.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSNameExtensions.cs` 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 2 separate duplicated blocks between them, totalling at least 27 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 (20 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:157— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:157-176 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:157-176 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (20 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:295— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:295-314 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:328-347 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×6
Edited copy of a member (34 corresponding lines) REDACTED:332— REDACTED:332-365 | REDACTED:444-478 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) src/Paramore.Brighter/CommandProcessor.cs:943— src/Paramore.Brighter/CommandProcessor.cs:943-979 | src/Paramore.Brighter/CommandProcessor.cs:1193-1226 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:251— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:251-284 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:251-290 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) src/Paramore.Brighter/RelationalDatabaseInbox.cs:78— src/Paramore.Brighter/RelationalDatabaseInbox.cs:78-111 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:177-211 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:142— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:142-178 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:135-168 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:909— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:909-942 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:897-930 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (30 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:38— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:38-67 | src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:38-67 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 153 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (30 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:99— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:99-128 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:99-128 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 143 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 (30 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:106— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:106-135 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:108-137 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs` 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 6 separate duplicated blocks between them, totalling at least 106 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 (30 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:380— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:380-409 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:367-396 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (30 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:63— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:63-92 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqTlsConfigurator.cs:63-92 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqTlsConfigurator.cs` 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 30 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (30 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1330— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1330-1359 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1318-1347 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1330` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D10 · Test Quality· Fixed-sleep synchronisation · ×5
Fixed-sleep synchronisation: When_the_outstanding_count_yields_inside_the_pump_should_not_deadlock tests/Paramore.Brighter.Core.Tests/CommandProcessors/Post/When_the_outstanding_limit_is_exceeded_with_an_async_only_outbox_should_throw.cs:52— This test starts a background task and then orders itself against it with `Task.Delay(50)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: When_more_callbacks_are_queued_than_the_batch_size_should_run_a_batch_at_once tests/Paramore.Brighter.Core.Tests/Tasks/When_more_callbacks_are_queued_than_the_batch_size_should_run_a_batch_at_once.cs:15— This test starts a thread through `BatchedCallbackQueue.Enqueue` and then orders itself against it with `Thread.Sleep(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: When_a_gcp_stream_channel_is_disposed_with_a_redelivery_buffered_after_requeue_should_return_promptly tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Stream/When_a_gcp_stream_channel_is_disposed_with_a_redelivery_buffered_after_requeue_should_return_promptly.cs:46— This test starts a background task and then orders itself against it with `Thread.Sleep(TimeSpan.FromSeconds(2))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: When_a_message_is_acknowledged_update_offset tests/Paramore.Brighter.Kafka.Tests/MessagingGateway/Proactor/When_a_message_is_acknowledged_update_offset_async.cs:44— This test starts a background task and then orders itself against it with `Task.Delay(500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: When_committing_offsets_during_revoke_should_not_race_with_background_commit tests/Paramore.Brighter.Kafka.Tests/MessagingGateway/Reactor/When_committing_offsets_during_revoke_should_not_race.cs:58— This test starts a background task and then orders itself against it with `Task.Delay(500)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Hotspot: src/Paramore.Brighter.ServiceActivator/Proactor.cs src/Paramore.Brighter.ServiceActivator/Proactor.cs:134— src/Paramore.Brighter.ServiceActivator/Proactor.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in Proactor.EventLoop at line 134. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.ServiceActivator/Proactor.cs`: 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: src/Paramore.Brighter.ServiceActivator/Reactor.cs src/Paramore.Brighter.ServiceActivator/Reactor.cs:95— src/Paramore.Brighter.ServiceActivator/Reactor.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in Reactor.Run at line 95. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.ServiceActivator/Reactor.cs`: 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: src/Paramore.Brighter/OutboxProducerMediator.cs src/Paramore.Brighter/OutboxProducerMediator.cs:1152— src/Paramore.Brighter/OutboxProducerMediator.cs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in OutboxProducerMediator.BulkDispatchAsync at line 1152. 8 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter/OutboxProducerMediator.cs`: 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: src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:312— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ServiceCollectionExtensions.AddProducers at line 312. 6 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs`: 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: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs:96— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in AzureServiceBusConsumerFactory.CreateConsumer at line 96. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:13:09 +00:00' --until='2026-11-16 10:13:09 +00:00' --full-history --no-merges -- src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs`: 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.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×5
Edited copy of a member (31 corresponding lines) src/Paramore.Brighter/WrapPipeline.cs:91— src/Paramore.Brighter/WrapPipeline.cs:91-121 | src/Paramore.Brighter/WrapPipelineAsync.cs:96-128 — 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.
Edited copy of a member (31 corresponding lines) src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:97— src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:97-136 | src/Paramore.Brighter/Transforms/Transformers/CompressPayloadTransformer.cs:183-213 — 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.
Edited copy of a member (31 corresponding lines) src/Paramore.Brighter/CommandProcessor.cs:308— src/Paramore.Brighter/CommandProcessor.cs:308-338 | src/Paramore.Brighter/CommandProcessor.cs:390-421 — 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.
Edited copy of a member (31 corresponding lines) src/Paramore.Brighter/RelationDatabaseOutbox.cs:186— src/Paramore.Brighter/RelationDatabaseOutbox.cs:186-225 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:242-272 — 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.
Edited copy of a member (31 corresponding lines) REDACTED:356— REDACTED:356-386 | REDACTED:391-421 — 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.
Duplicated block (26 lines × 2) src/Paramore.Brighter/TransformPipelineBuilder.cs:109— src/Paramore.Brighter/TransformPipelineBuilder.cs:109-134 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:109-134 — before extracting anything, compare `src/Paramore.Brighter/TransformPipelineBuilder.cs` and `src/Paramore.Brighter/TransformPipelineBuilderAsync.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/TransformPipelineBuilder.cs:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/Paramore.Brighter/TransformPipelineBuilder.cs:157— src/Paramore.Brighter/TransformPipelineBuilder.cs:157-182 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:157-182 — before extracting anything, compare `src/Paramore.Brighter/TransformPipelineBuilder.cs` and `src/Paramore.Brighter/TransformPipelineBuilderAsync.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/TransformPipelineBuilder.cs:157` 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 (26 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:179— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:179-204 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:161-186 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs` 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 5 separate duplicated blocks between them, totalling at least 136 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 (26 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:249— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:249-274 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:281-306 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (26 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:192— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:192-217 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:595-620 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:192` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:178— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:178-189 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:173-184 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxDetectionHelper.cs:224-235 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxDetectionHelper.cs:156-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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, `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:191` calls `HasMessageIdIndexAsync` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:185` 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 × 4) src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:510— src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs:510-521 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:456-467 | REDACTED:549-560 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:604-615 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 4) REDACTED:87— REDACTED:87-98 | REDACTED:59-70 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlOutboxMigrationCatalog.cs:60-71 | REDACTED:73-84 — 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 (12 lines × 4) samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:11— samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:11-22 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:11-22 | samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:11-22 | samples/TaskQueue/RMQTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs:11-22 — before extracting anything, compare `samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs` and `samples/TaskQueue/PostgresTaskQueue/Greetings/Ports/CommandHandlers/FarewellEventHandler.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 4) samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs:15— samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs:15-42 | samples/WebAPI/WebAPI_Dynamo/SalutationApp/Policies/Retry.cs:13-24 | samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/Retry.cs:15-42 | samples/WebAPI/WebAPI_EFCore/SalutationApp/Policies/Retry.cs:14-25 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/Retry.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/Retry.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
ED2 · Event/command shape· Command with no handler · ×5
Command with no handler: FireSchedulerMessage src/Paramore.Brighter/Scheduler/Events/FireSchedulerMessage.cs:6— `FireSchedulerMessage` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch.
Command with no handler: FireSchedulerRequest src/Paramore.Brighter/Scheduler/Events/FireSchedulerRequest.cs:8— `FireSchedulerRequest` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch.
Command with no handler: AddGreeting samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/AddGreeting.cs:6— `AddGreeting` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch.
Command with no handler: DeletePerson samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/DeletePerson.cs:6— `DeletePerson` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch.
Command with no handler: AddPerson samples/WebAPI/WebAPI_Dapper/GreetingsApp/Requests/AddPerson.cs:6— `AddPerson` is a command dispatched in process, but no type in the repository handles it, so the dispatch fails at run time. A command should have exactly one handler that owns the decision: add it, or remove the dispatch.
X2 · Cancellation propagation· Async delegate without CancellationToken · ×5
Async delegate without CancellationToken: Get src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:184— Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
Async delegate without CancellationToken: Exists src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:267— Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
Async delegate without CancellationToken: GetCausationId src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:517— Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
Async delegate without CancellationToken: Schedule src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:513— Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
Async delegate without CancellationToken: Schedule src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:514— Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
Races the wall clock: When_scheduling_a_post_should_preserve_context_metadata tests/Paramore.Brighter.AWSScheduler.Tests/When_scheduling_a_post_should_preserve_context_metadata.cs:48— This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
Races the wall clock: When_scheduling_a_post_should_preserve_context_metadata tests/Paramore.Brighter.AWSScheduler.V4.Tests/When_scheduling_a_post_should_preserve_context_metadata.cs:48— This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
Races the wall clock: When_scheduling_a_request_should_preserve_its_context_data tests/Paramore.Brighter.Azure.Tests/Scheduler/When_scheduling_a_request_should_preserve_its_context_data.cs:39— This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
Races the wall clock: When_scheduling_a_post_should_preserve_context_metadata tests/Paramore.Brighter.TickerQ.Tests/When_scheduling_a_post_should_preserve_context_metadata.cs:49— This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
MethodTooLong: Reactor.Run src/Paramore.Brighter.ServiceActivator/Reactor.cs:95— MethodTooLong — Run runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× 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: Proactor.EventLoop src/Paramore.Brighter.ServiceActivator/Proactor.cs:134— MethodTooLong — EventLoop runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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: RocketMessageConsumer.CreateMessage src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:333— MethodTooLong — CreateMessage runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: KafkaMessageConsumer.KafkaMessageConsumer(…) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:121— MethodTooLong — KafkaMessageConsumer(…) 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.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×4
Edited copy of a member (40 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:74— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:74-115 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:74-113 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:52— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:52-91 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs:95-136 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) src/Paramore.Brighter/OutboxArchiver.cs:98— src/Paramore.Brighter/OutboxArchiver.cs:98-137 | src/Paramore.Brighter/OutboxArchiver.cs:148-190 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (40 corresponding lines) REDACTED:116— REDACTED:116-155 | REDACTED:166-207 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×4
Edited copy of a member (33 corresponding lines) src/Paramore.Brighter.ServiceActivator/Proactor.cs:529— src/Paramore.Brighter.ServiceActivator/Proactor.cs:529-564 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:523-555 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:114— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:114-146 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpRejectionRouter.cs:164-196 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) src/Paramore.Brighter/MessageMapperRegistry.cs:92— src/Paramore.Brighter/MessageMapperRegistry.cs:92-124 | src/Paramore.Brighter/MessageMapperRegistry.cs:133-165 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (33 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:509— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:509-542 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:424-456 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×4
Edited copy of a member (27 corresponding lines) src/Paramore.Brighter/CommandProcessor.cs:1030— src/Paramore.Brighter/CommandProcessor.cs:1030-1057 | src/Paramore.Brighter/CommandProcessor.cs:1279-1305 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:95— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:95-121 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:131-159 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:386— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:386-415 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:318-344 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) src/Paramore.Brighter/RelationDatabaseOutbox.cs:434— src/Paramore.Brighter/RelationDatabaseOutbox.cs:434-460 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:479-506 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×4
Edited copy of a member (22 corresponding lines) src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:111— src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:111-132 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:237-258 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:163— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:163-214 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGatewayConnectionPool.cs:122-143 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:68— src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:68-89 | src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs:193-214 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) samples/Transforms/JustSaying/BrighterSide/Program.cs:28— samples/Transforms/JustSaying/BrighterSide/Program.cs:28-49 | samples/Transforms/MassTransit/MBrigtherSide/Program.cs:28-49 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (27 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:92— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:92-118 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:92-118 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs` 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 5 separate duplicated blocks between them, totalling at least 88 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 (27 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:138— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:138-164 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:532-558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:135— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:135-161 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:135-161 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (27 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Program.cs:12— samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Program.cs:12-38 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Program.cs:18-44 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Program.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Program.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:202— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:202-226 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:202-226 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (25 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:366— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:366-390 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:372-396 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (25 lines × 2) src/Paramore.Brighter/TransformPipelineBuilder.cs:442— src/Paramore.Brighter/TransformPipelineBuilder.cs:442-466 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:351-375 — before extracting anything, compare `src/Paramore.Brighter/TransformPipelineBuilder.cs` and `src/Paramore.Brighter/TransformPipelineBuilderAsync.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/TransformPipelineBuilder.cs:442` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs:26— samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs:26-50 | samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:26-50 — before extracting anything, compare `samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs` and `samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 4) src/Paramore.Brighter/TransformPipelineBuilder.cs:117— src/Paramore.Brighter/TransformPipelineBuilder.cs:117-131 | src/Paramore.Brighter/TransformPipelineBuilder.cs:165-179 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:117-131 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:165-179 — before extracting anything, compare `src/Paramore.Brighter/TransformPipelineBuilder.cs` and `src/Paramore.Brighter/TransformPipelineBuilderAsync.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 92 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/TransformPipelineBuilder.cs:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 4) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:272— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:272-286 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:119-133 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageProducer.cs:134-148 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:125-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:272` it does not close everything it opens, so those 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, `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:269` calls `ArgumentNullException`, `nameof` and `src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:117` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 4) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:348— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:348-362 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:152-166 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageProducer.cs:178-192 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:174-188 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:348` it does not close everything it opens, so those 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, `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:345` calls `ArgumentNullException`, `nameof` and `src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:150` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 4) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:444— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:444-458 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:484-498 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:431-445 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:471-485 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:444` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:277— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:277-291 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:309-324 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. 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 (15–16 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:186— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:186-201 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:187-201 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 87 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:186` 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–16 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:252— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:252-266 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:252-267 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15–16 lines × 2) src/Paramore.Brighter/OutboxProducerMediator.cs:1089— src/Paramore.Brighter/OutboxProducerMediator.cs:1089-1103 | src/Paramore.Brighter/OutboxProducerMediator.cs:1263-1278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/OutboxProducerMediator.cs:1089` it does not close everything it opens, so those 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.
X2 · Cancellation propagation· Async local function without CancellationToken · ×4
Async local function without CancellationToken: GetQueueUrlAsync src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:327— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: CreateRoleArnAsync src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:131— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: GetQueueUrlAsync src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:328— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async local function without CancellationToken: CreateRoleArnAsync src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:131— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Stateful shared instance: SubscriberRegistry src/Paramore.Brighter/SubscriberRegistry.cs:39— `SubscriberRegistry` is not registered, but the singleton `ServiceCollectionSubscriberRegistry` creates it and keeps it in `_registry`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_observers, _allHandlerTypes; e.g. `_observers` at line 54).
Stateful shared instance: Baggage src/Paramore.Brighter/Observability/Baggage.cs:39— `Baggage` keeps one instance of itself in the static `Empty`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_entries; e.g. `_entries` at line 77).
Stateful shared instance: MessageHeader REDACTED:80— `MessageHeader` is not registered, but the singleton `Message` creates it and keeps it in `Header`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (HandledCount; e.g. `HandledCount` at line 601).
No assertions: When_Unwrapping_A_Vanilla_Message_Mapper tests/Paramore.Brighter.Core.Tests/MessageSerialisation/When_Unwrapping_A_Vanilla_Message_Mapper.cs:39— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: When_Unwrapping_A_Vanilla_Message_Mapper tests/Paramore.Brighter.Core.Tests/MessageSerialisation/When_Unwrapping_A_Vanilla_Message_MapperAsync.cs:41— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: When_checking_store_that_exists tests/Paramore.Brighter.Gcp.Tests/Transformers/When_validating_a_luggage_store_exists.cs:12— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (8 members, 50+ identical tokens) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:267— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:267-331 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:343-399 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:117-141 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:150-174 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageProducer.cs:129-161 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageProducer.cs:172-205 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:123-159 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:172-208 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:59— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:59-94 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:111-148 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:319-358 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:479-527 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:537-570 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:579-615 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:759-798 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:928-975 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42— samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-51 | samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-51 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-56 | samples/TaskQueue/KafkaTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-56 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/AnotherGreetingEventMessageMapperAsync.cs:44-56 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-56 | samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-49 | samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-49 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×3
Edited copy of a member (50 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:188— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:188-250 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:288-337 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1329— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1329-1378 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1317-1366 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) samples/WebAPI/WebAPI_Dapper/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:39— samples/WebAPI/WebAPI_Dapper/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:39-94 | samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:35-84 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×3
Edited copy of a member (60 corresponding lines) REDACTED:205— REDACTED:205-264 | REDACTED:225-286 — 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.
Edited copy of a member (60 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:340— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:340-403 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1056-1115 — 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.
Edited copy of a member (60 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:639— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:639-698 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1126-1190 — 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 (47 corresponding lines) · ×3
Edited copy of a member (47 corresponding lines) src/Paramore.Brighter/OutboxProducerMediator.cs:385— src/Paramore.Brighter/OutboxProducerMediator.cs:385-431 | src/Paramore.Brighter/OutboxProducerMediator.cs:454-500 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (47 corresponding lines) REDACTED:42— REDACTED:42-88 | REDACTED:105-151 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (47 corresponding lines) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:282— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:282-329 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:480-526 — 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 (45 corresponding lines) · ×3
Edited copy of a member (45 corresponding lines) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:459— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:459-503 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:513-557 — 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.
Edited copy of a member (45 corresponding lines) src/Paramore.Brighter/TransformPipelineDrain.cs:56— src/Paramore.Brighter/TransformPipelineDrain.cs:56-102 | src/Paramore.Brighter/TransformPipelineDrain.cs:116-160 — 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.
Edited copy of a member (45 corresponding lines) samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs:40— samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs:40-84 | samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/Program.cs:40-84 — 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 (42 corresponding lines) · ×3
Edited copy of a member (42 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1113— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1113-1154 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1101-1142 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (42 corresponding lines) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs:97— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueConsumer.cs:97-138 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusTopicConsumer.cs:79-126 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (42 corresponding lines) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:76— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:76-118 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:91-132 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×3
Edited copy of a member (35 corresponding lines) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:887— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:887-924 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:994-1028 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueMessageProducer.cs:64— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueMessageProducer.cs:64-98 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusTopicMessageProducer.cs:64-98 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) samples/WebAPI/WebAPI_Common/DbMaker/SchemaCreation.cs:64— samples/WebAPI/WebAPI_Common/DbMaker/SchemaCreation.cs:64-98 | samples/WebAPI/WebAPI_Common/DbMaker/SchemaCreation.cs:101-135 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×3
Edited copy of a member (29 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:79— src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:79-107 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:116-147 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:237— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:237-265 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:703-735 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) src/Paramore.Brighter/RelationDatabaseOutbox.cs:90— src/Paramore.Brighter/RelationDatabaseOutbox.cs:90-125 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:141-169 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×3
Edited copy of a member (2 corresponding lines) src/Paramore.Brighter/TransformPipelineBuilder.cs:421— src/Paramore.Brighter/TransformPipelineBuilder.cs:421-422 | src/Paramore.Brighter/TransformPipelineBuilderAsync.cs:330-331 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) REDACTED:147— REDACTED:147-148 | REDACTED:258-259 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (2 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:230— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:230-231 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGatewayConnectionPool.cs:155-157 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (46 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:952— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:952-997 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:940-985 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (46 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1159— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1159-1204 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1147-1192 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (46 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1229— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1229-1274 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1217-1262 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (44 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:401— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:401-444 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:402-445 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (44 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs:212— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs:212-255 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsSubscription.cs:212-255 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsSubscription.cs` 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 44 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsSubscription.cs:212` 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 (44 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1048— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1048-1091 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1036-1079 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (40 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:352— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:352-391 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:353-392 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (40 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsAttributes.cs:57— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsAttributes.cs:57-96 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsAttributes.cs:57-96 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsAttributes.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsAttributes.cs` 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 40 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (40 lines × 2) samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs:45— samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs:45-84 | samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/Program.cs:45-84 — before extracting anything, compare `samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs` and `samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/Program.cs` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 `samples/TaskQueue/RMQDeferOnError/GreetingsSender/Program.cs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) REDACTED:300— REDACTED:300-334 | REDACTED:324-358 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `connection` to `SqlConnection` in one and `NpgsqlConnection` 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 (35 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:165— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:165-199 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:171-205 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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 (35 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:268— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:268-302 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:268-302 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs` 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 5 separate duplicated blocks between them, totalling at least 313 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:268` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:344— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:344-375 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:345-376 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (32 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:872— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:872-903 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:860-891 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (32 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:26— samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs:26-57 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs:26-57 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/PeopleController.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/PeopleController.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (29 lines × 2) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:77— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:77-105 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:283-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:77` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:336— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:336-364 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:398-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:336` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1115— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1115-1143 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1103-1131 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:910— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:910-937 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:898-925 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:910` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (28 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:87— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:87-114 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:88-115 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (28 lines × 2) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:193— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:193-220 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:257-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs: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 (14–15 lines × 2) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:358— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:358-372 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:502-515 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 2) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:175— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:175-188 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:507-521 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:175` it does not close everything it opens, so those exact lines 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) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:388— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:388-401 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:533-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:388` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:279— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:279-288 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:529-538 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:266-275 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:516-525 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) REDACTED:243— REDACTED:243-252 | REDACTED:203-212 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlOutboxMigrationCatalog.cs:199-208 | REDACTED:185-194 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:243` 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 (10 lines × 4) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:375— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:375-385 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:406-415 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:410-420 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:392-401 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:375` it does not close everything it opens, so those 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–11 lines × 2) src/Paramore.Brighter/Observability/BrighterTracer.cs:360— src/Paramore.Brighter/Observability/BrighterTracer.cs:360-369 | src/Paramore.Brighter/Observability/BrighterTracer.cs:522-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Observability/BrighterTracer.cs:360` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) samples/TaskQueue/AWSTaskQueue/GreetingsReceiverConsole/Program.cs:66— samples/TaskQueue/AWSTaskQueue/GreetingsReceiverConsole/Program.cs:66-76 | samples/TaskQueue/AWSTaskQueue/GreetingsSender/Program.cs:56-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/TaskQueue/AWSTaskQueue/GreetingsReceiverConsole/Program.cs: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 (10–11 lines × 2) samples/WebAPI/WebAPI_Common/DbMaker/DbFactory.cs:20— samples/WebAPI/WebAPI_Common/DbMaker/DbFactory.cs:20-30 | samples/WebAPI/WebAPI_Common/DbMaker/InboxFactory.cs:39-48 — 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 `samples/WebAPI/WebAPI_Common/DbMaker/DbFactory.cs:20` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:245— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:245-249 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:274-278 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionBrighterBuilder.cs:289-293 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 3) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:512— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:512-517 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:515-520 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:294-298 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:512` it does not close everything it opens, so those 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, `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:521` calls `Remove` and `src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:301` 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 (5 lines × 3) samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:108— samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:108-112 | samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs:96-100 | samples/Transforms/AWSTransfomers/Compression/GreetingsSender/Program.cs:99-103 — before extracting anything, compare `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs` and `samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs` as WHOLE FILES: this scan already matched 4 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 (9 lines × 3) src/Paramore.Brighter/ChannelNameConverter.cs:37— src/Paramore.Brighter/ChannelNameConverter.cs:37-45 | src/Paramore.Brighter/JsonConverters/RoutingKeyConvertor.cs:37-45 | src/Paramore.Brighter/JsonConverters/SubscriptionNameConverter.cs:37-45 — before extracting anything, compare `src/Paramore.Brighter/ChannelNameConverter.cs` and `src/Paramore.Brighter/JsonConverters/RoutingKeyConvertor.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `ChannelName?` in one and `RoutingKey?` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) src/Paramore.Brighter/JsonConverters/IdConverter.cs:37— src/Paramore.Brighter/JsonConverters/IdConverter.cs:37-45 | src/Paramore.Brighter/JsonConverters/TraceStateConverter.cs:37-45 | src/Paramore.Brighter/PartitionKeyConverter.cs:37-45 — before extracting anything, compare `src/Paramore.Brighter/JsonConverters/IdConverter.cs` and `src/Paramore.Brighter/JsonConverters/TraceStateConverter.cs` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 `value` to `Id?` in one and `TraceState?` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 3) src/Paramore.Brighter.Inbox.Spanner/SpannerInboxAsync.cs:45— src/Paramore.Brighter.Inbox.Spanner/SpannerInboxAsync.cs:45-55 | src/Paramore.Brighter/RelationDatabaseOutbox.cs:1586-1594 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:521-530 — 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.
Unfinished stub — throws NotImplementedException bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:162— `MapToRequest` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:164— `MapToRequestAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqProducerRegistryFactory.cs:32— `CreateAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
DynamoDbTableFactory.GetDynamoDbType (cyclomatic 20) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:358— DynamoDbTableFactory.GetDynamoDbType has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DynamoDbTableFactory.GetDynamoDbType (cyclomatic 20) src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:337— DynamoDbTableFactory.GetDynamoDbType has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Deprecated: xunit REDACTED:170— xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
Deprecated: Polly.Extensions.Http REDACTED:140— Polly.Extensions.Http 3.0.0 — Legacy — the publisher's replacement is `Microsoft.Extensions.Http.Resilience`; migrate the reference to it.
DynamoDbTableFactory.GetGlobalSecondaryIndices (cognitive 22) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:206— DynamoDbTableFactory.GetGlobalSecondaryIndices has cognitive complexity 22 (threshold 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.
DynamoDbTableFactory.GetGlobalSecondaryIndices (cognitive 22) src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:188— DynamoDbTableFactory.GetGlobalSecondaryIndices has cognitive complexity 22 (threshold 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.
SqsMessageProducer.SendWithDelayAsync (cognitive 20) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:142— SqsMessageProducer.SendWithDelayAsync has cognitive complexity 20 (threshold 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.
SqsMessageProducer.SendWithDelayAsync (cognitive 20) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:142— SqsMessageProducer.SendWithDelayAsync has cognitive complexity 20 (threshold 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.
SnsMessageProducer.SendWithDelayAsync (cognitive 18) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:164— SnsMessageProducer.SendWithDelayAsync has cognitive complexity 18 (threshold 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.
SnsMessageProducer.SendWithDelayAsync (cognitive 18) src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:164— SnsMessageProducer.SendWithDelayAsync has cognitive complexity 18 (threshold 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.
SqsMessageConsumer.RejectAsync (cognitive 16) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:153— SqsMessageConsumer.RejectAsync has cognitive complexity 16 (threshold 15). 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.
SqsMessageConsumer.RejectAsync (cognitive 16) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:256— SqsMessageConsumer.RejectAsync has cognitive complexity 16 (threshold 15). 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.
Change coupling: OutboxProducerMediator.cs ↔ ProducersConfiguration.cs src/Paramore.Brighter/OutboxProducerMediator.cs:1— `src/Paramore.Brighter/OutboxProducerMediator.cs` and `src/Paramore.Brighter/ProducersConfiguration.cs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 7 shared commits counted here, the most recent 3 are `82dd0ce3` fix(outbox): keep at most one outstanding check in flight per mediator; `fa4e3c37` fix(outbox): record the outstanding check time when the check is queued; `ab5ff17c` fix(outbox): skip the outstanding count when no limit is set — run `git show` on any of them.
Change coupling: MessagePump.cs ↔ Performer.cs src/Paramore.Brighter.ServiceActivator/MessagePump.cs:1— `src/Paramore.Brighter.ServiceActivator/MessagePump.cs` and `src/Paramore.Brighter.ServiceActivator/Performer.cs` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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 8 shared commits counted here, the most recent 3 are `e18e9537` fix(health-checks): report persistent consumer receive failures; `69ed8078` Make MessagePump Run a Task so that we can provide an async version (at that commit the files were still `Brighter/paramore.brighter.serviceactivator/MessagePump.cs` and `Brighter/paramore.brighter.serviceactivator/Performer.cs`); `ddadd838` RabbitMQ Model lifecycle improvement (at that commit the files were still `Brighter/paramore.brighter.serviceactivator/MessagePump.cs` and `Brighter/paramore.brighter.serviceactivator/Performer.cs`) — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (10 members, 50+ identical tokens) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:50— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:50-78 | src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:116-144 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:73-101 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:139-167 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:50-78 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:116-144 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:70-95 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:130-155 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:88-116 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:166-194 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
Members sharing a duplicated core (10 members, 50+ identical tokens) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:189— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:189-226 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:278-334 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:442-467 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:482-512 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:528-573 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:176-213 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:265-321 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:429-454 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:469-499 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:515-560 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:50— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:50-84 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:159-192 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:184-232 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:240-279 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:644-686 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:691-725 — 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) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:604— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:604-621 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:607-624 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:1155-1175 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:473-490 | REDACTED:566-583 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:621-638 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×2
Edited copy of a member (61 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:267— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:267-327 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:267-327 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (61 corresponding lines) src/Paramore.Brighter/CommandProcessor.cs:475— src/Paramore.Brighter/CommandProcessor.cs:475-535 | src/Paramore.Brighter/CommandProcessor.cs:596-661 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (57 corresponding lines) · ×2
Edited copy of a member (57 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:36— src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:36-92 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:95-152 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (57 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:272— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:272-328 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:247-305 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (62 corresponding lines) · ×2
Edited copy of a member (62 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:484— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:484-545 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:552-613 — These two members are one piece of code written twice and then edited apart: 62 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (62 corresponding lines) src/Paramore.Brighter/OutboxProducerMediator.cs:1089— src/Paramore.Brighter/OutboxProducerMediator.cs:1089-1150 | src/Paramore.Brighter/OutboxProducerMediator.cs:1263-1324 — These two members are one piece of code written twice and then edited apart: 62 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (72 corresponding lines) · ×2
Edited copy of a member (72 corresponding lines) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:207— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:207-278 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:189-260 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (72 corresponding lines) samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:23— samples/Scheduler/AwsTaskQueue/GreetingsPumper/Program.cs:23-94 | samples/Scheduler/AwsTaskQueue/GreetingsReceiverConsole/Program.cs:47-148 — These two members are one piece of code written twice and then edited apart: 72 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (51 corresponding lines) · ×2
Edited copy of a member (51 corresponding lines) src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:89— src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:89-139 | src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs:90-150 — 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.
Edited copy of a member (51 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:137— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:137-187 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:531-589 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×2
Edited copy of a member (43 corresponding lines) src/Paramore.Brighter/PipelineBuilder.cs:188— src/Paramore.Brighter/PipelineBuilder.cs:188-230 | src/Paramore.Brighter/PipelineBuilder.cs:248-291 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (43 corresponding lines) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:231— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:231-276 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:285-327 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (49 corresponding lines) · ×2
Edited copy of a member (49 corresponding lines) REDACTED:127— REDACTED:127-181 | REDACTED:392-440 — 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.
Edited copy of a member (49 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:275— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:275-323 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:740-794 — 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 (39 corresponding lines) · ×2
Edited copy of a member (39 corresponding lines) src/Paramore.Brighter/PipelineBuilder.cs:326— src/Paramore.Brighter/PipelineBuilder.cs:326-366 | src/Paramore.Brighter/PipelineBuilder.cs:369-407 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (39 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:466— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:466-506 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:369-407 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×2
Edited copy of a member (46 corresponding lines) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:347— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:347-392 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:403-448 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (46 corresponding lines) src/Paramore.Brighter/OutboxProducerMediator.cs:914— src/Paramore.Brighter/OutboxProducerMediator.cs:914-959 | src/Paramore.Brighter/OutboxProducerMediator.cs:1006-1062 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (58 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:269— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:269-326 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:181-238 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (58 lines × 2) samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/AddGreetingHandlerAsync.cs:56— samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/AddGreetingHandlerAsync.cs:56-113 | samples/Tutorials/03-DurableOutbox/GreetingsSender/AddGreetingHandlerAsync.cs:55-112 — before extracting anything, compare `samples/TaskQueue/PostgresTaskQueue/GreetingsSenderWithOutbox/AddGreetingHandlerAsync.cs` and `samples/Tutorials/03-DurableOutbox/GreetingsSender/AddGreetingHandlerAsync.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (54 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:207— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:207-260 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:207-260 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (54 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:101— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:101-154 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:101-154 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (49 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderNames.cs:33— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderNames.cs:33-81 | src/Paramore.Brighter.MessagingGateway.AWSSQS/HeaderNames.cs:33-81 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderNames.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/HeaderNames.cs` 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 49 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/HeaderNames.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (49 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:96— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs:96-144 | src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs:96-144 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageOptions.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageOptions.cs` 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 2 separate duplicated blocks between them, totalling at least 66 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (45 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:529— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:529-573 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:516-560 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (45 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:29— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:29-74 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:29-73 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` 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 6 separate duplicated blocks between them, totalling at least 111 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:290— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:290-330 | src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs:296-336 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs` 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 10 separate duplicated blocks between them, totalling at least 191 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 (41 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:399— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:399-439 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:402-442 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (37 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:190— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:190-226 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:177-213 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (37 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1286— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1286-1322 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1274-1310 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (36 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:814— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:814-849 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:802-837 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (36 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:229— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:229-264 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:229-264 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs` 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 5 separate duplicated blocks between them, totalling at least 313 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 (34 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:264— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:264-297 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:264-297 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (34 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumerFactory.cs:59— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumerFactory.cs:59-92 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumerFactory.cs:59-92 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumerFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumerFactory.cs` 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 34 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 (26–27 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:348— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:348-373 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:422-448 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:348` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–27 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:512— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:512-537 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:579-605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:512` it does not close everything it opens, so those 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, `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:508` calls `ParseOrCreateTopicName` and `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:574` 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) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:82— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:82-94 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:136-148 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:346-358 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:515-527 — 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 `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:558— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:558-570 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:603-615 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:786-798 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:963-975 — 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 `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:558` 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 × 3) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:279— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:279-290 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:194-205 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:192-203 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 181 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `headers` to `Headers` in one and `IDictionary<string, object?>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 3) samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:49— samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:49-60 | samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs:48-59 | samples/Transforms/AWSTransfomers/Compression/GreetingsSender/Program.cs:48-59 — before extracting anything, compare `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs` and `samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs` as WHOLE FILES: this scan already matched 4 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 `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:449— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:449-458 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:450-459 | src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:312-321 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 3) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:521— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:521-530 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:524-533 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:298-308 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12–13 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:325— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:325-336 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:765-777 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:325` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–13 lines × 2) src/Paramore.Brighter/PipelineBuilder.cs:332— src/Paramore.Brighter/PipelineBuilder.cs:332-344 | src/Paramore.Brighter/PipelineBuilder.cs:376-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `implicitHandler` to `RequestHandler<TRequest>` in one and `RequestHandlerAsync<TRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 3) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55-65 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:78-88 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:55-65 — before extracting anything, compare `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121-131 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:144-154 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:121-131 — before extracting anything, compare `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55-63 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:78-86 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:55-63 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:74-82 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:93-101 — before extracting anything, compare `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 5) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121-129 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:144-152 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:121-129 | src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxProvisioningExtensions.cs:134-142 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:171-179 — before extracting anything, compare `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121` it does not close everything it opens, so those exact lines 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 × 8) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55-62 | src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:121-128 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:78-85 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs:144-151 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:55-62 | src/Paramore.Brighter.BoxProvisioning.PostgreSql/PostgreSqlBoxProvisioningExtensions.cs:121-128 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:93-100 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxProvisioningExtensions.cs:171-178 — before extracting anything, compare `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs` and `src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxProvisioningExtensions.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxProvisioningExtensions.cs:55` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 8) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:134— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:134-141 | src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:139-146 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:165-172 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:173-180 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:201-208 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:184-191 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:132-139 | src/Paramore.Brighter/Subscription.cs:301-308 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:142` calls `FromMilliseconds` and `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:147` 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 × 4) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:69— src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs:69-74 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs:70-75 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactory.cs:69-74 | src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderTransformerFactoryAsync.cs:70-75 — before extracting anything, compare `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactory.cs` and `src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderMapperFactoryAsync.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 4) src/Paramore.Brighter.ServiceActivator/Proactor.cs:323— src/Paramore.Brighter.ServiceActivator/Proactor.cs:323-328 | src/Paramore.Brighter.ServiceActivator/Proactor.cs:378-383 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:287-292 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:346-351 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:323` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) REDACTED:136— REDACTED:136-141 | REDACTED:147-152 | REDACTED:115-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 3) src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:216— src/Paramore.Brighter.BoxProvisioning.MsSql/MsSqlBoxDetectionHelper.cs:216-221 | src/Paramore.Brighter.BoxProvisioning.MySql/MySqlBoxDetectionHelper.cs:194-199 | src/Paramore.Brighter.BoxProvisioning.Sqlite/SqliteBoxDetectionHelper.cs:191-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×2
Edited copies of one member (3 members, 18+ corresponding lines) samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:81— samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:81-98 | samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/Program.cs:78-95 | samples/WebAPI/WebAPI_Dynamo/Greetings_Sweeper/Program.cs:27-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 18+ corresponding lines) samples/WebAPI/WebAPI_Common/DbMaker/DbFactory.cs:12— samples/WebAPI/WebAPI_Common/DbMaker/DbFactory.cs:12-30 | samples/WebAPI/WebAPI_Common/DbMaker/InboxFactory.cs:31-48 | samples/WebAPI/WebAPI_Common/DbMaker/OutboxFactory.cs:39-58 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Off the main sequence: Paramore.Brighter.Extensions.DependencyInjection(netstandard2.0) src/Paramore.Brighter.Extensions.DependencyInjection/Paramore.Brighter.Extensions.DependencyInjection.csproj:1— Paramore.Brighter.Extensions.DependencyInjection(netstandard2.0): abstractness 0.11, instability 0.08, distance 0.81 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: Paramore.Brighter.MySql(net8.0) src/Paramore.Brighter.MySql/Paramore.Brighter.MySql.csproj:1— Paramore.Brighter.MySql(net8.0): abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Low cohesion: BrighterTracer (LCOM4 5) src/Paramore.Brighter/Observability/BrighterTracer.cs:39— BrighterTracer's methods fall into 5 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 5 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: MessagePump (LCOM4 4) src/Paramore.Brighter.ServiceActivator/MessagePump.cs:69— MessagePump'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.
Blocking `KafkaMessageConsumer.AcknowledgeOffset` inside an `async` method src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:727— `KafkaMessageConsumer.AcknowledgeOffset` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
Blocking `KafkaMessageConsumer.AcknowledgeOffset` inside an `async` method src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:792— `KafkaMessageConsumer.AcknowledgeOffset` is a synchronous helper that blocks (`SemaphoreSlim.Wait`): called from an `async` method it parks the thread exactly as the inline call would. Make the helper `async` and `await` it (`await Task.Delay`, `SemaphoreSlim.WaitAsync`, a `TaskCompletionSource` instead of the poll).
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×2
Owned disposable field is never released src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:31— `GcpPullMessageConsumer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_purgeLock` itself (line 31), which makes that instance its own. But `_purgeLock` is named in none of the methods the disposal search covered: `DisposeAsync` (line 512), `Dispose` (line 517) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_purgeLock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/Paramore.Brighter/OutboxProducerMediator.cs:71— `OutboxProducerMediator` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_backgroundClearSemaphore` itself (line 71), which makes that instance its own. But `_backgroundClearSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 211), `Dispose` (line 217), `Dispose` (line 211), `Dispose` (line 217), `DisposeQuietly` (line 255) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_backgroundClearSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Proactor.EventLoop (cyclomatic 36) src/Paramore.Brighter.ServiceActivator/Proactor.cs:134— Proactor.EventLoop 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.
Reactor.Run (cyclomatic 36) src/Paramore.Brighter.ServiceActivator/Reactor.cs:95— Reactor.Run 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.
RocketMessageConsumer.CreateMessage (cyclomatic 28) src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:333— RocketMessageConsumer.CreateMessage has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to 18 function items inside it that branch (ReadTimeStamp, ReadMessageType, ReadContentType, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AzureServiceBusConsumerFactory.CreateConsumer (cyclomatic 21) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs:96— AzureServiceBusConsumerFactory.CreateConsumer has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ServiceCollectionExtensions.AddProducers (cyclomatic 19) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:312— ServiceCollectionExtensions.AddProducers has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
OutboxMessage.ConvertToMessage (cyclomatic 19) src/Paramore.Brighter.Outbox.MongoDb/OutboxMessage.cs:227— OutboxMessage.ConvertToMessage 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.
top-level statements (cyclomatic 18) bugfixes/0037-gcp-requeue-immediate-redelivery/diagnostic/Program.cs:31— top-level statements has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FirestoreOutbox.ToDocument (cyclomatic 17) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1294— FirestoreOutbox.ToDocument has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FirestoreOutbox.ToMessage (cyclomatic 17) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1403— FirestoreOutbox.ToMessage has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GcpPubSubMessageGateway.EnsureTopicExistAsync (cyclomatic 16) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:40— GcpPubSubMessageGateway.EnsureTopicExistAsync has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (UpdateTopicAsync, CreateTopic). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OutboxProducerMediator.BulkDispatchAsync (cyclomatic 16) src/Paramore.Brighter/OutboxProducerMediator.cs:1152— OutboxProducerMediator.BulkDispatchAsync 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.
ScheduledRequestContextBagConverter.Read (cyclomatic 16) src/Paramore.Brighter/Scheduler/ScheduledRequestContextBagConverter.cs:63— ScheduledRequestContextBagConverter.Read has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Prerelease dependency: OpenTelemetry.Exporter.Prometheus.AspNetCore — OpenTelemetry.Exporter.Prometheus.AspNetCore resolves to 1.19.1-beta.1, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Proactor.EventLoop (cognitive 91) src/Paramore.Brighter.ServiceActivator/Proactor.cs:134— Proactor.EventLoop has cognitive complexity 91 (threshold 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.
Reactor.Run (cognitive 91) src/Paramore.Brighter.ServiceActivator/Reactor.cs:95— Reactor.Run has cognitive complexity 91 (threshold 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.
OutboxProducerMediator.BulkDispatchAsync (cognitive 46) src/Paramore.Brighter/OutboxProducerMediator.cs:1152— OutboxProducerMediator.BulkDispatchAsync has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ArtefactExclusionSet.Build (cognitive 29) src/Paramore.Brighter.Extensions.DependencyInjection/ArtefactExclusionSet.cs:63— ArtefactExclusionSet.Build has cognitive complexity 29 (threshold 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.
RocketMessageConsumer.CreateMessage (cognitive 27) src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:333— RocketMessageConsumer.CreateMessage has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 18 function items inside it that branch (ReadTimeStamp, ReadMessageType, ReadContentType, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ServiceBusLock.RenewAsync (cognitive 25) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusLock.cs:100— ServiceBusLock.RenewAsync has cognitive complexity 25 (threshold 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.
KafkaMessagingGateway.FindTopic (cognitive 24) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessagingGateway.cs:138— KafkaMessagingGateway.FindTopic has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BrighterTracer.CreateDbSpan (cognitive 21) src/Paramore.Brighter/Observability/BrighterTracer.cs:558— BrighterTracer.CreateDbSpan has cognitive complexity 21 (threshold 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.
OutboxProducerMediator.Dispatch (cognitive 21) src/Paramore.Brighter/OutboxProducerMediator.cs:1088— OutboxProducerMediator.Dispatch has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ServiceCollectionExtensions.AddProducers (cognitive 19) src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:312— ServiceCollectionExtensions.AddProducers has cognitive complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
OutboxMessage.ConvertToMessage (cognitive 19) src/Paramore.Brighter.Outbox.MongoDb/OutboxMessage.cs:227— OutboxMessage.ConvertToMessage has cognitive complexity 19 (threshold 15). 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.
OutboxProducerMediator.DispatchAsync (cognitive 19) src/Paramore.Brighter/OutboxProducerMediator.cs:1257— OutboxProducerMediator.DispatchAsync has cognitive complexity 19 (threshold 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.
top-level statements (cognitive 19) bugfixes/0037-gcp-requeue-immediate-redelivery/diagnostic/Program.cs:31— top-level statements has cognitive complexity 19 (threshold 15). 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.
BrighterMetricsFromTracesProcessor.OnEnd (cognitive 18) src/Paramore.Brighter/Observability/BrighterMetricsFromTracesProcessor.cs:45— BrighterMetricsFromTracesProcessor.OnEnd has cognitive complexity 18 (threshold 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.
top-level statements (cognitive 18) bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:17— top-level statements has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 55, 70). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GcpPubSubMessageGateway.EnsureTopicExistAsync (cognitive 17) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubMessageGateway.cs:40— GcpPubSubMessageGateway.EnsureTopicExistAsync has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (UpdateTopicAsync, CreateTopic). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FirestoreOutbox.ToDocument (cognitive 17) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1294— FirestoreOutbox.ToDocument has cognitive complexity 17 (threshold 15). 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.
PipelineDiagnosticWriter.LogPublications (cognitive 17) src/Paramore.Brighter/Validation/PipelineDiagnosticWriter.cs:135— PipelineDiagnosticWriter.LogPublications has cognitive complexity 17 (threshold 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.
top-level statements (cognitive 17) bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/Program.cs:7— top-level statements has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 29, 35, 47, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AzureServiceBusConsumer.ReceiveAsync (cognitive 16) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:178— AzureServiceBusConsumer.ReceiveAsync has cognitive complexity 16 (threshold 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.
AzureServiceBusConsumerFactory.CreateConsumer (cognitive 16) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs:96— AzureServiceBusConsumerFactory.CreateConsumer has cognitive complexity 16 (threshold 15). 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.
FirestoreOutbox.ToMessage (cognitive 16) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1403— FirestoreOutbox.ToMessage has cognitive complexity 16 (threshold 15). 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.
D4 · Code Duplication· Near-duplicate member family (4 members, 36 shared lines) · ×1
Near-duplicate member family (4 members, 36 shared lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1158— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1158-1208 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1228-1278 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1146-1196 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1216-1266 — These 4 members are variants of one another: a block of 36 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Near-duplicate member pair (169 shared lines) src/Paramore.Brighter.ServiceActivator/Proactor.cs:135— src/Paramore.Brighter.ServiceActivator/Proactor.cs:135-442 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:96-410 — These two members are variants of one another: 169 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 (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:154— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:154-224 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:257-327 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:192-243 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:256-307 | REDACTED:198-260 | REDACTED:264-326 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:335-388 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:397-450 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:131-187 — These 9 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 9 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 9 times.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:166— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageProducer.cs:166-248 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs:155-219 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:609— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:609-662 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:676-729 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) src/Paramore.Brighter.ServiceActivator/Proactor.cs:581— src/Paramore.Brighter.ServiceActivator/Proactor.cs:581-624 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:572-616 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1389— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1389-1441 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1377-1429 — These two members are one piece of code written twice and then edited apart: 53 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:162— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:162-207 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs:150-186 — 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 (79 corresponding lines) · ×1
Edited copy of a member (79 corresponding lines) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:122— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:122-200 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:334-412 — These two members are one piece of code written twice and then edited apart: 79 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (66 corresponding lines) · ×1
Edited copy of a member (66 corresponding lines) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:407— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:407-472 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:1194-1286 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (38 corresponding lines) · ×1
Edited copy of a member (38 corresponding lines) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:106— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:106-146 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs:258-295 — These two members are one piece of code written twice and then edited apart: 38 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:204— src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:204-277 | src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:417-492 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:61— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqTlsConfigurator.cs:61-96 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqTlsConfigurator.cs:61-96 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) samples/TaskQueue/RMQRequestReply/Greetings/Ports/Mappers/GreetingReplyMessageMapper.cs:26— samples/TaskQueue/RMQRequestReply/Greetings/Ports/Mappers/GreetingReplyMessageMapper.cs:26-34 | samples/TaskQueue/RMQRequestReply/Greetings/Ports/Mappers/GreetingRequestMessageMapper.cs:54-61 | src/Paramore.Brighter.ServiceActivator/Ports/Mappers/HeartbeatRequestCommandMessageMapper.cs:29-42 — 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, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) samples/TaskQueue/ASBTaskQueue/Greetings/Ports/Mappers/AddGreetingMessageMapper.cs:23— samples/TaskQueue/ASBTaskQueue/Greetings/Ports/Mappers/AddGreetingMessageMapper.cs:23-28 | samples/TaskQueue/MsSqlMessagingGateway/Events/Ports/Mappers/CompetingConsumerCommandMessageMapper.cs:13-18 | src/Paramore.Brighter.ServiceActivator/Ports/ConfigurationCommandMessageMapper.cs:14-21 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) src/Paramore.Brighter/RelationDatabaseOutbox.cs:1383— src/Paramore.Brighter/RelationDatabaseOutbox.cs:1383-1410 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:391-420 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:446-473 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:425— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:425-427 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:412-414 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (213 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:13— src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:13-225 | src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs:13-225 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/MessageItem.cs` 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 5 separate duplicated blocks between them, totalling at least 313 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (98 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:315— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:315-412 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:316-413 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (91 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:633— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:633-723 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:636-726 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:633` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (83 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:677— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:677-759 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:664-746 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (79 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:63— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs:63-141 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs:63-141 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 111 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (75 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/HeaderNames.cs:30— src/Paramore.Brighter.MessagingGateway.RMQ.Async/HeaderNames.cs:30-104 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/HeaderNames.cs:28-102 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/HeaderNames.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/HeaderNames.cs` 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 75 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/HeaderNames.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (69 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:50— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:50-118 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs:50-118 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs` 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 17 separate duplicated blocks between them, totalling at least 322 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:50` 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 (65–66 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:227— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:227-291 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:227-292 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (64 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:166— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:166-229 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:166-229 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 143 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 (60 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:360— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:360-419 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:339-398 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs` 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 5 separate duplicated blocks between them, totalling at least 136 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 (59 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs:43— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs:43-101 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagingGatewayConnection.cs:48-106 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagingGatewayConnection.cs` 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 2 separate duplicated blocks between them, totalling at least 77 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (52–59 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbConfiguration.cs:5— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbConfiguration.cs:5-56 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbConfiguration.cs:5-63 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbConfiguration.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbConfiguration.cs` 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 2 separate duplicated blocks between them, totalling at least 72 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbConfiguration.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (56 lines × 2) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:279— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:279-334 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:266-321 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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 (55 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:96— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:96-150 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:96-150 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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 (51–52 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:37— src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:37-88 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/Parser.cs:97-147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: the declarations holding them bind `receivedMessage` to `GcpStreamMessage` in one and `ReceivedMessage` 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 (66–69 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:262— src/Paramore.Brighter.ServiceActivator/Proactor.cs:262-327 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:223-291 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:262` 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 (84 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:94— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:94-177 | src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs:94-177 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 153 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. 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 (43 lines × 2) src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:180— src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs:180-222 | src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs:180-222 — `src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs` and `src/Paramore.Brighter.Transformers.AWS/S3LuggageStore.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 319 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 (42 lines × 2) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:459— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:459-500 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:460-501 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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 (28–43 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:607— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:607-634 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:813-855 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:607` 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 (33–42 lines × 4) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:167— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:167-208 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageProducer.cs:150-182 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs:167-208 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageProducer.cs:150-182 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessageProducer.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 143 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs:167` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (70 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:155— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:155-224 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:258-327 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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 (33–41 lines × 2) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:210— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:210-250 | src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:305-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs:210` 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 (62 lines × 2) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:59— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs:59-120 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs:62-123 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs` 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 13 separate duplicated blocks between them, totalling at least 190 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 (38 lines × 2) src/Paramore.Brighter/MessageMappers/CloudEventJsonMessageMapper.cs:136— src/Paramore.Brighter/MessageMappers/CloudEventJsonMessageMapper.cs:136-173 | src/Paramore.Brighter/Transforms/Transformers/CloudEventsTransformer.cs:377-414 — 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 (36 lines × 3) src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:125— src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:125-160 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:151-186 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:118-153 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:125` 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 (31–32 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:75— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:75-106 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:77-107 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 3) src/Paramore.Brighter.MessageScheduler.AWS.V4/FireAwsScheduler.cs:11— src/Paramore.Brighter.MessageScheduler.AWS.V4/FireAwsScheduler.cs:11-39 | src/Paramore.Brighter.MessageScheduler.AWS/FireAwsScheduler.cs:11-39 | src/Paramore.Brighter.MessageScheduler.Azure/FireAzureScheduler.cs:11-39 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/FireAwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/FireAwsScheduler.cs` 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 29 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (29–30 lines × 4) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:121— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:121-149 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs:138-167 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs:121-149 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageSender.cs:140-169 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SnsMessagePublisher.cs` 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 5 separate duplicated blocks between them, totalling at least 88 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessagePublisher.cs:121` it does not close everything it opens, so those 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 (28–29 lines × 3) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:210— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:210-238 | REDACTED:224-251 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:354-381 — 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 `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:210` 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, `src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:382` calls `Remove` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:239` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (27–29 lines × 2) src/Paramore.Brighter/TransformLifetimeScope.cs:42— src/Paramore.Brighter/TransformLifetimeScope.cs:42-70 | src/Paramore.Brighter/TransformLifetimeScopeAsync.cs:58-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (21–28 lines × 2) src/Paramore.Brighter/RelationalDatabaseInbox.cs:579— src/Paramore.Brighter/RelationalDatabaseInbox.cs:579-599 | src/Paramore.Brighter/RelationalDatabaseInbox.cs:606-633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/RelationalDatabaseInbox.cs:579` 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 (26 lines × 3) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFiredHandler.cs:16— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFiredHandler.cs:16-41 | src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFiredHandler.cs:16-41 | src/Paramore.Brighter.MessageScheduler.Azure/AzureSchedulerFiredHandler.cs:16-41 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFiredHandler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFiredHandler.cs` 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 26 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `command` to `FireAwsScheduler` in one and `FireAzureScheduler` 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 (23–27 lines × 2) src/Paramore.Brighter/OutboxProducerMediator.cs:937— src/Paramore.Brighter/OutboxProducerMediator.cs:937-959 | src/Paramore.Brighter/OutboxProducerMediator.cs:1031-1057 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/OutboxProducerMediator.cs:937` it begins part-way through the construct above it, so those 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 (16–23 lines × 6) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:195— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:195-217 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:298-320 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:284-302 | REDACTED:300-317 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:426-443 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:163-178 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:195` 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, `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:218` calls `ReleaseSourceMessageAsync` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:303` 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 (20–23 lines × 2) src/Paramore.Brighter/Observability/BrighterTracer.cs:620— src/Paramore.Brighter/Observability/BrighterTracer.cs:620-642 | src/Paramore.Brighter/Observability/BrighterTracer.cs:667-686 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/Observability/BrighterTracer.cs:620` it does not close everything it opens, so those 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 (21–22 lines × 4) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:376— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:376-397 | src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:430-450 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:377-398 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:431-451 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:376` 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 (21–22 lines × 2) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:111— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:111-131 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:579-600 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:111` it does not close everything it opens, so those 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 (18–21 lines × 6) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:604— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:604-621 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:607-624 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs:1155-1175 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:473-490 | REDACTED:566-583 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:621-638 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20 lines × 4) src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:137— src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:137-156 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:163-182 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:171-190 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:130-149 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15–21 lines × 2) src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:67— src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:67-87 | src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:67-81 — `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs` and `src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs` 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 5 separate duplicated blocks between them, totalling at least 136 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:67` it does not close everything it opens, so those 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 (39–40 lines × 2) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:283— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:283-321 | src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:359-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:283` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17–21 lines × 2) src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:91— src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:91-111 | src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:480-496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 4) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1190— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1190-1208 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1260-1278 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1178-1196 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1248-1266 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1190` 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–20 lines × 3) src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:343— src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:343-362 | src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageProducer.cs:150-166 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:172-188 — 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 `src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageProducer.cs:343` it does not close everything it opens, so those exact lines 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–20 lines × 3) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:555— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:555-569 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:778-797 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:955-974 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:555` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16–20 lines × 2) src/Paramore.Brighter/PipelineBuilder.cs:500— src/Paramore.Brighter/PipelineBuilder.cs:500-515 | src/Paramore.Brighter/PipelineBuilder.cs:569-588 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–20 lines × 2) src/Paramore.Brighter/TransformerFactory.cs:47— src/Paramore.Brighter/TransformerFactory.cs:47-64 | src/Paramore.Brighter/TransformerFactoryAsync.cs:45-64 — before extracting anything, compare `src/Paramore.Brighter/TransformerFactory.cs` and `src/Paramore.Brighter/TransformerFactoryAsync.cs` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter/TransformerFactory.cs:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (17 lines × 4) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1171— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1171-1187 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1241-1257 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1159-1175 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:1229-1245 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:1171` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 3) REDACTED:305— REDACTED:305-320 | REDACTED:169-184 | REDACTED:329-344 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:305` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:252— src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:252-268 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:302-319 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:252` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15–17 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:366— src/Paramore.Brighter.ServiceActivator/Proactor.cs:366-382 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:336-350 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:366` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15 lines × 3) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91-105 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:197-211 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:803-817 — 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 `src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–16 lines × 2) src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:150— src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:150-165 | src/Paramore.Brighter/Transforms/Transformers/ClaimCheckTransformer.cs:213-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 8) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:186— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:186-199 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:289-302 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:211-224 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:275-288 | REDACTED:225-238 | REDACTED:291-304 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:355-368 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:417-430 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:186` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 5) src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:50— src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:50-65 | src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:159-174 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:184-199 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:240-254 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:644-659 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 4) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:96— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:96-109 | src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:207-220 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:96-109 | src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:207-220 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs` 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 8 separate duplicated blocks between them, totalling at least 224 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:79— src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:79-92 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:343-356 | src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:512-525 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–14 lines × 3) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubSubscription.cs:207— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubSubscription.cs:207-214 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:152-165 | src/Paramore.Brighter/InMemorySubscription.cs:30-43 — 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 `src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubSubscription.cs:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12–14 lines × 2) src/Paramore.Brighter/PipelineBuilder.cs:348— src/Paramore.Brighter/PipelineBuilder.cs:348-361 | src/Paramore.Brighter/PipelineBuilder.cs:391-402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `implicitHandler` to `RequestHandler<TRequest>` in one and `RequestHandlerAsync<TRequest>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 7) src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:139— src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:139-150 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:165-176 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:173-184 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:201-212 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:184-195 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:132-143 | src/Paramore.Brighter/Subscription.cs:301-312 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) REDACTED:240— REDACTED:240-254 | REDACTED:306-320 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:169-181 — 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 `REDACTED:240` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11–12 lines × 7) src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:116— src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:116-127 | src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:121-131 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:147-157 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:149-160 | src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqSubscription.cs:177-188 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs:162-173 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:114-124 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqSubscription.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 6) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:190— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:190-199 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:443-452 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:483-492 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:177-186 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:430-439 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:470-479 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:190` it does not close everything it opens, so those exact lines 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 × 5) src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226— src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226-240 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:290-304 | REDACTED:240-253 | REDACTED:306-319 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:169-180 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:226` 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.
Duplicated block (9 lines × 10) src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:191— src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:191-199 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:280-288 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:444-452 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:484-492 | src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:530-538 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:178-186 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:267-275 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:431-439 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:471-479 | src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs:517-525 — `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs` and `src/Paramore.Brighter.Outbox.DynamoDB/DynamoDbOutbox.cs` 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 35 separate duplicated blocks between them, totalling at least 895 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.Outbox.DynamoDB.V4/DynamoDbOutbox.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `messageIds` to `Id[]` in one and `IEnumerable<Id>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 9) src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:200— src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:200-217 | src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs:303-320 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:225-238 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:289-302 | REDACTED:239-251 | REDACTED:305-317 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:369-381 | src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs:431-443 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMessageConsumer.cs:168-178 — `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs` 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 23 separate duplicated blocks between them, totalling at least 578 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:200` 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, `src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:218` calls `ReleaseSourceMessageAsync` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageConsumer.cs:239` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 6) src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsSubscription.cs:210— src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsSubscription.cs:210-218 | src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusSubscription.cs:119-127 | src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs:123-131 | src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs:149-157 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:152-160 | src/Paramore.Brighter.MessagingGateway.Redis/RedisSubscription.cs:116-124 — before extracting anything, compare `src/Paramore.Brighter.MessagingGateway.MQTT/MqttSubscription.cs` and `src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlSubscription.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 97 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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–11 lines × 2) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:390— src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:390-400 | src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs:322-329 — `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs` and `src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs` 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 8 separate duplicated blocks between them, totalling at least 120 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:390` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–11 lines × 2) src/Paramore.Brighter.ServiceActivator/Proactor.cs:355— src/Paramore.Brighter.ServiceActivator/Proactor.cs:355-363 | src/Paramore.Brighter.ServiceActivator/Reactor.cs:321-331 — before extracting anything, compare `src/Paramore.Brighter.ServiceActivator/Proactor.cs` and `src/Paramore.Brighter.ServiceActivator/Reactor.cs` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 225 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Paramore.Brighter.ServiceActivator/Proactor.cs:355` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 6) REDACTED:135— REDACTED:135-139 | REDACTED:241-245 | REDACTED:146-150 | REDACTED:201-205 | REDACTED:114-118 | REDACTED:183-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubSubscription.cs:208— src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubSubscription.cs:208-213 | src/Paramore.Brighter.MessagingGateway.Postgres/PostgresSubscription.cs:153-163 | src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqSubscription.cs:155-159 | src/Paramore.Brighter/InMemorySubscription.cs:31-41 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 3) src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:574— src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:574-581 | src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:575-582 | src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs:137-144 — `src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs` and `src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs` 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 17 separate duplicated blocks between them, totalling at least 379 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.
D4 · Code Duplication· Edited copy of a member (68 corresponding lines) · ×1
Edited copy of a member (68 corresponding lines) samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:76— samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Program.cs:76-143 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Program.cs:65-146 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Startup.cs:75— samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Startup.cs:75-122 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Startup.cs:73-125 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 47+ corresponding lines) · ×1
Edited copies of one member (3 members, 47+ corresponding lines) samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:48— samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:48-105 | samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs:47-93 | samples/Transforms/AWSTransfomers/Compression/GreetingsSender/Program.cs:47-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 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 (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) samples/TaskQueue/RMQRequestReply/GreetingsClient/Program.cs:40— samples/TaskQueue/RMQRequestReply/GreetingsClient/Program.cs:40-104 | samples/TaskQueue/RMQTaskQueue/GreetingsSender/Program.cs:41-96 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:17— samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:17-27 | samples/WebAPI/WebAPI_Dapper/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:18-27 | samples/WebAPI/WebAPI_Dynamo/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:16-24 | samples/WebAPI/WebAPI_EFCore/SalutationAnalytics/Mappers/SalutationReceivedMessageMapperAsync.cs:16-24 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) samples/Validation/DataAnnotationsSample/Program.cs:52— samples/Validation/DataAnnotationsSample/Program.cs:52-60 | samples/Validation/FluentValidationSample/Program.cs:55-63 | samples/Validation/SpecificationSample/Program.cs:55-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 8+ corresponding lines) · ×1
Edited copies of one member (5 members, 8+ corresponding lines) samples/TaskQueue/ASBTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventAsyncHandler.cs:20— samples/TaskQueue/ASBTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventAsyncHandler.cs:20-28 | samples/TaskQueue/KafkaSchemaRegistry/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:36-43 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:36-43 | samples/TaskQueue/MultiBus/Greetings/Ports/CommandHandlers/AnotherGreetingEventHandler.cs:36-43 | samples/TaskQueue/MultiBus/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:36-43 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 8+ corresponding lines) · ×1
Edited copies of one member (8 members, 8+ corresponding lines) samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34— samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/Scheduler/QuartzTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/TaskQueue/MsSqlMessagingGateway/GreetingsReceiverConsole/GreetingEventHandler.cs:44-51 | samples/TaskQueue/RedisTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/Transforms/AWSTransfomers/ClaimCheck/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/Transforms/AWSTransfomers/CloudEvents/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 | samples/Transforms/AWSTransfomers/Compression/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:34-41 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Startup.cs:54— samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Startup.cs:54-72 | samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Startup.cs:56-72 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Startup.cs:52-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:27— samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Controllers/GreetingsController.cs:27-33 | samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Controllers/GreetingsController.cs:27-33 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Controllers/GreetingsController.cs:27-33 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 5+ corresponding lines) · ×1
Edited copies of one member (8 members, 5+ corresponding lines) samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:43— samples/TaskQueue/KafkaDeferOnError/GreetingsSender/TimedMessageGenerator.cs:43-47 | samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/TimedMessageGenerator.cs:43-47 | samples/TaskQueue/KafkaSchemaRegistry/GreetingsSender/TimedMessageGenerator.cs:25-33 | samples/TaskQueue/KafkaTaskQueue/GreetingsSender/TimedMessageGenerator.cs:18-24 | samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:18-24 | samples/TaskQueue/MultiBus/GreetingsSender/TimedMessageGenerator.cs:18-24 | samples/TaskQueue/RMQDeferOnError/GreetingsSender/TimedMessageGenerator.cs:43-47 | samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsSender/TimedMessageGenerator.cs:43-47 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
Duplicated block (50–54 lines × 4) samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs:42— samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs:42-93 | samples/TaskQueue/KafkaDontAckOnError/GreetingsReceiverConsole/Program.cs:42-91 | samples/TaskQueue/KafkaTaskQueueWithDLQ/DlqConsole/Program.cs:42-94 | samples/TaskQueue/KafkaTaskQueueWithDLQ/GreetingsReceiverConsole/Program.cs:42-95 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs` and `samples/TaskQueue/KafkaDontAckOnError/GreetingsReceiverConsole/Program.cs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/TaskQueue/KafkaDeferOnError/GreetingsReceiverConsole/Program.cs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (48–51 lines × 3) samples/TaskQueue/RMQDeferOnError/GreetingsReceiverConsole/Program.cs:41— samples/TaskQueue/RMQDeferOnError/GreetingsReceiverConsole/Program.cs:41-88 | samples/TaskQueue/RMQTaskQueueWithDLQ/DlqConsole/Program.cs:41-89 | samples/TaskQueue/RMQTaskQueueWithDLQ/GreetingsReceiverConsole/Program.cs:41-91 — before extracting anything, compare `samples/TaskQueue/RMQDeferOnError/GreetingsReceiverConsole/Program.cs` and `samples/TaskQueue/RMQTaskQueueWithDLQ/DlqConsole/Program.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 `samples/TaskQueue/RMQDeferOnError/GreetingsReceiverConsole/Program.cs:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41–43 lines × 2) samples/TaskQueue/KafkaDeferOnError/GreetingsSender/Program.cs:40— samples/TaskQueue/KafkaDeferOnError/GreetingsSender/Program.cs:40-82 | samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/Program.cs:40-80 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/GreetingsSender/Program.cs` and `samples/TaskQueue/KafkaDontAckOnError/GreetingsSender/Program.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/TaskQueue/KafkaDeferOnError/GreetingsSender/Program.cs:40` it begins part-way through the construct above it, so those exact lines 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–22 lines × 2) samples/TaskQueue/KafkaTaskQueueWithDLQ/DlqConsole/DlqGreetingEventHandlerAsync.cs:36— samples/TaskQueue/KafkaTaskQueueWithDLQ/DlqConsole/DlqGreetingEventHandlerAsync.cs:36-57 | samples/TaskQueue/RMQTaskQueueWithDLQ/DlqConsole/DlqGreetingEventHandlerAsync.cs:37-56 — before extracting anything, compare `samples/TaskQueue/KafkaTaskQueueWithDLQ/DlqConsole/DlqGreetingEventHandlerAsync.cs` and `samples/TaskQueue/RMQTaskQueueWithDLQ/DlqConsole/DlqGreetingEventHandlerAsync.cs` 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 (19–20 lines × 2) samples/WebAPI/WebAPI_Dapper/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:75— samples/WebAPI/WebAPI_Dapper/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:75-94 | samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs:66-84 — 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 `samples/WebAPI/WebAPI_Dapper/GreetingsApp/Handlers/AddGreetingHandlerAsync.cs: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. 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 × 4) samples/TaskQueue/AWSTaskQueue/GreetingsSender/Program.cs:46— samples/TaskQueue/AWSTaskQueue/GreetingsSender/Program.cs:46-56 | samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs:49-59 | samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs:48-58 | samples/Transforms/AWSTransfomers/Compression/GreetingsSender/Program.cs:48-58 — before extracting anything, compare `samples/Transforms/AWSTransfomers/ClaimCheck/GreetingsSender/Program.cs` and `samples/Transforms/AWSTransfomers/CloudEvents/GreetingsSender/Program.cs` as WHOLE FILES: this scan already matched 4 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 `samples/TaskQueue/AWSTaskQueue/GreetingsSender/Program.cs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–11 lines × 6) samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43— samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43-51 | samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:43-51 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:46-56 | samples/TaskQueue/KafkaTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:46-56 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/AnotherGreetingEventMessageMapperAsync.cs:46-56 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:46-56 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` and `samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `GreetingEvent` in one and `AnotherGreetingEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–10 lines × 2) samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:16— samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:16-24 | samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs:16-25 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Mappers/GreetingMadeMessageMapperAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/GreetingsPolicy.cs:13— samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/GreetingsPolicy.cs:13-18 | samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/GreetingsPolicy.cs:13-19 — before extracting anything, compare `samples/WebAPI/WebAPI_Dynamo/GreetingsApp/Policies/GreetingsPolicy.cs` and `samples/WebAPI/WebAPI_EFCore/GreetingsApp/Policies/GreetingsPolicy.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 8) samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42— samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-46 | samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-46 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-49 | samples/TaskQueue/KafkaTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-49 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/AnotherGreetingEventMessageMapperAsync.cs:44-49 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:44-49 | samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-46 | samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42-46 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` and `samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:42` it does not close everything it opens, so those 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 `request` to `GreetingEvent` in one and `AnotherGreetingEvent` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 8) samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:38— samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:38-50 | samples/Scheduler/QuartzTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:38-50 | samples/TaskQueue/ASBTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:16-35 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:38-50 | samples/TaskQueue/MsSqlMessagingGateway/Events/Ports/Mappers/GreetingEventMessageMapper.cs:37-49 | samples/TaskQueue/RedisTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:37-49 | samples/Transforms/AWSTransfomers/ClaimCheck/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:42-55 | samples/Transforms/AWSTransfomers/Compression/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:48-61 — before extracting anything, compare `samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs` and `samples/Scheduler/QuartzTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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, `samples/Transforms/AWSTransfomers/ClaimCheck/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:40` calls `ClaimCheck` and `samples/Scheduler/AwsTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapper.cs:35` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 6) samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35— samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 | samples/Scheduler/QuartzTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 | samples/TaskQueue/AWSTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 | samples/Transforms/AWSTransfomers/ClaimCheck/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 | samples/Transforms/AWSTransfomers/CloudEvents/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 | samples/Transforms/AWSTransfomers/Compression/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:35-41 — before extracting anything, compare `samples/Scheduler/AwsTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs` and `samples/Scheduler/QuartzTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 5) samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:47— samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:47-60 | samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:47-60 | samples/TaskQueue/KafkaTaskQueueWithDLQ/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:40-54 | samples/TaskQueue/RMQDeferOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:47-60 | samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:41-54 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs` and `samples/TaskQueue/RMQDeferOnError/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 7) samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:54— samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:54-58 | samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:54-58 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:59-63 | samples/TaskQueue/KafkaTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:59-63 | samples/TaskQueue/MultiBus/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:59-63 | samples/TaskQueue/RMQDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:52-56 | samples/TaskQueue/RMQTaskQueueWithDLQ/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs:52-56 — before extracting anything, compare `samples/TaskQueue/KafkaDeferOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` and `samples/TaskQueue/KafkaDontAckOnError/Greetings/Ports/Mappers/GreetingEventMessageMapperAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 3) samples/TaskQueue/KafkaSchemaRegistry/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:37— samples/TaskQueue/KafkaSchemaRegistry/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:37-43 | samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs:37-43 | samples/TaskQueue/MultiBus/Greetings/Ports/CommandHandlers/GreetingEventHandler.cs:37-43 — before extracting anything, compare `samples/TaskQueue/KafkaSchemaRegistry/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs` and `samples/TaskQueue/KafkaTaskQueue/Greetings/Ports/CommandHandlers/GreetingEventHandlerAsync.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D8 · Code Coverage· No test project references Paramore.Brighter.MsSql.Azure · ×1
No test project references Paramore.Brighter.MsSql.Azure src/Paramore.Brighter.MsSql.Azure/Paramore.Brighter.MsSql.Azure.csproj— No test project in this repository references Paramore.Brighter.MsSql.Azure (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 31.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fr15Diagnostic · ×1
No test project references Fr15Diagnostic bugfixes/0037-gcp-requeue-immediate-redelivery/diagnostic/Fr15Diagnostic.csproj— No test project in this repository references Fr15Diagnostic (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 31.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Paramore.Brighter.Dapper · ×1
No test project references Paramore.Brighter.Dapper src/Paramore.Brighter.Dapper/Paramore.Brighter.Dapper.csproj— No test project in this repository references Paramore.Brighter.Dapper (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 31.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references pileup · ×1
No test project references pileup bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/pileup.csproj— No test project in this repository references pileup (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 31.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references starve · ×1
No test project references starve bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/starve.csproj— No test project in this repository references starve (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 31.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
Sync-over-async (deadlock risk) through `.Wait(…)` src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs:56— `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
X18 · Disposal-pattern correctness· Owned disposable field overwritten without releasing the previous instance · ×1
Owned disposable field overwritten without releasing the previous instance src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs:162— `Channel` is a `IModel` this type creates itself, and here (line 162) a new instance is written over it — but `ConnectToBroker` itself reads through `Channel` before replacing it, so it expects an instance to be there, and nothing earlier in `ConnectToBroker` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`Channel?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
Swallowed exception (caught, then discarded) src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGatewayConnectionPool.cs:188— `catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Orphaned file src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs: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 src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs: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 src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs: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 src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs: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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs: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 src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs: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 src/Paramore.Brighter.MessageScheduler.TickerQ/TickerQScheduler.cs: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 src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs: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 src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs: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 src/Paramore.Brighter.Transformers.MongoGridFS/MongoDbLuggageStore.cs: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 src/Paramore.Brighter/Policies/Handlers/TimeoutPolicyHandler.cs: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 src/Paramore.Brighter/RequestHandlerAsync.cs: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 src/Paramore.Brighter.Transformers.MassTransit/MassTransitTransform.cs: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 src/Paramore.Brighter.MessageScheduler.Hangfire/HangfireMessageScheduler.cs: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 src/Paramore.Brighter.Transformers.JustSaying/JustSayingTransform.cs: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 src/Paramore.Brighter.Transformers.Gcp/GcsLuggageOptions.cs: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 src/Paramore.Brighter/Transforms/Storage/FileSystemStorageProvider.cs: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 src/Paramore.Brighter/RequestHandler.cs: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 src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessagingGatewayConnection.cs: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 src/Paramore.Brighter.Transformers.MassTransit/MassTransitMessageMapper.cs: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 src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs: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 src/Paramore.Brighter/MessageMappers/CloudEventJsonMessageMapper.cs: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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageSender.cs: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.
redundant comment src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:208— "global secondary indexes" repeats the code it sits on: 3 of its 3 words (global, secondary, indexes) are already in `var gsiMap = new Dictionary<string, GlobalSecondaryIndex>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs:282— "local secondary indexes" repeats the code it sits on: 3 of its 3 words (local, secondary, indexes) are already in `var lsiList = new List<LocalSecondaryIndex>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:190— "global secondary indexes" repeats the code it sits on: 3 of its 3 words (global, secondary, indexes) are already in `var gsiMap = new Dictionary<string, GlobalSecondaryIndex?>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.DynamoDb/DynamoDbTableFactory.cs:264— "local secondary indexes" repeats the code it sits on: 3 of its 3 words (local, secondary, indexes) are already in `var lsiList = new List<LocalSecondaryIndex>();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs:350— "register the generic interface with the transaction type" repeats the code it sits on: 4 of its 5 words (generic, interface, transaction, type) are already in `var boxProviderType = transactionProviderInterface.MakeGenericType(transactionType);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:304— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:305— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.Inbox.Firestore/FirestoreInbox.cs:624— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.Inbox.MongoDb/MongoDbInbox.cs:288— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessagePublisher.cs:65— "Add Brighter message properties to the Azure Service Bus message" repeats the code it sits on: 6 of its 7 words (add, brighter, message, azure, service, bus) are already in `azureServiceBusMessage.MessageId = message.Header.MessageId;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpMessageProducer.cs:68— "Write instrumentation event for the producer" repeats the code it sits on: 4 of its 4 words (write, instrumentation, event, producer) are already in `BrighterTracer.WriteProducerEvent(Span, MessagingSystem.PubSub, message, instrumentation);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubProducerRegistryFactory.cs:21— "Create the message producer factory" repeats the code it sits on: 4 of its 4 words (create, message, producer, factory) are already in `var factory = new GcpPubSubMessageProducerFactory(connection, publications);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPubSubProducerRegistryFactory.cs:37— "Create the message producer factory" repeats the code it sits on: 4 of its 4 words (create, message, producer, factory) are already in `var factory = new GcpPubSubMessageProducerFactory(connection, publications);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:700— "Set queue type for quorum queues" repeats the code it sits on: 4 of its 5 words (queue, type, quorum, queues) are already in `if (_queueType == QueueType.Quorum)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageGateway.cs:138— "we store the message at topic + msg id" repeats the code it sits on: 5 of its 5 words (store, message, topic, msg, id) are already in `var key = Topic + "." + msgId.ToString();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageGateway.cs:151— "we store the message at topic + msg id" repeats the code it sits on: 5 of its 5 words (store, message, topic, msg, id) are already in `var key = Topic + "." + msgId.ToString();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:152— "increment a counter to get the next message id" repeats the code it sits on: 5 of its 6 words (increment, counter, next, message, id) are already in `var nextMsgId = IncrementMessageCounter(client);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageProducer.cs:201— "increment a counter to get the next message id" repeats the code it sits on: 5 of its 6 words (increment, counter, next, message, id) are already in `var nextMsgId = await IncrementMessageCounterAsync(client, cancellationToken);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.ServiceActivator/Proactor.cs:499— "Make the generic method with the runtime type" repeats the code it sits on: 4 of its 5 words (make, generic, method, type) are already in `typedPipelineFactory = pipelineFactory!.MakeGenericMethod(requestType);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.ServiceActivator/Proactor.cs:596— "Call UnwrapAsync on the pipeline" repeats the code it sits on: 4 of its 4 words (call, unwrap, async, pipeline) are already in `var unwrapMethod = pipeline!.GetType().GetMethod("UnwrapAsync");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.ServiceActivator/Reactor.cs:512— "Make the generic method with the runtime type" repeats the code it sits on: 4 of its 5 words (make, generic, method, type) are already in `typedPipelineFactory = pipelineFactory!.MakeGenericMethod(requestType);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter.ServiceActivator/Reactor.cs:589— "Call Unwrap on the pipeline" repeats the code it sits on: 3 of its 3 words (call, unwrap, pipeline) are already in `var unwrapMethod = pipeline!.GetType().GetMethod("Unwrap");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter/InMemoryInbox.cs:400— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter/InMemoryOutbox.cs:839— "Reads the causation id from the request context bag, if present" repeats the code it sits on: 6 of its 7 words (reads, causation, id, request, context, bag) are already in `private static string? ReadCausationId(RequestContext? requestContext)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Paramore.Brighter/RelationDatabaseOutbox.cs:1759— "Async counterpart of MapBoolFunction." repeats the code it sits on: 4 of its 5 words (async, map, bool, function) are already in `protected virtual Task<bool> MapBoolFunctionAsync(DbDataReader dr, CancellationToken cancellationToken)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Duplicated predicate src/Paramore.Brighter.Outbox.MySql/MySqlOutbox.cs:85— `!TryGetOrdinal(dr, TimestampColumnName, out var ordinal) || dr.IsDBNull(ordinal)` appears character-identically in 3 files — src/Paramore.Brighter.Outbox.MySql/MySqlOutbox.cs, src/Paramore.Brighter.Outbox.Sqlite/SqliteOutbox.cs, src/Paramore.Brighter/RelationDatabaseOutbox.cs. 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 src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs:171— `!Volatile.Read(ref _purging) && _messages.TryDequeue(out var message)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.RMQ.Async/PullConsumer.cs, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/PullConsumer.cs. 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 src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs:234— `!_headersToReset.Contains(header.Key) && !MessageHeader.IsLocalHeader(header.Key)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagePublisher.cs, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessagePublisher.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:366— `!isDLQ && sqsAttributes.RedrivePolicy != null` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs. 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 src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFiredHandler.cs:22— `!string.IsNullOrEmpty(command.RequestType) && !string.IsNullOrEmpty(command.RequestData)` appears character-identically in 3 files — src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFiredHandler.cs, src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFiredHandler.cs, src/Paramore.Brighter.MessageScheduler.Azure/AzureSchedulerFiredHandler.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs:508— `"sqs".Equals(sub.Protocol, StringComparison.OrdinalIgnoreCase) && sub.Endpoint == queueArn` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/AWSMessagingGateway.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs:75— `(topicAttributes.HttpStatusCode == HttpStatusCode.OK) && (topicAttributes.Attributes["TopicArn"] == topicArn)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArn.cs. 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 src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs:481— `DelaySupported || timeout <= TimeSpan.Zero` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageConsumer.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:191— `HeaderNames.IsKnown(attribute.Key) || bag.ContainsKey(attribute.Key)` appears character-identically in 4 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageCreator.cs. 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 src/Paramore.Brighter/AndSpecification.cs:79— `IsSatisfiedBy(x) || !other.IsSatisfiedBy(x)` appears character-identically in 2 files — src/Paramore.Brighter/AndSpecification.cs, src/Paramore.Brighter/Specification.cs. 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 src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs:94— `MakeRole == OnMissingRole.Assume && Arn.IsArn(role)` appears character-identically in 2 files — src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsSchedulerFactory.cs, src/Paramore.Brighter.MessageScheduler.AWS/AwsSchedulerFactory.cs. 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 src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueMessageProducer.cs:65— `TopicCreated || Publication.MakeChannels.Equals(OnMissingChannel.Assume)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusQueueMessageProducer.cs, src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusTopicMessageProducer.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:165— `_deadLetterProducer == null && _invalidMessageProducer == null` appears character-identically in 7 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.MQTT/MQTTMessageConsumer.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:457— `_deadLetterProducer?.IsValueCreated == true && _deadLetterProducer.Value is IAsyncDisposable deadLetterAsync` appears character-identically in 3 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs. 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 src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:180— `_inbox is not IAmACausationTrackingInbox trackingInbox || _outbox is null` appears character-identically in 2 files — src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs, src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs:462— `_invalidMessageProducer?.IsValueCreated == true && _invalidMessageProducer.Value is IAsyncDisposable invalidAsync` appears character-identically in 3 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsMessageConsumer.cs, src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageConsumer.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:278— `_messageAttributes.TryGetValue(HeaderNames.DataSchema, out var source) && Uri.TryCreate(source.GetValueInString(), UriKind.RelativeOrAbsolut…` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:332— `_messageAttributes.TryGetValue(HeaderNames.HandledCount, out var handledCount) && int.TryParse(handledCount.GetValueInString(), out var hc)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:255— `_messageAttributes.TryGetValue(HeaderNames.LEGACY_SOURCE, out source) && Uri.TryCreate(source.GetValueInString(), UriKind.RelativeOrAbsolute…` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:249— `_messageAttributes.TryGetValue(HeaderNames.Source, out var source) && Uri.TryCreate(source.GetValueInString(), UriKind.RelativeOrAbsolute, o…` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:301— `_messageAttributes.TryGetValue(HeaderNames.Time, out var timeStamp) && DateTimeOffset.TryParse(timeStamp.GetValueInString(), out value)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs:307— `_messageAttributes.TryGetValue(HeaderNames.Timestamp, out timeStamp) && DateTimeOffset.TryParse(timeStamp.GetValueInString(), out value)` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsInlineMessageCreator.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsInlineMessageCreator.cs. 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 src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs:158— `_onceOnlyAction is OnceOnlyAction.Replay && Interlocked.CompareExchange(ref s_warnedAboutCustomContext, 1, 0) == 0` appears character-identically in 2 files — src/Paramore.Brighter/Inbox/Handlers/UseInboxHandler.cs, src/Paramore.Brighter/Inbox/Handlers/UseInboxHandlerAsync.cs. 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 src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs:152— `_pooledConnection == null || !_pooledConnection.IsOpen` appears character-identically in 2 files — src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageGateway.cs, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageGateway.cs. 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 src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:363— `args != null && args.TryGetValue("Topic", out var topic)` appears character-identically in 2 files — src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs, src/Paramore.Brighter.Outbox.MongoDb/MongoDbOutbox.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Disabled test tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:44— A test is skipped ("Deferred: #4240 — reject with unacceptable reason to invalid channel not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:63— A test is skipped ("Deferred: #4240 — requeue budget exhausted to DLQ not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:43— A test is skipped ("Deferred: #4240 — reject with unacceptable reason to invalid channel not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:59— A test is skipped ("Deferred: #4240 — requeue budget exhausted to DLQ not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Bulk_Clearing_The_PostBox_On_The_Command_Processor_Async.cs:88— A test is skipped ("Erratic due to timing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Implicit_Clearing_The_PostBox_On_The_Command_Processor.cs:81— A test is skipped ("Erratic due to timing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/CommandProcessors/Post/When_Posting_Via_A_Control_Bus_Sender_Async.cs:72— A test is skipped ("Requires publisher confirmation") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported.cs:106— A test is skipped ("This test is fragile due to background processing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported_Bulk.cs:106— A test is skipped ("This test is fragile due to background processing") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_failing_a_timeout_policy_check.cs:60— A test is skipped ("Replace with Polly Timeout") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_passing_a_timeout_policy_check.cs:58— A test is skipped ("Replace with Polly Timeout") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:70— A test is skipped ("measurement — AC-39") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:132— A test is skipped ("measurement — AC-39") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:48— A test is skipped ("Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:95— A test is skipped ("Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:48— A test is skipped ("Deferred: #4240 — no channels configured: acknowledge and log not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_should_be_redelivered.cs:46— A test is skipped ("Deferred: #4240 — canonical plain requeue not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:46— A test is skipped ("Deferred: #4240 — requeue with delay not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_zero_delay_should_redeliver_immediately.cs:46— A test is skipped ("Deferred: #4240 — explicit zero-delay requeue not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_sending_a_delayed_message_should_deliver_after_delay.cs:46— A test is skipped ("Deferred: #4240 — delayed send not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_nacking_a_message_it_should_be_redelivered.cs:47— A test is skipped ("Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_nacking_a_message_it_should_be_redelivered.cs:89— A test is skipped ("Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:47— A test is skipped ("Deferred: #4240 — no channels configured: acknowledge and log not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_should_be_redelivered.cs:40— A test is skipped ("Deferred: #4240 — canonical plain requeue not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:44— A test is skipped ("Deferred: #4240 — requeue with delay not yet conformant for GCP / Pull (maintainer sign-off)") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Silent fallback default in catch src/Paramore.Brighter.Extensions.DependencyInjection/AmbientScopeProbe.cs:62— `CanResolveFrom` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:222— `ExistsAsync` swallows `RequestNotFoundException<T>` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:214— `ExistsAsync` swallows `RequestNotFoundException<T>` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessageScheduler.AWS.V4/AwsScheduler.cs:156— `ReSchedulerCoreAsync` swallows `ResourceNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessageScheduler.AWS/AwsScheduler.cs:156— `ReSchedulerCoreAsync` swallows `ResourceNotFoundException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs:291— `QueueExistsAsync` swallows `QueueDoesNotExistException` and sets `exists = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ValidateTopicByArn.cs:77— `ValidateAsync` swallows `InternalErrorException` and sets `exists = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessagingGateway.AWSSQS/ChannelFactory.cs:291— `QueueExistsAsync` swallows `QueueDoesNotExistException` and sets `exists = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.MessagingGateway.AWSSQS/ValidateTopicByArn.cs:77— `ValidateAsync` swallows `InternalErrorException` and sets `exists = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:257— `Get` swallows `RpcException` into `return new Message();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Outbox.Firestore/FirestoreOutbox.cs:727— `GetAsync` swallows `RpcException` into `return new Message();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:144— `HasClaimAsync` swallows `GoogleApiException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs:270— `HasClaim` swallows `GoogleApiException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter/InMemoryScheduledTimer.cs:87— `TryChange` swallows `ObjectDisposedException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Paramore.Brighter/Tasks/BatchedCallbackQueue.cs:132— `TryAdd` swallows `InvalidOperationException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected samples/Scheduler/TickerQ/Greeting.Consumer/Program.cs:9— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:17— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/TaskQueue/ASBTaskQueue/GreetingsSender.Web/Program.cs:19— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/TaskQueue/ASBTaskQueue/GreetingsWorker/Program.cs:20— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_Dapper/GreetingsWeb/Program.cs:25— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_Dapper/Greetings_Sweeper/Program.cs:19— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_Dapper/Salutation_Sweeper/Program.cs:19— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_Dynamo/GreetingsWeb/Program.cs:12— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_Dynamo/Greetings_Sweeper/Program.cs:14— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_EFCore/GreetingsWeb/Program.cs:18— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_EFCore/Greetings_Sweeper/Program.cs:12— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected samples/WebAPI/WebAPI_mTLS_TestHarness/TodoApi/Program.cs:8— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
D20 · ADR Quality· ADR still proposed, but the code already adopted it · ×12
ADR still proposed, but the code already adopted it docs/adr/0024-scheduling-requests-and-messages.md:4— docs/adr/0024-scheduling-requests-and-messages.md:4 says "Proposed", but the production code already uses every element its Decision names: `IAmACommandProcessor` (src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionExtensions.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0030-add-a-mediator.md:4— docs/adr/0030-add-a-mediator.md:4 says "Proposed", but the production code already uses every element its Decision names: `Mediator` (src/Paramore.Brighter.Mediator/IAmAJobChannel.cs), `Command` (src/Paramore.Brighter.MessageScheduler.AWS.V4/FireAwsScheduler.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0037-provide-roslyn-analyzers-for-brighter.md:4— docs/adr/0037-provide-roslyn-analyzers-for-brighter.md:4 says "Proposed", but the production code already uses every element its Decision names: `Paramore.Brighter.Analyzer` (src/Paramore.Brighter.Analyzer/Analyzers/PublicationRequestTypeAssignmentAnalyzer.cs), `Publication` (src/Paramore.Brighter.AsyncAPI/AsyncApiBrighterBuilderExtensions.cs), `RequestType` (src/Paramore.Brighter.AsyncAPI/AsyncApiDocumentGenerator.cs), `IRequest` (src/Paramore.Brighter.AsyncAPI/AsyncApiDocumentGenerator.cs), `Subscription` (src/Paramore.Brighter.AsyncAPI/AsyncApiDocumentGenerator.cs), `MapToMessage` (src/Paramore.Brighter.Analyzer/Analyzers/WrapAttributeAnalyzer.cs), `MapToRequest` (src/Paramore.Brighter.Analyzer/Analyzers/WrapAttributeAnalyzer.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0043-rabbitmq-mutual-tls.md:4— docs/adr/0043-rabbitmq-mutual-tls.md:4 says "Proposed", but the production code already uses every element its Decision names: `X509Certificate2` (src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessagingGatewayConnection.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0054-roslyn-analyzer-extensions-for-pipeline-validation.md:4— docs/adr/0054-roslyn-analyzer-extensions-for-pipeline-validation.md:4 says "Proposed", but the production code already uses every element its Decision names: `Paramore.Brighter.Analyzer` (src/Paramore.Brighter.Analyzer/Analyzers/PublicationRequestTypeAssignmentAnalyzer.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0073-azure-service-bus-publication-time-to-live.md:4— docs/adr/0073-azure-service-bus-publication-time-to-live.md:4 says "Proposed", but the production code already uses every element its Decision names: `TimeSpan` (src/Paramore.Brighter.BoxProvisioning.MsSql/IMsSqlAdvisoryLock.cs), `TimeToLive` (src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageProducer.cs), `AzureServiceBusPublication` (src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumerFactory.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0073-kafka-consumer-protocol-missing-topic-detection.md:4— docs/adr/0073-kafka-consumer-protocol-missing-topic-detection.md:4 says "Proposed", but the production code already uses every element its Decision names: `ConsumerGroupProtocol` (src/Paramore.Brighter.MessagingGateway.Kafka/ConsumerGroupProtocol.cs), `OnMissingChannel.Assume` (src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/AWSMessagingGateway.cs), `ISpecification` (src/Paramore.Brighter.Extensions.DependencyInjection/BrighterPipelineValidationExtensions.cs), `ValidatePipelines` (src/Paramore.Brighter.Extensions.DependencyInjection/BrighterPipelineValidationExtensions.cs), `IGroupProtocol` (src/Paramore.Brighter.MessagingGateway.Kafka/ClassicGroupProtocol.cs), `ConfigHook` (src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageConsumerFactory.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0074-isolate-publish-resilience-context.md:4— docs/adr/0074-isolate-publish-resilience-context.md:4 says "Proposed", but the production code already uses every element its Decision names: `Publish` (src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusRequeueScheduler.cs), `PublishAsync` (src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SnsMessageProducer.cs), `IRequestContext` (src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionSubscriberRegistry.cs), `Send` (src/Paramore.Brighter.AsyncAPI/AsyncApiDocumentGenerator.cs), `SendAsync` (src/Paramore.Brighter.Mediator/Tasks.cs), `CreateCopy` (src/Paramore.Brighter/IRequestContext.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0080-share-resilience-registry-between-handlers-and-producers.md:4— docs/adr/0080-share-resilience-registry-between-handlers-and-producers.md:4 says "Proposed", but the production code already uses every element its Decision names: `AddBrighterDefault` (src/Paramore.Brighter.Extensions.DependencyInjection/BrighterResiliencePipelineRegistry.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0082-isolate-azure-service-bus-subscription-retries.md:4— docs/adr/0082-isolate-azure-service-bus-subscription-retries.md:4 says "Proposed", but the production code already uses every element its Decision names: `ForwardTo` (src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusConsumer.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0085-gcp-purge-server-boundary.md:4— docs/adr/0085-gcp-purge-server-boundary.md:4 says "Proposed", but the production code already uses every element its Decision names: `PublishTime` (src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPurgeWatermark.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
ADR still proposed, but the code already adopted it docs/adr/0089-mssql-explicit-subscriber-queues.md:4— docs/adr/0089-mssql-explicit-subscriber-queues.md:4 says "Proposed", but the production code already uses every element its Decision names: `MsSqlPublication.SubscriberChannels` (src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlPublication.cs), `Topic` (src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProviderOptions.cs). A proposal the code has adopted is a decision in force; mark it accepted, or, if the code should not do this, say so.
README/code drift CONTRIBUTING.md:56— CONTRIBUTING.md names .NET 8, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:29— README.md names .NET 8, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0001-kafka-dead-letter-queue/README.md:41— specs/0001-kafka-dead-letter-queue/README.md links to `../../docs/Kafka-DeadLetterQueue-Usage.md`, but `docs/Kafka-DeadLetterQueue-Usage.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0010-aws-sqs-dead-letter-queue/README.md:30— specs/0010-aws-sqs-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0011-redis-dead-letter-queue/README.md:30— specs/0011-redis-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0012-mssql-dead-letter-queue/README.md:30— specs/0012-mssql-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0013-postgres-dead-letter-queue/README.md:30— specs/0013-postgres-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0014-rocketmq-dead-letter-queue/README.md:31— specs/0014-rocketmq-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0015-mqtt-dead-letter-queue/README.md:30— specs/0015-mqtt-dead-letter-queue/README.md links to `../../docs/adr/0036-message-rejection-routing-strategy.md`, but `docs/adr/0036-message-rejection-routing-strategy.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift specs/0023-asyncapi-document-generation/README.md:16— specs/0023-asyncapi-document-generation/README.md links to `../../docs/adr/0040-asyncapi-document-generation.md`, but `docs/adr/0040-asyncapi-document-generation.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/features/asyncapi-sdk-adoption/RESEARCH.md:442— docs/features/asyncapi-sdk-adoption/RESEARCH.md names .NET 6, but the projects target .NET 9, 10. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P2 · Observability· Console output used as the logging channel · ×8
Console output used as the logging channel samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:35— `samples/AsyncAPI/KafkaAsyncAPI/Handlers/PaymentReceivedEventHandler.cs` reports through `Console.Write…` at line 35 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs:35— `samples/AsyncAPI/RMQAsyncAPI/Handlers/PaymentReceivedEventHandler.cs` reports through `Console.Write…` at line 35 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:72— `samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 72 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:78— `samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 78 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs:84— `samples/TaskQueue/KafkaDynamicEventStream/TaskStatusSender/TimedStatusSender.cs` reports through `Console.Write…` at line 84 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/Transforms/JustSaying/BrighterSide/Program.cs:63— `samples/Transforms/JustSaying/BrighterSide/Program.cs` reports through `Console.Write…` at line 63 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/Transforms/JustSaying/JustSayingSide/Program.cs:34— `samples/Transforms/JustSaying/JustSayingSide/Program.cs` reports through `Console.Write…` at line 34 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel samples/Transforms/MassTransit/MBrigtherSide/Program.cs:63— `samples/Transforms/MassTransit/MBrigtherSide/Program.cs` reports through `Console.Write…` at line 63 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 116 significant file(s) lose their only recent owner: src/Paramore.Brighter.Extensions.DependencyInjection/ServiceProviderLifetimeScope.cs, src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpPullMessageConsumer.cs, src/Paramore.Brighter.BoxProvisioning/SqlBoxMigrationRunner.cs, REDACTED, REDACTED, src/Paramore.Brighter.Extensions.DependencyInjection/ScopeConfigurationRules.cs, src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerBoxMigrationRunner.cs, REDACTED (+108 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 20 significant file(s) lose their only recent owner: src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/AdministrationClientWrapper.cs, src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusRequeueScheduler.cs, src/Paramore.Brighter.MessageScheduler.Quartz/QuartzScheduler.cs, src/Paramore.Brighter.MessagingGateway.GcpPubSub/GcpSubscriptionPurger.cs, src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusWrappers/ServiceBusLock.cs, src/Paramore.Brighter.Extensions.DependencyInjection/IBrighterBuilder.cs, src/Paramore.Brighter.Mediator/Scheduler.cs, src/Paramore.Brighter/Scheduler/ScheduledRequestContext.cs (+12 more). 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: src/Paramore.Brighter.AsyncAPI/AsyncApiDocumentGenerator.cs, src/Paramore.Brighter.AsyncAPI/AsyncApiHostExtensions.cs, src/Paramore.Brighter.AsyncAPI/SchemaHoister.cs, src/Paramore.Brighter.AsyncAPI/AsyncApiBrighterBuilderExtensions.cs, src/Paramore.Brighter.AsyncAPI.NJsonSchema/NJsonSchemaGenerator.cs, src/Paramore.Brighter.AsyncAPI/AsyncApiOptions.cs, src/Paramore.Brighter.AsyncAPI/IAmASchemaGenerator.cs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 7 significant file(s) lose their only recent owner: src/Paramore.Brighter/Validation/ProducerValidationRules.cs, src/Paramore.Brighter.Validation.FluentValidation/FluentValidationRequestHandler.cs, src/Paramore.Brighter.Validation.Specification/SpecificationBuilderExtensions.cs, src/Paramore.Brighter.Validation.FluentValidation/FluentValidationBuilderExtensions.cs, src/Paramore.Brighter.Validation.FluentValidation/FluentValidationRequestHandlerAsync.cs, src/Paramore.Brighter.Extensions.DependencyInjection/ServiceCollectionTransformerResolvabilityProbe.cs, src/Paramore.Brighter/Validation/IAmATransformerResolvabilityProbe.cs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 3 significant file(s) lose their only recent owner: src/Paramore.Brighter/Observability/OutboxMeter.cs, src/Paramore.Brighter/Observability/IAmABrighterOutboxMeter.cs, src/Paramore.Brighter/Observability/OutboxClearSource.cs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 3 significant file(s) lose their only recent owner: src/Paramore.Brighter.MySql/MySqlTransactionProvider.cs, src/Paramore.Brighter.Sqlite.EntityFrameworkCore/SqliteEntityFrameworkTransactionProvider.cs, src/Paramore.Brighter.PostgreSql.EntityFrameworkCore/PostgreSqlEntityFrameworkTransactionProvider.cs. Pair on, review, or document these before any departure.
ADR not followed: Provide a Dead Letter Channel Where Native Support is Missing docs/adr/0045-provide-dlq-where-missing.md:73— docs/adr/0045-provide-dlq-where-missing.md:73 rules out `Message` in option, but production code uses it: src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProviderOptions.cs:51, src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProviderOptions.cs:66. Remove the use, or supersede the record if the decision changed.
ADR not followed: Failed Delivery Context for Confirmation-Based Producers docs/adr/0063-failed-delivery-context.md:46— docs/adr/0063-failed-delivery-context.md:46 rules out `Async` in producer, but production code uses it: samples/Scheduler/TickerQ/Greeting.Producer/Program.cs:7. Remove the use, or supersede the record if the decision changed.
ADR not followed: Failed Delivery Context for Confirmation-Based Producers docs/adr/0063-failed-delivery-context.md:46— docs/adr/0063-failed-delivery-context.md:46 rules out `Send` in producer, but production code uses it: src/Paramore.Brighter.MessagingGateway.RocketMQ/RocketMqMessageProducer.cs:77, src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs:230, REDACTED:128, src/Paramore.Brighter.MessagingGateway.MsSql/MsSqlMessageProducer.cs:158, src/Paramore.Brighter/InMemoryMessageProducer.cs:327 (+2 more). Remove the use, or supersede the record if the decision changed.
ADR not followed: Failed Delivery Context for Confirmation-Based Producers docs/adr/0063-failed-delivery-context.md:48— docs/adr/0063-failed-delivery-context.md:48 rules out `Send` in Producer, but production code uses it: src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageProducer.cs:230, REDACTED:128, src/Paramore.Brighter/InMemoryMessageProducer.cs:327, bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:146, bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs:147. Remove the use, or supersede the record if the decision changed.
ADR not followed: Validate Pipeline Assembly Scanning and Validation-Provider Registration docs/adr/0064-validate-pipeline-assembly-and-provider-registration.md:62— docs/adr/0064-validate-pipeline-assembly-and-provider-registration.md:62 rules out `throwOnError`, but production code uses it: src/Paramore.Brighter.Extensions.DependencyInjection/BrighterPipelineValidationExtensions.cs:65. Remove the use, or supersede the record if the decision changed.
ADR not followed: Validate Subscription and Channel Factory Compatibility at Startup docs/adr/0072-subscription-channel-factory-compatibility.md:123— docs/adr/0072-subscription-channel-factory-compatibility.md:123 rules out `PipelineValidator`, but production code uses it: src/Paramore.Brighter.Extensions.DependencyInjection/BrighterPipelineValidationExtensions.cs:99. Remove the use, or supersede the record if the decision changed.
Silent fallback default on parse failure src/Paramore.Brighter.MessagingGateway.AzureServiceBus/AzureServiceBusMessageCreator.cs:312— `GetMessageType` falls back to `MessageType.MT_EVENT` when `Enum.TryParse(property.ToString(), true, out MessageType messageType)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Paramore.Brighter.MessagingGateway.Kafka/KafkaMessageCreator.cs:128— `SuccessMessage` falls back to `Id.Empty` when `headers.MessageId.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Paramore.Brighter.MessagingGateway.Redis/RedisMessageCreator.cs:179— `ReadHeader` falls back to `TimeSpan.Zero` when `delayed.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Paramore.Brighter.MessagingGateway.RMQ.Async/RmqMessageCreator.cs:218— `ReadHandledCount` falls back to `0` when `int.TryParse(Encoding.UTF8.GetString(value), out var handledCount)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Paramore.Brighter.MessagingGateway.RMQ.Sync/RmqMessageCreator.cs:216— `ReadHandledCount` falls back to `0` when `int.TryParse(Encoding.UTF8.GetString(value), out var handledCount)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Fat interface: IAmACommandProcessor (29 members) src/Paramore.Brighter/IAmACommandProcessor.cs:53— `IAmACommandProcessor` declares 29 members under just 11 distinct name(s): `Send`, `Send`, `Send`, `SendAsync`, `SendAsync`, `SendAsync`, `Publish`, `Publish`, `Publish`, `PublishAsync`, `PublishAsync`, `PublishAsync`, `Post`, `Post`, `Post`, `PostAsync`, `PostAsync`, `PostAsync`, `DepositPost`, `DepositPost`, `DepositPost`, `DepositPost`, `DepositPostAsync`, `DepositPostAsync`, `DepositPostAsync`, `DepositPostAsync`, `ClearOutbox`, `ClearOutboxAsync`, `Call`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 29 separate responsibilities: a caller binds to 11 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 29 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.
Fat interface: IAmProducersConfiguration (20 members) src/Paramore.Brighter/ProducersConfiguration.cs:32— `IAmProducersConfiguration` declares 20 members: `ArchiveBatchSize`, `ArchiveProvider`, `ConnectionProvider`, `DistributedLock`, `MessageMapperRegistry`, `Outbox`, `OutboxBulkChunkSize`, `OutboxTimeout`, `MaxOutStandingMessages`, `MaxOutStandingCheckInterval`, `OutBoxBag`, `ProducerRegistry`, `ResponseChannelFactory`, `ReplyQueueSubscriptions`, `RequestContextFactory`, `MessageSchedulerFactory`, `RequestSchedulerFactory`, `TransactionProvider`, `UseRpc`, `DefaultBoxConfiguration`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IAmABrighterTracer (20 members) src/Paramore.Brighter/Observability/IAmABrighterTracer.cs:33— `IAmABrighterTracer` declares 20 members: `ActivitySource`, `CreateSpan`, `CreateReceiveSpan`, `EnrichReceiveSpan`, `PropagateConsumerContext`, `CreateSpan`, `CreateArchiveSpan`, `CreateClaimCheckSpan`, `CreateBatchSpan`, `CreateMessagePumpSpan`, `CreateMessagePumpExceptionSpan`, `CreateClearSpan`, `CreateDbSpan`, `CreateProducerSpan`, `CreateConfirmationSpan`, `EndSpan`, `EndSpans`, `LinkSpans`, `AddExceptionToSpan`, `CreateCircuitBreakerSpan`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 20 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D20 · ADR Quality· ADR has no Consequences section · ×3
ADR has no Consequences section docs/adr/0024-scheduling-requests-and-messages.md:16— docs/adr/0024-scheduling-requests-and-messages.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Consequences section docs/adr/0026-use-source-generated-logging.md:15— docs/adr/0026-use-source-generated-logging.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ADR has no Consequences section docs/adr/0027-allow-custom-publication-finder.md:16— docs/adr/0027-allow-custom-publication-finder.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
ED3 · Event naming· Event not named in past tense · ×2
Event not named in past tense: EventSample samples/Analyzer/AnalyzerSamples/PublicationSample.cs:37— `EventSample` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
Event not named in past tense: SampleEvent samples/Analyzer/AnalyzerSamples/WrapWithMapperSample.cs:44— `SampleEvent` reads as an instruction, not a fact that happened: events describe something that already occurred. Name new events for the fact that occurred (e.g. `OrderPlaced`). Do not rename this one if it is already stored or published: its type name is written with every event recorded under it, so a rename can break replay of the stored stream and every subscriber that reads it, and a clearer name does not pay for that. If it has never been written or sent, renaming it now is safe.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (163 single-owned of 755 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; 755 of the 1170 production source files in this repository met that bar). They are anonymized user #7 (2 file(s)), anonymized user #8 (2 file(s)), anonymized user #9 (2 file(s)), anonymized user #10 (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: src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/SqsAttributes.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS/SqsAttributes.cs, src/Paramore.Brighter/ISupportPublishConfirmationAsync.cs, src/Paramore.Brighter/PublishConfirmationExtensions.cs, src/Paramore.Brighter.Outbox.Hosting/HostedServiceCollectionExtensions.cs, src/Paramore.Brighter.Firestore/FirestoreConfiguration.cs, src/Paramore.Brighter/MessageDelivery.cs.
D20 · ADR Quality· ADR superseded but its status says otherwise · ×1
ADR superseded but its status says otherwise docs/adr/0053-box-database-migration.md:4— docs/adr/0053-box-database-migration.md:4 says "Accepted", but docs/adr/0057-box-schema-versioning-and-migrations.md supersedes it. Two records now claim the same ground; mark this one "Superseded by" its successor.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion src/Paramore.Brighter/Paramore.Brighter.csproj:1— `Paramore.Brighter(netstandard2.0)` overshoots its size bounds (43006 LoC, 458 public types across 46 namespaces). 1 of 259 project(s) overshoot their size bounds, lowering Project Cohesion to 9.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Split Paramore.Brighter(netstandard2.0) src/Paramore.Brighter/Paramore.Brighter.csproj:1— `Paramore.Brighter(netstandard2.0)` overshoots its size bounds (43006 LoC, 458 public types across 46 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Actions`, `BindingAttributes`), so they are the cleanest seams: `Paramore.Brighter.Policies` (14 types in 14 files): 4 of 129 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 122 times; `Paramore.Brighter.Defer` (5 types in 4 files): 2 of 22 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 18 times; `Paramore.Brighter.Reject` (5 types in 4 files): 2 of 22 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 18 times. Extract each into its own project.
Pass-through layer src/Paramore.Brighter/Logging/ApplicationLogging.cs:44— ForwardingLogger: all 3 public methods forward their arguments unchanged to CurrentLogger and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call CurrentLogger directly, or give the layer a job.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 164 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: src/Paramore.Brighter.Transformers.AWS.V4/S3LuggageStore.cs, src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableFactory.cs, src/Paramore.Brighter.Outbox.DynamoDB.V4/MessageItem.cs, src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs, src/Paramore.Brighter.MessagingGateway.AWSSQS.V4/ChannelFactory.cs, src/Paramore.Brighter.Transformers.Gcp/GcsLuggageStore.cs, src/Paramore.Brighter.MessageScheduler.TickerQ/TickerQScheduler.cs, src/Paramore.Brighter.Transformers.Azure/AzureBlobLuggageStore.cs (and 156 more) (165 orphaned of 757 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; 757 of the 1170 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Commented-out code src/Paramore.Brighter/Observability/BrighterTracer.cs:901— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 12 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 96/140 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 140, 68 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 786/949 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted src/Paramore.Brighter/NullOutboxArchiveProvider.cs:70— `LogDebug` at line 70 is called with an argument built by `string.Join(",", messages.Select(m => m.Id.ToString()).ToArray())` (line 71), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Interpolated log message defeats structured logging src/Paramore.Brighter.Mediator/InMemoryStateStoreAsync.cs:114— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Nullable reference types not enabled everywhere — 126/219 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~1.4 `!` suppressions per 1k syntax nodes — 653 suppression(s) across the 451489 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Skipped (documented): When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel_async tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:44— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — reject with unacceptable reason to invalid channel not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)
Skipped (documented): When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue_async tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Proactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:63— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — requeue budget exhausted to DLQ not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)
Skipped (documented): When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_rejecting_message_with_unacceptable_reason_should_send_to_invalid_channel.cs:43— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — reject with unacceptable reason to invalid channel not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)
Skipped (documented): When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue tests/Paramore.Brighter.AzureServiceBus.Tests/MessagingGateway/Generated/Reactor/When_requeuing_a_message_too_many_times_should_move_to_dead_letter_queue.cs:59— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — requeue budget exhausted to DLQ not yet conformant for AzureServiceBus / AzureServiceBusMessagingGateway (maintainer sign-off)
Skipped (documented): When_Clearing_The_PostBox_On_The_Command_Processor_Async tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Bulk_Clearing_The_PostBox_On_The_Command_Processor_Async.cs:88— Skipped with a documented reason — a deferral, not lazy debt: Erratic due to timing
Skipped (documented): When_Implicit_Clearing_The_PostBox_On_The_Command_Processor tests/Paramore.Brighter.Core.Tests/CommandProcessors/Clear/When_Implicit_Clearing_The_PostBox_On_The_Command_Processor.cs:81— Skipped with a documented reason — a deferral, not lazy debt: Erratic due to timing
Skipped (documented): When_Posting_Via_A_Control_Bus_Sender_Async tests/Paramore.Brighter.Core.Tests/CommandProcessors/Post/When_Posting_Via_A_Control_Bus_Sender_Async.cs:72— Skipped with a documented reason — a deferral, not lazy debt: Requires publisher confirmation
Skipped (documented): When_Clearing_Outstanding_Messages_Spans_Are_Exported tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported.cs:106— Skipped with a documented reason — a deferral, not lazy debt: This test is fragile due to background processing
Skipped (documented): When_Clearing_Outstanding_Messages_Spans_Are_Exported tests/Paramore.Brighter.Core.Tests/Observability/CommandProcessor/Clear/When_Clearing_Outstanding_Messages_Spans_Are_Exported_Bulk.cs:106— Skipped with a documented reason — a deferral, not lazy debt: This test is fragile due to background processing
Skipped (documented): When_Sending_A_Command_To_The_Processor_Failing_A_Timeout_Policy_Check tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_failing_a_timeout_policy_check.cs:60— Skipped with a documented reason — a deferral, not lazy debt: Replace with Polly Timeout
Skipped (documented): When_Sending_A_Command_To_The_Processor_Passing_A_Timeout_Policy_Check tests/Paramore.Brighter.Core.Tests/Timeout/When_sending_a_command_to_the_processor_passing_a_timeout_policy_check.cs:58— Skipped with a documented reason — a deferral, not lazy debt: Replace with Polly Timeout
Skipped (documented): Measure_pull_delivery_attempt_over_three_deliveries_on_a_dlq_backed_subscription tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:70— Skipped with a documented reason — a deferral, not lazy debt: measurement — AC-39
Skipped (documented): Measure_stream_delivery_attempt_over_three_deliveries_on_a_dlq_backed_subscription tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/GcpDeliveryAttemptMeasurementTests.cs:132— Skipped with a documented reason — a deferral, not lazy debt: measurement — AC-39
Skipped (documented): When_nacking_a_message_it_should_be_redelivered_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:48— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_nacking_first_of_two_messages_should_redeliver_nacked_then_receive_second_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_nacking_a_message_it_should_be_redelivered.cs:95— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:48— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — no channels configured: acknowledge and log not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_requeuing_a_failed_message_should_be_redelivered_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_should_be_redelivered.cs:46— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — canonical plain requeue not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:46— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — requeue with delay not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_requeuing_a_failed_message_with_zero_delay_should_redeliver_immediately_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_requeuing_a_failed_message_with_zero_delay_should_redeliver_immediately.cs:46— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — explicit zero-delay requeue not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_sending_a_delayed_message_should_deliver_after_delay_async tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Proactor/When_sending_a_delayed_message_should_deliver_after_delay.cs:46— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — delayed send not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_nacking_a_message_it_should_be_redelivered tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_nacking_a_message_it_should_be_redelivered.cs:47— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_nacking_first_of_two_messages_should_redeliver_nacked_then_receive_second tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_nacking_a_message_it_should_be_redelivered.cs:89— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — Nack redelivers not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_rejecting_message_with_no_channels_configured_should_acknowledge_and_log.cs:47— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — no channels configured: acknowledge and log not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_requeuing_a_failed_message_should_be_redelivered tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_should_be_redelivered.cs:40— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — canonical plain requeue not yet conformant for GCP / Pull (maintainer sign-off)
Skipped (documented): When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay tests/Paramore.Brighter.Gcp.Tests/MessagingGateway/Pull/Generated/Reactor/When_requeuing_a_failed_message_with_delay_should_redeliver_after_delay.cs:44— Skipped with a documented reason — a deferral, not lazy debt: Deferred: #4240 — requeue with delay not yet conformant for GCP / Pull (maintainer sign-off)
doc comments repeat the names src/Paramore.Brighter/AsyncHandlerFactory.cs:29— 266 of 2003 documented parameters and 112 of 1977 summaries in `Paramore.Brighter(netstandard2.0)` only repeat the member or parameter name (e.g. "Class AsyncHandlerFactory" for `AsyncHandlerFactory`). 82 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Archive.Azure/AzureBlobArchiveProvider.cs:40— 2 of 5 documented parameters and 1 of 11 summaries in `Paramore.Brighter.Archive.Azure(netstandard2.0)` only repeat the member or parameter name (e.g. "The Cancellation Token" for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.BoxProvisioning/IAmABoxMigrationRunner.cs:55— 3 of 86 documented parameters and 1 of 105 summaries in `Paramore.Brighter.BoxProvisioning(netstandard2.0)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:51— 1 of 24 documented parameters and 0 of 30 summaries in `Paramore.Brighter.BoxProvisioning.MsSql(net462)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:50— 1 of 31 documented parameters and 0 of 32 summaries in `Paramore.Brighter.BoxProvisioning.MySql(net8.0)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:52— 1 of 24 documented parameters and 0 of 30 summaries in `Paramore.Brighter.BoxProvisioning.PostgreSql(net8.0)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.BoxProvisioning.Spanner/SpannerPayloadModeValidator.cs:62— 1 of 16 documented parameters and 0 of 20 summaries in `Paramore.Brighter.BoxProvisioning.Spanner(net8.0)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.BoxProvisioning.Sqlite/SqlitePayloadModeValidator.cs:50— 1 of 22 documented parameters and 0 of 27 summaries in `Paramore.Brighter.BoxProvisioning.Sqlite(net8.0)` only repeat the member or parameter name (e.g. "Cancellation token." for `cancellationToken`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Paramore.Brighter.Core.Tests/MessageSerialisation/Test Doubles/Transform.cs:25— 0 of 37 documented parameters and 0 of 285 summaries in `Paramore.Brighter.Core.Tests(net9.0)` only repeat the member or parameter name (e.g. "" for `initializerList`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.DynamoDb/DynamoDbTableBuilder.cs:26— 0 of 14 documented parameters and 0 of 16 summaries in `Paramore.Brighter.DynamoDb(netstandard2.0)` only repeat the member or parameter name (e.g. "" for `ct`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.DynamoDb.V4/DynamoDbTableBuilder.cs:19— 0 of 14 documented parameters and 0 of 16 summaries in `Paramore.Brighter.DynamoDb.V4(netstandard2.0)` only repeat the member or parameter name (e.g. "" for `ct`). 4 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Paramore.Brighter.Extensions.AspNetCore.Tests/TestDoubles/CapturedLogEntry.cs:30— 0 of 34 documented parameters and 6 of 281 summaries in `Paramore.Brighter.Extensions.AspNetCore.Tests(net9.0)` only repeat the member or parameter name (e.g. "One log entry captured by ." for `CapturedLogEntry`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Extensions.DependencyInjection/BrighterValidationHostedService.cs:59— 7 of 200 documented parameters and 4 of 223 summaries in `Paramore.Brighter.Extensions.DependencyInjection(netstandard2.0)` only repeat the member or parameter name (e.g. "The logger." for `logger`). 10 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Paramore.Brighter.Extensions.Tests/TestDoubles/CapturedLogEntry.cs:30— 0 of 1 documented parameters and 1 of 228 summaries in `Paramore.Brighter.Extensions.Tests(net9.0)` only repeat the member or parameter name (e.g. "One log entry captured by ." for `CapturedLogEntry`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Firestore/FirestoreConfiguration.cs:105— 2 of 8 documented parameters and 0 of 25 summaries in `Paramore.Brighter.Firestore(netstandard2.0)` only repeat the member or parameter name (e.g. "The id." for `id`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.DynamoDB/DynamoDbInbox.cs:75— 2 of 29 documented parameters and 0 of 12 summaries in `Paramore.Brighter.Inbox.DynamoDB(netstandard2.0)` only repeat the member or parameter name (e.g. "The command." for `command`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.DynamoDB.V4/DynamoDbInbox.cs:83— 2 of 28 documented parameters and 0 of 12 summaries in `Paramore.Brighter.Inbox.DynamoDB.V4(netstandard2.0)` only repeat the member or parameter name (e.g. "The command." for `command`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.MongoDb/InboxMessage.cs:23— 3 of 8 documented parameters and 4 of 16 summaries in `Paramore.Brighter.Inbox.MongoDb(net472)` only repeat the member or parameter name (e.g. "The command." for `command`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.MsSql/MsSqlInbox.cs:35— 3 of 8 documented parameters and 1 of 6 summaries in `Paramore.Brighter.Inbox.MsSql(net462)` only repeat the member or parameter name (e.g. "Class MsSqlInbox." for `MsSqlInbox`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.MySql/MySqlInbox.cs:35— 4 of 9 documented parameters and 1 of 6 summaries in `Paramore.Brighter.Inbox.MySql(net8.0)` only repeat the member or parameter name (e.g. "Class MySqlInbox." for `MySqlInbox`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names REDACTED:3— 0 of 1 documented parameters and 1 of 4 summaries in `Paramore.Brighter.Inbox.Spanner(net462)` only repeat the member or parameter name (e.g. "The spanner SQL queries" for `SpannerSqlQueries`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Inbox.Sqlite/SqliteInbox.cs:35— 0 of 5 documented parameters and 1 of 6 summaries in `Paramore.Brighter.Inbox.Sqlite(netstandard2.0)` only repeat the member or parameter name (e.g. "Class SqliteInbox." for `SqliteInbox`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Locking.Azure/AzureBlobLockingProvider.cs:49— 1 of 6 documented parameters and 2 of 7 summaries in `Paramore.Brighter.Locking.Azure(netstandard2.0)` only repeat the member or parameter name (e.g. "The Cancellation Token" for `cancellationToken`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Locking.DynamoDB/DynamoDbLockingProvider.cs:54— 1 of 5 documented parameters and 1 of 9 summaries in `Paramore.Brighter.Locking.DynamoDB(netstandard2.0)` only repeat the member or parameter name (e.g. "The Cancellation Token" for `cancellationToken`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Paramore.Brighter.Locking.DynamoDB.V4/DynamoDbLockingProvider.cs:55— 1 of 5 documented parameters and 1 of 9 summaries in `Paramore.Brighter.Locking.DynamoDB.V4(netstandard2.0)` only repeat the member or parameter name (e.g. "The Cancellation Token" for `cancellationToken`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 206 file(s) — `.claude/commands/refactor/comment_census.cs`, `.claude/commands/refactor/comment_only_check.cs`, `benchmarks/Paramore.Brighter.Benchmarks/BenchmarkCommand.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/pileup/Program.cs`, `bugfixes/0052-timed-outbox-sweeper-starvation/diagnostic/starve/Program.cs`, … (+201 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e833-9ce7-7bbe-8d09-b06a7c123b9f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 2 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 249 · Warnings: 1470 · Recommendations: 427 · Info: 245 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 06:30 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.