Public report of ArroyoSystems/arroyo, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 19:29 UTC · Survey ID cd_c8cfd914a764447bb40aaf84be910b2c
ArroyoSystems/arroyo
Measured 14 November 2026, 19:28 UTC, at code version 56cc719
CAI scoreAt riskUp 4 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 88,674 lines of product code in 27 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Accessibility, 30
Findings by how serious they are
77 critical617 serious133 minor
14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 19:28 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 ▸
68of 68 dimensions measured by tools.
748of 827 findings point to an exact file and line, so you can open each one in the code. The other 79 concern the repository as a whole, such as missing documentation.
68dimensions across 8 lenses, read from 88,674 lines of product code in 27 projects.
ArroyoSystems/arroyo is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 46 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Accessibility, at 30, is the weakest lens and counts most in the score. The best first steps are adding text alternatives and fixing focus, motion and contrast, each worth about 7 points. Raising Accessibility to 65 would lift the score to about 58.
Thirty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-five known security holes in the packages the code depends on can be used by attackers, and eight settings leave the servers or containers unsafe. Pinning each tool to an exact version, updating the vulnerable packages and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the two 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. The image with no text description needs a text description.
The product code is 88,674 lines, about €81,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 Accessibility rose from 30 to 65, the lowest score rated Strong, the score would rise from 46 to about 58.
Code composition: what the lines of code are
Product code 98%Tests 2%
New since the last survey: 144 findings
These 144 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 76 findings
These 76 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.
Cancellation propagation · Async function without AbortSignal: useConnectionTableTest webui/src/lib/data_fetching.ts
Forms & labels · <NumberInput> field component without a label webui/src/components/StartPipelineModal.tsx
Forms & labels · <Select> field component without a label webui/src/routes/connections/DefineSchema.tsx
Forms & labels · <Select> field component without a label webui/src/routes/connections/DefineSchema.tsx
Forms & labels · <Select> field component without a label webui/src/routes/connections/DefineSchema.tsx
Forms & labels · <Select> field component without a label webui/src/routes/connections/DefineSchema.tsx
Forms & labels · <Select> field component without a label webui/src/routes/connections/JsonForm.tsx
Forms & labels · <Textarea> field component without a label webui/src/routes/udfs/GlobalizeModal.tsx
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €81,000 · Estimate
Cost to rebuild
€27,000 to €130,000, for 447 to 1,419 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 46. 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
Medium: 88,674 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 7 points · Medium effort · Text alternatives
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 3 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €81,000 to build again, about 0.6 person-years of work. Its weakest lens is Accessibility, at 30 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. Of all the actions in this report, it raises the score most for the work it takes: about 7 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
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.
266 modules, with 549 dependencies between them. 5 loops run through 11 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 226 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.
arroyo_api uses arroyo_server_common.shutdown, so a change to arroyo_server_common.shutdown can break arroyo_api, while a change to arroyo_api can't break arroyo_server_common.shutdown.
Position
Below the diagonal: arroyo_api uses a module listed above it, which is the healthy direction.
arroyo_controller.states uses arroyo_rpc.errors, so a change to arroyo_rpc.errors can break arroyo_controller.states, while a change to arroyo_controller.states can't break arroyo_rpc.errors.
Position
Below the diagonal: arroyo_controller.states uses a module listed above it, which is the healthy direction.
arroyo_controller.states uses arroyo_server_common.shutdown, so a change to arroyo_server_common.shutdown can break arroyo_controller.states, while a change to arroyo_controller.states can't break arroyo_server_common.shutdown.
Position
Below the diagonal: arroyo_controller.states uses a module listed above it, which is the healthy direction.
8→12 arroyo_rpc.formats uses arroyo_rpcpart of a loop✕
Connections
8 pairs of types, where a type in arroyo_rpc.formats uses a type in arroyo_rpc.
arroyo_rpc.formats uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_rpc.formats, while a change to arroyo_rpc.formats can't break arroyo_rpc.
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.
arroyo_rpc.worker_types uses arroyo_rpc.errors, so a change to arroyo_rpc.errors can break arroyo_rpc.worker_types, while a change to arroyo_rpc.worker_types can't break arroyo_rpc.errors.
Position
Below the diagonal: arroyo_rpc.worker_types uses a module listed above it, which is the healthy direction.
arroyo_rpc.worker_types uses arroyo_types, so a change to arroyo_types can break arroyo_rpc.worker_types, while a change to arroyo_rpc.worker_types can't break arroyo_types.
Position
Below the diagonal: arroyo_rpc.worker_types uses a module listed above it, which is the healthy direction.
arroyo_state_protocol.types uses arroyo_types, so a change to arroyo_types can break arroyo_state_protocol.types, while a change to arroyo_state_protocol.types can't break arroyo_types.
Position
Below the diagonal: arroyo_state_protocol.types uses a module listed above it, which is the healthy direction.
arroyo_formats.ser uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_formats.ser, while a change to arroyo_formats.ser can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_formats.ser uses a module listed above it, which is the healthy direction.
arroyo_rpc uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_rpc, while a change to arroyo_rpc can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_rpc uses a module listed above it, which is the healthy direction.
29 pairs of types, where a type in arroyo_connectors.filesystem.config uses a type in arroyo_rpc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
arroyo_connectors.filesystem.config uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_connectors.filesystem.config, while a change to arroyo_connectors.filesystem.config can't break arroyo_rpc.
Position
Below the diagonal: arroyo_connectors.filesystem.config uses a module listed above it, which is the healthy direction.
arroyo_rpc.api_types.connections uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_rpc.api_types.connections, while a change to arroyo_rpc.api_types.connections can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_rpc.api_types.connections uses a module listed above it, which is the healthy direction.
arroyo_rpc.api_types.connections uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_rpc.api_types.connections, while a change to arroyo_rpc.api_types.connections can't break arroyo_rpc.
Position
Below the diagonal: arroyo_rpc.api_types.connections uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink uses arroyo_rpc.errors, so a change to arroyo_rpc.errors can break arroyo_connectors.filesystem.sink, while a change to arroyo_connectors.filesystem.sink can't break arroyo_rpc.errors.
Position
Below the diagonal: arroyo_connectors.filesystem.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.filesystem.sink, while a change to arroyo_connectors.filesystem.sink can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.filesystem.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_connectors.filesystem.sink, while a change to arroyo_connectors.filesystem.sink can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_connectors.filesystem.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink uses arroyo_connectors.filesystem.config, so a change to arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink, while a change to arroyo_connectors.filesystem.sink can't break arroyo_connectors.filesystem.config.
Position
Below the diagonal: arroyo_connectors.filesystem.sink uses a module listed above it, which is the healthy direction.
arroyo_operator.connector uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_operator.connector, while a change to arroyo_operator.connector can't break arroyo_rpc.
Position
Below the diagonal: arroyo_operator.connector uses a module listed above it, which is the healthy direction.
arroyo_operator.connector uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_operator.connector, while a change to arroyo_operator.connector can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_operator.connector uses a module listed above it, which is the healthy direction.
arroyo_rpc.df uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_rpc.df, while a change to arroyo_rpc.df can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_rpc.df uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.filesystem, while a change to arroyo_connectors.filesystem can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.filesystem uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_connectors.filesystem, while a change to arroyo_connectors.filesystem can't break arroyo_rpc.
Position
Below the diagonal: arroyo_connectors.filesystem uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem uses arroyo_connectors.filesystem.config, so a change to arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem, while a change to arroyo_connectors.filesystem can't break arroyo_connectors.filesystem.config.
Position
Below the diagonal: arroyo_connectors.filesystem uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_connectors.filesystem, while a change to arroyo_connectors.filesystem can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_connectors.filesystem uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem uses arroyo_operator.connector, so a change to arroyo_operator.connector can break arroyo_connectors.filesystem, while a change to arroyo_connectors.filesystem can't break arroyo_operator.connector.
Position
Below the diagonal: arroyo_connectors.filesystem uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_connectors.kafka, while a change to arroyo_connectors.kafka can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_connectors.kafka uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_connectors.kafka, while a change to arroyo_connectors.kafka can't break arroyo_rpc.
Position
Below the diagonal: arroyo_connectors.kafka uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_connectors.kafka, while a change to arroyo_connectors.kafka can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_connectors.kafka uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka uses arroyo_operator.connector, so a change to arroyo_operator.connector can break arroyo_connectors.kafka, while a change to arroyo_connectors.kafka can't break arroyo_operator.connector.
Position
Below the diagonal: arroyo_connectors.kafka uses a module listed above it, which is the healthy direction.
arroyo_datastream.logical uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_datastream.logical, while a change to arroyo_datastream.logical can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_datastream.logical uses a module listed above it, which is the healthy direction.
arroyo_planner.tables uses arroyo_rpc.config, so a change to arroyo_rpc.config can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_rpc.config.
Position
Below the diagonal: arroyo_planner.tables uses a module listed above it, which is the healthy direction.
arroyo_planner.tables uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_planner.tables uses a module listed above it, which is the healthy direction.
arroyo_planner.tables uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_rpc.
Position
Below the diagonal: arroyo_planner.tables uses a module listed above it, which is the healthy direction.
arroyo_planner.tables uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_planner.tables uses a module listed above it, which is the healthy direction.
arroyo_planner.tables uses arroyo_operator.connector, so a change to arroyo_operator.connector can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_operator.connector.
Position
Below the diagonal: arroyo_planner.tables uses a module listed above it, which is the healthy direction.
21→23 arroyo_planner.tables uses arroyo_plannerpart of a loop✕
Connections
5 pairs of types, where a type in arroyo_planner.tables uses a type in arroyo_planner.
arroyo_planner.tables uses arroyo_planner, so a change to arroyo_planner can break arroyo_planner.tables, while a change to arroyo_planner.tables can't break arroyo_planner.
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.
arroyo_operator.operator uses arroyo_types, so a change to arroyo_types can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_types.
Position
Below the diagonal: arroyo_operator.operator uses a module listed above it, which is the healthy direction.
arroyo_operator.operator uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_rpc.
Position
Below the diagonal: arroyo_operator.operator uses a module listed above it, which is the healthy direction.
arroyo_operator.operator uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_operator.operator uses a module listed above it, which is the healthy direction.
arroyo_operator.operator uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_operator.operator uses a module listed above it, which is the healthy direction.
22→26 arroyo_operator.operator uses arroyo_operatorpart of a loop✕
Connections
1 pair of types, where a type in arroyo_operator.operator uses a type in arroyo_operator.
arroyo_operator.operator uses arroyo_operator, so a change to arroyo_operator can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_operator.
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.
22→29 arroyo_operator.operator uses arroyo_operator.contextpart of a loop✕
Connections
12 pairs of types, where a type in arroyo_operator.operator uses a type in arroyo_operator.context.
arroyo_operator.operator uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_operator.operator, while a change to arroyo_operator.operator can't break arroyo_operator.context.
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.
arroyo_planner uses arroyo_rpc.config, so a change to arroyo_rpc.config can break arroyo_planner, while a change to arroyo_planner can't break arroyo_rpc.config.
Position
Below the diagonal: arroyo_planner uses a module listed above it, which is the healthy direction.
arroyo_planner uses arroyo_rpc.api_types.connections, so a change to arroyo_rpc.api_types.connections can break arroyo_planner, while a change to arroyo_planner can't break arroyo_rpc.api_types.connections.
Position
Below the diagonal: arroyo_planner uses a module listed above it, which is the healthy direction.
arroyo_planner uses arroyo_operator.connector, so a change to arroyo_operator.connector can break arroyo_planner, while a change to arroyo_planner can't break arroyo_operator.connector.
Position
Below the diagonal: arroyo_planner uses a module listed above it, which is the healthy direction.
arroyo_planner uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_planner, while a change to arroyo_planner can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_planner uses a module listed above it, which is the healthy direction.
arroyo_planner uses arroyo_planner.tables, so a change to arroyo_planner.tables can break arroyo_planner, while a change to arroyo_planner can't break arroyo_planner.tables.
Position
Below the diagonal: arroyo_planner uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.model uses arroyo_types, so a change to arroyo_types can break arroyo_worker.job_controller.model, while a change to arroyo_worker.job_controller.model can't break arroyo_types.
Position
Below the diagonal: arroyo_worker.job_controller.model uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.model uses arroyo_rpc.worker_types, so a change to arroyo_rpc.worker_types can break arroyo_worker.job_controller.model, while a change to arroyo_worker.job_controller.model can't break arroyo_rpc.worker_types.
Position
Below the diagonal: arroyo_worker.job_controller.model uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.model uses arroyo_state_protocol.types, so a change to arroyo_state_protocol.types can break arroyo_worker.job_controller.model, while a change to arroyo_worker.job_controller.model can't break arroyo_state_protocol.types.
Position
Below the diagonal: arroyo_worker.job_controller.model uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.model uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_worker.job_controller.model, while a change to arroyo_worker.job_controller.model can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_worker.job_controller.model uses a module listed above it, which is the healthy direction.
arroyo_api.pipelines uses arroyo_rpc.config, so a change to arroyo_rpc.config can break arroyo_api.pipelines, while a change to arroyo_api.pipelines can't break arroyo_rpc.config.
Position
Below the diagonal: arroyo_api.pipelines uses a module listed above it, which is the healthy direction.
arroyo_api.pipelines uses arroyo_api, so a change to arroyo_api can break arroyo_api.pipelines, while a change to arroyo_api.pipelines can't break arroyo_api.
Position
Below the diagonal: arroyo_api.pipelines uses a module listed above it, which is the healthy direction.
arroyo_api.pipelines uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_api.pipelines, while a change to arroyo_api.pipelines can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_api.pipelines uses a module listed above it, which is the healthy direction.
arroyo_api.pipelines uses arroyo_planner, so a change to arroyo_planner can break arroyo_api.pipelines, while a change to arroyo_api.pipelines can't break arroyo_planner.
Position
Below the diagonal: arroyo_api.pipelines uses a module listed above it, which is the healthy direction.
arroyo_operator uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_operator, while a change to arroyo_operator can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_operator uses a module listed above it, which is the healthy direction.
26→29 arroyo_operator uses arroyo_operator.contextpart of a loop✕
Connections
1 pair of types, where a type in arroyo_operator uses a type in arroyo_operator.context.
arroyo_operator uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_operator, while a change to arroyo_operator can't break arroyo_operator.context.
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.
arroyo_planner.builder uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_planner.builder, while a change to arroyo_planner.builder can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_planner.builder uses a module listed above it, which is the healthy direction.
arroyo_planner.builder uses arroyo_planner, so a change to arroyo_planner can break arroyo_planner.builder, while a change to arroyo_planner.builder can't break arroyo_planner.
Position
Below the diagonal: arroyo_planner.builder uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller uses arroyo_types, so a change to arroyo_types can break arroyo_worker.job_controller, while a change to arroyo_worker.job_controller can't break arroyo_types.
Position
Below the diagonal: arroyo_worker.job_controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller uses arroyo_rpc.worker_types, so a change to arroyo_rpc.worker_types can break arroyo_worker.job_controller, while a change to arroyo_worker.job_controller can't break arroyo_rpc.worker_types.
Position
Below the diagonal: arroyo_worker.job_controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller uses arroyo_worker.job_controller.model, so a change to arroyo_worker.job_controller.model can break arroyo_worker.job_controller, while a change to arroyo_worker.job_controller can't break arroyo_worker.job_controller.model.
Position
Below the diagonal: arroyo_worker.job_controller uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_rpc.errors, so a change to arroyo_rpc.errors can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_rpc.errors.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_types, so a change to arroyo_types can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_types.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_rpc.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_operator.context uses arroyo_operator, so a change to arroyo_operator can break arroyo_operator.context, while a change to arroyo_operator.context can't break arroyo_operator.
Position
Below the diagonal: arroyo_operator.context uses a module listed above it, which is the healthy direction.
arroyo_planner.extension uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_planner.extension, while a change to arroyo_planner.extension can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_planner.extension uses a module listed above it, which is the healthy direction.
arroyo_planner.extension uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_planner.extension, while a change to arroyo_planner.extension can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_planner.extension uses a module listed above it, which is the healthy direction.
arroyo_planner.extension uses arroyo_planner.builder, so a change to arroyo_planner.builder can break arroyo_planner.extension, while a change to arroyo_planner.extension can't break arroyo_planner.builder.
Position
Below the diagonal: arroyo_planner.extension uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_server_common.shutdown, so a change to arroyo_server_common.shutdown can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_server_common.shutdown.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_rpc.worker_types, so a change to arroyo_rpc.worker_types can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_rpc.worker_types.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_state_protocol.types, so a change to arroyo_state_protocol.types can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_state_protocol.types.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_worker.job_controller.model, so a change to arroyo_worker.job_controller.model can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_worker.job_controller.model.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_worker.job_controller.controller uses arroyo_worker.job_controller, so a change to arroyo_worker.job_controller can break arroyo_worker.job_controller.controller, while a change to arroyo_worker.job_controller.controller can't break arroyo_worker.job_controller.
Position
Below the diagonal: arroyo_worker.job_controller.controller uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.filesystem.sink.two_phase_committer, while a change to arroyo_connectors.filesystem.sink.two_phase_committer can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.two_phase_committer uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_connectors.filesystem.sink.two_phase_committer, while a change to arroyo_connectors.filesystem.sink.two_phase_committer can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.two_phase_committer uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.two_phase_committer uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.filesystem.sink.two_phase_committer, while a change to arroyo_connectors.filesystem.sink.two_phase_committer can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.two_phase_committer uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_storage, so a change to arroyo_storage can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_storage.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_rpc.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_connectors.filesystem.config, so a change to arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_connectors.filesystem.config.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_operator, so a change to arroyo_operator can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_operator.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.source uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.filesystem.source, while a change to arroyo_connectors.filesystem.source can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.filesystem.source uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_formats.ser, so a change to arroyo_formats.ser can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_formats.ser.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_connectors.kafka, so a change to arroyo_connectors.kafka can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_connectors.kafka.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.kafka.sink uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.kafka.sink, while a change to arroyo_connectors.kafka.sink can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.kafka.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.redis.sink uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.redis.sink, while a change to arroyo_connectors.redis.sink can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.redis.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.redis.sink uses arroyo_formats.ser, so a change to arroyo_formats.ser can break arroyo_connectors.redis.sink, while a change to arroyo_connectors.redis.sink can't break arroyo_formats.ser.
Position
Below the diagonal: arroyo_connectors.redis.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.redis.sink uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_connectors.redis.sink, while a change to arroyo_connectors.redis.sink can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_connectors.redis.sink uses a module listed above it, which is the healthy direction.
arroyo_connectors.redis.sink uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.redis.sink, while a change to arroyo_connectors.redis.sink can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.redis.sink uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_types, so a change to arroyo_types can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_types.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_rpc.worker_types, so a change to arroyo_rpc.worker_types can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_rpc.worker_types.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_rpc, so a change to arroyo_rpc can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_rpc.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_rpc.df, so a change to arroyo_rpc.df can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_rpc.df.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_worker.engine uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_worker.engine, while a change to arroyo_worker.engine can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_worker.engine uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_rpc.errors, so a change to arroyo_rpc.errors can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_rpc.errors.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.config, so a change to arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_connectors.filesystem.config.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.sink, so a change to arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_connectors.filesystem.sink.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem, so a change to arroyo_connectors.filesystem can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_connectors.filesystem.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.local uses arroyo_connectors.filesystem.sink.two_phase_committer, so a change to arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.local, while a change to arroyo_connectors.filesystem.sink.local can't break arroyo_connectors.filesystem.sink.two_phase_committer.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.local uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_storage, so a change to arroyo_storage can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_storage.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_types, so a change to arroyo_types can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_types.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_rpc.formats, so a change to arroyo_rpc.formats can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_rpc.formats.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem.config, so a change to arroyo_connectors.filesystem.config can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_connectors.filesystem.config.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem.sink, so a change to arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_connectors.filesystem.sink.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem, so a change to arroyo_connectors.filesystem can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_connectors.filesystem.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_operator.operator, so a change to arroyo_operator.operator can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_operator.operator.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_operator.context, so a change to arroyo_operator.context can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_operator.context.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem.sink.two_phase_committer, so a change to arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_connectors.filesystem.sink.two_phase_committer.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.operator uses a module listed above it, which is the healthy direction.
38→40 arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem.sink.open_filepart of a loop✕
Connections
2 pairs of types, where a type in arroyo_connectors.filesystem.sink.operator uses a type in arroyo_connectors.filesystem.sink.open_file.
arroyo_connectors.filesystem.sink.operator uses arroyo_connectors.filesystem.sink.open_file, so a change to arroyo_connectors.filesystem.sink.open_file can break arroyo_connectors.filesystem.sink.operator, while a change to arroyo_connectors.filesystem.sink.operator can't break arroyo_connectors.filesystem.sink.open_file.
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.
arroyo_worker uses arroyo_server_common.shutdown, so a change to arroyo_server_common.shutdown can break arroyo_worker, while a change to arroyo_worker can't break arroyo_server_common.shutdown.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_rpc.worker_types, so a change to arroyo_rpc.worker_types can break arroyo_worker, while a change to arroyo_worker can't break arroyo_rpc.worker_types.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_state_protocol.types, so a change to arroyo_state_protocol.types can break arroyo_worker, while a change to arroyo_worker can't break arroyo_state_protocol.types.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_datastream.logical, so a change to arroyo_datastream.logical can break arroyo_worker, while a change to arroyo_worker can't break arroyo_datastream.logical.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_worker.job_controller.model, so a change to arroyo_worker.job_controller.model can break arroyo_worker, while a change to arroyo_worker can't break arroyo_worker.job_controller.model.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_worker.job_controller, so a change to arroyo_worker.job_controller can break arroyo_worker, while a change to arroyo_worker can't break arroyo_worker.job_controller.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_worker uses arroyo_worker.engine, so a change to arroyo_worker.engine can break arroyo_worker, while a change to arroyo_worker can't break arroyo_worker.engine.
Position
Below the diagonal: arroyo_worker uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.open_file uses arroyo_storage, so a change to arroyo_storage can break arroyo_connectors.filesystem.sink.open_file, while a change to arroyo_connectors.filesystem.sink.open_file can't break arroyo_storage.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.open_file uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.open_file uses arroyo_connectors.filesystem.sink, so a change to arroyo_connectors.filesystem.sink can break arroyo_connectors.filesystem.sink.open_file, while a change to arroyo_connectors.filesystem.sink.open_file can't break arroyo_connectors.filesystem.sink.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.open_file uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.open_file uses arroyo_connectors.filesystem.sink.two_phase_committer, so a change to arroyo_connectors.filesystem.sink.two_phase_committer can break arroyo_connectors.filesystem.sink.open_file, while a change to arroyo_connectors.filesystem.sink.open_file can't break arroyo_connectors.filesystem.sink.two_phase_committer.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.open_file uses a module listed above it, which is the healthy direction.
arroyo_connectors.filesystem.sink.open_file uses arroyo_connectors.filesystem.sink.operator, so a change to arroyo_connectors.filesystem.sink.operator can break arroyo_connectors.filesystem.sink.open_file, while a change to arroyo_connectors.filesystem.sink.open_file can't break arroyo_connectors.filesystem.sink.operator.
Position
Below the diagonal: arroyo_connectors.filesystem.sink.open_file uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 61% · Adequate · gated by X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
90
High / Critical
A05:2025 — Injection
44
High / Critical
A02:2025 — Security Misconfiguration
13
High / Critical
Roadmap
Top priorities: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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 — 77
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 — 617
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 — 133
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
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 68 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 — 68 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, 748 of 827 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 54 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `crates/arroyo-sql-testing/golden_outputs/async_udf.json`, `crates/arroyo-sql-testing/golden_outputs/cast_to_sink_type.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_agg.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_coercion.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_pass_through.json` and 31 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D41 Kernel & Syscall Confinement — 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. K8s/arroyo/templates/controller.yaml:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ ------ > [builder 11/15] COPY crates crates: ------ ------ > [builder 12/15] COPY webui webui: ------ ------ > [builder 14/15] COPY docker/refinery.toml refinery.toml: ------ ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 509a7117-4241-4bd6-812d-757e42515683::xx2pccn5349e890noltwi6kbd: "/docker/refinery.toml": not found; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 231 further occurrence(s) are not listed individually; the score already reflects all 271.
Repo exclusion declarations: 3 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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
38 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CreatePipeline.CreatePipeline at 64. A further 12 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 arroyo_operator::udfs::scalar_none at 52 — they are counted neither in the figure above nor in this dimension's score. 9 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/arroyo-operator/src/udfs.rs (arroyo_operator::udfs::scalar_none at 52), crates/arroyo-planner/src/types.rs (arroyo_planner::types::convert_simple_data_type at 31), crates/arroyo-api/src/jobs.rs (arroyo_api::jobs::get_action at 30), crates/arroyo-formats/src/avro/schema.rs (arroyo_formats::avro::schema::arrow_to_avro at 29), crates/arroyo-formats/src/json/mod.rs (arroyo_formats::json::field_to_kafka_json at 27), and 4 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 30 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with CreatePipeline.CreatePipeline (cyclomatic 64), arroyo_formats::avro::ser::serialize_column (cyclomatic 41), ArroyoRewriter::f_up (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: 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.
+ 62 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with CreatePipeline.CreatePipeline (cognitive 84), arroyo_formats::avro::ser::serialize_column (cognitive 67). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.0 / 10Adequate✓ 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 31 FileTooLong finding(s) in God Classes — start with lib.rs (4), operator.rs (3), mod.rs (3). — One of this dimension's main actionable groups (31 warning-level).
Resolve the 25 MethodTooLong finding(s) in God Classes — start with mod.rs (6), tables.rs (2), controller.rs (2). — One of this dimension's main actionable groups (25 warning-level).
Resolve the 23 FunctionTooLong finding(s) in God Classes — start with JsonForm.tsx (3), DefineSchema.tsx (2), CreatePipeline.tsx. — One of this dimension's main actionable groups (23 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.
101 duplicated block group(s) detected. 5.1 % of the production lines (4,558 of 88,674) are in a reported copy. A further 72 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 91 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), engine.rs (2), connection_tables.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with sliding_aggregating_window.rs (2), metadata.rs, source.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with open_file.rs, uploads.rs, sink.rs. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.9 / 10Strong✓ 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.
27 production modules (Cargo+npm), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 22 of the 27 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: arroyo-rpc · ×6
Unstable project arroyo-api
Off the main sequence: arroyo-udf-common
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Unstable project arroyo-api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
46 outdated, 0 yanked direct Cargo dependencies. 142 of 143 direct crates were graded against crates.io (0 not published there, 1 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: arc-swap · ×46
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 981 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 46 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with controller.rs, leader_running.rs, scheduling.rs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
19 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/arroyo-state-protocol/src/lib.rs. Counted over 232 of the 301 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
92 deducted task-comment markers across 88674 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 89 TodoComment finding(s) in Explicit Debt — start with mod.rs (19), lib.rs (11), session_aggregating_window.rs (7). — One of this dimension's main actionable groups (89 warning-level).
Resolve the 2 XxxComment finding(s) in Explicit Debt — start with interpreter.rs, pyarrow.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with interpreter.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 3 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
2 of 27 build units (Cargo, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
44 finding(s): 0 critical, 42 high, 2 medium, 0 low. 33 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 44 file(s) — `crates/arroyo-sql-testing/golden_outputs/async_udf.json`, `crates/arroyo-sql-testing/golden_outputs/cast_to_sink_type.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_agg.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_coercion.json`, `crates/arroyo-sql-testing/golden_outputs/debezium_pass_through.json`, … (+39 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 33 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 (33 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 23 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (16), REDACTED (7). — One of this dimension's main actionable groups (23 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Critical IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
14 of 232 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/arroyo-connectors/src/nats/mod.rs. Counted over 232 of the 301 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 4 Change coupling finding(s) in Change Coupling — start with scheduling.rs, expiring_time_key_map.rs, jobs.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — webui/src/components/WelcomeModal.tsx:30
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels3.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — webui/src/components/ConfigViewer.tsx:59
This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — webui/src/components/ConfigViewer.tsx:75, webui/src/routes/pipelines/PipelineConfigModal.tsx:69
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — webui/src/routes/connections/JsonForm.tsx:92, webui/src/routes/connections/JsonForm.tsx:101
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — webui/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`:where([class^='ag-'])` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — webui/src/styles/data-grid-style.css:236
`.ag-ltr .ag-column-moving .ag-cell` moves (`transition: left 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:561
`.ag-rtl .ag-column-moving .ag-cell` moves (`transition: right 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:564
`.ag-ltr .ag-column-moving .ag-header-cell` moves (`transition: left 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:567
`.ag-rtl .ag-column-moving .ag-header-cell` moves (`transition: right 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:570
`.ag-ltr .ag-column-moving .ag-header-group-cell` moves (`transition: left 0.2s, width 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:573
`.ag-rtl .ag-column-moving .ag-header-group-cell` moves (`transition: right 0.2s, width 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:576
`.ag-row-animation .ag-row` moves (`transition: transform 0.4s, top 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:579
`.ag-row-animation .ag-row.ag-after-created` moves (`transition: transform 0.4s, top 0.4s, height 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:582
`.ag-ltr .ag-value-slide-out` moves (`transition: opacity 3s, margin-right 3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:710
`.ag-rtl .ag-value-slide-out` moves (`transition: opacity 3s, margin-left 3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:714
`.ag-icon-loading` moves (`animation-name: spin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:1181
`.ag-chart-docked-container` moves (`transition: min-width 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:1803
`.ag-chart-settings-mini-wrapper.ag-animating` moves (`transition: left 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:1925
`.ag-chart-tool-panel-button-enable .ag-chart-menu-close` moves (`transition: transform 0.33s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:2015
`.ag-ltr .ag-toggle-button-input-wrapper:before` moves (`transition: left 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:3789
`.ag-rtl .ag-toggle-button-input-wrapper:before` moves (`transition: right 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/styles/data-grid-style.css:3793
`.operator-checkpoint .in-progress` moves (`animation: scale-up-center 0.4s cubic-bezier(0.645, 0.045, 0.355, 1) infinite alternate-reverse
both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — webui/src/routes/pipelines/pipelines.css:67
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
`webui/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — webui/package.json:15
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/arroyo-connectors/src/filesystem/iceberg.rs:37
`Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/arroyo-server-common/src/lib.rs:228
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
webui/src/routes/connections/JsonForm.tsx:215 · webui/src/routes/connections/JsonForm.tsx:358 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — webui/src/routes/connections/JsonForm.tsx:215
webui/src/routes/connections/DefineSchema.tsx:212 · webui/src/routes/connections/DefineSchema.tsx:259 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/DefineSchema.tsx:212
webui/src/routes/connections/JsonForm.tsx:536 · webui/src/routes/connections/JsonForm.tsx:686 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/JsonForm.tsx:536
webui/src/routes/connections/Connections.tsx:202 · webui/src/routes/home/Home.tsx:121 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — webui/src/routes/connections/Connections.tsx:202
webui/src/lib/util.ts:7 · webui/src/lib/util.ts:32 · webui/src/lib/util.ts:57 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/lib/util.ts:7
webui/src/routes/connections/JsonForm.tsx:497 · webui/src/routes/connections/JsonForm.tsx:661 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/JsonForm.tsx:497
webui/src/routes/connections/ConnectionTester.tsx:205 · webui/src/routes/connections/CreateProfile.tsx:134 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — webui/src/routes/connections/ConnectionTester.tsx:205
webui/src/routes/connections/CreateConnection.tsx:49 · webui/src/routes/connections/CreateConnection.tsx:81 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/CreateConnection.tsx:49
webui/src/routes/not_found/ApiUnavailable.tsx:5 · webui/src/routes/not_found/PageNotFound.tsx:5 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — webui/src/routes/not_found/ApiUnavailable.tsx:5
webui/src/routes/udfs/UdfsResourceTab.tsx:69 · webui/src/routes/udfs/UdfsResourceTab.tsx:102 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/udfs/UdfsResourceTab.tsx:69
webui/src/lib/data_fetching.ts:511 · webui/src/lib/data_fetching.ts:591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — webui/src/lib/data_fetching.ts:511
webui/src/components/PipelinesTable.tsx:40 · webui/src/routes/connections/Connections.tsx:108 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — webui/src/components/PipelinesTable.tsx:40
webui/src/routes/connections/DefineSchema.tsx:443 · webui/src/routes/connections/DefineSchema.tsx:455 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/routes/connections/DefineSchema.tsx:443
webui/src/routes/connections/JsonForm.tsx:525 · webui/src/routes/connections/JsonForm.tsx:647 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — webui/src/routes/connections/JsonForm.tsx:525
webui/src/components/CreatePipelineTourModal.tsx:24 · webui/src/components/TourCompleteModal.tsx:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — webui/src/components/CreatePipelineTourModal.tsx:24
webui/src/routes/connections/JsonForm.tsx:865 · webui/src/routes/connections/JsonForm.tsx:914 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — webui/src/routes/connections/JsonForm.tsx:865
webui/src/components/CheckpointDetails.tsx:78 · webui/src/components/CheckpointDetails.tsx:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/components/CheckpointDetails.tsx:78
webui/src/lib/data_fetching.ts:150 · webui/src/lib/data_fetching.ts:173 · webui/src/lib/data_fetching.ts:194 · webui/src/lib/data_fetching.ts:212 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/lib/data_fetching.ts:150
webui/src/components/PipelinesTable.tsx:45 · webui/src/components/PipelinesTable.tsx:55 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — webui/src/components/PipelinesTable.tsx:45
webui/src/components/CheckpointDetails.tsx:42 · webui/src/components/PipelineRow.tsx:67 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — webui/src/components/CheckpointDetails.tsx:42
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
webui/src/components/ExampleQueryCard.tsx:18 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/components/ExampleQueryCard.tsx:18
webui/src/routes/connections/JsonForm.tsx:27 imports ajv/dist/2019, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/connections/JsonForm.tsx:27
webui/src/routes/pipelines/CreatePipeline.tsx:52 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/pipelines/CreatePipeline.tsx:52
webui/src/routes/pipelines/PipelineDetails.tsx:66 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/pipelines/PipelineDetails.tsx:66
webui/src/routes/udfs/UdfNodePopover.tsx:20 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — webui/src/routes/udfs/UdfNodePopover.tsx:20
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
CreatePipeline has cyclomatic complexity 38 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/pipelines/CreatePipeline.tsx:75
(anonymous) has cyclomatic complexity 27 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/connections/JsonForm.tsx:751
PipelineDetails has cyclomatic complexity 25 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/pipelines/PipelineDetails.tsx:69
Checkpoints has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/components/Checkpoints.tsx:91
ConnectionTester has cyclomatic complexity 22 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/connections/ConnectionTester.tsx:36
SchemaFormatEditor has cyclomatic complexity 17 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/connections/DefineSchema.tsx:25
(anonymous) has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/components/CheckpointDetails.tsx:58
ConfigEntry has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/components/ConfigViewer.tsx:105
AutocompleteWidget has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — webui/src/routes/connections/JsonForm.tsx:230
Do you agree with this assessment?
R3 · Large Files7.5 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
webui/src/routes/connections/JsonForm.tsx has 1045 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — webui/src/routes/connections/JsonForm.tsx:1
webui/src/routes/pipelines/CreatePipeline.tsx has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — webui/src/routes/pipelines/CreatePipeline.tsx:1
webui/src/lib/data_fetching.ts has 652 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — webui/src/lib/data_fetching.ts:1
webui/src/routes/connections/DefineSchema.tsx has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — webui/src/routes/connections/DefineSchema.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.1 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 1 application, 2 tooling and 0 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — webui/src/lib/RadioGroup.tsx, webui/src/routes/pipelines/ResourcePanel.tsx
Nothing imports this binding — it is safe to review for removal. (×6) — webui/src/components/PipelineRow.tsx:33, webui/src/lib/data_fetching.ts:26, webui/src/lib/data_fetching.ts:32, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — webui/src/App.tsx:30
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
webui/src/App.tsx → webui/src/lib/CloudComponents.tsx → webui/src/router.tsx → webui/src/App.tsx (one verified cycle inside a mutually-dependent group of 10 files) — webui/src/App.tsx:18
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`axum_server::bind_rustls(` (crates/arroyo-server-common/src/lib.rs:426)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum_server::bind_rustls(` (crates/arroyo-server-common/src/lib.rs:426).
What to do
Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
`meta_size` is read from the bytes being parsed at line 609 (`get_u32_le`), then used to size a `vec![…; n]` at line 610 — and nowhere in its scope is `meta_size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `meta_size` against the bytes actually remaining and a maximum the format allows before allocating. — crates/arroyo-worker/src/network_manager.rs:610
What to do
Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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.
`info!` at line 225 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:225
`debug!` at line 238 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:238
`warn!` at line 272 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:272
`info!` at line 529 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:529
`info!` at line 626 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:626
`info!` at line 678 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:678
`info!` at line 693 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/engine.rs:693
`debug!` at line 192 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:192
`error!` at line 248 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:248
`debug!` at line 284 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:284
`debug!` at line 339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:339
`info!` at line 347 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:347
`info!` at line 358 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:358
`error!` at line 620 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:620
`error!` at line 634 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:634
`warn!` at line 743 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:743
`info!` at line 786 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:786
`info!` at line 801 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:801
`debug!` at line 967 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:967
`warn!` at line 1042 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:1042
`debug!` at line 1270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/lib.rs:1270
`warn!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/network_manager.rs:263
`warn!` at line 303 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/network_manager.rs:303
`warn!` at line 321 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/network_manager.rs:321
`info!` at line 455 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/network_manager.rs:455
`warn!` at line 476 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/network_manager.rs:476
`warn!` at line 157 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/utils.rs:157
`warn!` at line 309 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/checkpoint_state.rs:309
`debug!` at line 367 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/controller.rs:367
`warn!` at line 71 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/job_metrics.rs:71
`warn!` at line 131 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/mod.rs:131
`warn!` at line 150 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/mod.rs:150
`warn!` at line 169 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/model.rs:169
`warn!` at line 600 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/job_controller/model.rs:600
`info!` at line 157 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/arrow/async_udf.rs:157
`debug!` at line 141 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:141
`debug!` at line 558 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — REDACTED:558
`debug!` at line 353 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/arrow/instant_join.rs:353
`debug!` at line 70 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/arrow/session_aggregating_window.rs:70
`debug!` at line 72 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/arroyo-worker/src/arrow/session_aggregating_window.rs:72
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
1/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~4.4 `!` null assertions per 1k TypeScript source lines — 47 assertion(s) across the 10566 source line(s) of the 63 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: webui/src/routes/connections/SchemaEditor.tsx (8), webui/src/routes/connections/JsonForm.tsx (7), webui/src/routes/connections/ConfluentSchemaEditor.tsx (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. 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
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 59 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 11% of this repository's production lines — rust (79,045 lines), python (10 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — ------ ------ > [builder 11/15] COPY crates crates: ------ ------ > [builder 12/15] COPY webui webui: ------ ------ > [builder 14/15] COPY docker/refinery.toml refinery.toml: ------ ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 509a7117-4241-4bd6-812d-757e42515683::xx2pccn5349e890noltwi6kbd: "/docker/refinery.toml": not found; runtime evidence skipped 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.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~2128 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its sibling role token rows: 2 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs source were not judged.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — Rust suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 49 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 3 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R4 Test Coverage — the JS/TS workspace (62 production file(s)) has no JavaScript/TypeScript test, but it is 10.85% of this repository's production source and the other 89.15% carries 2,128 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — X12 reached only 11% of this repository's production lines — rust (79,045 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 11% of this repository's production lines — rust (79,045 lines), python (10 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — 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
X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — X24 reached only 11% of this repository's production lines — rust (79,045 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 11% of this repository's production lines — rust (79,045 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC1 · Text alternatives· <img> without a text alternative · ×1
<img> without a text alternative webui/src/components/WelcomeModal.tsx:30— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
TodoComment webui/src/App.tsx:31— // TODO: also send a request to the server to delete the session — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/lib.rs:1— // TODO: factor out complex types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-controller/src/lib.rs:2— // TODO: factor out complex types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/lib.rs:388— // TODO: the leader needs to load checkpoint metadata and figure out epochs/min epochs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/lib.rs:474— // TODO: We need this just for sending TaskStarted notifications to the actual controller for — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/lib.rs:614— // TODO: remove the control queue from the select at this point — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/job_controller/checkpoint_state.rs:275— // TODO: UI management — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/job_controller/controller.rs:322— // TODO: this really should happen after we've replayed the initial commit, but — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/job_controller/job_metrics.rs:215— // TODO: The unwrap case should never happen because a new RateMetric will be created — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/job_controller/model.rs:489— // TODO: this is pretty expensive — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:366— // TODO: the timestamp should really be coming from the original _timestamp column of — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/mod.rs:279— //TODO: sort by the key — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:50— // TODO: advance futures outside of method calls. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:393— // TODO: perform partial aggregations and checkpoint those. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:467— // TODO: test best way to compute this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:820— // TODO: this will subtract the retention from start time, so hold more than it should, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:852— // TODO: filter out late data — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:593— // TODO: filter out late data — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:881— // TODO: pre-aggregate data before sending to state backend. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/session_aggregating_window.rs:937— // TODO: something better — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:214— // TODO: don't repeat this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:706— // TODO: this was a separate map just to the active execs, which could, in corner cases, be much smaller. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-state-protocol/src/gc.rs:124— // TODO: use a metadata cache here so we're not re-reading checkpoints we've just written — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-state-protocol/src/workflow.rs:233— // TODO: this read is not strictly necessary if update_current_generation is true, but is here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/arroyo-state/src/parquet.rs:93— // TODO: propagate error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FileTooLong: src/operator.rs crates/arroyo-operator/src/operator.rs— FileTooLong — 1059 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 559 over it, 2.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-worker/src/lib.rs— FileTooLong — 1057 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 557 over it, 2.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-rpc/src/lib.rs— FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 401 over it, 1.80× 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: connections/JsonForm.tsx webui/src/routes/connections/JsonForm.tsx— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tables/expiring_time_key_map.rs crates/arroyo-state/src/tables/expiring_time_key_map.rs— FileTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 382 over it, 1.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/pipelines.rs crates/arroyo-api/src/pipelines.rs— FileTooLong — 853 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 353 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/physical.rs crates/arroyo-planner/src/physical.rs— FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 337 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-planner/src/lib.rs— FileTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 336 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 825 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 67% of them inside a single declaration: IncrementalAggregatingFunc (3 blocks, 201-1025). The bar is 500 significant lines; this is 325 over it, 1.65× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: sink/open_file.rs crates/arroyo-connectors/src/filesystem/sink/open_file.rs— FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: OpenFile (2 blocks, 205-1105). The bar is 500 significant lines; this is 300 over it, 1.60× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/tables.rs crates/arroyo-planner/src/tables.rs— FileTooLong — 765 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 265 over it, 1.53× 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: states/mod.rs crates/arroyo-controller/src/states/mod.rs— FileTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 241 over it, 1.48× 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: kafka/mod.rs crates/arroyo-connectors/src/kafka/mod.rs— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 236 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/connection_tables.rs crates/arroyo-api/src/connection_tables.rs— FileTooLong — 709 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 209 over it, 1.42× 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: nexmark/operator.rs crates/arroyo-connectors/src/nexmark/operator.rs— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 195 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/engine.rs crates/arroyo-worker/src/engine.rs— FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 192 over it, 1.38× 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: filesystem/config.rs crates/arroyo-connectors/src/filesystem/config.rs— FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 185 over it, 1.37× 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: arrow/session_aggregating_window.rs crates/arroyo-worker/src/arrow/session_aggregating_window.rs— FileTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 185 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/lib.rs crates/arroyo-storage/src/lib.rs— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: StorageProvider (3 blocks, 56-1020). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: sink/operator.rs crates/arroyo-connectors/src/filesystem/sink/operator.rs— FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: FileSystemSinkV2 (3 blocks, 251-952). The bar is 500 significant lines; this is 170 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/config.rs crates/arroyo-rpc/src/config.rs— FileTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 143 over it, 1.29× 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: schedulers/mod.rs crates/arroyo-controller/src/schedulers/mod.rs— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: job_controller/controller.rs crates/arroyo-worker/src/job_controller/controller.rs— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 84% of them inside a single declaration: WorkerJobController (3 blocks, 46-879). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/de.rs crates/arroyo-formats/src/de.rs— FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/workflow.rs crates/arroyo-state-protocol/src/workflow.rs— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 87 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: Scheduling.next crates/arroyo-controller/src/states/scheduling.rs:371— MethodTooLong — next runs 253 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LeaderRunning.next crates/arroyo-controller/src/states/leader_running.rs:30— MethodTooLong — next runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConnectorTable.from_options crates/arroyo-planner/src/tables.rs:254— MethodTooLong — from_options runs 147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WorkerJobController.start_inner crates/arroyo-worker/src/job_controller/controller.rs:293— MethodTooLong — start_inner runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: RunningJobModel.finish_checkpoint crates/arroyo-worker/src/job_controller/model.rs:354— MethodTooLong — finish_checkpoint runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: WorkerJobController.init crates/arroyo-worker/src/job_controller/controller.rs:86— MethodTooLong — init runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: NatsSourceFunc.run_int crates/arroyo-connectors/src/nats/source/mod.rs:323— MethodTooLong — run_int runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 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: WorkerState.run_control_loop crates/arroyo-worker/src/lib.rs:468— MethodTooLong — run_control_loop runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: AggregateRewriter.f_up crates/arroyo-planner/src/plan/aggregate.rs:124— MethodTooLong — f_up runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Program.from_logical crates/arroyo-worker/src/engine.rs:210— MethodTooLong — from_logical runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IncrementalAggregatingFunc.initialize REDACTED:447— MethodTooLong — initialize runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowDetectingVisitor.f_up crates/arroyo-planner/src/plan/mod.rs:93— MethodTooLong — f_up runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IncrementalAggregatingConstructor.with_config REDACTED:1039— MethodTooLong — with_config runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ArroyoRewriter.f_up crates/arroyo-planner/src/plan/mod.rs:265— MethodTooLong — f_up runs 115 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RedisConnector.from_options crates/arroyo-connectors/src/redis/mod.rs:232— MethodTooLong — from_options runs 112 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: KafkaTester.validate_schema crates/arroyo-connectors/src/kafka/mod.rs:598— MethodTooLong — validate_schema runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: RunningJobModel.handle_message crates/arroyo-worker/src/job_controller/model.rs:143— MethodTooLong — handle_message runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: AsyncUdfOperator.on_start crates/arroyo-worker/src/arrow/async_udf.rs:156— MethodTooLong — on_start runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CheckpointState.checkpoint_finished crates/arroyo-worker/src/job_controller/checkpoint_state.rs:271— MethodTooLong — checkpoint_finished runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ImpulseSourceFunc.run crates/arroyo-connectors/src/impulse/operator.rs:96— MethodTooLong — run runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Table.try_from_statement crates/arroyo-planner/src/tables.rs:797— MethodTooLong — try_from_statement runs 107 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NatsSourceFunc.create_nats_consumer crates/arroyo-connectors/src/nats/source/mod.rs:162— MethodTooLong — create_nats_consumer runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: WorkerState.initialize_inner crates/arroyo-worker/src/lib.rs:323— MethodTooLong — initialize_inner runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: ArroyoPhysicalExtensionCodec.try_decode crates/arroyo-planner/src/physical.rs:205— MethodTooLong — try_decode runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WindowFunctionRewriter.f_up crates/arroyo-planner/src/plan/window_fn.rs:40— MethodTooLong — f_up runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CreatePipeline.CreatePipeline webui/src/routes/pipelines/CreatePipeline.tsx:75— FunctionTooLong — CreatePipeline runs 504 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 404 over it, 5.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineDetails.PipelineDetails webui/src/routes/pipelines/PipelineDetails.tsx:69— FunctionTooLong — PipelineDetails runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineEditorTabs.PipelineEditorTabs webui/src/routes/pipelines/PipelineEditorTabs.tsx:57— FunctionTooLong — PipelineEditorTabs runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: JsonForm.FormInner webui/src/routes/connections/JsonForm.tsx:703— FunctionTooLong — FormInner runs 216 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 116 over it, 2.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CheckpointDetails.CheckpointTimeline webui/src/components/CheckpointDetails.tsx:54— FunctionTooLong — CheckpointTimeline runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DefineSchema.DefineSchema webui/src/routes/connections/DefineSchema.tsx:309— FunctionTooLong — DefineSchema runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ConnectionTester.ConnectionTester webui/src/routes/connections/ConnectionTester.tsx:36— FunctionTooLong — ConnectionTester runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_api::pipelines::create_pipeline_int crates/arroyo-api/src/pipelines.rs:300— FunctionTooLong — arroyo_api::pipelines::create_pipeline_int runs 149 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SchemaEditor.SchemaEditor webui/src/routes/connections/SchemaEditor.tsx:21— FunctionTooLong — SchemaEditor runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_formats::avro::ser::serialize_column crates/arroyo-formats/src/avro/ser.rs:63— FunctionTooLong — arroyo_formats::avro::ser::serialize_column runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Connections.Connections webui/src/routes/connections/Connections.tsx:71— FunctionTooLong — Connections runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Checkpoints.Checkpoints webui/src/components/Checkpoints.tsx:91— FunctionTooLong — Checkpoints runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DefineSchema.SchemaFormatEditor webui/src/routes/connections/DefineSchema.tsx:25— FunctionTooLong — SchemaFormatEditor runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineConfigs.PipelineConfigs webui/src/routes/pipelines/PipelineConfigs.tsx:113— FunctionTooLong — PipelineConfigs runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelineOutputs.PipelineOutputs webui/src/routes/pipelines/PipelineOutputs.tsx:9— FunctionTooLong — PipelineOutputs runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_controller::states::execute_state crates/arroyo-controller/src/states/mod.rs:591— FunctionTooLong — arroyo_controller::states::execute_state runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ConfigureProfile.ClusterChooser webui/src/routes/connections/ConfigureProfile.tsx:74— FunctionTooLong — ClusterChooser runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: JsonForm.AutocompleteWidget webui/src/routes/connections/JsonForm.tsx:230— FunctionTooLong — AutocompleteWidget runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: JsonForm.MapWidget webui/src/routes/connections/JsonForm.tsx:553— FunctionTooLong — MapWidget runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CreateProfile.CreateProfile webui/src/routes/connections/CreateProfile.tsx:18— FunctionTooLong — CreateProfile runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: arroyo_planner::parse_and_get_arrow_program crates/arroyo-planner/src/lib.rs:884— FunctionTooLong — arroyo_planner::parse_and_get_arrow_program runs 106 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GlobalizeModal.GlobalizeModal webui/src/routes/udfs/GlobalizeModal.tsx:34— FunctionTooLong — GlobalizeModal runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PipelinesTable.PipelinesTable webui/src/components/PipelinesTable.tsx:29— FunctionTooLong — PipelinesTable runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×17
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:561— `.ag-ltr .ag-column-moving .ag-cell` moves (`transition: left 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:564— `.ag-rtl .ag-column-moving .ag-cell` moves (`transition: right 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:567— `.ag-ltr .ag-column-moving .ag-header-cell` moves (`transition: left 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:570— `.ag-rtl .ag-column-moving .ag-header-cell` moves (`transition: right 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:573— `.ag-ltr .ag-column-moving .ag-header-group-cell` moves (`transition: left 0.2s, width 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:576— `.ag-rtl .ag-column-moving .ag-header-group-cell` moves (`transition: right 0.2s, width 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:579— `.ag-row-animation .ag-row` moves (`transition: transform 0.4s, top 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:582— `.ag-row-animation .ag-row.ag-after-created` moves (`transition: transform 0.4s, top 0.4s, height 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:710— `.ag-ltr .ag-value-slide-out` moves (`transition: opacity 3s, margin-right 3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:714— `.ag-rtl .ag-value-slide-out` moves (`transition: opacity 3s, margin-left 3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:1181— `.ag-icon-loading` moves (`animation-name: spin`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:1803— `.ag-chart-docked-container` moves (`transition: min-width 0.4s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:1925— `.ag-chart-settings-mini-wrapper.ag-animating` moves (`transition: left 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:2015— `.ag-chart-tool-panel-button-enable .ag-chart-menu-close` moves (`transition: transform 0.33s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:3789— `.ag-ltr .ag-toggle-button-input-wrapper:before` moves (`transition: left 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/styles/data-grid-style.css:3793— `.ag-rtl .ag-toggle-button-input-wrapper:before` moves (`transition: right 0.1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard webui/src/routes/pipelines/pipelines.css:67— `.operator-checkpoint .in-progress` moves (`animation: scale-up-center 0.4s cubic-bezier(0.645, 0.045, 0.355, 1) infinite alternate-reverse
both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×15
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×14
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium CVE · ×13
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×10
Duplicated block (10 lines × 2) crates/arroyo-api/src/connection_tables.rs:239— crates/arroyo-api/src/connection_tables.rs:239-248 | crates/arroyo-api/src/connection_tables.rs:543-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.
Duplicated block (10 lines × 2) crates/arroyo-connectors/src/filesystem/config.rs:502— crates/arroyo-connectors/src/filesystem/config.rs:502-511 | crates/arroyo-connectors/src/filesystem/config.rs:581-590 — both copies are in the same file, so extract the 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/arroyo-connectors/src/filesystem/config.rs:518` calls `Source` and `crates/arroyo-connectors/src/filesystem/config.rs:596` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:324— crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:324-333 | crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:405-414 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:324` 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) crates/arroyo-planner/src/plan/mod.rs:104— crates/arroyo-planner/src/plan/mod.rs:104-113 | crates/arroyo-planner/src/plan/mod.rs:176-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-planner/src/plan/mod.rs:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/arroyo-planner/src/plan/mod.rs:116— crates/arroyo-planner/src/plan/mod.rs:116-125 | crates/arroyo-planner/src/plan/mod.rs:188-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-planner/src/plan/mod.rs:116` 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) crates/arroyo-worker/src/engine.rs:334— crates/arroyo-worker/src/engine.rs:334-343 | crates/arroyo-worker/src/engine.rs:352-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-worker/src/engine.rs:334` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/arroyo-worker/src/engine.rs:396— crates/arroyo-worker/src/engine.rs:396-405 | crates/arroyo-worker/src/engine.rs:412-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-worker/src/engine.rs:396` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/arroyo-planner/src/builder.rs:369— crates/arroyo-planner/src/builder.rs:369-378 | crates/arroyo-planner/src/builder.rs:396-406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-planner/src/builder.rs:369` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:335— crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:335-343 | crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:416-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:335` 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) crates/arroyo-connectors/src/fluvio/source.rs:186— crates/arroyo-connectors/src/fluvio/source.rs:186-194 | crates/arroyo-connectors/src/kafka/source/mod.rs:239-247 — 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 `crates/arroyo-connectors/src/fluvio/source.rs: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 (9 lines × 2) crates/arroyo-state/src/tables/global_keyed_map.rs:102— crates/arroyo-state/src/tables/global_keyed_map.rs:102-110 | crates/arroyo-state/src/tables/global_keyed_map.rs:168-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 `crates/arroyo-state/src/tables/global_keyed_map.rs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:183— crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:183-191 | crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:208-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:183` it does not close everything it opens, so those exact lines 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) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:644— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:644-652 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:288-296 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:644` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:278— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:278-286 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:68-76 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (9 lines × 2) crates/arroyo-connectors/src/polling_http/mod.rs:129— crates/arroyo-connectors/src/polling_http/mod.rs:129-137 | crates/arroyo-connectors/src/webhook/mod.rs:116-124 — `crates/arroyo-connectors/src/polling_http/mod.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` 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 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 `crates/arroyo-connectors/src/polling_http/mod.rs:129` it does not close everything it opens, so those exact lines 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) crates/arroyo-worker/src/job_controller/model.rs:150— crates/arroyo-worker/src/job_controller/model.rs:150-158 | crates/arroyo-worker/src/job_controller/model.rs:184-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-worker/src/job_controller/model.rs:150` it does not close everything it opens, so those exact lines 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) crates/arroyo-connectors/src/filesystem/sink/open_file.rs:711— crates/arroyo-connectors/src/filesystem/sink/open_file.rs:711-717 | crates/arroyo-connectors/src/filesystem/sink/open_file.rs:719-725 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/filesystem/sink/uploads.rs:80— crates/arroyo-connectors/src/filesystem/sink/uploads.rs:80-86 | crates/arroyo-connectors/src/filesystem/sink/uploads.rs: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 `crates/arroyo-connectors/src/filesystem/sink/uploads.rs:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/fluvio/sink.rs:82— crates/arroyo-connectors/src/fluvio/sink.rs:82-88 | crates/arroyo-connectors/src/fluvio/source.rs:75-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/arroyo-controller/src/states/scheduling.rs:655— crates/arroyo-controller/src/states/scheduling.rs:655-661 | crates/arroyo-controller/src/states/scheduling.rs:697-704 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-controller/src/states/scheduling.rs:655` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) crates/arroyo-state/src/tables/expiring_time_key_map.rs:269— crates/arroyo-state/src/tables/expiring_time_key_map.rs:269-276 | crates/arroyo-state/src/tables/expiring_time_key_map.rs:421-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/expiring_time_key_map.rs:269` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-controller/src/states/leader_running.rs:156— crates/arroyo-controller/src/states/leader_running.rs:156-162 | crates/arroyo-controller/src/states/scheduling.rs:379-385 — 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 `crates/arroyo-controller/src/states/leader_running.rs:156` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/arroyo-connectors/src/rabbitmq/mod.rs:99— crates/arroyo-connectors/src/rabbitmq/mod.rs:99-105 | crates/arroyo-connectors/src/redis/mod.rs:239-245 — 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 `crates/arroyo-connectors/src/rabbitmq/mod.rs:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/arroyo-planner/src/physical.rs:862— crates/arroyo-planner/src/physical.rs:862-868 | crates/arroyo-planner/src/physical.rs:870-876 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-planner/src/physical.rs:862` 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.
ClassTooLong: OpenFile crates/arroyo-connectors/src/filesystem/sink/open_file.rs:205— ClassTooLong — 652 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 2 blocks, lines 205-1105. The bar is 400 significant lines; this is 252 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: IncrementalAggregatingFunc REDACTED:201— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 201-1025. The bar is 400 significant lines; this is 154 over it, 1.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WorkerJobController crates/arroyo-worker/src/job_controller/controller.rs:46— ClassTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 3 blocks, lines 46-879. The bar is 400 significant lines; this is 126 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CreatePipeline webui/src/routes/pipelines/CreatePipeline.tsx:1— ClassTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 104 over it, 1.26× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RunningJobModel crates/arroyo-worker/src/job_controller/model.rs:37— ClassTooLong — 471 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 14 methods, 3 blocks, lines 37-702. The bar is 400 significant lines; this is 71 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FileSystemSinkV2 crates/arroyo-connectors/src/filesystem/sink/operator.rs:251— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 251-952. The bar is 400 significant lines; this is 36 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StorageProvider crates/arroyo-storage/src/lib.rs:56— ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 3 blocks, lines 56-1020. The bar is 400 significant lines; this is 3 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×6
Edited copy of a member (16 corresponding lines) REDACTED:223— REDACTED:223-238 | REDACTED:245-262 — 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) crates/arroyo-connectors/src/filesystem/sink/uploads.rs:75— crates/arroyo-connectors/src/filesystem/sink/uploads.rs:75-93 | crates/arroyo-connectors/src/filesystem/sink/uploads.rs:153-168 — 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) crates/arroyo-worker/src/arrow/window_fn.rs:133— crates/arroyo-worker/src/arrow/window_fn.rs:133-148 | crates/arroyo-worker/src/arrow/window_fn.rs:155-170 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/arroyo-connectors/src/impulse/mod.rs:47— crates/arroyo-connectors/src/impulse/mod.rs:47-62 | crates/arroyo-connectors/src/nexmark/mod.rs:105-120 — 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) crates/arroyo-rpc/src/lib.rs:697— crates/arroyo-rpc/src/lib.rs:697-712 | crates/arroyo-rpc/src/lib.rs:879-900 — 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) crates/arroyo-storage/src/lib.rs:951— crates/arroyo-storage/src/lib.rs:951-966 | crates/arroyo-storage/src/lib.rs:974-996 — 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.
Duplicated block (13 lines × 2) crates/arroyo-connectors/src/filesystem/sink/json.rs:320— crates/arroyo-connectors/src/filesystem/sink/json.rs:320-332 | crates/arroyo-connectors/src/filesystem/sink/parquet.rs:303-315 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) crates/arroyo-connectors/src/redis/mod.rs:119— crates/arroyo-connectors/src/redis/mod.rs:119-131 | crates/arroyo-connectors/src/redis/mod.rs:135-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/redis/mod.rs:119` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-controller/src/schedulers/mod.rs:810— crates/arroyo-controller/src/schedulers/mod.rs:810-823 | crates/arroyo-controller/src/schedulers/mod.rs:841-853 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-controller/src/schedulers/mod.rs:810` it begins part-way through the construct above it, so those exact lines 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:454— REDACTED:454-466 | REDACTED:510-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:454` it does not close everything it opens, so those 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:452` calls `sort_fields` and `REDACTED:509` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:695— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:695-707 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:430-442 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:695` it does not close everything it opens, so those exact lines 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) crates/arroyo-controller/src/leader_manager.rs:225— crates/arroyo-controller/src/leader_manager.rs:225-237 | crates/arroyo-controller/src/states/leader_restarting.rs:67-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-controller/src/leader_manager.rs:225` 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 (6 lines × 2) crates/arroyo-operator/src/context.rs:521— crates/arroyo-operator/src/context.rs:521-526 | crates/arroyo-state/src/tables/expiring_time_key_map.rs:560-567 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) REDACTED:226— REDACTED:226-231 | REDACTED:248-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 `REDACTED:226` it does not close everything it opens, so those exact lines 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) crates/arroyo-planner/src/extension/aggregate.rs:506— crates/arroyo-planner/src/extension/aggregate.rs:506-511 | crates/arroyo-planner/src/extension/window_fn.rs:74-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/arroyo-rpc/src/config.rs:995— crates/arroyo-rpc/src/config.rs:995-1000 | crates/arroyo-udf/arroyo-udf-common/src/parse.rs:224-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/arroyo-storage/src/lib.rs:409— crates/arroyo-storage/src/lib.rs:409-414 | crates/arroyo-storage/src/lib.rs:470-475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-storage/src/lib.rs:409` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-worker/src/arrow/updating_cache.rs:161— crates/arroyo-worker/src/arrow/updating_cache.rs:161-166 | crates/arroyo-worker/src/arrow/updating_cache.rs:192-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: arroyo-rpc — arroyo-rpc: abstractness 0.03, instability 0.06, distance 0.91 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: arroyo-udf-host — arroyo-udf-host: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: arroyo-types — arroyo-types: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: arroyo-udf-python — arroyo-udf-python: 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.
Off the main sequence: arroyo-datastream — arroyo-datastream: abstractness 0.06, instability 0.17, distance 0.77 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: arroyo-storage — arroyo-storage: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Hotspot: crates/arroyo-worker/src/job_controller/controller.rs crates/arroyo-worker/src/job_controller/controller.rs:293— crates/arroyo-worker/src/job_controller/controller.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in WorkerJobController::start_inner at line 293. 1 of those changes was a fix/bug commit, 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:54:33 -08:00' --until='2026-11-13 15:54:33 -08:00' --full-history --no-merges -- crates/arroyo-worker/src/job_controller/controller.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/arroyo-controller/src/states/leader_running.rs crates/arroyo-controller/src/states/leader_running.rs:30— crates/arroyo-controller/src/states/leader_running.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in LeaderRunning::next at line 30. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:54:33 -08:00' --until='2026-11-13 15:54:33 -08:00' --full-history --no-merges -- crates/arroyo-controller/src/states/leader_running.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/arroyo-controller/src/states/scheduling.rs crates/arroyo-controller/src/states/scheduling.rs:371— crates/arroyo-controller/src/states/scheduling.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Scheduling::next at line 371. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:54:33 -08:00' --until='2026-11-13 15:54:33 -08:00' --full-history --no-merges -- crates/arroyo-controller/src/states/scheduling.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/arroyo-controller/src/states/mod.rs crates/arroyo-controller/src/states/mod.rs:914— crates/arroyo-controller/src/states/mod.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in StateMachine::start at line 914. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:54:33 -08:00' --until='2026-11-13 15:54:33 -08:00' --full-history --no-merges -- crates/arroyo-controller/src/states/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/arroyo-worker/src/job_controller/model.rs crates/arroyo-worker/src/job_controller/model.rs:143— crates/arroyo-worker/src/job_controller/model.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in RunningJobModel::handle_message at line 143. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 15:54:33 -08:00' --until='2026-11-13 15:54:33 -08:00' --full-history --no-merges -- crates/arroyo-worker/src/job_controller/model.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (16 lines × 2) crates/arroyo-connectors/src/filesystem/source.rs:320— crates/arroyo-connectors/src/filesystem/source.rs:320-335 | crates/arroyo-connectors/src/filesystem/source.rs:359-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/filesystem/source.rs:320` 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, `crates/arroyo-connectors/src/filesystem/source.rs:358` calls `flush_buffer` and `crates/arroyo-connectors/src/filesystem/source.rs:319` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) crates/arroyo-connectors/src/kafka/mod.rs:680— crates/arroyo-connectors/src/kafka/mod.rs:680-695 | crates/arroyo-connectors/src/kafka/mod.rs:723-738 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/kafka/mod.rs:680` it does not close everything it opens, so those exact lines 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) crates/arroyo-connectors/src/sse/mod.rs:106— crates/arroyo-connectors/src/sse/mod.rs:106-121 | crates/arroyo-connectors/src/websocket/mod.rs:248-263 — `crates/arroyo-connectors/src/sse/mod.rs` and `crates/arroyo-connectors/src/websocket/mod.rs` 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 54 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 `crates/arroyo-connectors/src/sse/mod.rs:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/arroyo-state/src/tables/expiring_time_key_map.rs:73— crates/arroyo-state/src/tables/expiring_time_key_map.rs:73-88 | crates/arroyo-state/src/tables/expiring_time_key_map.rs:209-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/expiring_time_key_map.rs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:437— crates/arroyo-state/src/tables/table_manager.rs:437-452 | crates/arroyo-state/src/tables/table_manager.rs:478-493 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/table_manager.rs:437` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Boundary violation [package:third-party-deep-import] webui/src/components/ExampleQueryCard.tsx:18— webui/src/components/ExampleQueryCard.tsx:18 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/connections/JsonForm.tsx:27— webui/src/routes/connections/JsonForm.tsx:27 imports ajv/dist/2019, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/pipelines/CreatePipeline.tsx:52— webui/src/routes/pipelines/CreatePipeline.tsx:52 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/pipelines/PipelineDetails.tsx:66— webui/src/routes/pipelines/PipelineDetails.tsx:66 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] webui/src/routes/udfs/UdfNodePopover.tsx:20— webui/src/routes/udfs/UdfNodePopover.tsx:20 imports react-syntax-highlighter/dist/esm/styles/hljs, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Change coupling: scheduling.rs ↔ mod.rs crates/arroyo-controller/src/states/scheduling.rs:1— `crates/arroyo-controller/src/states/scheduling.rs` and `crates/arroyo-worker/src/job_controller/mod.rs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `9e4e25ab` Expose checkpoint-stop completion in job status (#1204); `e578bbf2` Add gRPC connect timeout on LeaderManager::connect (#1118); `584a9d11` Implement checkpoint cleanup for leader mode (#1076) — run `git show` on any of them.
Change coupling: expiring_time_key_map.rs ↔ engine.rs crates/arroyo-state/src/tables/expiring_time_key_map.rs:1— `crates/arroyo-state/src/tables/expiring_time_key_map.rs` and `crates/arroyo-worker/src/engine.rs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `29ceaa60` implement window functions over already windowed inputs. (#563); `1e3ec854` Queue based on batch size, rather than batch count (#556); `2c86e009` Support non-windowed inner joins. (#510) (at that commit the files were still `arroyo-state/src/tables/expiring_time_key_map.rs` and `arroyo-worker/src/engine.rs`) — run `git show` on any of them.
Change coupling: jobs.rs ↔ mod.rs crates/arroyo-api/src/jobs.rs:1— `crates/arroyo-api/src/jobs.rs` and `crates/arroyo-worker/src/job_controller/mod.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9e4e25ab` Expose checkpoint-stop completion in job status (#1204); `e578bbf2` Add gRPC connect timeout on LeaderManager::connect (#1118); `ccbd0eab` Add checkpoint_type to /checkpoints response (#1078) — run `git show` on any of them.
Change coupling: table_manager.rs ↔ engine.rs crates/arroyo-state/src/tables/table_manager.rs:1— `crates/arroyo-state/src/tables/table_manager.rs` and `crates/arroyo-worker/src/engine.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `9c7f1bd3` Add optional state_url and tags to pipelines (#1053); `a6e798ac` Structured error handling (part 2) (#980); `2c86e009` Support non-windowed inner joins. (#510) (at that commit the files were still `arroyo-state/src/tables/table_manager.rs` and `arroyo-worker/src/engine.rs`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) crates/arroyo-worker/src/engine.rs:391— crates/arroyo-worker/src/engine.rs:391-405 | crates/arroyo-worker/src/engine.rs:407-421 — 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) crates/arroyo-connectors/src/mqtt/mod.rs:203— crates/arroyo-connectors/src/mqtt/mod.rs:203-217 | crates/arroyo-connectors/src/redis/mod.rs:198-212 — 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) crates/arroyo-connectors/src/filesystem/sink/json.rs:226— crates/arroyo-connectors/src/filesystem/sink/json.rs:226-246 | crates/arroyo-connectors/src/filesystem/sink/json.rs:248-262 — 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) crates/arroyo-rpc/src/df.rs:209— crates/arroyo-rpc/src/df.rs:209-225 | crates/arroyo-worker/src/arrow/session_aggregating_window.rs:291-305 — 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 (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) crates/arroyo-storage/src/lib.rs:434— crates/arroyo-storage/src/lib.rs:434-444 | crates/arroyo-storage/src/lib.rs:453-465 — 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) crates/arroyo-api/src/jobs.rs:622— crates/arroyo-api/src/jobs.rs:622-634 | crates/arroyo-api/src/udfs.rs:131-141 — 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) crates/arroyo-state-protocol/src/store.rs:128— crates/arroyo-state-protocol/src/store.rs:128-140 | crates/arroyo-state-protocol/src/store.rs:191-201 — 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) crates/arroyo-connectors/src/filesystem/config.rs:530— crates/arroyo-connectors/src/filesystem/config.rs:530-540 | crates/arroyo-connectors/src/filesystem/config.rs:607-619 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:296— crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:296-300 | crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:337-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:296` it does not close everything it opens, so those exact lines 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) crates/arroyo-rpc/src/config.rs:987— crates/arroyo-rpc/src/config.rs:987-991 | crates/arroyo-udf/arroyo-udf-common/src/parse.rs:216-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:518— crates/arroyo-state/src/tables/table_manager.rs:518-522 | crates/arroyo-state/src/tables/table_manager.rs:556-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/table_manager.rs:518` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/arroyo-worker/src/engine.rs:312— crates/arroyo-worker/src/engine.rs:312-316 | crates/arroyo-worker/src/engine.rs:317-321 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×3
Edited copy of a member (23 corresponding lines) crates/arroyo-connectors/src/filesystem/sink/json.rs:319— crates/arroyo-connectors/src/filesystem/sink/json.rs:319-341 | crates/arroyo-connectors/src/filesystem/sink/parquet.rs:302-325 — 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) crates/arroyo-operator/src/operator.rs:886— crates/arroyo-operator/src/operator.rs:886-908 | crates/arroyo-operator/src/operator.rs:914-938 — 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) crates/arroyo-connectors/src/impulse/mod.rs:101— crates/arroyo-connectors/src/impulse/mod.rs:101-126 | crates/arroyo-connectors/src/nexmark/mod.rs:159-181 — 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 (10 corresponding lines) · ×3
Edited copy of a member (10 corresponding lines) crates/arroyo-rpc/src/df.rs:316— crates/arroyo-rpc/src/df.rs:316-329 | crates/arroyo-worker/src/arrow/session_aggregating_window.rs:307-316 — 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) crates/arroyo-connectors/src/mqtt/mod.rs:226— crates/arroyo-connectors/src/mqtt/mod.rs:226-235 | crates/arroyo-connectors/src/redis/mod.rs:221-230 — 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) crates/arroyo-connectors/src/mqtt/mod.rs:384— crates/arroyo-connectors/src/mqtt/mod.rs:384-393 | crates/arroyo-connectors/src/mqtt/mod.rs:395-405 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) crates/arroyo-operator/src/lib.rs:33— crates/arroyo-operator/src/lib.rs:33-41 | crates/arroyo-rpc/src/df.rs:434-440 — 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) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:219— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:219-225 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:102-109 — 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) crates/arroyo-planner/src/extension/sink.rs:141— crates/arroyo-planner/src/extension/sink.rs:141-148 | crates/arroyo-planner/src/extension/table_source.rs:80-86 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13–14 lines × 3) crates/arroyo-connectors/src/filesystem/iceberg.rs:248— crates/arroyo-connectors/src/filesystem/iceberg.rs:248-261 | crates/arroyo-connectors/src/preview/mod.rs:95-107 | crates/arroyo-connectors/src/webhook/mod.rs:162-174 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/iceberg.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/filesystem/iceberg.rs:248` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 3) crates/arroyo-connectors/src/polling_http/operator.rs:215— crates/arroyo-connectors/src/polling_http/operator.rs:215-227 | crates/arroyo-connectors/src/sse/operator.rs:224-237 | crates/arroyo-connectors/src/websocket/operator.rs:249-261 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 41 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 `crates/arroyo-connectors/src/polling_http/operator.rs:215` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 3) crates/arroyo-state/src/tables/table_manager.rs:501— crates/arroyo-state/src/tables/table_manager.rs:501-513 | crates/arroyo-state/src/tables/table_manager.rs:539-551 | crates/arroyo-state/src/tables/table_manager.rs:576-589 — 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 `crates/arroyo-state/src/tables/table_manager.rs:501` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) crates/arroyo-connectors/src/kafka/mod.rs:358— crates/arroyo-connectors/src/kafka/mod.rs:358-368 | crates/arroyo-connectors/src/mqtt/mod.rs:259-269 | crates/arroyo-connectors/src/nats/mod.rs:294-304 — `crates/arroyo-connectors/src/kafka/mod.rs` and `crates/arroyo-connectors/src/mqtt/mod.rs` 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 12 separate duplicated blocks between them, totalling at least 114 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 `crates/arroyo-connectors/src/kafka/mod.rs:358` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-connectors/src/polling_http/mod.rs:196— crates/arroyo-connectors/src/polling_http/mod.rs:196-206 | crates/arroyo-connectors/src/sse/mod.rs:83-93 | crates/arroyo-connectors/src/websocket/mod.rs:225-235 — `crates/arroyo-connectors/src/sse/mod.rs` and `crates/arroyo-connectors/src/websocket/mod.rs` 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 54 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 × 3) crates/arroyo-connectors/src/confluent/mod.rs:105— crates/arroyo-connectors/src/confluent/mod.rs:105-115 | crates/arroyo-connectors/src/kafka/mod.rs:182-192 | crates/arroyo-connectors/src/mqtt/mod.rs:139-149 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 33 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 `crates/arroyo-connectors/src/confluent/mod.rs:105` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/arroyo-worker/src/arrow/join_with_expiration.rs:58— crates/arroyo-worker/src/arrow/join_with_expiration.rs:58-65 | crates/arroyo-worker/src/arrow/join_with_expiration.rs:93-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-worker/src/arrow/join_with_expiration.rs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:489— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:489-496 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:154-164 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:489` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/arroyo-connectors/src/fluvio/mod.rs:92— crates/arroyo-connectors/src/fluvio/mod.rs:92-99 | crates/arroyo-connectors/src/rabbitmq/mod.rs:142-149 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/rabbitmq/mod.rs` 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 7 separate duplicated blocks between them, totalling at least 67 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 `crates/arroyo-connectors/src/fluvio/mod.rs: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/arroyo-connectors/src/rabbitmq/mod.rs:151` calls `Some` and `crates/arroyo-connectors/src/fluvio/mod.rs:101` 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.
AC2 · Forms & labels· <Input> field component without a label · ×2
<Input> field component without a label webui/src/components/ConfigViewer.tsx:75— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Input> field component without a label webui/src/routes/connections/JsonForm.tsx:92— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
arroyo_formats::avro::ser::serialize_column (cyclomatic 41) crates/arroyo-formats/src/avro/ser.rs:63— arroyo_formats::avro::ser::serialize_column has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
arroyo_formats::proto::de::proto_value_to_json (cyclomatic 21) crates/arroyo-formats/src/proto/de.rs:46— arroyo_formats::proto::de::proto_value_to_json has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WorkerJobController::start_inner (cyclomatic 29) crates/arroyo-worker/src/job_controller/controller.rs:293— WorkerJobController::start_inner has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WorkerJobController::progress (cyclomatic 26) crates/arroyo-worker/src/job_controller/controller.rs:564— WorkerJobController::progress has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum (cyclomatic 22) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:273— arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum (cyclomatic 22) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:353— arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_max_as_datum has cyclomatic complexity 22 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This shape REPEATS in the file: one other method here (arroyo_connectors::filesystem::sink::iceberg::metadata::get_parquet_stat_min_as_datum) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
XxxComment crates/arroyo-udf/arroyo-udf-python/src/interpreter.rs:34— // XXX: import the `decimal` module in the main interpreter before creating sub-interpreters. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:113— // // XXX: it is slow to call eval every time — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
IncrementalAggregatingFunc::initialize (cognitive 52) REDACTED:447— IncrementalAggregatingFunc::initialize has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (38 pts), loops 7 (14 pts) (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IncrementalAggregatingFunc::flush (cognitive 21) REDACTED:638— IncrementalAggregatingFunc::flush has cognitive complexity 21 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 5 (9 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WorkerJobController::start_inner (cognitive 38) crates/arroyo-worker/src/job_controller/controller.rs:293— WorkerJobController::start_inner has cognitive complexity 38 (threshold 15). Drivers by points: match/switch 7 (19 pts), if/else 4 (14 pts), loops 4 (5 pts) (nesting depth added 23). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WorkerJobController::progress (cognitive 25) crates/arroyo-worker/src/job_controller/controller.rs:564— WorkerJobController::progress has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12, boolean chains 9, match/switch 2 (4 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
arroyo_api::pipelines::compile_sql (cognitive 32) crates/arroyo-api/src/pipelines.rs:61— arroyo_api::pipelines::compile_sql has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (5 pts), match/switch 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_api::pipelines::create_pipeline_int (cognitive 26) crates/arroyo-api/src/pipelines.rs:300— arroyo_api::pipelines::create_pipeline_int has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KinesisSourceFunc::run_int (cognitive 27) crates/arroyo-connectors/src/kinesis/source.rs:352— KinesisSourceFunc::run_int has cognitive complexity 27 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 3 (10 pts), loops 2 (5 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KinesisSourceFunc::read_data_from_shard_iterator (cognitive 21) crates/arroyo-connectors/src/kinesis/source.rs:267— KinesisSourceFunc::read_data_from_shard_iterator has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_planner::parse_and_get_arrow_program (cognitive 27) crates/arroyo-planner/src/lib.rs:884— arroyo_planner::parse_and_get_arrow_program has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 3 (7 pts), loops 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_planner::find_window (cognitive 19) crates/arroyo-planner/src/lib.rs:690— arroyo_planner::find_window has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (3 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) crates/arroyo-connectors/src/filesystem/source.rs:309— crates/arroyo-connectors/src/filesystem/source.rs:309-335 | crates/arroyo-connectors/src/filesystem/source.rs:344-374 — 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) crates/arroyo-worker/src/arrow/join_with_expiration.rs:49— crates/arroyo-worker/src/arrow/join_with_expiration.rs:49-75 | crates/arroyo-worker/src/arrow/join_with_expiration.rs:82-110 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) crates/arroyo-formats/src/ser.rs:177— crates/arroyo-formats/src/ser.rs:177-200 | crates/arroyo-formats/src/ser.rs:202-225 — 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) crates/arroyo-worker/src/arrow/instant_join.rs:305— crates/arroyo-worker/src/arrow/instant_join.rs:305-328 | crates/arroyo-worker/src/arrow/join_with_expiration.rs:186-209 — 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 (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) crates/arroyo-planner/src/builder.rs:366— crates/arroyo-planner/src/builder.rs:366-390 | crates/arroyo-planner/src/builder.rs:393-423 — 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) crates/arroyo-connectors/src/polling_http/mod.rs:63— crates/arroyo-connectors/src/polling_http/mod.rs:63-87 | crates/arroyo-connectors/src/webhook/mod.rs:54-78 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 1+ corresponding lines) · ×2
Edited copies of one member (3 members, 1+ corresponding lines) crates/arroyo-planner/src/extension/debezium.rs:29— crates/arroyo-planner/src/extension/debezium.rs:29-29 | crates/arroyo-planner/src/extension/remote_table.rs:35-35 | crates/arroyo-planner/src/extension/watermark_node.rs:27-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 1+ corresponding lines) crates/arroyo-planner/src/extension/projection.rs:31— crates/arroyo-planner/src/extension/projection.rs:31-31 | crates/arroyo-planner/src/extension/sink.rs:36-36 | crates/arroyo-planner/src/extension/table_source.rs:28-28 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 1 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×2
Edited copy of a member (20 corresponding lines) crates/arroyo-datastream/src/logical.rs:530— crates/arroyo-datastream/src/logical.rs:530-550 | crates/arroyo-datastream/src/logical.rs:554-573 — 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) crates/arroyo-connectors/src/kafka/sink/mod.rs:79— crates/arroyo-connectors/src/kafka/sink/mod.rs:79-104 | crates/arroyo-connectors/src/kafka/sink/mod.rs:106-125 — 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 (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) crates/arroyo-controller/src/states/leader_checkpoint_stopping.rs:15— crates/arroyo-controller/src/states/leader_checkpoint_stopping.rs:15-32 | crates/arroyo-controller/src/states/leader_rescaling.rs:14-35 — 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) crates/arroyo-datastream/src/logical.rs:508— crates/arroyo-datastream/src/logical.rs:508-526 | crates/arroyo-datastream/src/logical.rs:577-594 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) crates/arroyo-rpc/src/api_types/connections.rs:241— crates/arroyo-rpc/src/api_types/connections.rs:241-257 | crates/arroyo-rpc/src/api_types/connections.rs:293-312 — 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) crates/arroyo-connectors/src/filesystem/sink/operator.rs:456— crates/arroyo-connectors/src/filesystem/sink/operator.rs:456-472 | crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:143-159 — 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 copies of one member (5 members, 16+ corresponding lines) · ×2
Edited copies of one member (5 members, 16+ corresponding lines) crates/arroyo-connectors/src/confluent/mod.rs:101— crates/arroyo-connectors/src/confluent/mod.rs:101-116 | crates/arroyo-connectors/src/kafka/mod.rs:178-193 | crates/arroyo-connectors/src/mqtt/mod.rs:135-150 | crates/arroyo-connectors/src/nats/mod.rs:153-168 | crates/arroyo-connectors/src/rabbitmq/mod.rs:32-47 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 16+ corresponding lines) crates/arroyo-connectors/src/kinesis/mod.rs:37— crates/arroyo-connectors/src/kinesis/mod.rs:37-52 | crates/arroyo-connectors/src/polling_http/mod.rs:99-114 | crates/arroyo-connectors/src/sse/mod.rs:41-56 | crates/arroyo-connectors/src/webhook/mod.rs:90-105 | crates/arroyo-connectors/src/websocket/mod.rs:45-60 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×2
Edited copy of a member (1 corresponding lines) crates/arroyo-planner/src/extension/aggregate.rs:572— crates/arroyo-planner/src/extension/aggregate.rs:572-572 | crates/arroyo-planner/src/extension/mod.rs:111-149 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) crates/arroyo-planner/src/functions.rs:39— crates/arroyo-planner/src/functions.rs:39-51 | crates/arroyo-planner/src/physical.rs:155-155 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) crates/arroyo-worker/src/lib.rs:1429— crates/arroyo-worker/src/lib.rs:1429-1441 | crates/arroyo-worker/src/lib.rs:1446-1461 — 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) crates/arroyo-worker/src/job_controller/mod.rs:120— crates/arroyo-worker/src/job_controller/mod.rs:120-133 | crates/arroyo-worker/src/job_controller/mod.rs:140-152 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) crates/arroyo-state-protocol/src/store.rs:89— crates/arroyo-state-protocol/src/store.rs:89-100 | crates/arroyo-state-protocol/src/store.rs:149-160 — 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) crates/arroyo-udf/arroyo-udf-host/src/lib.rs:243— crates/arroyo-udf/arroyo-udf-host/src/lib.rs:243-254 | crates/arroyo-udf/arroyo-udf-host/src/lib.rs:267-278 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (18 lines × 2) crates/arroyo-connectors/src/impulse/operator.rs:143— crates/arroyo-connectors/src/impulse/operator.rs:143-160 | crates/arroyo-connectors/src/impulse/operator.rs:169-186 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/impulse/operator.rs:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) crates/arroyo-state/src/tables/table_manager.rs:418— crates/arroyo-state/src/tables/table_manager.rs:418-435 | crates/arroyo-state/src/tables/table_manager.rs:459-476 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/table_manager.rs:418` it does not close everything it opens, so those exact lines 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) crates/arroyo-datastream/src/logical.rs:533— crates/arroyo-datastream/src/logical.rs:533-546 | crates/arroyo-datastream/src/logical.rs:556-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.
Duplicated block (14 lines × 2) crates/arroyo-connectors/src/polling_http/mod.rs:73— crates/arroyo-connectors/src/polling_http/mod.rs:73-86 | crates/arroyo-connectors/src/webhook/mod.rs:64-77 — `crates/arroyo-connectors/src/polling_http/mod.rs` and `crates/arroyo-connectors/src/webhook/mod.rs` 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 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.
Duplicated block (12–13 lines × 2) crates/arroyo-connectors/src/fluvio/mod.rs:93— crates/arroyo-connectors/src/fluvio/mod.rs:93-105 | crates/arroyo-connectors/src/kinesis/mod.rs:135-146 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kinesis/mod.rs` 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 82 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 `crates/arroyo-connectors/src/fluvio/mod.rs:93` it does not close everything it opens, so those 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, `crates/arroyo-connectors/src/fluvio/mod.rs:91` calls `pull_opt_str`, `pull_str` and `crates/arroyo-connectors/src/kinesis/mod.rs:134` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–13 lines × 2) crates/arroyo-planner/src/extension/aggregate.rs:79— crates/arroyo-planner/src/extension/aggregate.rs:79-90 | crates/arroyo-planner/src/extension/aggregate.rs:127-139 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 3) crates/arroyo-planner/src/extension/aggregate.rs:96— crates/arroyo-planner/src/extension/aggregate.rs:96-105 | crates/arroyo-planner/src/extension/aggregate.rs:146-155 | crates/arroyo-planner/src/extension/aggregate.rs:266-275 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) crates/arroyo-connectors/src/kinesis/mod.rs:95— crates/arroyo-connectors/src/kinesis/mod.rs:95-104 | crates/arroyo-connectors/src/nats/mod.rs:252-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:186-196 — `crates/arroyo-connectors/src/kinesis/mod.rs` and `crates/arroyo-connectors/src/nats/mod.rs` 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 81 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 `crates/arroyo-connectors/src/kinesis/mod.rs:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) crates/arroyo-operator/src/context.rs:522— crates/arroyo-operator/src/context.rs:522-527 | crates/arroyo-worker/src/arrow/instant_join.rs:151-156 | crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:607-612 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:258-263 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:122— crates/arroyo-connectors/src/confluent/mod.rs:122-127 | crates/arroyo-connectors/src/kafka/mod.rs:318-323 | crates/arroyo-connectors/src/kinesis/mod.rs:72-77 | crates/arroyo-connectors/src/mqtt/mod.rs:237-242 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 33 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.
Outbound HTTP without resilience crates/arroyo-connectors/src/filesystem/iceberg.rs:37— `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/arroyo-server-common/src/lib.rs:228— `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplicated block (15 lines × 2 locations) webui/src/routes/not_found/ApiUnavailable.tsx:5— webui/src/routes/not_found/ApiUnavailable.tsx:5 · webui/src/routes/not_found/PageNotFound.tsx:5 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (15 lines × 2 locations) webui/src/routes/udfs/UdfsResourceTab.tsx:69— webui/src/routes/udfs/UdfsResourceTab.tsx:69 · webui/src/routes/udfs/UdfsResourceTab.tsx:102 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 2 locations) webui/src/routes/connections/DefineSchema.tsx:443— webui/src/routes/connections/DefineSchema.tsx:443 · webui/src/routes/connections/DefineSchema.tsx:455 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:525— webui/src/routes/connections/JsonForm.tsx:525 · webui/src/routes/connections/JsonForm.tsx:647 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
AC2 · Forms & labels· <Select> field component without a label · ×1
<Select> field component without a label webui/src/components/ConfigViewer.tsx:59— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <Textarea> field component without a label · ×1
<Textarea> field component without a label webui/src/routes/connections/JsonForm.tsx:101— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <NumberInput> field component without a label · ×1
<NumberInput> field component without a label webui/src/routes/pipelines/PipelineConfigModal.tsx:69— This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark webui/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement webui/src/styles/data-grid-style.css:236— `:where([class^='ag-'])` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
CreatePipeline.CreatePipeline (cyclomatic 64) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline.CreatePipeline has cyclomatic complexity 64 (threshold 15). Of this number, 36 points are the body's own statements and 28 belong to 12 function items 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.
ArroyoRewriter::f_up (cyclomatic 33) crates/arroyo-planner/src/plan/mod.rs:265— ArroyoRewriter::f_up has cyclomatic complexity 33 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Scheduling::next (cyclomatic 32) crates/arroyo-controller/src/states/scheduling.rs:371— Scheduling::next has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
JsonForm.FormInner (cyclomatic 31) webui/src/routes/connections/JsonForm.tsx:703— JsonForm.FormInner has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 2 of the 31 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 751, 728, 737, …). 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.
Converter::build_array (cyclomatic 30) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:150— Converter::build_array has cyclomatic complexity 30 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
CheckpointDetails.CheckpointTimeline (cyclomatic 30) webui/src/components/CheckpointDetails.tsx:54— CheckpointDetails.CheckpointTimeline has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 58, 102, 78, …). 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.
ConnectionTester.ConnectionTester (cyclomatic 28) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester.ConnectionTester has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LeaderRunning::next (cyclomatic 27) crates/arroyo-controller/src/states/leader_running.rs:30— LeaderRunning::next has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KafkaSourceFunc::run_int (cyclomatic 26) crates/arroyo-connectors/src/kafka/source/mod.rs:153— KafkaSourceFunc::run_int has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NatsSourceFunc::run_int (cyclomatic 26) crates/arroyo-connectors/src/nats/source/mod.rs:323— NatsSourceFunc::run_int has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Checkpoints.Checkpoints (cyclomatic 26) webui/src/components/Checkpoints.tsx:91— Checkpoints.Checkpoints has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to 3 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.
RunningJobModel::handle_message (cyclomatic 25) crates/arroyo-worker/src/job_controller/model.rs:143— RunningJobModel::handle_message has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ConnectorTable::from_options (cyclomatic 24) crates/arroyo-planner/src/tables.rs:254— ConnectorTable::from_options has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PipelineOutputs.PipelineOutputs (cyclomatic 24) webui/src/routes/pipelines/PipelineOutputs.tsx:9— PipelineOutputs.PipelineOutputs has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 111, sseHandler, a function literal at line 63, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PipelineDetails.PipelineDetails (cyclomatic 24) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails.PipelineDetails has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WindowDetectingVisitor::f_up (cyclomatic 23) crates/arroyo-planner/src/plan/mod.rs:93— WindowDetectingVisitor::f_up has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SSESourceFunc::run_int (cyclomatic 21) crates/arroyo-connectors/src/sse/operator.rs:134— SSESourceFunc::run_int has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DefineSchema.SchemaFormatEditor (cyclomatic 21) webui/src/routes/connections/DefineSchema.tsx:25— DefineSchema.SchemaFormatEditor has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
arroyo_udf_common::parse::rust_to_arrow (cyclomatic 20) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:61— arroyo_udf_common::parse::rust_to_arrow has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
KafkaTester::validate_schema (cyclomatic 19) crates/arroyo-connectors/src/kafka/mod.rs:598— KafkaTester::validate_schema has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MqttSourceFunc::run_int (cyclomatic 19) crates/arroyo-connectors/src/mqtt/source/mod.rs:90— MqttSourceFunc::run_int has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
arroyo_operator::operator::operator_run_behavior (cyclomatic 19) crates/arroyo-operator/src/operator.rs:941— arroyo_operator::operator::operator_run_behavior has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
IncrementalAggregatingFunc::initialize (cyclomatic 19) REDACTED:447— IncrementalAggregatingFunc::initialize has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebsocketSourceFunc::run_int (cyclomatic 18) crates/arroyo-connectors/src/websocket/operator.rs:135— WebsocketSourceFunc::run_int has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
FluvioSourceFunc::run_int (cyclomatic 17) crates/arroyo-connectors/src/fluvio/source.rs:143— FluvioSourceFunc::run_int has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RedisConnector::from_options (cyclomatic 17) crates/arroyo-connectors/src/redis/mod.rs:232— RedisConnector::from_options has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
StateMachine::start (cyclomatic 17) crates/arroyo-controller/src/states/mod.rs:914— StateMachine::start has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
arroyo_planner::parse_and_get_arrow_program (cyclomatic 17) crates/arroyo-planner/src/lib.rs:884— arroyo_planner::parse_and_get_arrow_program has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsonForm.AutocompleteWidget (cyclomatic 17) webui/src/routes/connections/JsonForm.tsx:230— JsonForm.AutocompleteWidget has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
RabbitmqStreamSourceFunc::run_int (cyclomatic 16) crates/arroyo-connectors/src/rabbitmq/source.rs:91— RabbitmqStreamSourceFunc::run_int 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.
LogicalProgram::features (cyclomatic 16) crates/arroyo-datastream/src/logical.rs:397— LogicalProgram::features has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeEditor.CodeEditor (cyclomatic 16) webui/src/routes/pipelines/CodeEditor.tsx:22— CodeEditor.CodeEditor has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 86, onChange, a function literal at line 80, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FixmeComment crates/arroyo-udf/arroyo-udf-python/src/interpreter.rs:52— // FIXME: according to the documentation: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
CreatePipeline.CreatePipeline (cognitive 84) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline.CreatePipeline has cognitive complexity 84 (threshold 15). Drivers by points: if/else 41 (56 pts), boolean chains 14, ternaries 9 (10 pts), loops 2 (4 pts) (nesting depth added 18). Of this number, 39 points are the body's own statements and 45 belong to 12 function items inside it that branch. 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.
arroyo_formats::avro::ser::serialize_column (cognitive 67) crates/arroyo-formats/src/avro/ser.rs:63— arroyo_formats::avro::ser::serialize_column has cognitive complexity 67 (threshold 15). Drivers by points: if/else 27 (52 pts), loops 5 (14 pts), match/switch 1 (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KafkaSourceFunc::run_int (cognitive 59) crates/arroyo-connectors/src/kafka/source/mod.rs:153— KafkaSourceFunc::run_int has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (29 pts), match/switch 5 (19 pts), loops 3 (11 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NatsSourceFunc::run_int (cognitive 58) crates/arroyo-connectors/src/nats/source/mod.rs:323— NatsSourceFunc::run_int has cognitive complexity 58 (threshold 15). Drivers by points: match/switch 9 (29 pts), if/else 4 (20 pts), loops 3 (9 pts) (nesting depth added 42). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RunningJobModel::handle_message (cognitive 57) crates/arroyo-worker/src/job_controller/model.rs:143— RunningJobModel::handle_message has cognitive complexity 57 (threshold 15). Drivers by points: if/else 23 (48 pts), match/switch 2 (5 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SSESourceFunc::run_int (cognitive 56) crates/arroyo-connectors/src/sse/operator.rs:134— SSESourceFunc::run_int has cognitive complexity 56 (threshold 15). Drivers by points: if/else 10 (38 pts), match/switch 3 (12 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scheduling::next (cognitive 51) crates/arroyo-controller/src/states/scheduling.rs:371— Scheduling::next has cognitive complexity 51 (threshold 15). Drivers by points: if/else 9 (26 pts), match/switch 10 (20 pts), loops 4, boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowDetectingVisitor::f_up (cognitive 51) crates/arroyo-planner/src/plan/mod.rs:93— WindowDetectingVisitor::f_up has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (36 pts), loops 3 (7 pts), match/switch 4 (7 pts), boolean chains 1 (nesting depth added 30). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LeaderRunning::next (cognitive 50) crates/arroyo-controller/src/states/leader_running.rs:30— LeaderRunning::next has cognitive complexity 50 (threshold 15). Drivers by points: if/else 9 (26 pts), match/switch 6 (20 pts), boolean chains 3, loops 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_operator::operator::operator_run_behavior (cognitive 42) crates/arroyo-operator/src/operator.rs:941— arroyo_operator::operator::operator_run_behavior has cognitive complexity 42 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 4 (14 pts), loops 4 (10 pts), boolean chains 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TumblingAggregatingWindowFunc::handle_watermark (cognitive 42) crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:316— TumblingAggregatingWindowFunc::handle_watermark has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 4 (16 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CheckpointDetails.CheckpointTimeline (cognitive 40) webui/src/components/CheckpointDetails.tsx:54— CheckpointDetails.CheckpointTimeline has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 13, loops 4 (7 pts), ternaries 2 (nesting depth added 10). None of this is in the body itself: all 40 points belong to 8 function literals inside it that branch (lines 58, 102, 78, …). 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.
KafkaTester::validate_schema (cognitive 38) crates/arroyo-connectors/src/kafka/mod.rs:598— KafkaTester::validate_schema has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (34 pts), match/switch 2 (4 pts) (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MqttSourceFunc::run_int (cognitive 37) crates/arroyo-connectors/src/mqtt/source/mod.rs:90— MqttSourceFunc::run_int has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 5 (18 pts), if/else 5 (13 pts), loops 2 (6 pts) (nesting depth added 25). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsonForm.FormInner (cognitive 36) webui/src/routes/connections/JsonForm.tsx:703— JsonForm.FormInner has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 12, ternaries 2 (7 pts), match/switch 1 (2 pts) (nesting depth added 12). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 751, 728, 737, …). 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.
RedisWriter::start (cognitive 35) crates/arroyo-connectors/src/redis/sink.rs:114— RedisWriter::start has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (23 pts), match/switch 3 (9 pts), boolean chains 2, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectorTable::from_options (cognitive 35) crates/arroyo-planner/src/tables.rs:254— ConnectorTable::from_options has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (26 pts), match/switch 2 (5 pts), boolean chains 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PollingHttpSourceFunc::run_int (cognitive 31) crates/arroyo-connectors/src/polling_http/operator.rs:169— PollingHttpSourceFunc::run_int has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (19 pts), match/switch 2 (7 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebsocketSourceFunc::run_int (cognitive 31) crates/arroyo-connectors/src/websocket/operator.rs:135— WebsocketSourceFunc::run_int has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 3 (12 pts), loops 4 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Table::try_from_statement (cognitive 31) crates/arroyo-planner/src/tables.rs:797— Table::try_from_statement has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 6 (15 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Converter::build_array (cognitive 30) crates/arroyo-udf/arroyo-udf-python/src/pyarrow.rs:150— Converter::build_array has cognitive complexity 30 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 5 (12 pts), match/switch 1 (nesting depth added 18). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
FluvioSourceFunc::run_int (cognitive 29) crates/arroyo-connectors/src/fluvio/source.rs:143— FluvioSourceFunc::run_int has cognitive complexity 29 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 4 (12 pts), loops 2 (5 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RabbitmqStreamSourceFunc::run_int (cognitive 28) crates/arroyo-connectors/src/rabbitmq/source.rs:91— RabbitmqStreamSourceFunc::run_int has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (15 pts), match/switch 4 (12 pts), loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LookupJoin::process_batch (cognitive 28) crates/arroyo-worker/src/arrow/lookup_join.rs:54— LookupJoin::process_batch has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 6 (11 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Checkpoints.Checkpoints (cognitive 28) webui/src/components/Checkpoints.tsx:91— Checkpoints.Checkpoints has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 5 (8 pts) (nesting depth added 4). Of this number, 23 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
KubernetesScheduler::make_pod (cognitive 27) crates/arroyo-controller/src/schedulers/kubernetes/mod.rs:75— KubernetesScheduler::make_pod has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 3 (4 pts), match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Program::from_logical (cognitive 26) crates/arroyo-worker/src/engine.rs:210— Program::from_logical has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (15 pts), if/else 4 (6 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
FileSystemSinkV2::handle_commit (cognitive 24) crates/arroyo-connectors/src/filesystem/sink/operator.rs:761— FileSystemSinkV2::handle_commit has cognitive complexity 24 (threshold 15). Drivers by points: loops 6 (10 pts), if/else 4 (9 pts), match/switch 2 (5 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LeaderRestarting::next (cognitive 24) crates/arroyo-controller/src/states/leader_restarting.rs:25— LeaderRestarting::next has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PipelineDetails.PipelineDetails (cognitive 24) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails.PipelineDetails has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 7 (8 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProcessScheduler::start_workers (cognitive 23) crates/arroyo-controller/src/schedulers/mod.rs:113— ProcessScheduler::start_workers has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (4 pts), loops 2 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnnestRewriter::f_up (cognitive 23) crates/arroyo-planner/src/rewriters.rs:371— UnnestRewriter::f_up has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BackendFlusher::flush_iteration (cognitive 22) crates/arroyo-state/src/tables/table_manager.rs:95— BackendFlusher::flush_iteration has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), match/switch 2 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImpulseSourceFunc::run (cognitive 21) crates/arroyo-connectors/src/impulse/operator.rs:96— ImpulseSourceFunc::run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionTester.ConnectionTester (cognitive 21) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester.ConnectionTester has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 14, if/else 6, ternaries 1. Of this number, 15 points are the body's own statements and 6 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
IcebergFileMetadata::from_parquet (cognitive 20) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:45— IcebergFileMetadata::from_parquet has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_node::start_server (cognitive 20) crates/arroyo-node/src/lib.rs:264— arroyo_node::start_server has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (6 pts), loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArroyoRewriter::f_up (cognitive 20) crates/arroyo-planner/src/plan/mod.rs:265— ArroyoRewriter::f_up has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ParsedUdf::try_parse (cognitive 20) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:257— ParsedUdf::try_parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_udf_common::parse::rust_to_arrow (cognitive 19) crates/arroyo-udf/arroyo-udf-common/src/parse.rs:61— arroyo_udf_common::parse::rust_to_arrow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 3 (7 pts) (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PipelineOutputs.PipelineOutputs (cognitive 19) webui/src/routes/pipelines/PipelineOutputs.tsx:9— PipelineOutputs.PipelineOutputs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 111, sseHandler, a function literal at line 63, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
NexmarkSourceFunc::run (cognitive 18) crates/arroyo-connectors/src/nexmark/operator.rs:248— NexmarkSourceFunc::run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (7 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionAggregatingWindowFunc::results_at_watermark (cognitive 18) crates/arroyo-worker/src/arrow/session_aggregating_window.rs:101— SessionAggregatingWindowFunc::results_at_watermark has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonForm.AutocompleteWidget (cognitive 18) webui/src/routes/connections/JsonForm.tsx:230— JsonForm.AutocompleteWidget has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 3 (nesting depth added 2). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
FileSystemSourceFunc::read_line_file (cognitive 17) crates/arroyo-connectors/src/filesystem/source.rs:337— FileSystemSourceFunc::read_line_file has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (11 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RedisConnector::from_options (cognitive 17) crates/arroyo-connectors/src/redis/mod.rs:232— RedisConnector::from_options has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WebhookSinkFunc::process_batch (cognitive 17) crates/arroyo-connectors/src/webhook/operator.rs:41— WebhookSinkFunc::process_batch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
arroyo_connectors::mqtt::create_connection (cognitive 17) crates/arroyo-connectors/src/mqtt/mod.rs:407— arroyo_connectors::mqtt::create_connection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (6 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
arroyo_controller::leader_manager::handle_leader_stopping (cognitive 17) crates/arroyo-controller/src/leader_manager.rs:178— arroyo_controller::leader_manager::handle_leader_stopping has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 1 (4 pts), loops 1 (nesting depth added 11). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BufferDecoder::flush (cognitive 17) crates/arroyo-formats/src/de.rs:202— BufferDecoder::flush has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), match/switch 3 (6 pts), loops 1 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ChainedOperator::handle_control_message (cognitive 17) crates/arroyo-operator/src/operator.rs:670— ChainedOperator::handle_control_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ArroyoCredentialProvider::get_credential (cognitive 17) crates/arroyo-storage/src/aws.rs:111— ArroyoCredentialProvider::get_credential has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_worker::engine::construct_node (cognitive 17) crates/arroyo-worker/src/engine.rs:808— arroyo_worker::engine::construct_node has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
data_fetching.useConnectionTableTest (cognitive 17) webui/src/lib/data_fetching.ts:659— data_fetching.useConnectionTableTest has cognitive complexity 17 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 3 (6 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaEditor.SchemaEditor (cognitive 17) webui/src/routes/connections/SchemaEditor.tsx:21— SchemaEditor.SchemaEditor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 2). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (testSchema, a function literal at line 167). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MqttSinkFunc::on_start (cognitive 16) crates/arroyo-connectors/src/mqtt/sink/mod.rs:49— MqttSinkFunc::on_start has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
arroyo_server_common::init_logging_with_filter (cognitive 16) crates/arroyo-server-common/src/lib.rs:84— arroyo_server_common::init_logging_with_filter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeTableCompactor::compact_files (cognitive 16) crates/arroyo-state/src/tables/expiring_time_key_map.rs:477— TimeTableCompactor::compact_files has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CheckpointState::checkpoint_finished (cognitive 16) crates/arroyo-worker/src/job_controller/checkpoint_state.rs:271— CheckpointState::checkpoint_finished has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (6 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkerState::run_control_loop (cognitive 16) crates/arroyo-worker/src/lib.rs:468— WorkerState::run_control_loop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefineSchema.SchemaFormatEditor (cognitive 16) webui/src/routes/connections/DefineSchema.tsx:25— DefineSchema.SchemaFormatEditor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 6, match/switch 2. Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CreateProfile.CreateProfile (cognitive 16) webui/src/routes/connections/CreateProfile.tsx:18— CreateProfile.CreateProfile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3 (4 pts), boolean chains 3 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (validate, onSubmit, submit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TooManyMethods: StorageProvider crates/arroyo-storage/src/lib.rs:56— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: lib.rs → lib.rs, mod.rs, lib.rs crates/arroyo-node/src/lib.rs— `crates/arroyo-node/src/lib.rs` changes together with 3 other files — `crates/arroyo-controller/src/lib.rs`, `crates/arroyo-controller/src/schedulers/mod.rs`, `crates/arroyo-worker/src/lib.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Near-duplicate member family (4 members, 15 shared lines) · ×1
Near-duplicate member family (4 members, 15 shared lines) crates/arroyo-connectors/src/filesystem/delta.rs:77— crates/arroyo-connectors/src/filesystem/delta.rs:77-136 | crates/arroyo-connectors/src/filesystem/mod.rs:184-246 | crates/arroyo-connectors/src/redis/mod.rs:397-434 | crates/arroyo-connectors/src/single_file/mod.rs:86-117 — These 4 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/arroyo-state/src/tables/table_manager.rs:415— crates/arroyo-state/src/tables/table_manager.rs:415-452 | crates/arroyo-state/src/tables/table_manager.rs:457-493 | crates/arroyo-state/src/tables/table_manager.rs:499-531 | crates/arroyo-state/src/tables/table_manager.rs:537-569 | crates/arroyo-state/src/tables/table_manager.rs:574-611 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/arroyo-connectors/src/confluent/mod.rs:170— crates/arroyo-connectors/src/confluent/mod.rs:170-182 | crates/arroyo-connectors/src/kafka/mod.rs:356-368 | crates/arroyo-connectors/src/mqtt/mod.rs:257-269 | crates/arroyo-connectors/src/nats/mod.rs:292-304 — 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 (76 corresponding lines) · ×1
Edited copy of a member (76 corresponding lines) crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:276— crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:276-351 | crates/arroyo-connectors/src/filesystem/sink/iceberg/metadata.rs:356-432 — These two members are one piece of code written twice and then edited apart: 76 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:599— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:599-670 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:250-314 — 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 (79 corresponding lines) · ×1
Edited copy of a member (79 corresponding lines) crates/arroyo-connectors/src/fluvio/source.rs:147— crates/arroyo-connectors/src/fluvio/source.rs:147-236 | crates/arroyo-connectors/src/rabbitmq/source.rs:95-173 — 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) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:458— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:458-523 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:120-195 — These two members are one piece of code written twice and then edited apart: 66 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 39+ corresponding lines) · ×1
Edited copies of one member (5 members, 39+ corresponding lines) crates/arroyo-connectors/src/fluvio/mod.rs:128— crates/arroyo-connectors/src/fluvio/mod.rs:128-168 | crates/arroyo-connectors/src/kafka/mod.rs:206-244 | crates/arroyo-connectors/src/kinesis/mod.rs:86-126 | crates/arroyo-connectors/src/mqtt/mod.rs:163-201 | crates/arroyo-connectors/src/rabbitmq/mod.rs:177-218 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 39 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 42+ corresponding lines) · ×1
Edited copies of one member (3 members, 42+ corresponding lines) crates/arroyo-connectors/src/polling_http/mod.rs:193— crates/arroyo-connectors/src/polling_http/mod.rs:193-234 | crates/arroyo-connectors/src/sse/mod.rs:80-121 | crates/arroyo-connectors/src/websocket/mod.rs:222-263 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 42 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or 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 (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) crates/arroyo-planner/src/extension/aggregate.rs:78— crates/arroyo-planner/src/extension/aggregate.rs:78-117 | crates/arroyo-planner/src/extension/aggregate.rs:126-168 — 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) crates/arroyo-api/src/jobs.rs:414— crates/arroyo-api/src/jobs.rs:414-454 | crates/arroyo-api/src/jobs.rs:478-518 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) crates/arroyo-rpc/src/config.rs:980— crates/arroyo-rpc/src/config.rs:980-1008 | crates/arroyo-udf/arroyo-udf-common/src/parse.rs:211-232 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 36+ corresponding lines) · ×1
Edited copies of one member (3 members, 36+ corresponding lines) crates/arroyo-connectors/src/polling_http/operator.rs:81— crates/arroyo-connectors/src/polling_http/operator.rs:81-117 | crates/arroyo-connectors/src/sse/operator.rs:97-132 | crates/arroyo-connectors/src/websocket/operator.rs:81-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) crates/arroyo-connectors/src/preview/mod.rs:83— crates/arroyo-connectors/src/preview/mod.rs:83-109 | crates/arroyo-connectors/src/stdout/mod.rs:88-120 | crates/arroyo-connectors/src/webhook/mod.rs:144-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) crates/arroyo-connectors/src/impulse/mod.rs:135— crates/arroyo-connectors/src/impulse/mod.rs:135-169 | crates/arroyo-connectors/src/nexmark/mod.rs:190-220 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/arroyo-controller/src/lib.rs:261— crates/arroyo-controller/src/lib.rs:261-286 | crates/arroyo-controller/src/lib.rs:392-417 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 26+ corresponding lines) · ×1
Edited copies of one member (4 members, 26+ corresponding lines) crates/arroyo-rpc/src/lib.rs:719— crates/arroyo-rpc/src/lib.rs:719-746 | crates/arroyo-rpc/src/lib.rs:748-773 | crates/arroyo-rpc/src/lib.rs:794-819 | crates/arroyo-rpc/src/lib.rs:831-856 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) crates/arroyo-controller/src/schedulers/kubernetes/quantities.rs:148— crates/arroyo-controller/src/schedulers/kubernetes/quantities.rs:148-156 | crates/arroyo-rpc/src/lib.rs:616-629 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) crates/arroyo-connectors/src/polling_http/mod.rs:127— crates/arroyo-connectors/src/polling_http/mod.rs:127-144 | crates/arroyo-connectors/src/sse/mod.rs:163-181 | crates/arroyo-connectors/src/webhook/mod.rs:114-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 16+ corresponding lines) · ×1
Edited copies of one member (7 members, 16+ corresponding lines) crates/arroyo-connectors/src/blackhole/mod.rs:26— crates/arroyo-connectors/src/blackhole/mod.rs:26-41 | crates/arroyo-connectors/src/filesystem/delta.rs:31-46 | crates/arroyo-connectors/src/filesystem/iceberg.rs:144-159 | crates/arroyo-connectors/src/preview/mod.rs:27-42 | crates/arroyo-connectors/src/redis/mod.rs:161-176 | crates/arroyo-connectors/src/single_file/mod.rs:37-52 | crates/arroyo-connectors/src/stdout/mod.rs:32-47 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) crates/arroyo-api/src/connection_profiles.rs:169— crates/arroyo-api/src/connection_profiles.rs:169-185 | crates/arroyo-api/src/connection_tables.rs:147-163 | crates/arroyo-api/src/udfs.rs:159-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) crates/arroyo-controller/src/schedulers/embedded.rs:143— crates/arroyo-controller/src/schedulers/embedded.rs:143-152 | crates/arroyo-controller/src/schedulers/mod.rs:267-278 | crates/arroyo-controller/src/schedulers/mod.rs:748-760 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) crates/arroyo-worker/src/network_manager.rs:62— crates/arroyo-worker/src/network_manager.rs:62-68 | crates/arroyo-worker/src/network_manager.rs:76-82 | crates/arroyo-worker/src/network_manager.rs:87-93 | crates/arroyo-worker/src/network_manager.rs:98-104 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) crates/arroyo-formats/src/de.rs:706— crates/arroyo-formats/src/de.rs:706-717 | crates/arroyo-formats/src/de.rs:770-780 | crates/arroyo-formats/src/de.rs:782-792 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) crates/arroyo-connectors/src/polling_http/operator.rs:56— crates/arroyo-connectors/src/polling_http/operator.rs:56-64 | crates/arroyo-connectors/src/sse/operator.rs:79-88 | crates/arroyo-connectors/src/websocket/operator.rs:49-57 — 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 copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) crates/arroyo-worker/src/arrow/instant_join.rs:248— crates/arroyo-worker/src/arrow/instant_join.rs:248-255 | crates/arroyo-worker/src/arrow/join_with_expiration.rs:177-184 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:735— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:735-748 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:463-476 — 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 (29 lines × 2) crates/arroyo-connectors/src/nats/source/mod.rs:438— crates/arroyo-connectors/src/nats/source/mod.rs:438-466 | crates/arroyo-connectors/src/nats/source/mod.rs:495-523 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/nats/source/mod.rs:438` 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) crates/arroyo-planner/src/plan/aggregate.rs:33— crates/arroyo-planner/src/plan/aggregate.rs:33-58 | crates/arroyo-planner/src/plan/aggregate.rs:228-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.
Duplicated block (22–26 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:466— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:466-487 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:127-152 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:465` calls `from_micros` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:126` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 2) crates/arroyo-api/src/jobs.rs:415— crates/arroyo-api/src/jobs.rs:415-439 | crates/arroyo-api/src/jobs.rs:479-503 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-api/src/jobs.rs:415` it does not close everything it opens, so those exact lines 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) crates/arroyo-connectors/src/filesystem/delta.rs:102— crates/arroyo-connectors/src/filesystem/delta.rs:102-136 | crates/arroyo-connectors/src/filesystem/mod.rs:212-246 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-connectors/src/filesystem/delta.rs:102` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) crates/arroyo-connectors/src/kafka/source/mod.rs:275— crates/arroyo-connectors/src/kafka/source/mod.rs:275-294 | crates/arroyo-connectors/src/mqtt/source/mod.rs:197-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/kafka/source/mod.rs:275` 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 × 3) crates/arroyo-connectors/src/polling_http/operator.rs:99— crates/arroyo-connectors/src/polling_http/operator.rs:99-117 | crates/arroyo-connectors/src/sse/operator.rs:114-132 | crates/arroyo-connectors/src/websocket/operator.rs:99-117 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 41 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 `crates/arroyo-connectors/src/polling_http/operator.rs: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 (17 lines × 3) crates/arroyo-api/src/jobs.rs:420— crates/arroyo-api/src/jobs.rs:420-436 | crates/arroyo-api/src/jobs.rs:484-500 | crates/arroyo-api/src/metrics.rs:45-61 — 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 `crates/arroyo-api/src/jobs.rs:420` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 2) crates/arroyo-controller/src/schedulers/mod.rs:165— crates/arroyo-controller/src/schedulers/mod.rs:165-181 | crates/arroyo-node/src/lib.rs:99-115 — 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 `crates/arroyo-controller/src/schedulers/mod.rs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–16 lines × 3) crates/arroyo-connectors/src/blackhole/mod.rs:94— crates/arroyo-connectors/src/blackhole/mod.rs:94-107 | crates/arroyo-connectors/src/impulse/mod.rs:148-163 | crates/arroyo-connectors/src/nexmark/mod.rs:199-214 — 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 `crates/arroyo-connectors/src/blackhole/mod.rs:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–16 lines × 2) crates/arroyo-formats/src/avro/ser.rs:223— crates/arroyo-formats/src/avro/ser.rs:223-238 | crates/arroyo-formats/src/avro/ser.rs:254-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-formats/src/avro/ser.rs:223` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (14–15 lines × 3) crates/arroyo-connectors/src/kafka/source/mod.rs:271— crates/arroyo-connectors/src/kafka/source/mod.rs:271-285 | crates/arroyo-connectors/src/kinesis/source.rs:402-415 | crates/arroyo-connectors/src/mqtt/source/mod.rs:193-207 — 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 `crates/arroyo-connectors/src/kafka/source/mod.rs:271` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) crates/arroyo-connectors/src/filesystem/sink/operator.rs:458— crates/arroyo-connectors/src/filesystem/sink/operator.rs:458-472 | crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:145-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/filesystem/sink/operator.rs:458` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 8) crates/arroyo-connectors/src/filesystem/delta.rs:121— crates/arroyo-connectors/src/filesystem/delta.rs:121-134 | crates/arroyo-connectors/src/filesystem/mod.rs:231-244 | crates/arroyo-connectors/src/fluvio/mod.rs:154-166 | crates/arroyo-connectors/src/kafka/mod.rs:230-242 | crates/arroyo-connectors/src/kinesis/mod.rs:112-124 | crates/arroyo-connectors/src/mqtt/mod.rs:187-199 | crates/arroyo-connectors/src/nats/mod.rs:270-282 | crates/arroyo-connectors/src/rabbitmq/mod.rs:204-216 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-connectors/src/filesystem/delta.rs:121` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:113— crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:113-126 | crates/arroyo-connectors/src/kafka/sink/mod.rs:381-393 — 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 `crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs:113` 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 × 13) crates/arroyo-connectors/src/filesystem/delta.rs:117— crates/arroyo-connectors/src/filesystem/delta.rs:117-129 | crates/arroyo-connectors/src/filesystem/iceberg.rs:244-256 | crates/arroyo-connectors/src/filesystem/mod.rs:227-239 | crates/arroyo-connectors/src/fluvio/mod.rs:150-162 | crates/arroyo-connectors/src/kafka/mod.rs:226-238 | crates/arroyo-connectors/src/kinesis/mod.rs:108-120 | crates/arroyo-connectors/src/mqtt/mod.rs:183-195 | crates/arroyo-connectors/src/nats/mod.rs:266-278 | crates/arroyo-connectors/src/rabbitmq/mod.rs:200-212 | crates/arroyo-connectors/src/redis/mod.rs:416-428 | crates/arroyo-connectors/src/sse/mod.rs:103-115 | crates/arroyo-connectors/src/webhook/mod.rs:158-170 | crates/arroyo-connectors/src/websocket/mod.rs:245-257 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-connectors/src/filesystem/delta.rs: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 (13 lines × 3) crates/arroyo-connectors/src/polling_http/mod.rs:216— crates/arroyo-connectors/src/polling_http/mod.rs:216-228 | crates/arroyo-connectors/src/single_file/mod.rs:99-111 | crates/arroyo-connectors/src/stdout/mod.rs:102-114 — `crates/arroyo-connectors/src/single_file/mod.rs` and `crates/arroyo-connectors/src/stdout/mod.rs` 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 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 `crates/arroyo-connectors/src/polling_http/mod.rs:216` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/arroyo-connectors/src/single_file/mod.rs:96` calls `into` and `crates/arroyo-connectors/src/polling_http/mod.rs:213` 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 (25–26 lines × 2) crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:600— crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:600-625 | crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs:251-275 — before extracting anything, compare `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs` and `crates/arroyo-worker/src/arrow/tumbling_aggregating_window.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-worker/src/arrow/sliding_aggregating_window.rs:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 5) crates/arroyo-state/src/tables/table_manager.rs:417— crates/arroyo-state/src/tables/table_manager.rs:417-428 | crates/arroyo-state/src/tables/table_manager.rs:458-469 | crates/arroyo-state/src/tables/table_manager.rs:500-510 | crates/arroyo-state/src/tables/table_manager.rs:538-548 | crates/arroyo-state/src/tables/table_manager.rs:575-586 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/table_manager.rs:417` it does not close everything it opens, so those exact lines 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) crates/arroyo-connectors/src/kafka/mod.rs:662— crates/arroyo-connectors/src/kafka/mod.rs:662-673 | crates/arroyo-connectors/src/kafka/mod.rs:687-698 | crates/arroyo-connectors/src/kafka/mod.rs:730-741 — 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 `crates/arroyo-connectors/src/kafka/mod.rs:662` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) crates/arroyo-worker/src/job_controller/controller.rs:382— crates/arroyo-worker/src/job_controller/controller.rs:382-392 | crates/arroyo-worker/src/job_controller/controller.rs:480-491 — both copies are in the same file, so extract the 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 (11 lines × 2) crates/arroyo-planner/src/extension/aggregate.rs:95— crates/arroyo-planner/src/extension/aggregate.rs:95-105 | crates/arroyo-planner/src/extension/aggregate.rs:145-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.
Duplicated block (9–11 lines × 2) crates/arroyo-planner/src/extension/debezium.rs:55— crates/arroyo-planner/src/extension/debezium.rs:55-65 | crates/arroyo-planner/src/physical.rs:949-957 — 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 `crates/arroyo-planner/src/extension/debezium.rs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) crates/arroyo-rpc/src/lib.rs:749— crates/arroyo-rpc/src/lib.rs:749-756 | crates/arroyo-rpc/src/lib.rs:795-802 | crates/arroyo-rpc/src/lib.rs:832-839 — 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 `crates/arroyo-rpc/src/lib.rs:749` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) crates/arroyo-connectors/src/sse/operator.rs:105— crates/arroyo-connectors/src/sse/operator.rs:105-111 | crates/arroyo-connectors/src/websocket/operator.rs:89-96 — `crates/arroyo-connectors/src/sse/operator.rs` and `crates/arroyo-connectors/src/websocket/operator.rs` 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 41 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 `crates/arroyo-connectors/src/sse/operator.rs:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 16) crates/arroyo-connectors/src/filesystem/delta.rs:116— crates/arroyo-connectors/src/filesystem/delta.rs:116-122 | crates/arroyo-connectors/src/filesystem/iceberg.rs:243-249 | crates/arroyo-connectors/src/filesystem/mod.rs:226-232 | crates/arroyo-connectors/src/fluvio/mod.rs:149-155 | crates/arroyo-connectors/src/kafka/mod.rs:225-231 | crates/arroyo-connectors/src/kinesis/mod.rs:107-113 | crates/arroyo-connectors/src/mqtt/mod.rs:182-188 | crates/arroyo-connectors/src/nats/mod.rs:265-271 | crates/arroyo-connectors/src/polling_http/mod.rs:215-221 | crates/arroyo-connectors/src/rabbitmq/mod.rs:199-205 | crates/arroyo-connectors/src/redis/mod.rs:415-421 | crates/arroyo-connectors/src/single_file/mod.rs:98-104 | crates/arroyo-connectors/src/sse/mod.rs:102-108 | crates/arroyo-connectors/src/stdout/mod.rs:101-107 | crates/arroyo-connectors/src/webhook/mod.rs:157-163 | crates/arroyo-connectors/src/websocket/mod.rs:244-250 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-connectors/src/filesystem/delta.rs:116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/arroyo-connectors/src/single_file/mod.rs:96` calls `into` and `crates/arroyo-connectors/src/fluvio/mod.rs: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 (7 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:171— crates/arroyo-connectors/src/confluent/mod.rs:171-177 | crates/arroyo-connectors/src/kafka/mod.rs:357-363 | crates/arroyo-connectors/src/mqtt/mod.rs:258-264 | crates/arroyo-connectors/src/nats/mod.rs:293-299 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 33 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 (7 lines × 3) crates/arroyo-state/src/tables/table_manager.rs:437— crates/arroyo-state/src/tables/table_manager.rs:437-443 | crates/arroyo-state/src/tables/table_manager.rs:478-484 | crates/arroyo-state/src/tables/table_manager.rs:595-601 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-state/src/tables/table_manager.rs:437` it begins part-way through the construct above it, so those exact lines 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 × 10) crates/arroyo-connectors/src/blackhole/mod.rs:63— crates/arroyo-connectors/src/blackhole/mod.rs:63-72 | crates/arroyo-connectors/src/filesystem/delta.rs:55-64 | crates/arroyo-connectors/src/filesystem/mod.rs:159-168 | crates/arroyo-connectors/src/fluvio/mod.rs:73-82 | crates/arroyo-connectors/src/impulse/mod.rs:84-93 | crates/arroyo-connectors/src/kinesis/mod.rs:61-70 | crates/arroyo-connectors/src/nexmark/mod.rs:142-151 | crates/arroyo-connectors/src/preview/mod.rs:55-64 | crates/arroyo-connectors/src/single_file/mod.rs:61-70 | crates/arroyo-connectors/src/stdout/mod.rs:60-69 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/arroyo-connectors/src/blackhole/mod.rs:63` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-connectors/src/fluvio/source.rs:55— crates/arroyo-connectors/src/fluvio/source.rs:55-64 | crates/arroyo-connectors/src/kinesis/source.rs:171-180 | crates/arroyo-connectors/src/rabbitmq/source.rs:49-58 | crates/arroyo-connectors/src/websocket/operator.rs:63-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/arroyo-connectors/src/fluvio/source.rs:55` it begins part-way through the construct above it, so those exact lines 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) crates/arroyo-connectors/src/fluvio/source.rs:209— crates/arroyo-connectors/src/fluvio/source.rs:209-221 | crates/arroyo-connectors/src/kafka/source/mod.rs:267-279 | crates/arroyo-connectors/src/kinesis/source.rs:398-410 | crates/arroyo-connectors/src/rabbitmq/source.rs:149-160 — 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 `crates/arroyo-connectors/src/fluvio/source.rs:209` it begins part-way through the construct above it, so those exact lines 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 × 5) crates/arroyo-connectors/src/kafka/mod.rs:213— crates/arroyo-connectors/src/kafka/mod.rs:213-222 | crates/arroyo-connectors/src/kinesis/mod.rs:95-104 | crates/arroyo-connectors/src/mqtt/mod.rs:170-179 | crates/arroyo-connectors/src/nats/mod.rs:252-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:186-196 — `crates/arroyo-connectors/src/kafka/mod.rs` and `crates/arroyo-connectors/src/kinesis/mod.rs` 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 76 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 `crates/arroyo-connectors/src/kafka/mod.rs:213` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 6) crates/arroyo-connectors/src/fluvio/mod.rs:137— crates/arroyo-connectors/src/fluvio/mod.rs:137-146 | crates/arroyo-connectors/src/kafka/mod.rs:213-222 | crates/arroyo-connectors/src/kinesis/mod.rs:96-104 | crates/arroyo-connectors/src/mqtt/mod.rs:170-179 | crates/arroyo-connectors/src/nats/mod.rs:253-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:187-196 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 59 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 `crates/arroyo-connectors/src/fluvio/mod.rs:137` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) crates/arroyo-connectors/src/confluent/mod.rs:105— crates/arroyo-connectors/src/confluent/mod.rs:105-113 | crates/arroyo-connectors/src/kafka/mod.rs:182-190 | crates/arroyo-connectors/src/mqtt/mod.rs:139-147 | crates/arroyo-connectors/src/nats/mod.rs:157-165 — `crates/arroyo-connectors/src/confluent/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 33 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 (8 lines × 8) crates/arroyo-connectors/src/fluvio/mod.rs:139— crates/arroyo-connectors/src/fluvio/mod.rs:139-146 | crates/arroyo-connectors/src/kafka/mod.rs:215-222 | crates/arroyo-connectors/src/kinesis/mod.rs:97-104 | crates/arroyo-connectors/src/mqtt/mod.rs:172-179 | crates/arroyo-connectors/src/nats/mod.rs:255-262 | crates/arroyo-connectors/src/rabbitmq/mod.rs:189-196 | crates/arroyo-connectors/src/stdout/mod.rs:91-98 | crates/arroyo-connectors/src/webhook/mod.rs:147-154 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 59 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 (8 lines × 4) crates/arroyo-connectors/src/filesystem/delta.rs:78— crates/arroyo-connectors/src/filesystem/delta.rs:78-85 | crates/arroyo-connectors/src/filesystem/mod.rs:185-192 | crates/arroyo-connectors/src/redis/mod.rs:398-405 | crates/arroyo-connectors/src/single_file/mod.rs:87-94 — before extracting anything, compare `crates/arroyo-connectors/src/filesystem/delta.rs` and `crates/arroyo-connectors/src/filesystem/mod.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 12) crates/arroyo-connectors/src/fluvio/mod.rs:146— crates/arroyo-connectors/src/fluvio/mod.rs:146-152 | crates/arroyo-connectors/src/kafka/mod.rs:222-228 | crates/arroyo-connectors/src/kinesis/mod.rs:104-110 | crates/arroyo-connectors/src/mqtt/mod.rs:179-185 | crates/arroyo-connectors/src/nats/mod.rs:262-268 | crates/arroyo-connectors/src/polling_http/mod.rs:212-218 | crates/arroyo-connectors/src/preview/mod.rs:87-93 | crates/arroyo-connectors/src/rabbitmq/mod.rs:196-202 | crates/arroyo-connectors/src/sse/mod.rs:99-105 | crates/arroyo-connectors/src/stdout/mod.rs:98-104 | crates/arroyo-connectors/src/webhook/mod.rs:154-160 | crates/arroyo-connectors/src/websocket/mod.rs:241-247 — `crates/arroyo-connectors/src/fluvio/mod.rs` and `crates/arroyo-connectors/src/kafka/mod.rs` 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 59 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 `crates/arroyo-connectors/src/fluvio/mod.rs:146` it begins part-way through the construct above it, so those exact lines 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 locations) webui/src/routes/connections/JsonForm.tsx:215— webui/src/routes/connections/JsonForm.tsx:215 · webui/src/routes/connections/JsonForm.tsx:358 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (25 lines × 2 locations) webui/src/routes/connections/DefineSchema.tsx:212— webui/src/routes/connections/DefineSchema.tsx:212 · webui/src/routes/connections/DefineSchema.tsx:259 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:536— webui/src/routes/connections/JsonForm.tsx:536 · webui/src/routes/connections/JsonForm.tsx:686 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) webui/src/routes/connections/Connections.tsx:202— webui/src/routes/connections/Connections.tsx:202 · webui/src/routes/home/Home.tsx:121 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (20 lines × 3 locations) webui/src/lib/util.ts:7— webui/src/lib/util.ts:7 · webui/src/lib/util.ts:32 · webui/src/lib/util.ts:57 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:497— webui/src/routes/connections/JsonForm.tsx:497 · webui/src/routes/connections/JsonForm.tsx:661 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) webui/src/routes/connections/ConnectionTester.tsx:205— webui/src/routes/connections/ConnectionTester.tsx:205 · webui/src/routes/connections/CreateProfile.tsx:134 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (17 lines × 2 locations) webui/src/routes/connections/CreateConnection.tsx:49— webui/src/routes/connections/CreateConnection.tsx:49 · webui/src/routes/connections/CreateConnection.tsx:81 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) webui/src/lib/data_fetching.ts:511— webui/src/lib/data_fetching.ts:511 · webui/src/lib/data_fetching.ts:591 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) webui/src/components/PipelinesTable.tsx:40— webui/src/components/PipelinesTable.tsx:40 · webui/src/routes/connections/Connections.tsx:108 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (10 lines × 2 locations) webui/src/components/CreatePipelineTourModal.tsx:24— webui/src/components/CreatePipelineTourModal.tsx:24 · webui/src/components/TourCompleteModal.tsx:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (9 lines × 2 locations) webui/src/routes/connections/JsonForm.tsx:865— webui/src/routes/connections/JsonForm.tsx:865 · webui/src/routes/connections/JsonForm.tsx:914 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (8 lines × 2 locations) webui/src/components/CheckpointDetails.tsx:78— webui/src/components/CheckpointDetails.tsx:78 · webui/src/components/CheckpointDetails.tsx:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 5 locations) webui/src/lib/data_fetching.ts:150— webui/src/lib/data_fetching.ts:150 · webui/src/lib/data_fetching.ts:173 · webui/src/lib/data_fetching.ts:194 · webui/src/lib/data_fetching.ts:212 · +1 more site(s) not listed — all 5 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) webui/src/components/PipelinesTable.tsx:45— webui/src/components/PipelinesTable.tsx:45 · webui/src/components/PipelinesTable.tsx:55 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (5 lines × 2 locations) webui/src/components/CheckpointDetails.tsx:42— webui/src/components/CheckpointDetails.tsx:42 · webui/src/components/PipelineRow.tsx:67 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function CreatePipeline (cyclomatic 38, cognitive 44) webui/src/routes/pipelines/CreatePipeline.tsx:75— CreatePipeline has cyclomatic complexity 38 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 34) webui/src/routes/connections/JsonForm.tsx:751— (anonymous) has cyclomatic complexity 27 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PipelineDetails (cyclomatic 25, cognitive 29) webui/src/routes/pipelines/PipelineDetails.tsx:69— PipelineDetails has cyclomatic complexity 25 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Checkpoints (cyclomatic 24, cognitive 27) webui/src/components/Checkpoints.tsx:91— Checkpoints has cyclomatic complexity 24 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConnectionTester (cyclomatic 22, cognitive 16) webui/src/routes/connections/ConnectionTester.tsx:36— ConnectionTester has cyclomatic complexity 22 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SchemaFormatEditor (cyclomatic 17, cognitive 14) webui/src/routes/connections/DefineSchema.tsx:25— SchemaFormatEditor has cyclomatic complexity 17 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 23) webui/src/components/CheckpointDetails.tsx:58— (anonymous) has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ConfigEntry (cyclomatic 13, cognitive 14) webui/src/components/ConfigViewer.tsx:105— ConfigEntry has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function AutocompleteWidget (cyclomatic 12, cognitive 11) webui/src/routes/connections/JsonForm.tsx:230— AutocompleteWidget has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· webui/src/routes/connections/JsonForm.tsx · ×1
webui/src/routes/connections/JsonForm.tsx: 1045 lines of code webui/src/routes/connections/JsonForm.tsx:1— webui/src/routes/connections/JsonForm.tsx has 1045 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· webui/src/routes/pipelines/CreatePipeline.tsx · ×1
webui/src/routes/pipelines/CreatePipeline.tsx: 675 lines of code webui/src/routes/pipelines/CreatePipeline.tsx:1— webui/src/routes/pipelines/CreatePipeline.tsx has 675 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· webui/src/lib/data_fetching.ts · ×1
webui/src/lib/data_fetching.ts: 652 lines of code webui/src/lib/data_fetching.ts:1— webui/src/lib/data_fetching.ts has 652 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· webui/src/routes/connections/DefineSchema.tsx · ×1
webui/src/routes/connections/DefineSchema.tsx: 493 lines of code webui/src/routes/connections/DefineSchema.tsx:1— webui/src/routes/connections/DefineSchema.tsx has 493 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~108 LoC) webui/src/lib/RadioGroup.tsx— no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~47 LoC) webui/src/routes/pipelines/ResourcePanel.tsx— no import path from any entry point (1 application, 2 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@chakra-ui/stepper' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@rjsf/chakra-ui' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@rjsf/validator-ajv8' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'monaco-sql-languages' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'prop-types' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-test-renderer' — Declared in webui/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X15 · Unvalidated length from an untrusted reader· Length read from the parsed input is spent without ever being bounded · ×1
Length read from the parsed input is spent without ever being bounded crates/arroyo-worker/src/network_manager.rs:610— `meta_size` is read from the bytes being parsed at line 609 (`get_u32_le`), then used to size a `vec![…; n]` at line 610 — and nowhere in its scope is `meta_size` compared to anything, clamped, or bounded against the input that remains. Whoever wrote those bytes therefore chooses the allocation directly: it reserves the whole length before a single byte of the payload is known to exist, so a 32-bit length asks for up to 4 GiB, and an allocation the allocator refuses aborts the process with `memory allocation of … bytes failed` — an abort, not a panic, so no `catch_unwind` intercepts it and the whole process dies; a 64-bit length past `isize::MAX` panics with `capacity overflow` instead, out of a parser whose failure path was written for malformed input, not for hostile input. Bound `meta_size` against the bytes actually remaining and a maximum the format allows before allocating.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:225— `info!` at line 225 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:238— `debug!` at line 238 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:272— `warn!` at line 272 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:529— `info!` at line 529 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:626— `info!` at line 626 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:678— `info!` at line 678 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/engine.rs:693— `info!` at line 693 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:192— `debug!` at line 192 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:248— `error!` at line 248 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:284— `debug!` at line 284 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:339— `debug!` at line 339 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:347— `info!` at line 347 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:358— `info!` at line 358 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:620— `error!` at line 620 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:634— `error!` at line 634 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:743— `warn!` at line 743 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:786— `info!` at line 786 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:801— `info!` at line 801 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:967— `debug!` at line 967 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:1042— `warn!` at line 1042 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/lib.rs:1270— `debug!` at line 1270 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/network_manager.rs:263— `warn!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/network_manager.rs:303— `warn!` at line 303 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/network_manager.rs:321— `warn!` at line 321 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/arroyo-worker/src/network_manager.rs:455— `info!` at line 455 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Orphaned file crates/arroyo-connectors/src/nats/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/arroyo-connectors/src/rabbitmq/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file crates/arroyo-connectors/src/rabbitmq/source.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file webui/src/udf_state.ts: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 webui/src/routes/udfs/GlobalizeModal.tsx: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 webui/src/components/PipelinesTable.tsx: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 webui/src/routes/udfs/UdfsResourceTab.tsx: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 webui/src/routes/udfs/UdfEditTab.tsx: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 crates/arroyo-rpc/src/var_str.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file webui/src/routes/udfs/UdfNodePopover.tsx: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 webui/src/routes/pipelines/PipelineConfigModal.tsx: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 crates/arroyo-worker/src/arrow/sync/streams.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file webui/src/lib/example_queries.ts: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 webui/src/components/ExampleQueryCard.tsx: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.
Duplicated predicate webui/src/components/ConfigViewer.tsx:8— `value !== null && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 2 files — webui/src/components/ConfigViewer.tsx, webui/src/routes/pipelines/PipelineConfigs.tsx. 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 crates/arroyo-formats/src/avro/de.rs:40— `format.raw_datums || format.confluent_schema_registry` appears character-identically in 2 files — crates/arroyo-formats/src/avro/de.rs, crates/arroyo-formats/src/ser.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/arroyo-planner/src/lib.rs:184— `self.name == other.name && self.signature == other.signature` appears character-identically in 3 files — crates/arroyo-planner/src/lib.rs, crates/arroyo-udf/arroyo-udf-host/src/lib.rs, crates/arroyo-udf/arroyo-udf-python/src/lib.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 15 significant file(s) lose their only recent owner: crates/arroyo-state-protocol/src/lib.rs, crates/arroyo-state-protocol/src/workflow.rs, crates/arroyo-state/src/tables/global_keyed_map.rs, crates/arroyo-state-protocol/src/types.rs, crates/arroyo-state-protocol/src/store.rs, crates/arroyo-worker/src/job_controller/job_metrics.rs, crates/arroyo-connectors/src/filesystem/sink/two_phase_committer.rs, crates/arroyo-state-protocol/src/gc.rs (+7 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: crates/arroyo-udf/arroyo-udf-host/src/test.rs, crates/arroyo-udf/arroyo-udf-plugin/src/async_udf.rs, crates/arroyo-udf/arroyo-udf-python/src/types.rs, crates/arroyo-datastream/src/optimizers.rs. Pair on, review, or document these before any departure.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
No ADRs found crates/arroyo/src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `crates/arroyo/src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 27 project(s) overshoot their size bounds, lowering Project Cohesion to 8.7/10. The most over is `crates/arroyo-connectors` (21057 LoC, 158 module-visible types across 28 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 14 of 232 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 232 of the 301 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: crates/arroyo-connectors/src/nats/mod.rs, crates/arroyo-connectors/src/rabbitmq/mod.rs, crates/arroyo-connectors/src/rabbitmq/source.rs, webui/src/udf_state.ts, webui/src/routes/udfs/GlobalizeModal.tsx, webui/src/components/PipelinesTable.tsx, webui/src/routes/udfs/UdfsResourceTab.tsx, webui/src/routes/udfs/UdfEditTab.tsx (and 6 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No dependency-update automation webui/package.json:15— `webui/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Unused export 'Format' webui/src/lib/data_fetching.ts:26— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'SubtaskCheckpointGroup' · ×1
Unused export 'SubtaskCheckpointGroup' webui/src/lib/data_fetching.ts:32— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'durationFormat' · ×1
Unused export 'durationFormat' webui/src/lib/util.ts:3— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'datarateFormat' · ×1
Unused export 'datarateFormat' webui/src/lib/util.ts:29— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'stringifyBigint' · ×1
Unused export 'stringifyBigint' webui/src/lib/util.ts:79— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'logout' · ×1
Unused module-local declaration 'logout' webui/src/App.tsx:30— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `axum_server::bind_rustls(` (crates/arroyo-server-common/src/lib.rs:426).
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 1/2 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) override strict null checking — ~4.4 `!` null assertions per 1k TypeScript source lines — 47 assertion(s) across the 10566 source line(s) of the 63 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: webui/src/routes/connections/SchemaEditor.tsx (8), webui/src/routes/connections/JsonForm.tsx (7), webui/src/routes/connections/ConfluentSchemaEditor.tsx (6). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. 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.
Hand-rolled JSON/XML parsing via regex crates/arroyo-connectors/src/filesystem/sink/iceberg/mod.rs:96— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Rust code already uses a real parser in the same package; use it here too.
Outdated: arc-swap — `arc-swap` is locked at 1.7.1 but 1.9.5 is the current stable release on crates.io, and it already satisfies the `"1.7.1"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p arc-swap` and commit the updated REDACTED.
Outdated: async-compression — `async-compression` is locked at 0.4.44 but 0.4.52 is the current stable release on crates.io, and it already satisfies the `"0.4.3"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-compression` and commit the updated REDACTED.
Outdated: async-ffi — `async-ffi` is locked at 0.5.0 but 0.5.1 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in crates/arroyo-udf/arroyo-udf-host/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-ffi` and commit the updated REDACTED.
Outdated: aws-config — `aws-config` is locked at 1.8.15 but 1.13.2 is the current stable release on crates.io, and it already satisfies the `"1.5.13"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-config` and commit the updated REDACTED.
Outdated: aws-credential-types — `aws-credential-types` is locked at 1.3.0 but 1.3.1 is the current stable release on crates.io, and it already satisfies the `"1.2.0"` requirement declared in crates/arroyo-storage/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-credential-types` and commit the updated REDACTED.
Outdated: aws-msk-iam-sasl-signer — `aws-msk-iam-sasl-signer` is locked at 1.0.0 but 1.0.1 is the current stable release on crates.io, and it already satisfies the `"1.0.0"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-msk-iam-sasl-signer` and commit the updated REDACTED.
Outdated: aws-sdk-kinesis — `aws-sdk-kinesis` is locked at 1.98.0 but 1.132.0 is the current stable release on crates.io, and it already satisfies the `"1.95"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-kinesis` and commit the updated REDACTED.
Outdated: bytes — `bytes` is locked at 1.11.1 but 1.12.1 is the current stable release on crates.io, and it already satisfies the `"1.11.1"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytes` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.5.39 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/arroyo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: cornucopia_async — `cornucopia_async` is locked at 0.6.0 but 0.6.1 is the current stable release on crates.io, and it already satisfies the `"0.6.0"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p cornucopia_async` and commit the updated REDACTED.
Outdated: deadpool-postgres — `deadpool-postgres` is locked at 0.14.1 but 0.14.2 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/arroyo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p deadpool-postgres` and commit the updated REDACTED.
Outdated: flate2 — `flate2` is locked at 1.1.10 but 1.1.11 is the current stable release on crates.io, and it already satisfies the `"1.0.30"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p flate2` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.31 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.30"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.31 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3.28"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: glob — `glob` is locked at 0.3.2 but 0.3.4 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/arroyo-connectors/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glob` and commit the updated REDACTED.
Outdated: http — `http` is locked at 1.3.1 but 1.5.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p http` and commit the updated REDACTED.
Outdated: integer-encoding — `integer-encoding` is locked at 4.0.2 but 4.1.0 is the current stable release on crates.io, and it already satisfies the `"4.0.2"` requirement declared in crates/arroyo-formats/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p integer-encoding` and commit the updated REDACTED.
Outdated: lazy_static — `lazy_static` is locked at 1.5.0 but 1.5.1 is the current stable release on crates.io, and it already satisfies the `"1.4.0"` requirement declared in crates/arroyo-controller/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p lazy_static` and commit the updated REDACTED.
Outdated: local-ip-address — `local-ip-address` is locked at 0.6.5 but 0.6.13 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p local-ip-address` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.34 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4.20"` requirement declared in crates/arroyo-rpc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: postgres — `postgres` is locked at 0.19.10 but 0.19.14 is the current stable release on crates.io, and it already satisfies the `"0.19.5"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p postgres` and commit the updated REDACTED.
Outdated: postgres-types — `postgres-types` is locked at 0.2.9 but 0.2.14 is the current stable release on crates.io, and it already satisfies the `"*"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p postgres-types` and commit the updated REDACTED.
Outdated: prost — `prost` is locked at 0.14.4 but 0.14.6 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost` and commit the updated REDACTED.
Outdated: prost-build — `prost-build` is locked at 0.14.4 but 0.14.6 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/arroyo-formats/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost-build` and commit the updated REDACTED.
Outdated: rust-embed — `rust-embed` is locked at 8.7.2 but 8.14.0 is the current stable release on crates.io, and it already satisfies the `"8"` requirement declared in crates/arroyo-api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rust-embed` and commit the updated REDACTED.
Off the main sequence: arroyo-udf-common — arroyo-udf-common: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a1db88-5e03-7b33-80cc-a695851eada2 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 77 · Warnings: 617 · Recommendations: 86 · Info: 47 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 19:28 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.